We have always has asset named, 'Sites' that was checked to be the Locations function within Hudu. We have used this for a customer's sites (Meaning unique addresses or physical locations). Next, we have a asset named, 'Locations', this is to document all the locations within a site such as; floors, rooms, HVAC, Electrical, conference rooms, etc, locations also have parent location in the asset for building hierocracy, location ID, door pins, notes, etc. In million sq foot buildings with many floors, location accuracy is critical!
The issue we have hit, you can only have one 'Location' Asset that Hudu keys off. The hard coded assets such as 'Racks' only let you select 'location', which in our case we have tied to physical addresses in our 'sites'. It would be better to have something like Racks linked to our Locations asset.
I have tried to combine Sites and Locations into one asset, too painful without context driven forms (which is another ask). A customer with 30 sites, each site with 20 to 100 locations, its gets messy quick in Hudu.
Please give us ability to have multiple location assets that you then combine in your location list return (Not best idea!). Optionally ability to select which location asset is used if we can have more than one? Or in the case of Racks, give us ability to add custom assets and fields to the Rack Asset. Last option would solve this.
Our work around in Racks, we relate (Related Items) the rack to the locations over on the right.
Out of the box, Hudu's locations is fine for SMB clients with small office where none of this detail is all that relevant.