search

pulibrary / locations

Services around holding, delivery, and physical locations
MIT License
3 stars 0 forks source link

Add a remote_storage attribute in holding locations #87

Closed christinach closed 3 years ago

christinach commented 3 years ago

The remote_storage: recap_rmt is what is coming in the location level in alma. When populating the tables and the value of the remote_storage is recap_rmt, we should update the holding library id to be Recap. For example location code mendel$pk should have holding library Recap and not Mendel.

@mzelesky @kevinreiss Does this make sense?

kevinreiss commented 3 years ago

Hi, this makes sense to me @christinach

christinach commented 3 years ago

Thanks @kevinreiss

hackartisan commented 3 years ago

I thought with the remote storage feature we wouldn't need to use the holding library. If it's needed it would be helpful to spell out a use case here.

kevinreiss commented 3 years ago

Alma doesn't seem to tell you at the item level if something is in remote storage. It only seems available at location level. We need to know if something is in remote storage to both format the UI with the various messages and language we use for remote storage requests and to properly create the request for submission via API. So we need to add this configuration in some fashion to the data available when you call for information on a holding location. The only two scenarios for doing that seem:

  1. Manipulate the current holding library feature to infer items that have a holding library of recap are in remote storage.
  2. Create a new remote storage attribute attached to a holding location in marc liberation
hackartisan commented 3 years ago

A new flag seems simpler

christinach commented 3 years ago

@kevinreiss Thank you for adding the two scenarios. Adding a new remote storage attribute sounds better since we are going to have different remote storage options and not only recap.