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.
78 results found
-
Deleting Bib in NZ if record not Held by other IZs - Delete bib records job
When running the "Delete bibliographic records" job on a set of bib records in the IZ, check if the records being deleted are not held by any other members and if not - delete the bib on the NZ as well.
1 vote -
Bib Suppressed in NZ - Not showed suppressed in lZ
When a bib record is suppressed from Discovery at NZ level, it would be nice to have the Suppressed Icon when searching for the same bib record at the IZ level in the Network tab.
1 vote -
Add "equal" option to the title search "Authority id" index
When searching for titles by authority ID, currently the search supports searching with: Contains keywords, contains phrase, is empty, not contains keywords, not contains phrase, is not empty.
Add the option to also search by "equals".3 votes -
"Show linked bibliographic records" action in Authorities search.
Add a new action in the Authorities search, that will allow navigating to the bibliographic records in the institution's catalog that have bib headings linked to that authority record.
0 votes -
Add RFID Support for Ship Items
Where there is an RFID integration Profile, an RFID icon shows up at the Scan In Interface and Patron Services WB, allowing to scan in items using RFID.
The same icon should allow also shipping resource sharing items using their RFID information in the Ship Items interface
3 votes -
Alma overlap analysis tool to include different identifiers in one comparison
We would find it useful if the overlap analysis tool compare a list that includes different identifiers. i.e. ISSN, EISSN, ISBN, EISBN, TITLE in one comparison.
Currently it only allows you to compare overlap within just one identifier. This is very important with collections from vendors that include different kinds of material.
Being able to conduct this kind of overlap analysis is important for us in terms of making purchasing decisions and we feel that including this kind of feature in the overlap analysis tool would make this a more efficient process within Alma.208 votesDear community,
Thank you for the idea. We suggest the following high level solution:
1. In Resources menu > Overlap and Collection Analysis > Compare collection analysis, it will be possible to select multiple match methods, from the existing list of match methods, and the order in which they will be used
2. The match will work as following: Try to match by method #1. If no match was found, try to match by method #2.
3. The report will include information on the matched identifier and its value
4. Similarly, in Resources menu > Overlap and Collection Analysis > Look Up Titles, it will be possible to upload an input file with multiple identifiers columns. The possible identifiers are the existing ones, and columns format will be the same as today. The difference is that it will be possible to place multiple identifier columns, in the order they should be used.
Thaks,
Tamar Fuches
Alma team
-
Bursar integration: Additional fee statuses in Alma & Allow fee status change with job Import from Bursar
Currently there exist in Alma only the fee statuses “open”, “transferred” and “closed”. Transferred means fee was exported to external Bursar system. When the fee is imported back to Alma, it is automatically Closed. For staff it is not possible to tell if the closed fee was paid, waived, unpaid etc. without consulting the 3rd party Bursar system.
To give the librarians and end users more transparency about the (invoice) status of a fee, we would need more differentiated fee statuses. Also, we need to be able to set this status when importing the fees back to Alma using the…362 votesAdditional 10 closed fee statuses will be mapped in a code table. Libraries will be able to change their description. Fees with any of these statuses will be considered closed for all purposes.
The same types will be used also for transaction types.
When an import from bursar is processed, each fee may optionally include a code of the status to which the fee will change.
-
Additional Locations for Shelf Report
The ability to select multiple locations for the Shelf Report tool would be very valuable. For example, if we scan multiple floors but each floor is a separate location, we end up with a large number of items skew the report and require us running the same report again and trying to weed out the overlaps. This would also simplify the report if collections were intermixed within a physical location such as Floor 1 and Floor 1 - non-circulating or Floor 2 and Floor 2 - Oversized.
20 votesThank you for raising this idea. When running a shelf report, it will be possible to upload multiple files representing multiple locations in a certain library.
-
Alma collections: Allow to add from network zone
Our Alma consortium shares a common network zone. On the local institution level, we are building Alma collections (not digital/electronic collections). We can add titles from the institution zone, but we can't add titles from the network zone.
This is documented:
Alma Online Help (English) > Resource Management > Inventory > Managing Collections"You can only add titles from your Institution Zone to collections. NZ-managed inventory cannot be added to collections."
This is very bad since many of our e-book packages are managed on the NZ level. So we can't add e-books to our collection and present them together with…
158 votes -
Serials: Editing of Description Needed
When opening predicted items, the Description-Field is populated by the data provided in “Next Predicted Item´s information” and displays these data in a certain punctuation-logic. Unfortunately, this logic is not equal to the description- (and punctuation-) logic used in German speaking countries (which is following ZETA-Standard) – and there is no possibility to edit this. Since there has to be a correct description (for sorting etc.), the only way is to open and edit every single item once it is created by prediction pattern. This is causing a lot of unnecessary work to be done manually - we need the…
286 votesDear all,
It will be possible to have predicted items' descriptions created from the enum/chron fields using Alma's description templates.
-
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…
531 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
-
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…248 votes -
Don't link unauthorized headings based on 008 14-16
Alma should take into account positions 14-16 of the 008 of the authority record when "deciding" if it should link to and update a biographic heading.
In the case of the main entry if position 14 is not "b" then make the link and update. If it is "b" it should not link and update.
In the case of a subject entry if position 15 is not "b" then make the link and update. If it is "b" it should not link and update.
In the case of a series entry if position 16 is not "b" then make the…0 votesThis is a gap and will be handled as part of our backlog
-
NCIP request security
Currently a valid NCIP request from anywhere can retrieve information about a given library's patrons. In order to exploit this, the attacker would need to know server address, institution code, code of the profile for ILL, all of the correct metadata, and the correct message type/formatting. It's not trivial to gather up all that information for a given institution, but much of the information is publicly available (e.g. NCIP message formatting is a public standard), and none of it is generally treated as a secret.
Given the continuously evolving state of library systems security, it would be good to prevent…
81 votes -
Metadata editor: Enable moving up and down within a field using arrow keys
It would be nice to be able to move up and down within a field using arrow keys in MDE. For example, when a lengthy 505 or 520 MARC field has many lines, the cataloger must now move to the desired line using either mouse or left/right arrow keys, since pressing up/down arrow causes the pointer to move to the previous/next field.
My suggestion is that the pointer should be able to move within the field using up/down arrows and move only to the previous/next field when the pointer is on the first/last line of the field.
Using up/down arrow…
336 votesDear all, we are currently working on a design concept for a new form interface option for cataloging, which will make it easier to navigate long fields and subfields - we will take this request into account as part of this design. See our "Form Editing for MARC 21 Bibliographic Records" roadmap plans for more information: https://knowledge.exlibrisgroup.com/Alma/Product_Materials/010Roadmap/Alma_Roadmap_Highlights_(2024-2025)/Metadata_Management#Form_Editing_for_MARC_21_Bibliographic_Records
-
Add a facultative note to patron when rejecting purchase request
Our proposal is to add a free field text in the popup when rejecting a purchase request. This field would include a note to the user, detailing the reject reason.
This could be used by the library in several ways :
- give the link to the record in Primo for documents already available ;
- give the link to an Open Access version of the document ;
- give details about the book (out of print...).It would make communication more personal
140 votes -
Subdivided LCSH headings should be flipped by Preferred Term Correction
Preferred Term Correction is not flipping all LCSH headings when the authority record changes. If there is an authority record that has a subdivision, it is only flipped by PTC if the heading in the bib has no additional subdivisions. This means there is a significant gap in the PTC process that requires manual attention and handling, which is unsustainable. The PTC process needs to be more thorough.
For example, this LCSH:
$a Germany $x Politics and government $y 19th century
was updated by LC to be:
$a Germany $x Politics and government $y 1789-1900
When the authority record changed,…
309 votes -
Allow institution to determine which type of Bibliographic record will be created when creating a Purchase Request
This idea was submitted by Ex Libris product management team in order to better understand the need as well as get feedback from the community.
Current situation:
- A purchase request can be created from Primo/Leganto/Alma
- A purchase request must rely on a Bibliographic record, there are 2 options for the purchase request to match on a Bibliographic record:
- Match to an existing Bib record (if exists)
- Create a new Bib record (this is the use case described below)
When creating a purchase request, the user has the option to decide whether it is a "One Time" purchase (Book) or "Continuous"…
5 votes -
Please add the ability to use the facets for Archival Materials according to LDR pos. 8 = a
Hello,
Most archival materials are cataloged as follows:
LDR pos. 6 = p
LDR pos. 8 = a
Currently, the facet in Alma show these kind of materials as "Undefined".
Adding a facet of "Achieve Material" according to LDR pos.8 = a, would be very useful.Thanks.
63 votesDear all,
After further analysis, we believe the correct solution here would be to add a separate Alma facet for archival materials, so's not to create confusion or inconsistencies regarding resource types.
-
Add an order action in the Purchase Request to “Approve and order from the CZ
Add an order action in the Purchase Request to “Approve and order from the CZ.” Alma would add an alert to the citation and redirect the user to the Community Zone, to the desired portfolio. The operator will only need to click on the "Approve and order from the CZ". Currently the only Action is “Approve and Order” which creates a local portfolio not linked to an E-Collection. It’s cumbersome and time consuming to re-link the POL and portfolio to the correct Community Zone record.
313 votes
- Don't see your idea?