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.
46 results found
-
Mechanism to validate binary MARC record structure
There is currently no mechanism within Alma to ensure that exported or published binary MARC records have valid record structures. Even though Alma uses MARCXML and is not impacted internally by invalid binary MARC, libraries must still provide binary MARC records to external entities in the course of regular business (vendors, outsourcers, agencies, other stakeholders).
Structurally invalid binary MARC records significantly hamper data sharing for libraries. A third party application, MarcEdit, can be used to validate MARC record structure, but since our data is stored in Alma, there should be a mechanism native to Alma that validates binary MARC structure…
64 votes -
Bibliographic records editing history
Here is an enhancement request concerning bibliographic records editing history.
Currently, the "View Versions" can only tell the different version of a bib. record. However, this cannot tell logging history of updating/editing the bib. records, e.g. who add/remove a MARC fields/who suppressed/released the bib. record etc. This is no history tab to keep tracking the changes of a bib. record which is unlike other history tab functionality available in other Alma pages, e.g.
• The PO Line Summary page when editing a PO line
• The Physical Item Editor page when editing item records
• The License Terms Details page…128 votes -
Preferred term correction - correct coding when flipping LCSH to LCGFT
When a 655 field is coded for LCSH and matches a non-preferred term in LCGFT, Alma flips the heading to the preferred LCGFT term but does not update the coding (it should change the 2nd ind to 7 and add $2 lcgft).
The problem is limited to cases where:
A bib heading 655/_0 matches a non-preferred term in an LCGFT authority
What happens is:
The PTC job flips the heading to the LCGFT preferred form, but it does not change the 2nd-indicator from 0 to 7, and does not add $2lcgft
What is not a problem:
655/0 headings that…
73 votes -
search filters and better results display in the "search external resources" function
When we are searching WorldCat for a record to match a newly-ordered title, we often find duplicate records. The current search results display makes it difficult and time-consuming to choose the best record.
The external resources search would be much improved if we could limit search results by the language of cataloging (040 |b) and format. This would save us having to wade through multiple vendor records that aren't even in our local language of cataloging, and multiple records for resources in a format other than the one we are looking for.
It would save us a lot of time…
97 votes -
Reminders : extend the Add reminder functionality to other roles (only Cataloger now)
Reminders functionality could be more effective if extended to other roles than only cataloger role. At least Electronic and Physical inventory operators should be able to add a reminder on a Bib record in a repository search result.
The managing of reminders from Cataloging menu can be limited to catalogers.82 votes -
Ability to select records to release from MD editor
Cataloger can release 1 record per time or all records can be released, but it would be useful catalogers could select multiples records to release.
89 votes
- Don't see your idea?