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.
145 results found
-
Expand coverage of the 'single' ISBN and ISSN fields in the Analytics 'Titles' subject area
The fields 'ISBN Valid Single (Normalized)' and 'ISSN Valid Single (Normalized)' in the 'Titles' subject area are useful for matching purposes. However those fields only cover ISBNs/ISSNs from MARC bibliographic field 020a. Sometimes we're looking to match Alma records to sources which might use older identifiers, that appear instead in 020z, 776z, 022l, 022a and/or 776x respectively in the Alma records. Those MARC fields' contents are reportable in the general 'ISBN' and 'ISSN' Analytics fields, but those Analytics fields don't provide each identifier on its own row. Additional, expanded versions of the 'ISBN single' and 'ISSN single' fields (perhaps named…
4 votes -
Power BI access to Alma & Primo Analytics
Many libraries are using Power BI to analyse the suite of library services they offer. Data is derived from the library management system (LSM/ILS) but also chat services, reading list software, library guides and more.
Though Ex Libris has developed analytics in Alma, libraries need to analyse their data in the tools of choice.
Can Ex Libris open analytics so a direct connection to Power BI can be made without the need for intermediary workarounds, e.g., https://developers.exlibrisgroup.com/blog/microsoft-power-bi-connecting-to-alma-api/?
24 votes -
Subject headings's in Analytics
"Subjects" in analytics (6XX MARC fields) are all jumbled up in one index. This creates a problem for analysis of correctly applied LCSH subject headings (our focus). AND, 2nd indicator signifies the type of subject heading, such as LCSH "0"; NLM "2"; etc. Currently, working with the subject index, it is impossible to filter for the type of subject heading needed in an analytics report, even though the MARC variable fields contain this data. Therefore, it would be very useful to filter for the types of subject headings we would like to see in a report, without losing recall (i.e,…
2 votes -
Attachment presence and names in Analytics reports
We would like to use Alma to store vendor VPATs, and I'd like to be able to run a report that tells me which VPATs we have or do not have. I don't see any ability to add an Attachments (is empty/is not empty) in any analytics subject area, currently.
3 votes -
Enhance Analytics Support for Authority Records (Additional MARC Fields)
We would like to propose an enhancement to Alma Analytics for authority records.
Currently, Alma Analytics provides limited support for authority fields, such as 1XX and 373. However, many other important MARC authority fields are not available for reporting and analysis.
We recommend adding more authority fields to Analytics, including but not limited to:
046 – Special coded dates (commonly used for birth and death dates of authors)
372 – Field of activity
374 – Occupation
375 – GenderThese fields are widely used in authority records and are highly valuable for data analysis, authority control, and research purposes.
Providing…
1 vote -
Analytics Search Results - allow export or open in new tab
When using "Search" in Alma Analytics it would be useful to EITHER:
Be able to export the results of the Analytics Search into excel
OR
Be able to click on a search result and for the report to open in a new tab.Currently if you select a report from the search results it opens and you lose the search results page. If it is not the correct report then you have to start the search from scratch again and sometimes the search takes a while.
Having some way of exporting a record of the results - so you can…
24 votes -
Establish system to ensure complete coverage of LC classifications
Alma Analytics includes LC Classification code data, but frequently valid classification codes come up as "Unknown." Ex Libris currently has no reliable way of keeping up with changes in LC classification. They rely upon the "Library of Congress Classification Outline", which is not complete. They will add classifications upon customer request, though this process takes months or years and puts significant burden upon institutions. Ex Libris should develop a system to reliably update its LC classification coverage. This could take the form of e.g. establishing its own access to Classification Web, subscribing to LC updates, and/or setting up some alternative…
67 votes -
System Events Subject Area: Add "Record was Created", "Record was Updated", "Record was Deleted" for Holdings PIDs
Currently, the System Event subject area does not track the creation, update, or deletion of holdings records. Adding this functionality would provide valuable insight into how often these actions are performed by staff. This data would support performance reporting and make it also easier to identify the number of modified records when metadata corrections are needed.
2 votes -
Use same format for all dates in Analytics
When combining different subject areas (I use the button “Combine results based on union, intersection, and difference operations”, and I am using union) I find that it is not always possible to combine dates.
For example: The date "Event Start Date"."Event Start Time" from Physical Items Historical Events cannot be combined with "Loan Date"."Loan Date" from Fulfillment.
This is due to differences in date formats.
It's hard to predict which parts of Analytics a library would want to combine. So I suggest that the date formats be standardised across Analytics6 votes -
Overlap and Collection Analysis reports enhancement
As a collection development librarian, I propose allowing the selection of multiple collections we want to compare. Repeating the same process for different collections is time-consuming. For example, we have 8 active IEEE collections, and I have to match them one by one with other collections.
Also, is it possible to re-run the Overlap analysis report if I forget to include some collections, instead of creating a new analysis each time?29 votes -
Allow BOTH Analytics widgets and Data Visualisation workbooks on Alma homepage
I currently have a DV workbook on my Alma homepage. I recently wanted to add an Analytics Widget but was unable to.
I opened a case with ExLibris and was advised that it is not possible to have BOTH DV and a widget on your homepage and they suggested raising it as an ideas exchange.So I propose that it would be useful to be able to have BOTH Alma Analytics Widgets and DV Workbooks available to view together/at the same time on the Alma Homepage.
4 votes -
Create report in analytics for citations with no usage
It would helpful in the leganto student usage area of leganto to be able to generate a list of citations in a reading list with no engagement. Currently you can only report on citations with student usage.
5 votes -
Prevent the moving of Analytics reports to subfolders
We have identified an issue with Analytics reports being able to be moved, and some negative consequences of that.
One morning we noticed that our IZ shared reports folder is no longer in the shared folder. In spot checking our NZ and other IZs, this was the only one missing.
A member of our report groups reports that she is seeing that missing folder under her My Folder. When she tries to move it back it says Access Denied.
Essentially, the folder has the permissions for the Institution, so when it is cut/pasted/moved into a private folder, it is allowed.…
1 vote -
Enable reporting and filtering in Alma Analytics based on specific MARC indicator values by exposing them as separate, filterable fields
Please consider enhancing Alma Analytics to:
• Include MARC indicators as separate, filterable fields in the data model.
• Allow reporting and filtering based on specific indicator values for any MARC tag.
This would greatly improve our ability to manage bibliographic data quality and streamline workflows that depend on precise MARC structure.5 votes -
Display statistics note labels in Analytics
Controlling item statistics notes is optional in Alma. We have controlled our statistics notes and would like to have the option of displaying the more human-readable descriptions in Analytics reports rather than the raw codes. This is how for instance statistical categories work in Analytics--you can display the code or the description. Institutions that have not controlled statistics notes could have null descriptions, or the description could be the code.
3 votes -
Analytics : Add Website URL to Users subject area
On a user record there is a field called "Website URL" however this isn't included in Analytics.
It would be useful to have this as it would save the need to put URLs into other less appropriate fields just to get the data on an analytics report.
1 vote -
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.
41 votes -
Add Primary ID to Creators and Modifiers of Analytics Reports
Currently, Analytics displays only the Created Date and Modified Date for reports, without showing which user performed these actions. This makes it difficult to identify ownership or responsibility for a report, and complicates collaboration among staff.
I propose adding the Primary ID of the user who created a report and of the user who last modified it. This would:
1.Improve accountability and change tracking.
2.Make it easier to follow up with colleagues about report logic or updates.
3.Align Analytics with other Alma areas where user IDs are already visible in audit trails.
Adding this information would strengthen report governance and…
2 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.
40 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.
44 votes
- Don't see your idea?