Location Hierarchy v1: Create Locations via JSON File

Purpose: To extend our simple, flat location into a structure that can more accurately represent the institutional structure. The first iteration of this feature will support the creation of location records via JSON file. Future iterations will include a UI for CRUDing locations in Settings > Organization. UX is working on the designs for the UI, but you can see some wireframes in this deck(slides 13 - 19).

Scenarios:

1. Scenario
   • Given a FOLIO tenant
   • Then it should be possible to create location records via JSON
     • Page will be created in Settings > Organization
     • Large text input area will accept JSON
2. Scenario
   • Given a location record
   • When stored
   • Then the metadata included should correspond with the below linked wireframe
3. Scenario
   • Given a location record
   • When stored
   • Then every location record must have:
     • FOLIO name
     • Code (unique)
     • Status
     • Institution
     • Campus
     • Library
4. Scenario
   • Given a location record
   • When stored
   • Then the following are optional:
     • Discovery display name
     • Description
     • "Parking" properties
5. Scenario
   • Given the "Parking" level of a location record
   • When stored
   • Then there can be 0 to N name value pairs
6. Scenario
   • Given Location X with FOLIO name "Miller General Stacks" and Code "UA/CB/LC/GS" has been created via JSON
   • When the Permanent and Temporary location menus in the Holding and Item records are opened
   • Then "UA/CB/LC/GS (Miller General Stacks)" should appear as an option in the menu
7. Scenario
   • Given Item Y has Location X with FOLIO name "Miller General Stacks" and Code "UA/CB/LC/GS" has been created via JSON
   • When location is displayed for Item Y in Loans, Requests, Check out and Check in
   • Then "UA/CB/LC/GS (Miller General Stacks)" should display as the location

Wireframes etc.

• Create location page in Settings
• Locations overview deck
• Location hierarchy slide