Autoload collections – Better identification
Autoload collections are not always clearly identified in Alma. The default name of the collection does not always mention this information and there is no specific tag which can be searched or displayed in the CZ releases reports. This can be the source of useless changes by EIO or creation of cases.
We do not want to add terms like ‘AutoHoldings’ or ‘Autoload’ in the public name of the collection as this is not an useful information for end-users on Primo.
It would thus be very useful to tag these collections with the mention ”Autoload” in the Alma collection search results, in the CZ releases reports and to allow the search on collections concerned by this functionality.
![](https://secure.gravatar.com/avatar/783ddb6ff212f4452d22eb7473df0eba?size=40&default=https%3A%2F%2Fassets.uvcdn.com%2Fpkg%2Fadmin%2Ficons%2Fuser_70-6bcf9e08938533adb9bac95c3e487cb2a6d4a32f890ca6fdc82e3072e0ea0368.png)
-
Elizabeth York commented
It's important to remember that the collections used for Autoholdings aren't just used for Autoholdings—they're often the vendor's "All Titles" collection, so institutions that don't use Autoholdings are often using them too.
So, if this idea is implemented, please don't just add a fixed "autoholdings" label onto every CZ collection that can be used for autoholdings, as that would be confusing to all libraries that are not using autoholdings. Instead, if an institution has set up autoholdings, part of the autoholdings setup could be flagging the collection in which the autoholdings are deposited as a collection where autoholdings is in use. This flag would only appear if a library had set up autoholdings for a collection.