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.
130 results found
-
Process types and statuses in the list of predicted items
In the list of items, we would like to add to the customisation view the ability to see the date on which the process type was last modified. Currently, you have to edit each item and check the 'History' tab to get this information
Moreover, all the history disappears as soon as the item is received.1 vote -
Add Process types and statuses in the menu “Manage in Process items”
It would be helpful to be able to search by Call number in the menu « Manage in Process items ».
The list of results cannot be filtered or sorted by modification date, by status or by the operator who did the last change.
The description of the item (Year, Volume, Number…) is also missing from the list and can only be seen by editing the item. It would be helpful for the resource management of serial publications.2 votes -
Readability of the item availability column
The Item availability column becomes illegible if it’s more than two lines long, which is often the case for Serials. It would be helpful to be able to adjust the width of the column and it would also be helpful if there could be a line break for each new 866 zone (Marc21).
1 vote -
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…
2 votes -
Move requests and temporary locations - option to flag for processing, etc.
At present the item move requests sometimes work too seamlessly. Especially for items that are onloan when the request are made (or the item is restored to its permanent location). This is an issue when the items need manual intervention, e.g. relabelling. Items go through the process without being flagged unless another process is used, e.g. a work order or fulfillment note.
It should be possible to flag items for manual intervention when they arrive at their new or original location. A message on the lines of 'Move Request: check labels etc.,' in the manner of a fulfillment note.
53 votes -
Commitment to retain blocked by location
The commitment to retain functionality is really great for managing shared print collections, but not all physical locations should be eligible for retention commitments. For example, there are certain locations that might hold rented/leased material or material that the library cannot commit to retaining long term. Items in those locations should not present those fields. Can that be added to physical item configuration?
7 votes -
Add Reporting Codes and Dates to Items screen
Reporting Codes can be applied to POLs only.
Reporting codes and dates allow libraries the freedom to set codes and manage items.
For example, items can set Funds when it is no longer linked to a POLs with Change holding.
Also, missing book codes and date can be entered in case of a missing book.
Allowing Reporting codes, or some similar code, to be applied to Items would add a great deal of flexibility and utility to an already good idea.3 votes -
Option to restore Temporary Item Policy and Temporary Location when item is returned from Resource Sharing.
Issue: For items that have a temporary item policy or temporary location there should be a way to revert these temporary statuses when the items are returned from a Resource Sharing loan.
When items with these temporary designations are loaned via Resource Sharing Alma applies the Resource Sharing temporary statuses. When the items are returned the Resource Sharing statuses are cleared but library staff need to be able to direct items back to their temporary location. There are many instances when materials that have a temporary status are loaned via Resource Sharing (as we want them to be) but when…0 votes -
Change physical items job -- adding notes improvement
The "Append to field" option was added in November 2023, but two additional options are still required.
'Delimiter' should be an option.
Now, the default delimiter is ";".
Some institutions use symbols other than ";" as delimiters.
For example, we use "|".
Therefore, there is a need to make the delimiter optional.Writing forward in the note
The current specification is to write backwards.
Some institutions operate writing new information in the front of the note.
There are three reasons for this.
(1)It is easier to manually add notes at the front of the note.
(2)It is easier to see…
50 votes -
Add option to Quick Cataloging Template for Publish/Don't Publish to OCLC.
Add a checkbox option to the Quick Cataloging Template for Publish/Don't Publish to OCLC. This would prevent brief records for items created by circulation staff for professor's personal copies from being sent to OCLC and added as new records.
21 votes -
Changes made to Enumeration D - H, and Chronology K & M should appear in the item History tab
At this time, only changes made to the Enumeration Fields A-C, Chronology I-J, and Chronology L appear in the item record under the History tab; we would like for changes made to any of the Enumeration and Chronology fields to appear in the History tab of the item record.
If Alma is offering the use of 13 different enum/chron fields, they should all follow the same rules. Emphasis should not be given to just a handful of these fields, because many institutions use more than the 6 most popular fields.
16 votes -
Add "number of renewals" as a unit of measure for configuring maximum renewal period
Telling patrons that something can be renewed a maximum of one, three, or six times is much clearer than explaining a renewal period, and patrons are often caught off guard when a renewal goes through for fewer days than usual. Adding "number of renewals" as an option for configuring maximum renewal would greatly cut back on confusion.
6 votes -
Option to hide libraries from Alma persistent search indexes
We do not make use of the institution-level Resource Sharing Library for anything at all (our physical library locations are all resource sharing libraries and are all we use for res share purposes), and so it would be great if we didn't have to see the out of the box RSL in the libraries drop down menu in Alma when doing searches.
Options to hide any items we don't make use of in general in Alma search indexes / other menus would be great, as it would declutter the interface and be less confusing for staff.
2 votes -
Make accession numbers in configuration editable
In the Accession Configuration it is only possible to change the next sequence number. Not the sequence name, the library or the location. For example, when you want to add a library or change the library, you have to delete the row and enter the prefix again - with the correct sequence number. Because of the closure of our Central Library we had to delete nearly every single entry and make new entries for each prefix.
2 votes -
When a specific Operator runs a Job that updates physical items, the ID of the Operator that initiated the job should be included in physica
When a specific operator runs a job to update or change physical items, that operator should be listed in the physical item's history, rather than just "System".
6 votes -
Add 'loan date' to items list
after 6 long years, finally "due date" as added to items list..
"Loan date" field is as important to see, as the "due date". if we have 50 items which were loaned in different times, most of them can have the same due date (because we have periods of closed days-holydays). we have to be able to make the same decision, as system, regarding, which item can be recalled first, if we need to make manual request on specific item.
please consider adding this field also - and really hope it wouldn't take another 6 years1 vote -
slip for items sent to binding - improvements
we send to binding not only periodical issues that are bound together. we also send individual periodical volumes/books which binding wears out. in this case there is no option to add a note for the binder - options which exists when 2 or more issues are bound together in alma.
we send to binding hundreds of items. printing out hundreds of slips, when a slip takes up the whole page - is a waste of paper. so we stuck with continuing writing the info for the binder manually, on small pieces of paper. it would be a large improvement to…
1 vote -
"in process items" screen - circulation desk management: adding fields
At circ desk we use "in process items" screen to manage items in circ work order processes. Unfortunately the screen is unusable, if we are processing periodicals which are sent/recieved from binding: currently there is no way to distinguish at a glance which volume it is. as we send several volumes of the same periodical at once and our physical copies of periodicals don't have barcodes/barcode numbers. so please add a description field to this screen.
another field that is necessary is: Locationyes we can see this information via 3 dots...but it is not at a glance....
1 vote -
Add 130 and 246 fields to brief results in Physical Titles search
We would like data from the 130 and 246 fields to display in brief results for Physical titles searches. We would want the 130 field to be labeled as "Uniform Title" and the 246 field to be labeled as "Varying Form of Title." This is useful for serials where the title in the 245 field isn't necessarily the most well-known form of the title.
5 votes -
Avoid duplicate Item call numbers
At present, when duplicating an item, barcode is automatically generated and saved even before any changes in a duplicated item record are done. That means in practice, that if - for some reason - Item call number or any other field were not modified, duplication is created. That is a huge problem in fields that 1] require unique value, 2] there are no warnings about duplicate value in any moment of the process. Suggestion: Similar to duplicating bib record, the new barcode is created only after actual saving of the new (duplicated) item. The cataloguer will be required to generate…
1 vote
- Don't see your idea?