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.
135 results found
-
Add "General Notes" at the collection, service, and portfolio levels to Analytics
Please add the following note fields to Analytics:
Electronic Collection:
- General notes (multiple entries)
Electronic Service:
- General notes (multiple entries)
Electronic Portfolio:
- General notes (multiple entries)Why is this necessary?
You can search for many fields in Alma itself, but not all of note fields can be exported from Alma. But this is particularly important for note fields!Thank you very much in advance!
Note: this is a follow-up idea to:
Add "General Notes" at the collection, service, and portfolio levels as indexable/searchable fields
https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/46387843-add-general-notes-at-the-collection-service-an105 votes -
Ability to surface details of recipients/subscribers to Scheduled Analytics Reports
Allow for export/inclusion of subscriber details when exporting list of scheduled reports or creating Analytics reports from Analytics Usage Tracking subject area or Analytics Objects subject area.
I am trying to do an audit on recipients/subscribers of our Scheduled Reports in Alma. The aim is to streamline who receives which reports/ remove staff who have moved roles and/or staff who have left the institution.
Currently neither the extract of Analytics Objects from Alma or any of the Analytics Subject Areas include details about the recipients/subscribers and I feel this would be very useful for auditing/access control.
37 votes -
Add Alternative Title to Alma Analytics
Adding the Alternative Title for an electronic collection would allow us fully use Alma Analytics and not need to maintain separate reports that are created outside of Alma. As a consortium, this would also allow more information sharing with our members and more efficient troubleshooting and maintenance.
23 votes -
Include more than 30 or an unlimited number of local parameters in Alma Analytics
We find Analytics to be very powerful, but we are hampered by its limitation to only selected MARC and a limit of 30 local parameters.
We hope ExLibris will include more or an unlimited number of local parameters in the future.
When we signed up for Alma, our team expected all MARC bib codes would be available in Analytics and they are not. In addition, we have defined several local fields and must assign them a local parameter to be able to output them in Analytics. We have been rationing the 30-alloted local parameters ever since.
17 votes -
Add "Vendor invoice number" to PO Line dimension in Analytics
Please add the "Vendor invoice number" from the Vendor Information section of the PO Line screen to analytics. It should be specifically added to the PO Line dimension.
This field is necessary for quickly reporting on POLs that have this information stored at the POL level, but are not attached to an invoice. Workarounds include manually looking up the PO, then searching Analytics, but we shouldn't require staff to search Alma if they could directly query Analytics with an invoice number from a PDF or an email.
13 votes -
Alma - Analytics - Users - Add field 'Has password' true/false
Sometimes users may have no password set. For example, in our system we have some internally managed users left with no password when Alma switched to external IDP. Filtering them in Analytics would be useful, but currently there is no way to do so.
Please add Add field 'Has password' true/false in Alma Analytics Users dimension.
15 votes -
Allow option to only send scheduled report from Analytics object if report has results
We want to set up reports to help us monitor for data inconsistencies and other issues that need addressing. We have noticed that we can set up reports as analytics objects and users can subscribe to them, but the report is sent even if there are no results.
We should have the option to not send empty reports, and only send if the report brought back one or more records.
7 votes -
Add Vendor Type to Analytics
We would like to pull a report that lists vendors by type in analytics. Ex. Access provider, material supplier. This is not currently in analytics. This is a filter in the vendor module in Alma, but we want to pull more complex reports in analytics, such as all vendors listed as a material supplier only that are missing a financial code.
Thanks!0 votes -
Combining "Request Type", "Work Order Type" & "Process Type" in a single analytics report
We'd like to retrieve a full list (with breakdown of all Work Order Type, including withdrawn, display, missing, not for circulation items…etc) of physical records by Material Type, Word Order Type & Process Type via Analytics. However, only part of records can be retrieved currently after combining Process Type & Work Order Type together. After consulting Salesforce, it is confirmed Analytics do not support to combine these fields together in a single report. It's crucial to enable combining these fields in a report as library always need to review the figures of each Work Order Type & Process Type, not…
19 votes -
Please add 3xx field support in Bibliographic Details dimension of Alma Analytics
Currently there are many fields in the 3xx range which are not supported OTB in the Bibliographic Details dimension of Alma Analytics.
We have mapped 300 to a Local Param several years ago, but we are stymied in our work updating to RDA consistently as the desired foundation for then considering LOD work in BIBFRAME, given this is a key area with many 3xx fields utilised such as 334, 335, 336, 337, 338, 340, 344, 345, 346, 347, 380 and 382.
Although the number of Local Params increased in 2024 finally from 10 to 30 we use many of these…4 votes -
Remove library and locations from Analytics created in test period
During migration to Alma we found that there were some incorrect data in holdings records for libraries and locations. This was useful because those data were not exposed to metadata managers in our previous system. Prior to migration, these incorrect libraries and locations were removed from our data in the previous system.
Now I find that those incorrect libraries and locations remain in Analytics. In order to filter these incorrect data out, one needs to remember to filter them out. This is not a long-term tenable solution as fewer and fewer staff members recall the specifics of the data cleanup…
3 votes -
Add Bursar Transaction ID dimension to Fines and Fees Subject Area in Analytics
Bursar Transaction ID is a critical data element when an institution uses a Bursar integration profile to export fines/fees and import payments. We recently implemented this integration and are looking at ways to reconcile Alma transactions with data extracted from our bursar. If Bursar Transaction ID were present as a dimension in Analytics, this would be much easier. It should be added.
18 votes -
Ability to report on the source of a MARC record
It would be useful to be able to report on the source of a MARC record in Alma Analytics. This should be part of the 'Titles' Subject Area, providing information on whether the record was created using a record from a Z39.50 query or via a scheduled or manual import job.
If the record is imported via a Z39.50 query, the source bibliographic knowledgebase should be reportable (e.g. OCLC WorldCat, Jisc Library Hub etc.).
If the record was created via an import job, the name of the import profile should be reportable.
This would help libraries to better maintain statistics…
3 votes -
Analytics recover the fields in the original configuration language in ALMA
ALMA is configured for Spanish-speaking countries in Spanish, so Analytics reports are required to generate data in the same language in which the original fields are configured.
3 votes -
Addition of the Accrued fines field in the Fines and Fees subject area in Alma Analytics
It would be great if there was an option in Alma Analytics to create a report with a list of people with a specific amount of accured fines if they had returned overdue documents on a given day (the day before actually).
19 votes -
Add information regarding level URL clickthroughs to Analytics
Currently only clickthrough for portfolios are being captured in Analytics. It would be great if level URL clickthrough's in Electronic Collection could also be captured.
3 votes -
Analytics: Add the country to subject Area digital usage details
The country of download and the organization are key information about the digital usage details as they add value and context to the statistics. This information is very important to our institution. Would it be possible to add the country, country code and organization to the digital usage details the same way as in Esploro subject area Asset usage details
17 votes -
Have AFN/FN loan/fine information available in IZ
Similar idea to https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/44761048-user-purge-should-be-made-afn-aware-and-not-allow
BUT there should be information in the IZ analytics so that an IZ can determine if a local patron has an AFN (or FN) loan or fine.
This doesn't need to be the full loan/fine information, but could be as simple as a flag that says "active AFN/FN loan", "active AFN/FN fine".
At this time, there is no way in the IZ (without opening each patron account within Alma) to see if someone has an active loan or fine outside of the IZ.
This is required at a number of our institutions for when patrons leave…
10 votes -
Analytics re-fresh (ETL) time should be reevaluated
I understand that an ETL is run at the same time for all the institutions in a specific data center. Institutions in a specific data center should be from a similar geographic area. If that is not possible, the servers should be grouped by geographic regions spanning approximately 3-4 hours time differences.
The time of the ETL run should be optimized across clients in the given geographical area. For example, if the clients are largely from the United States, the ETL could run close to midnight Eastern, which would be close to 9 PM Pacific.
1 vote -
Ability to report on inventory for citations
We would like to analyse print and electronic inventory for citations for a single or multiple reading lists. We're interested to look at reading lists with high or low print/electronic inventory so that we could engage with reading list owners e.g. for lists with high amounts of print we may want to look at the addition of e-book versions of the titles.
Currently it is not possible to report on print and electronic inventory for citations due to the fact that the 'locate' process links the citation to a particular bibliographic record and it's consequently not possible to connect from…22 votes
- Don't see your idea?