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.
1760 results found
-
Add shortcut to viewing item history
Many of our staff have trouble remembering how to access an item's history in Alma. It would be nice if a shortcut to that information could be added. I imagine something like an extra tab on the Scan In Items page called Item History - it allows you to enter a barcode and quickly pull up all the info in the Item Changes, Holding Changes, and Fulfillment activities tables but without having to first enter the Physical Item Editor.
10 votes -
Facet for PO Lines Secondary & Tertiary Reporting Codes
We'd really like the ability to facet in PO Lines by the Secondary & Tertiary Reporting Code fields. It's possible to facet by the main Reporting Code but not by the other two reporting codes.
10 votes -
Create a widget from a set
It would be very useful to add the ability to create a widget based on the results of a logic set.
10 votes -
Expand Course Reserves Facet/Advanced Search Functionality
When working in Reading Lists and Courses the facet filtering limits staff to a single selection in a category at time. However, many institutions have multiple terms or staff liaisons serving more than one academic department. In such cases, it would be quite helpful to allow staff to select multiple facets. The inability to multi-select prevents staff and their managers from being able view the whole picture and effectively managing the work.
If that’s not possible, we’d like to request that you expand the advanced search options for reading lists, courses, and citations to make all of the facet options…
10 votes -
Make headings and descriptions editable for PO Lines without Inventory
It is possible to create a PO Line without inventory by using the "Order without Inventory" option in the Acquisitions area of Alma. When creating such an order, Order Heading, Alternative Heading, and Description are all required fields. However, these fields are not editable after the order is created, so if you make a typo or there is a change to the name of a service (or whatever it is you are ordering), it is not possible to update that information in the heading. Ex Libris should make these fields editable after the order is created.
10 votes -
Ability to assign fulfillment proxy to existing users
We recently tested the fulfillment proxy feature as we have a few departmental workflows we have been using shared internal accounts for. We find the functionality to be the inverse of what we would like to see. For example, we have about 10 users who place RS requests for the law review. We would like to add the fulfillment proxy to these existing user rather than making them new internal accounts.
10 votes -
SUSHI harvesting for JSTOR
I noticed that our SUSHI harvesting for JSTOR hadn't worked successfully since May 2023. The requests for reports were coming back with this message:
{"Code": 1011, "Severity": "Warning", "Message": "Report Queued for Processing", "Help_URL": "https://support.jstor.org/hc/en-us/articles/360015483214-SUSHI-reports-COUNTER-5-overview", "Data": "Successful request. You must re-request this report to receive data. Please allow 1 hour for processing before retrying."}
So I reviewed the information here:
https://support.jstor.org/hc/en-us/articles/360015483214-SUSHI-reports-COUNTER-5-overviewThis page makes it clear that this is expected behaviour.
I ran a custom harvest for June-Sept 2023 and it failed (as expected).
I ran a second custom harvest an hour later and it succeeded.I'm not…
10 votes -
Add Option to Toggle User Record Type
Add a simple toggle option for a user record to easily switch Record Types between Staff and Public. While there are more complicated ways to deal with it, if a user record is accidentally created and assigned the wrong Record Type there is no easy mechanism to change it, like we can when toggling an account between Internal and External.
10 votes -
'Notes' field in User Group configuration - note field for each user group in the user group table
I know there is a tab for notes in user group configuration (Fulfilment>Patron Configurations>User Groups) but it would be more useful if there was a way of adding a note to each user group in the table, so it would appear as a column in the table next to Description. Then we could add what that user group includes, or how they are defined.
Thanks very much,
Ruth10 votes -
Enable 'School' address to be used for Personal Delivery
Currently, only addresses of the 'Home' and 'Office' Address Types can be used for Personal Delivery. Consequently, we can't use Personal Delivery and have to rely on a local workaround instead.
We would like to see 'School' addresses usable for Personal Delivery, with options in the Request Terms of Use to enable us to show only the Address Types that we use and therefore that we want our users to be able to see. E.g. we use 'Home' and 'School' but not 'Office', so we don't want our users to be able to choose that option.
Also, when the request…
10 votes -
Add Option to Handle Multi-Matches Automatically Based on Brief Level
Alma’s import profile functionality currently includes the option "Do not override/merge a record with lower brief version", which ensures that an incoming record is not loaded if its brief level is lower than that of the matched record in Alma.
We would like to see this functionality extended to enable handling multi-matches automatically. Currently, when an incoming record matches multiple existing records in Alma, the import process still flags this as an multi-match issue, even if all matched records in Alma have a higher brief level than the incoming record. These cases must then be reviewed and resolved manually by…
10 votes -
Export electronic portfolios to one file regardless of electronic collection
Per the documentation at the link below, when using the Export Electronic Portfolios job, "each collection is written to a separate file ... even if you select the One File option". We would like the option to export to one file regardless of collection. This would support better integration between Alma and other systems by allowing libraries to more easily provide complete data on electronic holdings.
It is possible to use publishing profiles to publish electronic holdings in the form of MARC or XML, but these formats are not as easily processed by 3rd party vendors. It is also possible…
10 votes -
Allow for relative date searching on years in addition to days
We have logical managed sets where we want to filter on publication year within the last two years and would like to be able to use a relative date search instead of having to adjust the year each year.
10 votes -
Collection-level authentication method options for CDI Link in Record links
Please provide an option to configure the authentication method applied to CDI Link in record links at the collection level. As it stands, we are able to set a preference at the institution level that is applied to all CDI collections. Our selection to apply the default proxy (in our case, the OpenAthens redirector) is not appropriate for some collections and cannot be overridden. This is especially important as more providers move to federated authentication.
Ex Libris has configured exceptions for ProQuest legacy collections upon request, but not for other providers.
Mintel is a good example. When the OpenAthens redirector…10 votes -
ensure that when 'po_line_description_update_upon_bib_change' enabled, subfield A does not get overwritten by subfield L in 022
Sharing description from our Cataloger, CH:
We believe the following describes a defect.
Support indicates it is an enhancement request and suggests we propose on Idea Exchange.
Background:
1) We turned on the ‘polinedescriptionupdateuponbibchange’ enhancement in the sandbox.
2) The enhancement overwrote the $$l instead of pulling in the $$a from 022 – this behavior describes a defect
None of the following 3 options allow us to properly use the ‘polinedescriptionupdateuponbibchange’ enhancement:
1. Ideally, we want to enable the ‘polinedescriptionupdateuponbibchange’ function to…10 votes -
Request to Enhance the Purchase Requests API
We would like to request several enhancements to the Purchase Requests API.
First, when sending a purchase request API call from the library website to Alma, we would like the API to allow submission of the request date or request month and to return responses that reflect this information.
Second, the Purchase Requests API currently returns a maximum of 100 records. We request that these returned records be sorted in descending order by request date.
Finally, we would like the maximum number of records returned by the Purchase Requests API to be increased from 100 to 500.
10 votes -
Bulk update block expiry date
In January 2018, fulfillment enhancement was added to allow library staff to manually add a block expiry date and edit the expiration date on an existing block. (See https://knowledge.exlibrisgroup.com/Alma/Release_Notes/010_2018/12_January_2018/Alma_January_2018_Release_Notes/04Fulfillment_-_January_2018_Enhancements)
We would really like to have the option to input a block expiry date in the bulk update/notify users job when adding a block type, instead of manually adding the blocks with expiry date one at a time for a batch of library user records.
10 votes -
Relationship designators should not be searched in Field 5XX, subfield $a
In Authorities, when relationship designators are used to specify relationships between agents in field 5XX, with subfield $i (relationship information), Alma searchs the relationship designators included in $i instead of searching the agent name included in subfield $a (personal names; corporate names, etc.). The subfield $i is not part of the name of the author or contributor, it is a separate element that denotes a relationship between agents. It is for this reason that we propose that names be indexed by the name included in subfield $a instead of subfield $i.
10 votes -
Sort Routine for one-time receive items on “Receive” interface
Same problem to "Sort Routine for ordered items in PO Line" idea posted at https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/51154792-sort-routine-for-ordered-items-in-po-line , I would like for your support to the sort routine for one-time received items.
There is no sort routine for one-time received items. For receiving more than 100 items in a PO Line, we must input the barcode one item by one item (because the auto-generation of barcode cannot apply “Mod 10-Option 1” for the 14th digit as the check digit of the barcodes our library). No sorting of the one-time received items make us spend long time for locating the correct location and…
10 votes -
Sort Routine for ordered items in PO Line
I wish to get support from all Acquisition Librarians who visit this idea.
My library has to order more than 100 copies for different locations for certain titles. During creation of these PO Lines, the sorting of Ordered Items is in chaos after pressing the “Save” button. The sorting is not following the input sequence, or by alphabetical order. My acquisition colleagues, therefore, cannot double check the ordered items in sequence. Contacted Supports Team, it is confirmed that the sort routine functionality for Order Items is not currently supported in the system, and suggest me to post here for your…
10 votes
- Don't see your idea?