search

sul-dlss / sul-requests

Rails application for requesting materials from Stanford University Library
Other
4 stars 0 forks source link

Changes needed for Boundwith child requests :( #2586

Open saseestone opened 3 hours ago

saseestone commented 3 hours ago

Currently when a Bound with child is requested, we send the child instanceID to folio as part of the request. We also send the itemId of the parent record. Example request confirmation w/details: https://requests.stanford.edu/patron_requests/16073.

The request is visible in Folio on the child record and everything looks like it's going to be fine.

Unfortunately, we've heard from circulation staff that when they receive the physical item and try to make the request available, Folio doesn't recognize the request. Instead, it tries to send the item back to the owning library for shelving. So even though Folio understands the link between the child and parent enough to display the user request on both the child and parent record in the Folio UI, receiving the parent item id is not making the request available.

If the request is placed on the parent title, and we send the parent instanceID and parent itemId, then folio will recognize the request and make it available.

Darsi R. is reporting this issue to the Folio community, in hopes we can get a fix. In the meantime, we need to:

  1. Keep everything the same in Searchworks on the child record display - meaning we should continue to show the parent record information in the "At the library" panel AND we'll keep the request button displaying as well
  2. Keep the boundwith section of the request form as is.
  3. When the user submits the request, send the parent instanceID to Folio.
  4. Update the Request processing screens using new designs provided by Darcy B. (see comment below)
  5. Update the Request confirmation screen using new designs provided by Darcy B. (see comment below)
  6. (Also update the Request confirmation email accordingly).

We'll want to do all this in a way that we could easily revert back to our current way (sending the child instanceId) if/when Folio fixes their bug. (But we shouldn't hold our breath on this...)

A note that Darsi R. posted this issue in a Folio slack channel, and got a response from Brooks at EBSCO recommending we use the patronComments field to "store arbitrary data on the request record to pull the correct title for MyAccount display". We could look into that if we can get over the use of the "arbitrary data" comment. (Or maybe it's just me that gets ruffled by that.)

saseestone commented 2 hours ago

This issue was originally reported by Darsi via feedback: https://jirasul.stanford.edu/jira/browse/SW-4387

dbranchini commented 1 hour ago

Designs in Figma -- I provided two different examples. One has a longer title.