[FOLIO-1523] Locations and Service Points: Use Cases Created: 21/Sep/18  Updated: 12/Nov/18

Status: Open
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Umbrella Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to FOLIO-1525 SPIKE: Revisit Location to Service Po... Closed
Sprint:

 Description   

Some known use cases for locations and service points to help with the architecture of the relationship:

Home vs In Transit

  • One shelving location can be "served" by more than one service point. Imagine the shelf is equidistant between two service points (circ desk 1 and circ desk 2). Either desk is considered "home" for items living on the shelf. So, if an item is checked in at circ desk 1, the system looks to see if the item'e effective location has circ desk 1 as one of its service points.
    • If it does the item's status changes to "recently returned" and it's put on a cart to be re-shelved.
    • If it doesn't the item's status changes to "in transit" and the system needs to say which service point it needs to be sent to
      • How does the system know which service point it needs to go to when the location can have > 1 service point? It looks at which service point has been set as primary.

Fee and Fine Calculations

  • Not all service points in a library charge the same fees and fine rates
    • How does the system know which rate to apply for an overdue item (for example)?
    • It looks at the item's effective location, finds the primary service point for that location and then looks at the fee/fine table that is associated with that service point to determine rates

Requiring That a Location Have at Least One Service Point

  • Many things rely on a location having a service point (see above). Given this, I think we need to require that locations have at least one service point when created. For this reason, I think it would have been better to have service points added to location records when created rather than adding locations to service points.

User Relationship with Service Point

  • Staff users may be assigned to particular service points (e.g., to check in and check out items)
  • All patrons may have a service point set as default pick-up service point for requests
    • Not all service points are necessarily pick-up service points
    • Users can request an item with location A to pick up at service point B, even if service point B is not assigned (or vice versa) to location A
    • Is it possible that some items with location A, assigned to service point C, can only be picked up at service point C? (building use only items, if requestable?)

Inform Staff of Unusual Location Upon Check In

  • Reserve items are often tricky to shelve because they are in a temporary location, and that may not be reflected on the item's labeling
    • Could also use the fact that it is a temporary location, rather than the location itself, to inform staff to pay attention
  • A location is assigned to multiple service points A and B, but service point B is not really the best place for items in that location to go
    • Could users be notified when an item is checked in at the "secondary" service point?
    • More of a nice-to-have than a need-to-have

Other (for Problem Solving etc)

  • Which service points are associated with this location?
  • Which service point is primary for this location?
  • Which locations are associated with this service point?

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