Lesley Lowery
My feedback
9 results found
-
34 votes
-
391 votes
-
31 votes
-
419 votes
An error occurred while saving the comment -
64 votes
-
65 votes
-
163 votes
-
226 votes
An error occurred while saving the comment At the Orbis Cascade Alliance, there's support for this idea, and we would love to have the ability to let staff define multiple mandatory fields for the template - not just call number. This would make it much easier for Reserves and Circulation staff (who usually aren't catalogers) to quickly assess and fill out the template.
-
190 votes
Dear community,
Thank you for raising this idea.
I would like to better understand the use case here:
1 How often such check is done? if this is a "cleanup" that is done once in a few month, for example, perhaps an analytics report would be sufficient?
2 In the description you wrote about the "has inventory" index. Can you give more details, why it is not useful for the described use case?
Thanks,
Tamar Fuches
Alma product team
This is an absolutely critical functionality needed by consortia. In addition to equipment records, consortia members frequently have IZ-only records for resources that they are contractually prohibited from sharing outside of their institutions.
Having un-requestable resources appear in to Primo VE users in other member institutions leads to poor user experience and a glut of canceled item requests.
I should also note that the current workaround of creating a custom local data scope where the institution = NETWORK and Inventory = available physical is incomplete at best, as it will not display resources that are requestable from another consortial member but checked out or otherwise "unavailable" temporarily.