Alma
Your feedback matters to us. Help us improve Alma by telling us what you’d like to see using the message areas below. You can also can support something already posted.
We would love to be able to respond to every idea that is submitted, but this is not feasible. We are, however, committed to responding to the most popular ideas—those that have received the most points.
For more information please review our FAQ and guidelines. Thank you.
7 results found
-
Alma collections: Allow to add multiple titles from network zone
We very much appreciate that the idea Alma collections: Allow to add from network zone (https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/44841430-alma-collections-allow-to-add-from-network-zone), which allows to add NZ records to IZ collections, could be developed. However, we think the usefulness of this feature would be greatly improved if it was possible to add more than one record at a time, for example via sets.
62 votes -
Functionality to manage unique URLs for NZ local collections
In instances where there is no CZ collection for an e-resource, we have to create Network Zone local collections in Alma to allow our consortium members to discover and access the content in Primo. However, we are not able to do so if each member has a unique access URL for the resource.
We would like to see functionality in Alma that would allow us to manage unique identifiers for URLs for each member in NZ local collections.
19 votes -
Duplicate Title Analysis should include match option for Unique OCLC number match method
The Duplicate Title Analysis job and report currently include matching on only one attribute at a time, rather than on all of the attributes that might be covered by a given match rule. For instance, matching on system number provides only matches between 035$a in different records, while the Unique OCLC number match method covers both 035$a and 035$z. As a result the duplicate title analysis report is missing records that would otherwise be found by an import profile or the match method in the network zone.
24 votes -
Allow network zone administrators to unlink bibs from member institutions
In many cases member institutions share records with the NZ that go against the consortium's policy. In these cases the only recourse is to ask the member institution to "copy to catalog", which unlinks the record, allowing the NZ to delete the bib record. This can be cumbersome in a large consortium. It should be possible for the NZ admins to perform this action, i.e. while working in the NZ to unlink a bib from member IZs, as though any institutions holding that bib had selected "copy to catalog".
32 votes -
Deleting Network Zone Records from and Institution Zone in Bulk
Members of Consortia (with appropriate privilege's) need to be able to delete bibliographic records managed in the Network Zone in Bulk from within the member institution Zone
19 votes -
Create "Quick Cataloging" placement default as "Institution" rather than "Network"
When creating an item at checkout, or a brief record, Alma opens up a Quick Cataloging window that defaults the "Placement of new record" into the network. Since these records most often end up with the Cataloger under review, I feel that Alma should default to the Institution Zone instead. This will ensure that we do not unintentionally add these records to the Network zone.
27 votes -
Add a mapping structure for normalization/merge rules in MDE
The numbers of normalization rules is getting quite annoying. When we are in a consortium we also see every rule in the network zone.
I would like a posibility to create folders like in Analytics.
This would be helpful to group rules by institution or category.38 votes
- Don't see your idea?