| Location model review | Cate Boerema (Deactivated) | Location UX/UI model- - UI to set up locations in holdings and items
- Look at Vince's model- institutional, campus, building level-library, 4th level of location: floor, section,shelf
- consortia level is outside the level hierarchy; Collections outside the level hierarchy–Storage and library collections
- Flexibility in levels?
- Assumptions - locations set up at migration, edit location changes, new locations and moves, libraries have more 40-50 locations
- Reported by group more than 100 locations
- Quick data entry use location code to assign a location- widget to find codes and locations- autofill
- Configure locations- upload a jason file, UI with crud to enter or maintain locations- name, code, description, levels values (parking levels- UI crud)
- Controlled naming in crud
- Question can you have shelf and not floor how does the hierarchy work for 4th level (parking level)–deal with this in circulation policies too
- NCIP, SIP2, Z39.50 and interoperability standards need to parse out levels
- Requirements for levels populate floor and shelf
- Display in discovery layer: name/display name/description
- Active locations indicator- old data in system and do not allow staff to use for a current location
ACTION ITEM: GIVE CATE SOME LOCATION: SHELVING locations
|