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.
1999 results found
-
Please add the ability to run jobs on a representation level in digital records
Hello
Currently, the jobs for digital records run only on "Title" level.
If we run a job on a record that has more than one representation, the job will run on all the representations, even if we want it to run only on a specific one.In electronic records and physical records we have jobs that run on a portfolio level and item level.
The same should be applied on digital records.
The job should include changing information (for example public note) and deletion if needed.
This should also help the following idea:
https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/42199792-enable-withdrawing-digital-representations-job-basThanks,
Dafna83 votes -
Establish system to ensure complete coverage of LC classifications
Alma Analytics includes LC Classification code data, but frequently valid classification codes come up as "Unknown." Ex Libris currently has no reliable way of keeping up with changes in LC classification. They rely upon the "Library of Congress Classification Outline", which is not complete. They will add classifications upon customer request, though this process takes months or years and puts significant burden upon institutions. Ex Libris should develop a system to reliably update its LC classification coverage. This could take the form of e.g. establishing its own access to Classification Web, subscribing to LC updates, and/or setting up some alternative…
67 votes -
scan in items: Define the value of the "Register in-house use" blank by default
The value of the ‘Register In-House Use’ box is saved from session to session. This causes errors by staff who forget to activate or deactivate it as appropriate, so that statistical data may not be reliable.
We would like to propose that this field could be set to a default value (e.g. blank) and that staff should activate the tick when registering in-house use.92 votes -
replace "Do not show as Full Text available in CDI even if active in Alma" with a pair of show local / show CDI checkboxes
To avoid duplicates when we have both local portfolios and CDI records, we can rely on the "Do not show as Full Text available in CDI even if active in Alma".
Enabling this feature will show in Primo local IZ portfolios, and is very good when local records are rich and CZ records are limited/poor.
Sometimes however CDI records are richer and provide indexing at chapter level. In such a case we would like to hide IZ local portfolios and show CDI records instead.
It would be therefore useful and clearer to replace the "Do not show as Full Text…93 votes -
Consistent use of first ISBN in MARC field 020 for electronic resources in Alma
Right now which ISBN is displayed/taken for export relating to e-resources is rather inconsistent in Alma:
.) In the results list of an All Titles search the first ISBN of MARC field 020 is displayed and subsequently used for Excel export.
.) In the results list of an Electronic Portfolio search the second ISBN of MARC field 020 is displayed (if there is one) and subsequently used for Excel export.
.) In the portfolio list of an electronic collection the second ISBN of MARC field 020 is displayed (if there is one).
.) On the portfolio tab of the Electronic…153 votes -
Add Alma support for microlanguages and language codes recognised by Library of Congress, including Austlang
Alma’s support for Language for search indexing, facet, and display is hardcoded for 041 to the 3 digit MARC Code List for Languages.
This excludes languages recognised by Library of Congress, such as Austlang languages which were recognised more than 6 years ago in 2018.
This issue has been addressed in Primo in 2021 and 2022 with customer advocacy efforts, but remains a glaring omission within Alma.
See details: https://igelu.org/primo-support-for-austlang-and-iso-639-3/The only option currently within Alma for searching this data is to use the keyword field to search by information such as C15, and then use the Language filter to…
83 votes -
Job “Withdraw Physical items” and holding of related records
With the “Withdraw Physical items” job, Alma does not provide the option of preventing the deletion of holding and bibliographic records when there are Holding of related record. We would like an additional option “Delete holdings; delete bibliographic records that have no other holdings and that have no Holding of related records”.
32 votes -
linked-data-powered sets and collections
TL;DR: populate existing ALMA sets / collections infrastructure using retrieval of a list of LCCNs from an external URL to allow linked-data-powered sets and collections.
Problem
We've all seen the book displays that most physical libraries have in their high-traffic areas. These might be works by the in-house press, topical events, anniversaries of author's birth, etc, etc.
In the digital space, there are shallow-functionality RSS feeds and then a yawning gap out to things that are typically called 'digital exhibitions' which are resource-intensive glossy displays.
ALMA Collections can be used for digital exhibitions, but populating them is labour-intensive and slow.
…
34 votes -
All MARC records in the Alma Community Zone should be sorted chronologically between MARC fields 500 - 899.
The fact that the MARC fields between 500 and 899 are not sorted chronologically for all Alma Community Zone MARC records makes it difficult for us to use the “Collections” function in Primo.
In the Collections function in Primo, we display the author on the overview page in addition to the title. The author is displayed via a small script in Primo. This script takes the “au” field from the PNX record of the title or, if “au” is not available, the “addau” field and displays the first value from “au” or “addau” in the title overview of the collections.…37 votes -
Display the item process type in the Po line
In some cases it is important to know the process type of the item, more specifically whether it is on loan. In a purchase order line, it is currently only possible to see the availability of the item under 'Ordered Items', not the process type. The green dot under ‘Availability’ means whether the item has been received and not if it is actually available on the shelf, which is misleading. In order to see the process type, this must be done in the item record or in a title search. It would be very useful to know from the PO…
26 votes -
Display “Service unavailability display message” at Collection Level in Primo
Currently, the “Service unavailability display message” is only shown at the Journal and article level in Primo. It would be highly beneficial to extend this functionality to the collection level as well. This enhancement would provide users with clearer information about service availability, improving their overall experience and reducing confusion when accessing collections.
45 votes -
NOT erasing Return Items page every time we leave it
Every time we leave the Return Items page, it erases the list of returned books. This is disastrous for us, so we would like to keep the list of all books returned during the day (or since logging in until logging out).
If someone benefits from erasing the list, just give us a choice whether we want it erased or not.Now let me explain why it is crucial for our work:
We work in quite small public library where Patrons can move around freely and pick books from the shelves on their own. Often they return books first and…28 votes -
Update Customer Linking Parameters in Bulk via E-Collection Quick Update Cloud App
Please add the ability to update customer linking parameters (such as the Gale location ID) in bulk via the E-Collection Quick Update Cloud App.
As Ex Libris moves away from centrally configuring linking parameters for different interfaces, it would save so much time to be able to do this in bulk via the cloud app.
33 votes -
Add Ability to Exclude Holdings Records from LHR Publishing to OCLC When Holding/Bib Records Are Suppressed from Discovery
Currently, Alma's LHR Publishing job for OCLC does not exclude holdings records from publishing when the holdings record or the related bibliographic record is suppressed from discovery.
We request the addition of an option in the LHR publishing job to exclude such holdings records from publishing to OCLC. This functionality is particularly important for suppressed holdings records, as the management tag for publishing to OCLC is set at the bibliographic level. Currently, if a bib record contains two holdings records, it is not possible to publish one holding to OCLC while excluding the other.
25 votes -
Make physical item templates available in receiving workflow
The new physical item templates look super useful. However, the vast majority of our new items are added as part of our receiving workflow, so they do us little good currently. Can the physical item templates be made available as part of the receiving workflow?
120 votes -
Ability to create additional note fields in the physical item editor
At the physical item Editor, we currently have access to one public note, one Fulfillment note, 3 internal notes and 3 statistics notes. We would need 3 additional public note fields visible to the user in Primo and 3 additional internal note fields.
21 votes -
Enable API Access to the Community Zone Updates Task List
Currently, the Community Zone Updates Task List is accessible only through the Alma user interface. While this provides essential functionality for monitoring and acting on updates, it limits the potential for automation and integration with other tools in the library ecosystem. Many institutions use external systems such as workflow automation tools, electronic resource management platforms, and reporting systems that could benefit from direct access to the Community Zone Updates Task List data via API.
36 votes -
Improvements for the MDEs left pane
The left pane in the MDE is a very helpful tool for navigation in daily business. With the following improvements it could be even more helpful:
- Customization of the display of the different databases in all the tabs (records/templates/rules): it would be very helpful if one could select only the databases that are necessary for the daily work for display (example: I have in the record tab 14 different databases of which I only need 4, and one that I need is only accessible through the drop down menu); if a selection is not possible it would be helpful…68 votes -
Add roles to “Use Electronic Inventory Features” in DARA
Currently, the “Use Electronic Inventory Features” in DARA is available only to users with the “General System Administrator” role.
We propose making the “Use Electronic Inventory Features” available to users with the “Inventory Operator” role for viewing purposes only, without the ability to configure or run jobs.
This will allow more users to view important content news, and better understand and manage electronic resources.34 votes -
Save certain subfields from being overwritten via F3 and PTC
When linking names, subjects etc. from authority files in various BIB fields, some cataloguing conventions require giving additional information in certain cases.
One example for such a requirement, stemming from the German speaking countries, is to add the time and place of an auction when linking to the genre/form term “auction catalogs” in BIB field 655 (see attached screenshot). This additional information is, of course, specific for each BIB record and must not be overwritten or deleted, if at a later point in time either PTC processes said BIB record or a colleague invokes the F3 functionality.
Since different subfields…
24 votes
- Don't see your idea?