Hello,
We are in the process to move to a new campus. All departments will be located in 3 buildings. I want to clean up the Locations table to accommodate for this situation, but I need some help in understanding what would be the best practices to follow to accomplish this mission, since we have been using a reactive approach in the past when designing the method of populating the Locations table when doing asset management. I would like to keep things as simple as possible and use the cmn_location table in its original form, without introducing too many changes to it. The structure that we would like to use could be something like this: Campus -> Building -> Floor -> (Area|Office|Room) -> (Desk|Space).
A scenario could be something like this:
Maecenas (Campus); IT Support (Building); Floor 3 (Floor); 301 (Area or Office); A (Desk or Space)
I now that the field Location Type, can help me with the classification on all these different locations, but I am not sure how to use the Class, Parent, and Primary Location fields and how to take advantage of them. Also, I would like to know the best approach for a naming convention when creating a new desk location using this scenario.
Any help or insights on this matter will be welcomed and appreciated. Regards!
