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.
144 results found
-
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.
4 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 -
Analytics for count of resource sharing requests made via Course Reserves citations
We'd like to be able to see analytics data for resource sharing requests placed via Course Reserves citations. We are told by Support that this is not currently supported, and it was suggested that we create an idea here.
2 votes -
Analytics User - has course Yes/No option
Add the option for 'Has course' Yes/No option for user reports in analytics.
1 vote -
Use the same terminology in the search box as the field label - Analytics objects list
In the new Analytics objects list, one of the search field options is "location". It is searching the field labeled "Subject Areas".
Please use consistent terminology.
0 votes -
Add primary/user id of a Interested User as a Fund Expenditure Facet
Several Institutions have use cases that require the need to find the Primary ID of an interested User. This would allow an easier means of utilizing feeder reports in conjunction with the Fulfilment Subject Area. Currently, there is no easy way to obtain this information. Credit goes to Jihyun Song of Soul National Unversity for presenting this issue.
10 votes -
SUMIF function for Alma Analytics
There is currently no way to do a SUMIF function within Alma Analytics. In Excel, a formula like =SUMIF(A:A, A2, B:B) will perform the following operation: it will look for duplicates in the first column and if present, sum the numbers in the second column and output them in the third column. This is particularly helpful when trying to determine something like the total number of serial volumes per library (or some similar metric) without using the subtotal function. The subtotal function creates an additional row at the end of each unique set of instances instead of putting this data…
5 votes -
Add permanent location code or name to fulfillment analytics
Under Alma Analytics we want to request that Ex Libris add the field of permanent location code or name to the fulfillment area of analytics. We need to be able to grab the count of items in a library and how many of those items (held) in that library have circulated by any mean (resource sharing, digitization, loan, etc.). The current table allows us to pull what circulation desk they circulated from. That is not entirely accurate as we allow items to be delivered and circulated from any circulation desk on campus. This type of data is needed to assess…
3 votes -
Out-of-the-box reports - misleading column headers
A number of reports have column headers which do not reflect the results of the actual criteria used in the report e.g. Count of Items Loaned have a column header of Loans (In House + Not In House) where a filter of ‘In House Loan Indicator is equal to / is in N’ has been applied. Appreciate that you can go in and change the Column Heading description but not all users will think to check the criteria of a report and assume the results are for that indicated in the column header - see attached document for example and…
1 vote -
Add invoice vendor to Analytics
Add the invoice "Vendor" field to analytics; currently only the invoice "Vendor Account" code and description seem to be available via Funds Expenditure-Invoice Line.
3 votes -
Add "VAT Percentage" to Analytics
Currently there is no way to get the VAT percentage of an invoice or invoice line in Analytics. There is only "VAT Code %", but this is useless for institutions that don't use VAT Codes.
(see also cases 06640702 and 06605754)
1 vote -
Adding the borrower code stats to the patron detailstable in the fullfiment subject area
The fullfiment subject area contains several tables related to the readers who borrowed the document including the "patron details" and "borrower details" tables. According to the documentation the data stored in the patron detail table are the characteristics of the reader at the time of the transaction. The "borrower details" table stores the characteristics of the reader at the time of the request.
It would be useful if the patron statistical codes were stored in the "patron details" table so that they can be historized.
Indeed, like many other libraries, we use these statistics to identify the academic department of…7 votes -
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 general note(s) field from the Electronic Collection Editor to Analytics
Currently, only the public and authentication notes seem to be available. It would be useful to have a way to find and report on those collections that have general notes added.
15 votes -
Add a new Bibliographic ID field for OCLC Control Number 035z to display each OCN one row per MMS ID
Currently, a user may retrieve a delimited list of cancelled OCLC control numbers from the OCLC Control Number (035z) attribute under Bibliographic Details. However, this field has limited usefulness for a couple reasons. First, the field has a limit of 256 characters, which means when a bibliographic record shows more than 15 or 16 OCLC numbers have been merged, some numbers are excluded. Second, and more importantly, each individual control number cannot be matched to other cancelled or active control numbers in other records without being split to a separate field first. This is not a straightforward task in analytics…
12 votes
- Don't see your idea?