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
-
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 -
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.
27 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 -
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 -
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 -
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 -
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 -
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 -
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 -
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.
11 votes -
LUXURY RESIDENTIAL PROJECT IN GURGAON
Experience luxury living in Gurgaon with our exclusive luxury residential project. Located in India's fastest-growing urban landscape, this premium complex offers world-class amenities, spacious living areas, and stunning landscapes. With easy access to major highways, shopping malls, and top schools, this home is a sanctuary for relaxation and rejuvenation.call 7983028075 or 9711298311.
1 vote -
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 -
Add "Rule details", "Terms of use", and "Fulfillment Policy" as shared descriptive dimensions with Fulfillment subject area
We would find it very useful to be able to report on fulfillment activity as tied to configuration. For example, we'd like to be able to report on items that allow unlimited renewals versus items that allow renews but limit the time frame.
From what I can tell, only the loan length is included in the Fulfillment subject area, but the terms of use information is in the Configurations (Limited) subject area. But, we cannot do a multiple subject report without them being shared dimensions in Fulfillment. It would be very helpful if they could be added.
1 vote -
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 -
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 Campus Name as a Field in the Course Reserves Subject Area
Currently, the only location option in the Course Reserves subject area is "Campuses Name and Participants." This field is made up of "The campus description and the number participants per campus." "Campuses Name and Participants" is misleading in that it pulls the campus description field, rather than the campus name field.
We would prefer a field that contains only the campus name, without using the description or the number of participants.
3 votes -
Sort Option for Data Start Date or Data End Date in SUSHI Area/Vendor Details
It would be helpful to add a sort option for the 'Data Start Date and Data End Date" when analysing SUSHI reports that have been uploaded to the vendor details area/profile. When doing a custom harvest or uploading data it would make it so easy to see what date ranges have been uploaded and/or harvested. There is already sort functionality for the file name, uploaded date, SUSHI account and others, please see screen shot. I honestly think this is too important not to have been considered.
1 vote -
Improve event key data for System Events tracking
The data captured in System Events for code and mapping table changes could be useful for auditing purposes and tracking changes to administrative settings. However, the key value pair captures an internal code for the table rather than the name, and there is no way for Alma customers to retrieve the code, either from the Alma UI or the configuration API calls.
It would be much better to include the table name in the event log, or provide the table code in some fashion so that they could be linked together.
1 vote -
Add read-only parameter to Users > Role
In the Users subject area, you can report on roles, but not if a role is read-only. This means that reporting on who has administrator roles is very confusing and implies more access than may actually exist. That value needs to be added to this subject area.
4 votes -
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-an109 votes
- Don't see your idea?