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.
138 results found
-
Enhance the comprehensiveness of Analytics of usage analysis
For some vendors, it may have sub-databases in the subscriptions and collect usage for a particular database and the titles within seems not possible currently by Analytics. Though there’s a “Platform” field in Analytics, it did not separate the figures between different databases for a single vendor. It's strongly recommended to enhance the comprehensiveness of Analytics and enhance the functionality of usage analysis.
21 votes -
Choose start month in Alma Analytics schedule
Alma Analytics has been improved by a lot in ways of scheduling reports. But I am still missing a way to choose a start month when scheduling a quarterly or bimonthly report.
You can choose a recurrence pattern (eg. monthly, recur every nth month), but there is no way to choose a month for the next run. Each change in recipients or touching the analytics object may start a new interval.
When choosing a weekly interval, you can also choose a weekday. An option for choosing a month should be added for monthly schedules.
8 votes -
Overlap Analysis reports
These reports would and should utilize and contain within them subject headings and subject areas. It seems like it would be a very useful functionality for staff to make use of subject headings for comparison to other vendors' reports who use subject headings/terms while doing an overlap analysis. When trying to compare CZ electronic collections to our IZ collections, it would be good to know which subject coverage area and date range each matched portfolio has.
2 votes -
Different colour in left menu for shared dimensions
It would be nice to find shared dimensions in left menu in a different colour, not the same blue.
This way, it would be eassier to recognized and use them.3 votes -
Different color en left menu for shared dimensions
It would be nice to find shared dimensions in left menu in a different color, not the same blue.
This way, it would be eassier to recognized and use them.3 votes -
Add "Field searched" Column in "Primo Popular Searches" Analytics
"Field searched" is an attribute field that stores the field being searched. This is relevant if the user performed a search on a specific field (such as authors only). But now we can only use this function in the "Zero Result Searches". We would like to use this function in the "Primo Popular Searches", so that we could do more users behavior analysis.
1 vote -
Identify subscription databases in Alma analytics
It is possible to identify subscription collections in Alma analytics by marking the service editor: Free=Not free. However, databases do not have service editor. We do mark it in the collection editor as Free=not free.
In Alma analytics, there is no way to identify subscription databases. My case was closed with the support directing me to suggest an idea here.
Please add elements in Alma analytics so we can use to identify subscription databases.
1 vote -
Analytics widget - customize/remove Open in a new window link
I'd like to be able to remove or customize the "Open in a new window" link that appears on top of a widget of an analytics report.
The widget can only fit a very short report. Opening this short report in full view is not that useful. It would be better to link to a longer report or a dashboard.
1 vote -
Remove MARC Relator terms ($e) from Author and Author (Contributor) fields (1XX/7XX) in Analytics
The Author and Author (Contributor) fields in Bibliographic Details in Alma Analytics are mapped from several subfields in MARC fields 100/110/111 and 700/710/711, respectively, including subfield e. But subfield e should not be included in the Author and Author (Contributor) mapping because it is not part of the author name. It is instead a separate element that denotes the relationship between the named author/contributor and the work, the Relator. Thus the $e value may vary or be absent from records although the author/contributor is the same, making it impossible to search upon, identify, and unite author/contributor names in Analytics. Any…
28 votes -
Add SUSHI “Status Description” field for uploaded files as column option in Analytics
Ex Libris has said “No valid report items found in the file” is behavior that should still be listed as a “Fully Processed” file, but it would be helpful if we could more easily find files that we believe may not have loaded properly based on their Alma “Status Description” in Analytics.
1 vote -
Primo measure for number of Quick Link titles
Role: for deep analytics user and system administrator.
Proposed feature: Create a Primo measure in Analytics for the number of titles with a Quick Link, denote either PDF or HTML and also allow for method of purchase: OA, purchased or subscribed. It would be helpful to exclude any quick link generated from Unpaywall or create a separate measure if necessary.
Feature’s benefit:This would enable more indepth analysis of quick link usage. While the link usage is available in Primo Analytics as a click report, this number is less meaningful without having the number of titles with a quick link. Having…
3 votes -
serial type
Be able to lookup bibliographic titles by serial type (Fixed field 21 SrTp: Type of continuing resource), especially for monographic series type m. Our serials desk wants a way to easily find these so when they receive materials they can separate the standing orders from the subscriptions. They could also generate reports from the data parsed in Analytics to assist their students during the receiving process.
1 vote -
Index MARC field 440 contents to Series or Series statement in Bibliographic details of Design analytics
Series titles entered to MARC field 440 currently cannot be retrieved using Design analytics. Many old bib records carry series titles in field 440. Thank you for your consideration!
2 votes -
Track data on what in a record was modified, and add that data to analytics.
We run a couple reports that look at when a record was last modified. But there are many reasons why a record might be marked as "modified". It would be great if we could create filters on what in the record was modified, such as item status, location change, barcode change, note added, etc. This could allow for things such as running reports on what items had their fulfillment note last modified after "X" date.
9 votes -
Adding 'Normalized Item Call Number' field to analytics, similar to existing 'Normalized call number' field
We would like to have 'Normalized Item Call Number', derived from 'Item Call Number', in analytics. This field is similar to 'Normalised Call Number' derived from holdings 'Call number'
4 votes -
Finding the data in the Old Value field in Analytics
I would like to have the ability to pull up item records when supplying certain words/numbers in the old value field in Analytics.
3 votes -
Add a timestamp to 'modification date' for physical items and holdings in Physical Items area.
The timestamp and date of 'delete date' for physical items/holdings can only be found in "Manage Deleted Repository' in Alma.
It is good to have the timestamp appeared at the field 'modification date' of physical items/holdings in Analytics. It is particularly helpful when getting records of deleted items/holdings for weeding report.
2 votes -
Add "Loans (Not in House) From Resource Sharing Lending Request" measure
Currently in the Fulfillment subject area in Analytics, there is a measure for "Loans (Not in House) From Resource Sharing Borrowing Request". It would be helpful if any item loaned from our collection to another institution as part of a RS lending request have a loan measure applied to it as well so we can see how the collection is being used using just one report.
9 votes -
Add Financial System Code to the Vendor Dimension of Alma Analytics in the Funds Expenditure SA
The Financial System Code field is often the matchpoint between Alma and external payments systems. Being able to search or query on this would help avoid creating duplicate vendors, especially as vendor names can change so much over time, that a vendor name search will not return results. Having this reportable in Alma Analytics would be more beneficial than in the Alma Advanced Search, as it could also help to de-duplicate existing instances of having more than one vendor record for the same vendor.
25 votes -
Harvest and add Unique item requests to analytics IR_M1 usage reports
The IR_M1 usage reports come with the metrics: Unique item requests and Total item requests. Currently, Alma only harvests Total item requests, and leave out Unique item requests. So, in Alma analytics, we cannot retrieve the unique item requests statistics, which is more important than Total item requests.
0 votes
- Don't see your idea?