Locations and Service Points
(UXPROD-771)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Locations and Service Points |
| Type: | New Feature | Priority: | P4 |
| Reporter: | Erin Nettifee | Assignee: | Anne Ekblad |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | enettifee-reviewed | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| Issue links: |
|
||||||||||||||||
| Epic Link: | Locations and Service Points | ||||||||||||||||
| Development Team: | None | ||||||||||||||||
| PO Rank: | 0 | ||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R2 | ||||||||||||||||
| Rank: Mainz (Full TBD): | R2 | ||||||||||||||||
| Description |
|
Current situation or problem: For libraries with long location lists, and/or many campuses, libraries, and locations, it's not always intuitive to know where a location actually sits in a hierarchy. You may have the location's FOLIO Name or code, but because FOLIO does not impose requirements on those fields, if the library itself doesn't indicate the hierarchy in the name or code, it may not be obvious where it is. FOLIO can advise implementers to include a hierarchy in the naming, but implementers aren't obligated to do so, and in fact may not realize the utility of that approach until after implementation. This can be frustrating for staff if they are trying to edit a location to correct an error or change a particular workflow, and there can be a lot of extra clicks or extra time spent in the interface trying to find a particular record. The information can be found if you are able to spend the time exploring Developer Tools to view underlying JSON, but that's not a reasonable expectation. This feature encompasses adding a search functionality to Settings > Tenant > Location Setup to allow for searching the location hierarchy by keyword. In scope
Out of scope
Use case Proposed solution/stories
Links to additional info Questions
|
| Comments |
| Comment by Ann-Marie Breaux (Inactive) [ 21/Apr/23 ] |
|
Hi Erin Nettifee Here's a thought, but I don't know if it would work in the context of the Settings pages. When a user first clicks the Location settings, they get a grid with 9 columns, for the name and code for each of the 4 levels plus status - basically a dynamic spreadsheet, sortable on all of the columns. They see all names and codes at once. If they need to find something, they can do ctrl-f and find it on the page, no matter how many or at what level of the hierarchy. For any particular cell, the value is a hotlink. When the user clicks that hotlink
There's a Action menu at the top of the list that allows for
|
| Comment by Erin Nettifee [ 24/Apr/23 ] |
|
Hi Ann-Marie Breaux - thanks - I'm not sure a tabular format would work for editing since you need the ability to create new values at each level of the hierarchy. I have not had any UX done with this and that is probably the next step. I'll see if Kimie has any cycles. I still am not sure this is higher than a P4, especially given that a UX redesign is probably going to be fairly complex. But I will see if we can start the UX cycle, at least. |
| Comment by Ann-Marie Breaux (Inactive) [ 25/Apr/23 ] |
|
Hi Erin Nettifee - maybe - but if you make it so that each name and each code is a hotlink that opens the detail record for the particular location level, I think it could work. In any event, I'll leave it alone for now. Thank you! |
| Comment by Thomas Trutt [ 17/May/23 ] |
|
id agree. This is a pain but locations, like most settings are not changed all that often. For the most part they fall on a few staff members that know the system and the conventions for their library. I agree this should be done but i think a P4 is fair. Erin Nettifee do you want to close #UXPROD-3489 as a duplicate? I frel both issues are the same and this one has more details. |
| Comment by Erin Nettifee [ 22/May/23 ] |
|
Thomas Trutt I don't know in the Cornell context if 3489 was meant to be about searching more than just locations - it's written more broadly. |