You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 22, 2022. It is now read-only.
Is your feature request related to a problem? Please describe.
When a hold is blocked via the Symphony hold map, the following message displays:
Describe the solution you'd like
This sounds like delivered language and I hope it can be customized. Users will likely see this result more often in a curbside delivery environment, where holds will be restricted by user profile and holding library (users will only be able to request items from their institution). Some consideration is needed for how specific the language should be. Better ask Peggy... oh, wait...
Also applies to NEOS discovery.
The text was updated successfully, but these errors were encountered:
We use a Web Services Place Hold application that @jhennig built for both UAL and NEOS Discovery, so we can intercept that message and replace it with better text (without adjusting it in Symphony). We should come up with text for the current pandemic around holds being restricted to core users (whatever term we/NEOS want to use), and then have more straightforward text we can revert to whenever we go back to the regular holds process.
Is your feature request related to a problem? Please describe.
When a hold is blocked via the Symphony hold map, the following message displays:
Describe the solution you'd like
This sounds like delivered language and I hope it can be customized. Users will likely see this result more often in a curbside delivery environment, where holds will be restricted by user profile and holding library (users will only be able to request items from their institution). Some consideration is needed for how specific the language should be. Better ask Peggy... oh, wait...
Also applies to NEOS discovery.
The text was updated successfully, but these errors were encountered: