[UIORG-45] Location Hierarchy v1: Create Locations via JSON File Created: 24/Feb/18  Updated: 29/Mar/18  Resolved: 25/Mar/18

Status: Closed
Project: (inactive) ui-organization
Components: None
Affects versions: None
Fix versions: None

Type: Story Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: core, sprint0, sprint35
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks UXPROD-267 Assign location to item/holding Closed
blocks UXPROD-270 Associate service points with locations Closed
is blocked by MODINVSTOR-70 hierarchical location structure and e... Closed
Relates
relates to STSMACOM-79 Location Lookup Pop-up Closed
relates to STSMACOM-82 Location Selection Menu Closed
relates to UXPROD-114 Location hierarchy CRUD via UI Closed
Sprint:
Back End Estimate: XL < 15 days
Back End Estimator: Jakub Skoczen
Front End Estimate: Small < 3 days
Front End Estimator: Jakub Skoczen

 Description   

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.



 Comments   
Comment by Heikki Levanto [ 02/Mar/18 ]

I seem not to have permission to look at "Create location page in Settings" or "Location hierarchy slide". I have requested permission through google.

Comment by Cate Boerema (Inactive) [ 02/Mar/18 ]

I just gave you access.

Comment by Heikki Levanto [ 02/Mar/18 ]

Thanks. Turns out that I had seen them already in the "Locations overview deck"

Comment by Jakub Skoczen [ 22/Mar/18 ]

Cate Boerema can we resolve this as won't fix given that the UX for seting up locations and inst/camp/lib is ready?

Comment by Cate Boerema (Inactive) [ 25/Mar/18 ]

Closing as wont do, as we'll skip this interim step and go straight to developing the location crud ui

Generated at Thu Feb 08 23:10:44 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.