Best Practices for Locations and Work Spaces

[k_ab]

We're trying to track the specific work spaces. I.e, each office has multiple floors, and each floor has multiple work spaces.

Users or CIs could then be assigned to a work space;

Should each 'work space' be entered as an entry in the Location [cmn_location] table?

For example:

Americas

        United States

                  New York

                            New York City

                                      Office Building Name

                                                Floor 32

                                                          32-092

                                                          32-092

                                                          ...

If office buildings are already in the location table, when would you use the Building [cmn_building] or Buildings [cmdb_ci_building_facility] tables? Would floor and work spaces be fields within these tables instead?

Any thoughts to help us understand the best practices would be great. Thanks in advance!

[Ahmed Drar]

Hi , How about creating a custom table for instance u_position , relate the table to location table so one location has multiple positions .I think the issue can be fixed by using location parent/child structure   and a custom table to store position data Americas -->Location         United States --> location                     New York --> location                             New York City                                         Office Building Name                                                 Floor 32 -->position                                                             32-092 -->position                                                             32-092 -->position

[vkambham]

Keith,

Adding work spaces to cmn_location table will make the the table very large and slow down location look ups on forms. The other disadvantage will be the space names are typically coded so usually users will not be able to provide it always. The pro will be that you have only one location field.

An alternate way would be to load the spaces in another table and   relate it to cmn_location. Then add a second field on forms   (we called it Location Details)   and make it optional.

-Venkatesh