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.
159 results found
-
Add "credit" to Fees and Fines subject area
Users want to create reports that show credits issued by which operators, the date and amount of the credit, who the credit was issued to and what the credit was issued for.
1 vote -
Add "Electronic Collection Content Type" to Alma Analytics
In Alma, you're able to filter and view electronic collections by "Electronic Collection Content Type" (i.e. Book Package, Journal Package, etc.) -- However, this isn't a column or field available in Analytics.
It would be great if it could be included so we could create reports on electronic collections based on how the content is defined for that collection.4 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.
41 votes -
Alma Analytics: Usage Data Subject Area
In Alma Design Analytics, add "Fund Ledger" to the folders in the "Usage Data" Subject Area. Collections staff want to be able to look up titles they have ordered out of their "Fund Ledger Codes" and see how much they have been used, especially TotalItemRequests. The decimal-point breakdowns of usage in the "Cost Usage" folder in the "E-Inventory" Subject Area are too confusing/convoluted, and only use UniqueTitle/ItemRequests.
6 votes -
Map item level fields, Pattern Type and Linking Number in Analytics.
Area of concern: Analytics Fields for Reporting on Serials 863/866 Generation.
Please reference Ex Libris presentation ‘Automation Tasks for Summary Holdings’:
In order for 863/866 Summary Holdings generation to work properly, each item record must contain certain information in the ‘Pattern Type’ and ‘Linking Number’ fields. Currently, these fields are not mapped in analytics, so there is no way to report on which records lack this info. Without this reporting capability, we are stuck individually checking many thousands of records to be sure they have the required information.
What should be changed: As Serials Processors, we would like to…
49 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.
42 votes -
Ability to report on Note (5XX) fields - bibliographic details folder/dimension
We request that the Bibliographic Details dimension in Alma Analytics have an entry added for Notes, wherever the Subject Area has "Bibliographic Details" presented. This Notes attribute should include all 5XX fields and subfields in the bib record. The data should use a separator (e.g., ;) to identify the information from different and repeated 5XX fields. This is useful information for libraries for reporting purposes.
13 votes -
Lending Publication Date
In Lending Analytics, the Publication Date field retrieves the date the Journal began publishing, and not the date the Article was published, despite the fact that the date in the Lending request is the Article's publication date. As a result, we are unable to check if we have supplied scans according to Copyright Law.
22 votes -
Expand Number of User Identifiers in Analytics
In Alma Analytics, when running User analyses, only two user Identifier options are made available under the Users | User Details subject area. Each of these two Identifier options can be associated with a single user identifier type by Ex Libris, requiring that a case be opened with Ex Libris to change that association as needed. Given that there is no limit to the number of user record identifier types in Alma for an institution, having only two user identifiers readily available in Analytics is very limiting and inefficient. Ideally, Analytics should offer up to ten user identifier options as…
3 votes -
Add Normalized Call Numbers to eBook & eJournal Analytic Reports
Many academic departments ask for accreditation reports that count resources available for students. We typically use Library of Congress Call Number ranges from the OCLC conspectus to get counts of resources. The report runs well for all physical items. However, eBooks and eJournals (both ubiquitous to our collection) do not have normalized call numbers as a part of an analytics report. Therefore the counts of titles between a range of Call Numbers is not correct.
19 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.
5 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.
6 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: 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.43 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.
63 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…
19 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…79 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.
50 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 -…
37 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…
33 votes
- Don't see your idea?