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.
1859 results found
-
Please allow manual reordering of record fields inside the MDE, particularly Dublin Core records.
Within Alma search results, dc:creator doesn't display accurately if dc:contributor fields are present. Alma's internal logic displays the final dc:creator or dc:contributor field from the record as the primary creator within search results by digital title. There is no way to force a save or to "lock" the fields in the record within the Metadata Editor to accept dc:creator as a field AFTER dc:contributor. Upon "Save", the dc:creator is always reordered above dc:contributor. This has led to staff confusion when searching within Alma.
1 vote -
We would like to request an enhancement to the Item Scan feature in the library system.
We would like to request an enhancement to the Item Scan feature in the library system.
It would be helpful if the "Permanent Location" field could be included in the scanned items list after scanning is completed.
Since the current Destination may sometimes be assigned to a temporary shelf (e.g., New Arrivals Shelf), we would like to be able to view the item's final destination, namely its Permanent Location, at the same time.
If possible, we would also like the columns to be displayed in the following order:
Title / Destination / Location / Barcode
6 votes -
Please get rid of the message notifications that pop up in the top right corner telling people what they just did.
These inhibit workflow. The collapse-by-default feature is extremely slow, the pop-ups block the tool bar and need to be manually removed before I can continue with my workflow. If there are reasons why people feel this feature needs to be kept, could it please at least be an optional feature that we can turn off? Thanks.
14 votes -
Auto renewals resumption- block preferences
When a request is filled, all the other loans of that title each need to be manually renewed in order to restart auto renewals. These sometimes get missed, frustrating users when their loans needlessly go overdue. It's a very clunky process.
This can be done in Block Preferences, but if Not Renewable – Item has Request(s) is set to 'handle automatically, then it over-rides other requests, which completely defeats the object.
This block preference needs more granularity, so that recalls can resume auto renewing once a request is filled, without affecting requests on other titles.
3 votes -
Clearer terminology for loan and copy requests on ILL request form
Enable libraries to customise or replace terminology in Rapido request forms and request tiles so users can select services using plain language, such as "Loan" and "Digital Copy".
Current gap: The blank request form requires users requesting a loan to select Citation Type "Book" and Format Type "Physical". Rapido request tiles similarly use the term "Physical Copy". Nowhere in these workflows is the term "Loan" used. Users must interpret system terminology to understand which option will provide a borrowed item. Similarly, users requesting a scanned reproduction must select "Digital", which does not clearly communicate that they are requesting a copy…
5 votes -
Copyright declaration displayed only for copy requests on blank ILL form
Configure the copyright declaration on the blank ILL request form to display only when a copy request is being submitted, and not for physical loan requests.
Current gap: The copyright declaration currently appears for both copy and physical loan requests, even though it is only relevant to copies
Impact:
Users requesting physical loans are shown unnecessary copyright messaging
May cause confusion
Creates a less streamlined request experience
1 vote -
Incorporation of All Indigenous Syllabics from the Canadian Aboriginal Syllabics Unicode Block (Revisited)
A previous enhancement request (March 2019; now closed) states that "not all Indigenous syllabics render in Alma, and thus, do not render in Primo either. As an important aspect of Canadian Libraries' commitments to Truth and Reconciliation, and as it is UN's International Year of Indigenous Languages, it would be excellent if Ex Libris could prioritize resolving this issue so that we can allow Indigenous users full discoverability of resources in their own languages."
We have tested the whole range of Canadian Aboriginal Syllabics in our Alma/Primo and can report the following results:
Unified Canadian Aboriginal Syllabics (Range: 1400–167F)
**ALL…61 votes -
Allow institutions to create their own local electronic material types
At the moment, the current list of electronic material types are:
Book
Journal
Dissertation
Proceeding
Conference
Report
Document - This type is sometimes used for portfolios in electronic collections in the Community Zone when the type is not otherwise know. If you see this type in a collection and believe that it is incorrect, please open a Salesforce case to correct it.
Series
Newspaper
Transcript
Database
Wire
CD-ROM
Manuscript
Sound Recording
Map
Other Visual Material - Includes slides and pictures.
Musical Score
Streaming Video
Streaming Audio
Data Set
Website
Video
Primary (Master) Thesis
Government DocumentIt is currently not possible…
6 votes -
Extend bibliographic API to create/update/delete bibliographic sets
Currently, the only way you can interact with sets via API is to have permission to configuration read/write. This is unnecessarily broad - it allows the user to change integration profiles, update some mapping and configuration tables, and change location configurations.
The Bibliographic API needs to be extended to allow manipulation of bibliographic record sets. Anyone working with bibliographic records via API should be able to use sets as part of that workflow without also exposing configuration changes to the same API key.
1 vote -
Keep deleted Alma objects in Analytics
When I delete Alma objects such as PO lines, Purchase orders, course requests, invoices, purchase requests, they are deleted in Analytics as well. On the contrary, even if deleted in Alma, objects like bibliographic records or physical items are still accessible in Analytics.
It would be great if other Alma objects were also accessible in Analytics even if deleted.14 votes -
Add "Process Date" facet to Resource Request Monitoring
For some library processes, the Process Date is a more useful facet than Request Date when there is a need to identify newer vs. older processes. For example, an item currently in transit may have a Request Date from months ago when it was requested by a user, whereas the Process Date is the value that tells us how long the item has been in transit.
When using Resource Request Monitoring to identify items that have been in transit the longest, it would be very helpful to have the ability to facet by Process Date in the same way we…
6 votes -
Separate 655 genre/form from Subjects in Analytics
Since Library of Congress are putting more emphasis on genre/form (MARC 655) and removing the $v Form subdivisions, it would be helpful to separate the 655 searching as genre/form from the broader Subjects field (600, 610, 611, 630, 650, 651 etc) in Alma Analytics. There is already a separate Genre search in Alma advanced search which is very useful.
9 votes -
Limit title level request fulfillment to items from holding records without descriptions or items without descriptions
Current Problematic Functionality: Physical item requests (holds) are placed at the title level (any item from any holding record attached to the bibliographic record will be used to fill the hold) when a holding record has no items with descriptions. Requests are placed at the item level (the exact item requested will be used to fill the hold) when a holding record has one or more items with a description. As a result, if a user places a request on an item attached to a holding record with no description, but there exists on the bibliographic record a second holding…
18 votes -
NOTIFICATION TO CIRCULATION DESK REQUEST CANCELED BY USER AT HIS PRIMO PROFILE
We want that the Circulation-Desk receive a notification letter when the user cancel their requests at their Primo profile. The cancelled reason is Cancelled at patron request. Our institution have two branches, one in Madrid and other in Alcalá de Henares, when the user choice an item located in Alcalá de Henares, he can pick up in a Reading Room in Madrid, but when he did the request and did not change the room to Madrid. So they receive the notification letter that the request will be available in Alcalá de Henares and inmediatily they cancelled the request and made…
13 votes -
Expand the character limit for Inventory number field
The Inventory number field for physical items in Alma is currently limited to 20 characters. We are using RFID tags to track some of our items, and would like to store them in the Inventory number field. Because these codes are generally about 25 characters long, it'd be helpful if the size of the field could be extended to 30 or (preferably) 50 characters.
5 votes -
Find User in Other Institution
Currently, the "Find user in other institution" functionality is only available for designated Resource Sharing libraries.
Many institutions have multiple libraries, only some of which are designated Resource Sharing libraries, yet all libraries are open to all users. We would like to see the "Find user in other instutition" available for ALL libraries in the institution (not just Resource Sharing libraries), to facilitate checkout of library materials to borrowers visiting from other libraries within the network zone.
This functionality is found on the Patron Identification page after going to Fulfillment > Manage Patron Services.
1 vote -
Please allow customer-specific definition of local subfields regarding sorting and non-repeatability
The configuration of resources in Alma offers the option to define local subfields as "non-repeatable". However, this has no effect. No error message appears when saving if a local subfield is accidentally populated multiple times.
The normalization process "Marc21 Bib normalize on save" offers the option to sort subfields (tab "Task Parameters"). However, this has no effect on manually edited and saved data in MDE. Sorting can be triggered by the process from time to time for a dataset, but it does not run continuously. We had hoped to achieve sorting directly in MDE, which would allow operators to better…
30 votes -
Rialto marketplace Keywords Searching - not working
Rialto marketplace Keywords not working. When trying to "Manage Purchase Requests" and do "Search in market" the default Search by"Keywerds" is not working on works when you change to "Title", please have this fixed.
3 votes -
More flexibility in text fields within "Update PO Lines Information" job
While it's helpful to have the ability to update the "Note to vendor," "Activation note," "Renewal note," and "Internal note" fields in batch via the "Update PO Lines Information" job, the job only allows single-line text entry, so it's not possible to create line breaks/new paragraphs when performing a batch update. However, you can create line breaks/new paragraphs when updating these fields in individual PO lines. I would like this ability to be transferred to the "Update PO Lines Information" job so text with line breaks/new paragraphs can be added in batch to PO Lines.
5 votes -
Enable Printing of Borrow requests ("Print Slip")
There is no way to print a copy an outstanding Borrow request (that includes request citation information, patron info) from the Borrowing requests queue and this would be a very useful function to have. This could be like the Print Slip option available for requests in the Lending request queue.
43 votes
- Don't see your idea?