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: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Epic Link: | Locations and Service Points |
| Development Team: | None |
| PO Rank: | 0 |
| Rank: Cornell (Full Sum 2021): | R3 |
| Description |
|
Current situation or problem: Some libraries find this approach to be counterintuitive, and want to be able to associate locations and service points from the service point UI instead. In this approach, a library would open the service point in edit mode and be able to search for locations, add them to the service point, and designate whether the service point is primary or secondary to the location. In scope Out of scope
Use case(s)
Proposed solution/stories Links to additional info
Questions |
| Comments |
| Comment by Erin Nettifee [ 01/Feb/22 ] |
|
Captured from a Slack discussion in #resource-access: https://folio-project.slack.com/archives/C3G05TF3R/p1643318345107900 This way the feature exists and can be prioritized, but I am ranking it as a P4 since I don't see this as a development priority. If schools disagree with the ranking, please comment here or chime in over on Slack. |