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.
116 results found
-
RS borrowing request cancellation reason to be available in Analytics
When cancelling a Borrowing Request in Alma using the Change Status option in the Borrowing Request screen, there is the option to specify a Cancellation Reason. We would like the Cancellation Reason selected in the drop-down menu of the Request Cancellation box to be available in Analytics.
This would enable us to analyse reasons for the cancellation of borrowing requests by library staff and potentially identify opportunities for requester education. For example, if ‘copyright issue’ or ‘item already available’ are most frequently selected as the reason for borrowing request cancellation.
8 votes -
Add all fields from Invoice Payment Information area to Analytics
Currently the only field from the Invoice Payment Information area that is available in the Funds Expenditure subject area is Payment Status. I would like to be able to retrieve Payment Date, Payment Identifier, and Payment Amount in Analytics as well. These would be helpful for some of my reporting, especially when the payment amount is different from the invoice total because accounts payable has added or removed tax.
12 votes -
Create a single field in Analytics to identify Open Access resources
If I want to create a report for all of our activated OA resources, I have to use fields such as CDI Search Rights, CDI Full Text Rights, Service is Free etc. to capture all possible candidates and manually remove resources that are not really OA. It would be helpful to have a field that reliably identifies OA resources.
3 votes -
Filtering a report based on a user set
Right now if you want to filter a report on a user set...
- Run a search in Alma and save to a set
- Export the list, using Excel.
- Manipulate the needed field (e.g. of barcodes), to be stored in one row, with semicolon separating them (e.g. 365704-340;365704-350).
- Copy this list as a row to be used as a filter in Analytics
I would like Alma smart enough, when I click on filter to simply supply the user set I created.
2 votes -
Using Oracle Analytics Publisher to customize the notification letters
Oracle Analytics Publisher is the reporting solution to author, manage, and deliver all your reports and documents easier and faster than traditional reporting tools. Use your web browser or familiar desktop tools to create everything from pixel-perfect customer-facing documents to interactive management reports against practically any data source. We need to connect the desktop client to the Ama Analytics server to customize the look and feel of notification letters to our students and staff.
3 votes -
Addition of DOIs and Proprietary Identifiers as Title Identifiers to Analytics Criteria
In Analytics within the Subject Area "Usage Date" the "Book DOI" (Counter R4 Reports) or "DOI" (Counter R5 Reports) are not selectable as Title Identifiers.
The same is true for "Proprietary Identifier" (Counter R4) or "Proprietary_ID" (Counter R5).
Since this information is sometimes listed in the corresponding columns of the COUNTER Book reports, it would be helpful if this information could also be retrieved in Analytics.
9 votes -
Make Provider Account ID info available to users as an Analytics option
Need Provider Account ID in order to use the Resources report called 'My Electronic Resources by Provider' to get electronic resources counts on all providers not just the ProQuest default.
1 vote -
bibliographic MARC analytics
I've seen this suggested before, but I would like to suggest it again because the idea appears to be closed every time but it is still not available in analytics. I've seen it mentioned by other people every time I attend an analytics webinar, so I know I'm no the only person who would like to see this feature.
It would be incredible to have the ability to query by MARC tags, subfields, and indicators. Setting up local params is not enough because it is limited to only 10 fields. There are 10+ MARC fields alone that cover authority data,…
45 votes -
Ability to pull the"Unassigned tab" data in Analytics
It will be great to view the 'UnAssigned Tab' data in Analytics for for 'Waiting for Payment' invoices
3 votes -
Analytics : "Inventory Price" and subtotal
Currently, in Analytics, it is impossible to subtotal the "Inventory Price" column.
The answer from Ex Libris: the "Inventory Price" field is a "Text" field; it is therefore impossible to have a sum of the field in text format (in the Oracle sense).
Idea: to be able to calculate a subtotal for the "Inventory Price" field in Analytics.6 votes -
Make the current publication location discoverable in Analytics
When a record contains both a 260 and 264 field, Analytics will only display the publication location from the 260 field, which often isn't the current publisher's location if a publisher change has occurred. This is also inconsistent with how the publisher field works. The publisher field returns all publishers, separated by a semicolon, but publication place only returns the original publisher's location. Not returning all publication locations makes it difficult to do maintenance on the 260, 264, or 008 country code fields. It also doesn't allow you to accurately record collection development statistics by current country of publication.
3 votes -
Distinguish blank cells in Usage Reports
Hello, currently when creating an analytics report in alma for usage date harvested from SUSHI some months in their cell appear as blank. Can it be possible for these blank cells if they have 0 usages to be reported as the number 0? That way we can distinguish between what had 0 usages vs what was an error in gathering the data.
2 votes -
Add Library Tag (Course Reserves) field to the subject areas where Active Course code is already (eg Physical Items and E Inventory)
Currently we can get the Active Course codes to display in other Subject areas, such as E inventory or Physical Items, and this is very useful for several of our reports... but it would be significantly more useful if the report could also display the Library tag to indicate how important the item is. There is a big difference between items that are CORE and items that are Further reading. While it is possible to do a report based on another report- it would be much simpler if we could just add the tags to our original report.
6 votes -
Analytics: Transit end time NOT registered
Hello,
Please see our public ticket 00903860.
If you make a query containing the field "Physical item historical events->Event end date->event end date and time" with the conditional "event type description=physical item went into transit" on this field is NOT registered the end of transit process, but the start of the following process (if any). Please correct this behaviour.39 votes -
Analytics - make History tab in User Records indexed & searchable
We have been informed by Ex Libris that when a User Record is updated, either with an API or via the Alma interface, then those fields updated will not be updated with the daily SIS feed. They are considered "manual" changes and are therefore, locked. Now, in the history tab of User Records, you can see the changes made and by whom, but we have been told this information is not available in Analytics and the only way to know who has these locked fields is as we come across them. There is no way currently to systematically pull these…
21 votes -
Add publication date and subject fields to 'Portfolio Details for Consortia Members' analytics table
The bibliographic publication date and subject fields would be very useful additions to the 'Portfolio Details for Consortia Members' analytics table. Please include these fields.
46 votes -
Add Collection related subject area/dimensions/parameters in Analytics
Please elaborate Collection in Analytics. We suggest three ideas for that;
Idea 1)
Collection can be a separate dimension, with the existing/new parameters below;
- Collection ID (existing)
- Collection Name (existing)
- Collection External System
- Collection External ID
- Collection MMS ID (of the collection's BIB itself)
- ★★★ The PIDs of the collection's direct sub-collections (in different rows, not combined with semicolons; should be repeatable so that the created report can show the hierarchical structure of whole collections)
- Collection level (the depth)
- Collection Path (from the collection's top level collection to itself)
- Collection Description…74 votes -
Retain Course Reserves info in Alma Analytics
It would be helpful if the system would retain information about course reserves in Analytics, even after things are deleted in Alma. It would be useful to be able to look back over various terms and see what courses were run and when.
32 votes -
Cost Per Use *by fund* Report for Electronic Collections (Databases)
Problem: We are looking for a way to run a cost usage report by fund that includes titles with the PO Line Type ‘Name of Electronic Collection - Subscription.’
Description: Our library evaluates cost per use of all serials by fund. We have been able to run a cost per use report by fund for our print and electronic journals. We run into a roadblock, however, when we try to generate a report on the cost/use of a database by fund.
The E-Inventory Cost Usage report includes all titles with the PO Line Type Name of ‘Electronic Journal -…
38 votes -
Add Related Record MARC fields 76X thru 78X to Analytics
Library personnel would like to be able to generate a list of titles and related records in Analytics so as to document title changes, facilitate research and scholarly discovery and develop research guides for use within the institution. At this time, the 76X and 78X fields that are used to display various related record types in Primo VE are not currently indexed in Analytics. Rather than use up the limited number of bibliographic local param fields available – which would still not allow for full reporting on related records – our institution proposes that the aforementioned fields and associated data…
29 votes
- Don't see your idea?