hierarchical location structure and endpoint

collection: /locations
item: /locations/{id}

Location.json
{
  "id": "UUID"
  "name", "Miller General Stacks",
  "code" : "UA/CB/LC/GS", //unique
  "status": "active" | "inactive, //maybe boolean is better here
  "institution": "X",  
  "campus": "Y",
  "library": "Z", //all three should be controlled values
  "parking": {"a":"b", ...} //kv pairs, it's an object rather than an array since keys should be unique
}

We need also a set of services for controlling inst/camp/lib values and their hierarchy, e.g

collection/item: /org/institutions/{id}
collection/item: /org/campus/{id}
collection/item: /org/libraries/{id}

and lower-level item structure tpoints to the higher level, e.g

Campus.json
{
   "id": "UIID"
   "name": "Campus 1"
   "institutionId": UUID //points to parnent institution
}

Library.json would be similar.

This structure is clearly repetitive, so it might make sense to have a generic recursive structure for this (e.g Unit.json)

Also, notice that in Location.json we can either use UUIDs for inst/camp/lib, though preferably we would use name/values directly and validate behid the scened. It would make the input method described in UIORG-45 much simpler.