Forum GLPI-Project

AndiMb

Member

Registered: 2022-11-11

Posts: 12

Best practice for a location hierarchie

Hi,

I'm having a question on locations in GLPI. We have hundreds of buildings with thousands of rooms and want to add them as locations in GLPI to be available for assigning them to assets.

The hierarchy is something like:
Company > Area/Main Location > Building > Floor > Room

We thought that each building, floor, or room can be a single GLPI location in a hierarchical manner in GLPI, e.g. all room are children of a floor.

We tried to add this hierarchy with the REST API to GLPI. But since all names of the locations are checked for unicity before adding it to the database and nearly all buildings do have a room named "001" or a floor named "1" the name of the location can't be simply "room 001" or "floor 1" since it must be unique. So, we had to add an unique identifier to each building, floor and room name, which is just a numerical value and quite annoying.

What is the best practice in this case?

Regards

Sico31

Member

Registered: 2018-09-24

Posts: 607

Re: Best practice for a location hierarchie

Delete the unicity for the location ?
have a complete name for all building, floor and room with the building and floor ? B.A ; F.001 ; R.001 =BAF1R1 ; BAF1R2, etc

---

Manger un castor, c'est sauver un arbre.
Quand on est mort, on ne sait pas qu'on est mort ; c'est pour les autres que c'est difficile. Quand on est con, c'est pareil !