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.
87 results found
-
Test Voting Status
Testing if status change returns votes
2 votes -
Adding a field “Item Inventory Price” to the view customization table, as well as export files in item search results
It would be very useful and is much anticipated by customers to be able add a field containing Item’s Inventory Price to the Item information tile in the item search results in Alma.
The field should be added to the first column of the Manage Column Display/Customize View.
In addition, we would like to have this field added to export files that are created under the command: Export to Excel (current view / all fields).The National Library of Poland cooperates with 141 libraries. During consultations with other institutions most of them raised necessity of such solution.
Item Inventory Price…203 votesHi all, thank you for sharing this idea!
We will add the option to display item inventory price on the items search results page. This development will be part of the planned move to the new UX.
-
Creating POL from portfolio level should take the identifier from 020 and not from 776
When PO Line is created from the Portfolio level, ISBN comes from Marc21 field 776.
When PO Line is created directly from the bibliographic record, the ISBN comes from the first Marc21 field 020.
Desired behavior:
When PO Line is created from the Portfolio level, the ISBN should come from the first Marc21 field 020 (same as when PO Line is created directly from the bibliographic record).
142 votes -
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 -
Filter OUT cancelled PO Lines
Provide a facet to filter OUT cancelled PO Lines in the PO Line view. We have a lot of cancelled PO Lines with the same title as existing PO Lines, and it is confusing and time consuming to find the 'active' PO Lines. It would help us tremendously if we could filter OUT cancelled PO Lines, perhaps even by default.
13 votes -
Suppress bib record when no active portfolios/services
If a record has zero active services, it should be automatically suppressed in Primo. When we choose to use the CDI records for a collection instead of the CZ records, there is a button to "change to CDI-only full text activation." This suppresses the service, but it does not suppress the bib records. We have to manually run a job on each collection to also suppress the bib records. Most of the time this is fine (even though it's an extra step), but if some of the CZ bib records overlap with other collections, we don't necessarily want to suppress…
133 votesDear community,
Please see my last comment - This is CERV 8182 for 2024:
After discussing with the community focal people, this is the planned solution:
A new customer parameter will be introduced. If set to true, titles without available inventory will not appear in PrimoVE search. This will be the situation regardless of the “Suppress” status that appears as an eye icon in Alma or the workflow which deleted/deactivated a resource, and even if the title did not have inventory in the first place.
Please review the last comment - it includes additional details on the planned solution, and the design document that will be used by Alma developers for this.
I would appreciate your comments.
Thanks,
Tamar Fuches
Alma product manager
-
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…354 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.
-
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…
283 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…
524 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
-
Allow to define several local search indexes, including standard MARC fields
Following the partial implementation of idea "Ability to search via free text MARC tag and subfields" (https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/17197337-ability-to-search-via-free-text-marc-tag-and-subfi) under NERS 2020 #6795, here is perhaps a more modest suggestion, that hopefully can be more technically feasible and still provide a large chunk of the missing functionality.
Similar to the analytics "Local Param" concept, it would be very helpful if institutions were able to define 5-10 "Local Search Indexes", based on each institution's needs. These indexes should be able to include any MARC field or subfield, whether local or standard (and preferably also field combinations).
Use case: In our institution,…
64 votes -
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…
79 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…
332 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
130 votes
- Don't see your idea?