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.
184 results found
-
Create option to keep CZUTL deleted portfolios active in Institution Zone
When portfolios are deleted from a non-auto-active electionic collection and notifications for this appear in the Community Zone Updates Task List, the portfolios stay unlinked in your institution zone but are deactivated. Often these are portfolios that represent access that still exists for the institution and we merely reactivate the local portfolio. We would like to be able to select an option to keep these portfolios active in our institution zone. If they are really no longer necessary, we can delete them when we review the CZUTL, but it would save us time if the portfolios were not deactivated automatically.
7 votes -
Move set of Portfolios from CZ to Local collection-URL type
When moving a set of portfolios from a CZ collection to a locally made collection, ask and allow for the portfolio URL type to be changed and accurately reflect the change. For example, if the portfolios URL structure is set at Parser parameters in the CZ, and the local collection uses static URLs, change the portfolios to static (binary checkbox) and update the free text URL field to reflect the static URL. (By moving a set of portfolios from a CZ to a local collection, the resulting URLs still using parser parameters won't work, and the export URLs job won't…
7 votes -
Make "Available To Date" actions customizable so portfolio can be automatically deleted after "Available To Date"
The "Control the Availability of Portfolios Automatically at a Pre-defined Date" feature, introduced in the February 2023 release (https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2023/Alma_2023_Release_Notes?mon=202302BASE), allows libraries to enter an Available From Date and Available To Date in portfolios, and the portfolio will be automatically deactivated after the Available To Date. This feature is designed to be useful in cases where libraries lease a piece of content (typically, a streaming film) for a limited period of time.
However, after a portfolio has reached its "Available To Date," we don't just want to deactivate it; we want to delete it entirely from Alma (and its…
7 votes -
When CZ update "Portfolio bibliographic record updated" runs, if POL is attached to portfolio & bib, automatically move POL to new bib
When we order a portfolio, the PO Line attaches to both the portfolio and the bibliographic record attached to the portfolio (this is good; it's how Alma works by design). Every week, there are numerous "Portfolio bibliographic record updated" tasks on the CZ Updates Task List. This means that the portfolio has moved to a different bib record. When "Portfolio bibliographic record updated" happens, the portfolio moves to a new bib. The POL remains attached to the portfolio (which is good!). However, the POL is not moved to the new bib record; it remains attached to the old bib record.…
7 votes -
Record all changes to an Electronic Collection in the History tab, by user or System and the change made
All changes to be recorded in the Electronic Collection History tab, including the user account or System making the change and what was changed.
Currently there are many "System" changes only recording the Modification Date by Old Value of the previous last change and the New Value of the date of change.
But there is no information as to what was changed.
I am not going to provide examples of what should be changed and risk only those changed being done, as simply everything should be recorded. This is the purpose of a History log.
Currently Ex Libris expects customers…
7 votes -
Add CDI articles to (digital) collections
We'd like to be able to add individual articles to (digital) collections, as there are often articles which are relevant to the collection topic, but currently cannot be included, as only items with bib records in Alma can be added to collections.
6 votes -
Restrictions on access to electronic documentation on a user group basis
Restrictions on access to electronic documentation can only be made in Alma on a library or campus basis.
It would be desirable to be able to do this on a user group basis as well.
6 votes -
Add Oregon State University OER textbooks collection
Is it possible to add the OER ebook collection from Oregon State University to the Community Zone? They're located at: https://open.oregonstate.education
6 votes -
Display service temporarily unavailable message, add time option
Is it possible to add the time when the collection will be unavailable? For example, we received notice that the ASTM would be unavailable February 23rd, 7:00 p.m. to February 24th, 2:00 a.m. If I set up the Display Service Temp unavailable message for the 23rd and 24th, the collection would be made unavailable when we still have access. Adding a time option to the date would be helpful.
6 votes -
Ability to relink multiple portfolios to another bib instead of one at a time
I'd like to have the option to relink multiple portfolios from one bib record to another instead of one at a time. This happens when I want to use a different bib record than the one in the CZ.
6 votes -
Allow coverage comparison from uploaded files in Collection overlap analysis
When we upload a collection title list with coverage for collection overlap analysis, Alma doesn’t compare coverage. For comparing journals, this is fatal. A title match with no coverage overlap means nothing. We understand that the coverage column in the vendor’s file can be messy and non-standard. We would rather standardize and format the coverage in the EXCEL file and let Alma do the coverage comparison, than to eyeball the coverage of 15,000 titles or more.
Tell us the correct format to indicate coverage, and let us extract the values for the beginning year, ending year and embargo columns, so…
6 votes -
Mechanism to find instances when Synchronize from CZ has failed
When you've activated a CZ collection, updates to the collection/portfolios should be pushed to your IZ/NZ by the Synchronize from CZ job, but it's a known issue that sometimes this doesn't happen. The workaround is to delete and re-activate the collection, but this relies on an end user finding and reporting the error. Until this systemic issue is resolved, it would be good if Alma would report on instances where the job has failed so the library could proactively find and fix collection/portfolio-level issues before end users discover them.
6 votes -
Display only one of each resource recommender type
Currenlty the default is two of the first listed Type listed in Resource Recommender displays in PrimoVE. Would like to change it so that just one of each type of Resource Recommender displays to diversify results patron sees on page.
6 votes -
Add a Delete button for portfolios in the Community Zone Updates Task List
Could a "Delete" button be added to the set of available options when reviewing portfolios in the CZ Updates Task List? There are options to Test Access and Edit the portfolio, but in order to delete a portfolio you must leave the list and do a separate search. It would be much more efficient if there was an option to delete from within the list.
5 votes -
Add support for importing .mrk files
At the moment Alma only supports importation of resources as .mrc files. These files are trickier to work with than .mrk and add a lot of unnecessary time to our import workflows (converting back and forth, "saving as" frequently, losing changes - especially for large imports).
5 votes -
Disable Electronic Activation Tasklist
It would be helpful to have the option to disable/enable the electronic activation tasklist. Whether or not the tasklist is incorporated into local workflows, the tasklist continues to grow with resources as they are ordered from the community zone. This leads to a very bloated tasklist with no clean way to clear items from the tasklist (i.e. resources that have already been ordered and received/activated remain on this list).
In a case with ExL (06794492) it was confirmed that items from the tasklist cannot be cleared in batch and each resource needs to be manually deleted.
By disabling the tasklist,…
5 votes -
Automatic Upload of Electronic Holdings (Autoholdings integration) - American Mathematical Society (AMS)
Implement Upload Electronic Holdings (Autoholdings) integration for American Mathematical Society (AMS), as is already available for ProQuest, Elsevier, Ovid, Springer, Project MUSE, JSTOR
5 votes -
Saving Queries on the Community Zone
Please, let us save queries on the Community Zone as a logical set.
It is well understood that no one but Ex Libris is supposed to be able to run jobs on the CZ data and most likely that is why you currently cannot save a query on the Community Zone as a set. However, saving queries can often serve as just a shortcut for submitting a (more complex) query again and again, and for electronic resource librarians it is interesting to check the CZ regularly for newly added collections which are freely available, e.g., or adhere to any other…
4 votes -
Bulk add perpetual access dates
We would like to be able to add perpetual access dates in bulk to individual portfolios. This functionality would be helpful for tracking perpetual access on packages/bundles where a large number of portfolios share a common start and/or end date.
4 votes -
Include submitter name with Report to Ex Libris form
Any Alma user who can access the action menu of a portfolio or electronic collection can submit the Report to Ex Libris form, but the Salesforce case is opened with the CRM contact chosen on the form. Unless the submitter includes their own name in the form's description field, it becomes impossible for the CRM contact to determine who opened the Salesforce ticket.
Please include the name or primary ID of the logged-in Alma user in the Salesforce ticket. This will facilitate follow-up with the staff member who reported the issue.
4 votes
- Don't see your idea?