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.
152 results found
-
Incorporate All AI Metric Types/Access Method from recent 5.1.1 COUNTER Standard Update into Analytics
Counter Standards were recently updated to incorporate new metric types and new access methods for AI Bot Traffic within COUNTER standards (https://www.countermetrics.org/code-of-practice/best-practice/bp-ai/). Requesting that Ex Libris incorporate all metric types and the new access methods into analytics.
45 votes -
Add "Available for Group" record fields to Analytics
Currently, Analytics exposes which groups have Available for Group records, but it doesn't expose the other fields in those records.
For example, Analytics can show that a collection is available for Group A and Group F, and it can show that Electronic Collection Proxy Enabled is set to Yes at the collection level; however, it can't show whether proxy is enabled for Group A or Group F.
For Network Zones, and institutions that make extensive use of Available for Groups, the lack of access to these fields in Analytics means we can't periodically audit and correct configuration inconsistencies and data…
3 votes -
Add Analytics support to compare "Available for Group" settings on electronic collections and services
Currently, Analytics can show Available for Groups on the electronic service or, if none exist there (if they're inherited from the electronic collection), then on the electronic collection.
However, we can't report on discrepancies between collection-level and service-level groups.
3 votes -
Wildcard search for MMS ID.
When working in conjunction with Excel, pasting MMS ID will be limited by the floating point standard and truncate the the last 3 digits to '000'. Only just realised this, having wildcard search would allow me to at least more efficiently identify and retrieve the now corrupted MMS ID I've been pasting into Excel.
1 vote -
Allow faster 'All titles export' in UI by adding option to only download titles' MMS ID
We are grateful for 30 local parameters in Alma Analytics, but frankly could use way more (i.e. as many as the number of MARC fields that we use that are not already available in Analytics. For example '035' is available in Analytics via 'Network Number'). Sometimes to get Analytics to output what we need, we must run the search in Alma first. However, the 'All titles export' is intolerably slow for as few as 5K bib records. Possibly, if the Tech team thinks that 'All titles export' UI time could be shortened by adding an option to output/export only MMS…
12 votes -
Analytics Authorities Locals Deletes
We need an analytics report for deleted authorities in which we can determine the type of vocabulary it belongs to. We made an incident on the Alma support portal "10583316", and they gave us this explanation and suggest us to report a new idea:
"The Analytics behavior for authorities is that the vocabulary code is not displayed for deleted authority records. This is because the MMS ID is taken from the MMS record table, which preserves information on both live and deleted records, while the Vocabulary Code is taken from the authority heading table, which preserves information only on live…
1 vote -
Keep deleted Alma objects in Analytics
When I delete Alma objects such as PO lines, Purchase orders, course requests, invoices, purchase requests, they are deleted in Analytics as well. On the contrary, even if deleted in Alma, objects like bibliographic records or physical items are still accessible in Analytics.
It would be great if other Alma objects were also accessible in Analytics even if deleted.14 votes -
Separate 655 genre/form from Subjects in Analytics
Since Library of Congress are putting more emphasis on genre/form (MARC 655) and removing the $v Form subdivisions, it would be helpful to separate the 655 searching as genre/form from the broader Subjects field (600, 610, 611, 630, 650, 651 etc) in Alma Analytics. There is already a separate Genre search in Alma advanced search which is very useful.
9 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.
6 votes -
Alma Analytics: Cost per Use - calculate use on all platforms
When using Alma Analytics for cost per use reports, only use from the chosen COUNTER Platform are calculated. In part, this is because in Electronic Portfolio Editor, only one COUNTER Platform may be chosen. This is a problem for our Ovid Journal collections as Ovid records use across three platforms. We would like all use to be calculated in Alma Analytic Cost per Use reports, whether this be solved by allowing us to choose multiple platforms in Alma or have Alma Analytics calculate all use, not just the COUNTER Platform chosen in Alma.
34 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 -
Counting Searches in Alma Persistent Search Box
We know that the usage actions in Primo VE can be retrieved in Analytics to measure patrons’ various search actions. This helps library identify the strengths and limitations of current Primo VE user interface, and review it to better meet patrons’ needs.
However, there is currently NO way to retrieve search counts from Alma’s search persistent box in Analytics.
Counting Searches in Alma Persistent Search Box
Library staff often use the Alma persistent search box to search for records for various library operations—for example, locating a bibliographic record to create a PO line—across the institution and community zones (and the…
2 votes -
Add Resource Sharing partner address information to Alma Analytics
Information should include street, city, state, zip code, country, and latitude and longitude. This information is essential for creating reports showing where ILL items are coming from or going to. This would enable us to create reports showing how much borrowing and lending we do by regions, internationally, and make it possible to create maps that we can use to promote our services to patrons, library staff and university administration.
9 votes -
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…
5 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 -
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 -
Support linking Analytics Subject Areas Requests and Fulfillment
As analytics users, we would like to link request information to loan information in Analytics so that we can obtain a better picture of the entire end-to-end loan process for a patron, from request to loan.
For example, the Fulfillment subject area could contain fields such as:
- Loan is based on a prior request (True/False)
- Originating Request IDSimilarly, the Requests subject area could contain these fields:
- Request resulted in a loan (True/False)
- Resulting Loan ID7 votes -
Request expiration date in Analytics
We are trying to retrieve a list of items that are about to expire on our holdshelf but it looks like the Request Expiration Date is not available in the Requests subject area in Analytics. We were expecting it to be in the Request Details section.
Of course, the holdshelf is just a specific case, limited to patron physical item requests, but this idea can be extended to any other request type in which an expiration date is meaningful.
32 votes -
acquisition vendor analytics expansion: all URLs
We would like to see more complete vendor information in Analytics in general, however this specific request is for inclusion of all URL types, along with both their description and note fields.
The use case is that we are hindered from fully using all the fields within Alma when we cannot run reports on that information in order to back it up. The backup is necessary due to the lack of an "are you sure" popup for the Delete action. Also, administrative and statistics login information needs to be available to all acquisitions and e-resources staff, however it needs to…
20 votes -
Persistent User Group Data in Borrowing Requests Subject Area
We would like to request that the Borrowing Requests subject area in Analytics captures and stores the patron's information (specifically the User Group) at the time of the transaction, rather than pulling the current status from the user record.
Currently, historical reports on borrowing requests reflect the requester's present-day group. If a student who made a request three years ago is now a staff member, or if their record has been deleted, the historical data is either overwritten or lost. This makes the data entirely out of context and renders historical analysis and longitudinal reporting impossible.
In the Fulfillment subject…
62 votes
- Don't see your idea?