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.
1823 results found
-
Implement auto holdings for Ebsco
Often there are many collections with Ebsco and it would be great to be able to have them on auto holding to have everything in one collection
16 votes -
Ability To Search Invoices By Payment Status
We would like the ability to search invoices by payment status. This is important to us because we bulk export invoices (XML), one campus at a time. For example, we need to be able to check that all invoices in Ready to Be Paid status are of one campus before we send to the integration.
21 votes -
Seasonal Serials Prediction Patterns only work when beginning with Spring.
Area of concern: Serials Prediction in Alma.
Currently, when creating 853 predictive patterns, there are limitations to titles with a seasonal frequency. Attempting to create seasonal prediction patterns, whose enumerations begin with anything but Spring (21) results in errors, such as skipped issues, or improper numbering.
This limitation means that many journals with seasonal patterns cannot have their issues correctly predicted out through Alma’s automated process. Staff members are stuck manually creating/receiving issues for these titles. This decreases efficiency, increases the likelihood of human error, and prevents Alma’s claiming process from working correctly.
What should be changed: As Serials Processors,…
47 votes -
Add fields, ‘Pattern Type’ and ‘Linking Number’ to the ‘Change Physical Items’ Job
Area of concern: Additional indexes for ‘Change Physical Items’ Job.
Please reference Ex Libris presentation ‘Automation Tasks for Summary Holdings’:
In order for 863/866 Summary Holdings generation to work properly, each item record must contain certain information in the ‘Pattern Type’ and ‘Linking Number’ fields. Currently, neither of these fields are available via the ‘Change Physical Items’ job.
What should be changed: As Serials Processors, we would like item level fields, ‘Pattern Type’ and ‘Linking Number’, made editable via the ‘Change Physical Items’ Job. Being able to change these fields in batch would benefit our workflow by allowing us…
21 votes -
Map item level fields, Pattern Type and Linking Number in Analytics.
Area of concern: Analytics Fields for Reporting on Serials 863/866 Generation.
Please reference Ex Libris presentation ‘Automation Tasks for Summary Holdings’:
In order for 863/866 Summary Holdings generation to work properly, each item record must contain certain information in the ‘Pattern Type’ and ‘Linking Number’ fields. Currently, these fields are not mapped in analytics, so there is no way to report on which records lack this info. Without this reporting capability, we are stuck individually checking many thousands of records to be sure they have the required information.
What should be changed: As Serials Processors, we would like to…
48 votes -
Allow user to ‘Withdraw’ and ‘Open Predicted Items’ from the ‘Received Items Screen’.
Currently, ‘Withdraw’ and ‘Open Predicted Items’ functions cannot be performed from the ‘Received Items List’, during normal receiving operations.
https://drive.google.com/file/d/1qdNSY1xkPr71R7XJzPp8QtQJEa_h-00i/view?usp=sharing
Instead, a user must back out of the receiving windows, perform a title search, and access these features through the ‘List of Items’ window.
https://drive.google.com/file/d/17yB9XwMI6MYAmnHq95mna6cOUMpXzlbq/view?usp=sharing
This drastically decreases efficiency in performing routine tasks in Prediction, Receiving, and Weeding.
What should be changed: As Serials Processors, we would like to see the ‘Withdraw’ and ‘Open Predicted Items’ functions added to the ‘Received Items List’ window, so that all serials management tasks can be done from one screen. This would eliminate the…
539 votesDear community, as part of the ongoing UX improvements in Alma, the "Receive new material" screen (aka Receiving WB) is planned to be refactored and support the need described in this idea. For more information see Alma roadmap:
Thanks,
Noam Fass | Alma product team
-
Alma MDE: Filter by Marc21 field and subfield
As a cataloger I would like to have the possibility in MDE to filter the Marc21 data by field and subfield
value to have a better overview over the current part of the data which is to be checked/edited.
Further I would like to have the possibility to quick access filters which i use often.Proposal:
Add a possibility to filter by field and subfield, e.g. by having an input form for the Marc21
field (rows filtered by "Begins with {value}") and for the Marc21 subfield (rows filtered by
"Contains {value}"). The filtering should by done by "AND" condition. (See…73 votes -
Mejorar realizar cambios globales en ejemplares físicos
Permitir realizar cambios globales sobre los campos de signatura de ejemplares físicos, para modificar una parte de la signatura sin cambiar el resto. Por ejemplo:
EPP3500(075)/ALV cambiar a PLP3500(075)/ALV
EPP3300/WES cambiar a PLP3300/WES
22 votes -
Receipt for waived fees
Customers sometimes want a receipt for waived fees. Currently that's not possible within ALMA.
20 votes -
Collection Discovery manual title ordering
In collections and sub-collections, please allow adjusting the order of titles manually (and individually - like we change the order of collections by drag-and-drop).
While the ability to change the default sort method is useful, our collections require more granular control over the order in which titles display.
A drag-and-drop system would be ideal. Slightly less useful would be the ability to track and sort by the date that each title was added to a collection.
35 votes -
Estimated price -field for following year on continuous POL
Estimated price -field is needed for databases and another continuous purchase orders for following year budget planning. There should be price fields for both current year and the following year (also possibility to split them to different funds). Estimated price -field should also to be selected on the analytics reports. Publishers may change database or journals prices a lot more than average rate.
36 votes -
Add usage statistics -field for other statistics than Counter
A need for a new Usage Statistics -field that could be used for usage statistics other than Counter. Smaller e-journal etc. publishers don't have Sushi statistics but libraries collect usage data another way. The new usage statistics field should be for every year. The Usage Statistics -field should work on the Analytics. Statistics notes -field is also required.
34 votes -
Related holdings displayed only after "direct" holdings in the brief results
Currently, only 5 holdings are displayed in the "Physical" tab in the brief results list in Alma. In many cases holdings and "related" holdings are mixed and displayed without any particular ranking. Especially when many of them are present, it takes many clicks before one can exclude the related holdings and obtain a list of all holdings linked directly to a record.
The "Physical" tab in Alma could be changed like this: all holdings linked directly to the record are displayed first (regardless of the library), and only then come the holdings of related records.141 votes -
Customize the amount of holdings displayed in the brief results
Currently, only 5 holdings are displayed in the "Physical" tab in the brief results list in Alma. For IZs with many libraries, this is not always ideal and many clicks are necessary before getting to the complete list of holdings.
The new sortlibraryby_relevance parameter helps but doesn't solve all issues.
Therefore, we'd like to ask to implement a functionality similar to what can be done for the amount of records to be displayed in the results list (at the moment, one can choose between 10/20/50) so that for example staff users can choose whether they want to see…142 votes -
Improve the e-book purchase request workflow
The purchase request workflow needs to be improved for acqusition of electronic resources.
Currently, you can either approve or reject a purchase request. An approval automatically creates a POL and a standalone portfolio based in the Purchase Request BIB record. Both outcomes are unfortunate when working with e-books. An e-book will usually be ordered on the vendor site (e.g., the ProQuest portal) rather than through an Alma POL. It should be possible to select whether a POL is created. More importantly, we'd like the option, upon approval, to select and activeate a title from among CZ collections instead of having…254 votes -
Option to define another set of records to be included in the Database search
The database search in Primo includes only electronic collections with collection type “database” or electronic collections with a collection level URL and an unsuppressed bibliographic record.
Even though you can change the electronic material type of a portfolio to “database” these titles can’t be searched through the database search. This means we have to add local database collections even though the title can be activated through the community zone.
An example is the electronic collection “De Gruyter Databases”. I should like to be able to include these in the database search.52 votes -
Sort booking requests by Start Time
When monitoring resource requests on Fulfillment > Monitor Requests & Item Processes, a "Sort by" button with an option to sort by Start Time would ease the handling of booking requests.
The booking requests are currently sorted by Request Date, which is not very useful, and can not be sorted by any other field.A "Sort by" button actually does appear on Fulfillment > Pick From Shelf.
Another option could be adding the Start Time on the drop down menu of the bar "Requests" on top of the page.
62 votes -
The "maximum renewal date" (max_renew_date) should be part of the fields that are provided by API
The max-renew_date is viewable in Primo, but if you use another Discovery it can't be displayed because it is not provided by API.
50 votes -
Improve editing of large fields in the Metadata Editor
When creating and/or editing a MARC field with a large volume of text, such as the 505 or 520 field, occasionally the cursor will appear to be in a different position than it is, so that the user may accidentally delete the wrong characters, or insert them in the wrong place. This appears to happen at random, and saving the record, restarting Alma, and even clearing the browser cache does not consistently fix the problem, even in the short term.
57 votes -
Allow staff to override auto return when a borrowing request is received after needed by date has passed or request has been cancelled
When a borrowing library receives a resource sharing item after the request's needed by date has passed, Alma automatically updates the request to returned without displaying any alert. This causes a substantial amount of confusion for staff. We would like Alma to display an alert when a resource sharing item is being automatically returned to the lender because it was received after the request's needed by date. We would also like the opportunity to override this automatic return so users can have the option of using the item.
Likewise, Alma automatically updates borrowing reqeusts to returned when they've been cancelled…
51 votes
- Don't see your idea?