Locations and Service Points (UXPROD-771)

[UXPROD-3537] Allow for locations to be associated to service points from the Service Point UI Created: 01/Feb/22  Updated: 30/Nov/23

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:
Currently, service points are associated to locations from the location record. A user opens a location in the edit view and is able to designate a primary service point (required) and one or more secondary service points (optional).

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

  • Changes to the locations UI process already in place for associating service points and locations

Use case(s)

  • Smaller and/or more consolidated libraries that have scenarios where one service point in a building may manage ten or more locations; adding from the service point screen becomes one screen to associate the ten locations, whereas the current UI requires going to each of the ten or more locations individually.

Proposed solution/stories

Links to additional info

  • This feature is being added to capture desired additional functionality, but is unlikely to be developed soon due to competing development needs (this is a "nice to have" in terms of the UI and improving processes for new adopters, since the existing process does work as designed.)

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.

Generated at Fri Feb 09 00:32:47 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.