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.
91 results found
-
Apply physical item template with POL template
The POL template allows a small number of item record elements to be saved: library, location, material type.
It would be beneficial to save staff time by allowing staff creating POLs to also select a physical item templates when creating a POL. This would allow setting defaults such as copy ID, item policy, is magnetic, and pieces, that are generally known at the time of order.Templates are essential time savers.
11 votes -
Missing Padding Option for Accession Number Sequences in Call Number Generation
Currently, Alma does not support padding (adding leading zeros to reach a fixed number of digits) for accession number sequences used in the automatic generation of call numbers (e.g., via the "Generate" / "Calculate" button in the item editor). If the next sequence value is set to "0003," the leading zeros are removed upon saving. Even if the next sequence remains "0003" in the sequence configuration, the zeros are still automatically stripped when generating the next call number in the item editor.
Institutions that use custom call number schemes requiring padding can therefore only use Alma’s "Generate" or "Calculate" button…
9 votes -
Decouple temporary item policy and temporary location
Sometimes we have to set a temporary item policy for items that stay in their permanent location. This requires setting "Item is in a temporary location" = yes and setting the temporary location to the permanent location for the temporary item policy to apply. We would like the ability to set the temporary item policy without needing to set a temporary location.
Furthermore, no warning message is given when "Item is in a temporary location" = no and a temporary item policy is selected. This can lead to confusion because the temporary item policy is not emptied after the setting…
8 votes -
Generate barcodes in batch
Alma can be configured to generate a unique identfier in the barcode field of the item record one record at a time. Once the configuration is set, the unique identifier can be created by clicking the Generate button or simply by clicking Save.
It would be very helpful for Alma be able to generate sequential unique identifiers for each item in a set by running a job. That way, we could create a situation where each item in Alma has a unique identifier, either a real barcode number for a real barcode attached to an item or a different unique…
5 votes -
Add clarifying language to the Delete Holdings records with no Physical Items job
Adjust the wording on the “Delete Holdings records with no Physical items” job to match wording from the “Withdrawn Physical items” job. Change “Delete bibliographic records” to “Delete bibliographic records that have no other holdings” AND "Suppress bibliographic records” to “Suppress bibliographic records that have no other holdings from publishing”. This would add needed clarity to what is happening when running the "Delete Holdings records with no Physical items" job.
4 votes -
Customize search indexes for any Holdings field and subfield
The current Holdings indexes skip several valid fields, such as the 347 and 562 fields. The ability to index these fields (especially the 562 field) would help find records with local information that is only recorded in the holdings record.
Additionally, the ability to index any field and subfield combination would allow libraries to use custom subfields within a valid, relevant field (e.g., a 541$g for a non-public Gift Of note).
3 votes -
Predicted Items - Add columns in Metadata overview
When opening predicted items in the Metadata Editor, the "Predicted Items" pop-up window appears. It would be very useful if the following columns could be added to the overview presented in this window.
Currently, the following columns are shown:
- Description
- Status
- Expected arrival datePlease add:
- First level of enumeration (= Enumeration A in the physical item editor)
- Second level of enumeration (= Enumeration B)
- First level of chonology (= Chronology I)
- Second level of chronology (= Chronology J)This addition would make it easier to verify whether all relevant fields are correctly…
3 votesHi all,
Please note that this idea was mistakenly closed. It has now been reopened, and we apologize for any inconvenience caused.
-
Put related holdings in its own tab not displayed among the actual holdings in Alma
Add the option to turn off the display of related records holding in the holding display for a title in Alma. Having it among the 'true' holdings is very confusing and for most part not relevant when needing to locate the title at hand - In that case I'm not interested in a completely different title just because they share a relation to that title in our collection.
A tab with the related records information would make a less cluttered view3 votesHi all,
This idea was mistakenly closed. It has now been reopened, and we apologize for any inconvenience caused.
-
reuse sets with uploaded Excel Files
Currently, we can create itemized sets of physical books by uploading an Excel sheet of barcodes. But, we are not able to reuse the set in the same manner.
We would like to be able to create one set (for withdrawing books, etc.). Then, when the job is completed, we would like to reuse that set, upload a new Excel sheet and run another job. This will cut down on the number of new sets we need to create for a single task.
Thank you for considering this idea!
1 vote -
The Provenance field in the physical item editor
We would like the Provenance field in the physical item editor to be mandatory.
It is possible to have a default for the list but that is not the same thing. We are afraid people will be not so attentive, and the default option will be the one they always choose. We want it to be mandatory and default to nothing. The user then has to choose something in order to save the item.1 vote -
Enable forcing barcode number for new items
When cataloguing a new item, we wish to force cataloguers to add barcode number before save. If some libraries do not want that, forcing the barcode field could be optional.
1 vote
- Don't see your idea?