Locations and Service Points (UXPROD-771)

[UXPROD-4054] Indicate if a shelving location is open or closed to patrons Created: 09/Feb/23  Updated: 30/Nov/23

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Locations and Service Points

Type: New Feature Priority: TBD
Reporter: Erin Nettifee Assignee: Anne Ekblad
Resolution: Unresolved Votes: 0
Labels: enettifee-reviewed, locations
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by UITEN-244 Add field "Open to Patrons" to Shelvi... Open
Relates
relates to UXPROD-3977 CDL (Controlled Digital Lending) Open
relates to UXPROD-4070 Reading Room Access Open
relates to UXPROD-1835 Reading Room Feature Draft
Epic Link: Locations and Service Points
Development Team: None
PO Rank: 0
Rank: Cornell (Full Sum 2021): R2

 Description   

Current situation or problem:
Many libraries have shelving locations that are not open to patrons; instead, patrons request the items and they are brought to a reading room or service point for the patron to check out or use in-house.

There is no way currently to indicate if a shelving location is open or closed to the public; this feature encompasses the work to meet that requirement, both on the front end and back end.

In scope

  • Updates to shelving location schema to add a new boolean attribute, "staffOnly", as a required field with default value of "False"
  • Updates to locations UI to add the ability to manage the setting
    • Field name on UI: "Open to patrons" with two possible values - Yes or No.
      • "staffOnly" = False, then "Open to patrons" = "Yes"
      • "staffOnly" = True, then "Open to patrons" = "No"
  • Any work to expose the new attribute to locations APIs

Out of scope

  • Any integration with external-to-FOLIO tools that might use this data, other than making the field able to set via API
  • UI work within other FOLIO apps besides Settings > Tenant — that would need to be done in follow-on jiras with new features.

Use case(s)

  • A FOLIO library wishes to implement controlled digital lending; part of standard CDL workflows includes "sequestering" the physical copy while the digital copy is in use. The library creates a shelving location named "CDL Sequestered" and marks "Open to patrons" as "No". When an item is out on a controlled digital loan, they move the physical copy to that location temporarily, and then remove it from that location when the physical copy is back in circulation.
  • A library has several collections that are stored in locations not accessible to patrons. Those locations are marked as "Open to patrons" = False. As part of their discovery layer, they set up an integration such that if an item is at a location not open to patrons, a special message displays telling patrons that the item needs to be requested through a particular online form.

Proposed solution/stories

  • UITEN-244 Open > UI work for field.
  • Backend work > to be written by development team.

Links to additional info

  • We are calling the underlying data "staffOnly" instead of "isOpen" because saying shelving is closed could be read as saying that a location is not available, which is not the intent of this feature.
  • It may be desired to have an additional part of this where if a location is set to be remote storage, that it defaults to Open to patrons = No. But I think given that Open to patrons is unlikely to be a value that changes frequently, I don't think it is unreasonable to have the value be set manually.
  • It may be desired to add additional development in Inventory or Requests to include this information when displaying a location, but then can be addressed in other features if requested.

Questions

  • Does any development here need to happen within OAI-PMH or RTAC to make the new attribute available?
  • Could this influence request policies? Ideally you would be able to disable requesting (though since this is location based, that could be done in the circulation rules already)


 Comments   
Comment by Erin Nettifee [ 13/Feb/23 ]

Magda Zacharska Khalilah Gambrell - this is non-urgent.

This feature need has come up in the context of discussions about controlled digital lending, where there is a business requirement of placing an item in a "sequestered" location, not accessible by patrons.

I could see different ways this could potentially be helpful beyond CDL and have linked this to the long-standing Reading Room feature as well.

I'm looking for input from both of you on whether any work would be needed within additional apps to support OAI-PMH and RTAC using this information. You can assume that it would be possible to query a location via API to find out if it was "sequestered" - I'm more trying to consider if additional work would be desired beyond being able to query the API for that info, if that makes sense.

Comment by Charlotte Whitt [ 14/Feb/23 ]

Hi Erin Nettifee - I have linked this feature as related to the Epic UXPROD-3977 Open .

CC: Andrea Loigman Sarah Seestone David Bottorff

Comment by Thomas Trutt [ 15/Mar/23 ]

I wonder if this should be linked with UXPROD-4070 Open . I know that issue is about control lists but as i mentioned in my comment in that issue i think locations would be a better fit instead of a service point. 

Comment by Erin Nettifee [ 15/Mar/23 ]

Thomas Trutt I'm not sure I agree with 4070 being a better fit for an extension of the location model - I think reading rooms are service points since they are places where books are brought and used. They are tied to locations most often, though it's not a requirement.

There could be an argument for 4070 leading to a completely different object of "reading room" being built out - one of the challenges with service points and locations is that they are integrated into mod-inventory, and if you want to give true flexibility you might want to not build in another dependency piece with inventory.

I'll leave a comment over there just so this is considered when they get to it (not sure which PO will do 4070).

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