Please make it so that we can create analysis in analytics that display the creation date and creators of user notes. Both fields would be very useful filters for us.

Please add Licensor Name to the PO Line License in the Funds Expenditure area in Alma Analytics
This would help us report to our Finance Dept on all licensing parties associated with an order

In MARC bibliographic records, the 880 field is used for non-Roman script equivalents of other fields in the bib record. CJK (Chinese, Japanese & Korean) libraries, for example, may use the 880 to record the non-Roman script equivalent of the Romanized characters in a 245. We would like the 880 field to be searchable in Analytics so we can create new book lists in the CJK scripts. New book lists are very popular with our users and we would like to be able to present these lists in the CJK scripts.

It would be useful to include Renewal Operator details in the Fulfillment Analysis area on Alma Analytics. This would allow us to identify and report on the number of renewals that took place at the circulation desk, via self service or via Primo.

Adding the Subscription interval field in PO Line to the Funds Expenditure subject area in Analytics. This would allow reporting based on the frequency of a serial.

This would help us report to our Finance Dept on all licensing parties associated with an order.

Usage case: University of Wisconsin would like to create reports that inventory items that change permanent locations by date. Currently, a report that can inventory all items that were added to a permanent location from various other locations by fiscal year isn't possible. With the addition of item changed permanent location as an event that is timestamped such a report would be possible. For example, a report of all items relocated to off-site storage during the past fiscal year is a desired report.

Real-time Analytics data would be a fantastic feature. I foresee the lag in data refresh to be an issue validating our FPC data. Overall, it would just be beneficial to have up-to-the-minute data.

As a possible improvement for the Fulfillment subject area, please consider adding an indicator, much like the In House Loan indicator, to loans made while an item is on course reserve. This would allow us to easily include or exclude loans made for items on reserve in our circulation reports. Currently we exclude by location, but we suspect that this is not a reliable method, in part because the inactive temporary location is still attached to many items.

A course reserve flag on a loan would also allow us to easily pull circulation counts when reporting on course reserve.

We'd like to have the permalink for a bib record included in the Analytics report.

It would be helpful to include a "Last page" or "end page" arrow on the Results tab in Analytics. There is an arrow to take you to the beginning of the analysis but not to the end. Sometimes it is helpful to go to the end of an analysis to check the data and it is very time-consuming to click the "Next 500 rows" arrow several times on large analyses.

Analytics doesnt have the updated information for our institution at the end of the day, we need to wait another day to get the info updated for that day, we want that every intitution can have their own update time for data.

Items details are missing from the Course reserves subject area in Alma Analytics. So can't get Barcode and other item details for course reserves.

As it currently stands only 'Active Course Code' or 'Active Course Name' is available in the Bibliographic Details dimension. As our use of Leganto and Course Reserves grows we are increasingly needing to report on physical items on a course, active or not, this is currently difficult to do as the information is currently silo'd across subject areas that don't contain shared dimensions.

It will be great to have a search for the Alma Analytics reports off the Alma menu.

Some areas in analytics only have date stamps instead of date+time stamps, so reporting on for example, Events from analytics will only ever bring back the date the event occurred and not the date+time required for auditing.

We'd like all dimension datestamps to have a version of the timestamp which includes the date+time so that they are useful in working out when a transaction occurred and not just the date it happened. This is good for consistency across analytics data as well.

I appreciate the ability to export Analytics results directly into an Alma set, but I would like to be able to export a set of records directly into Analytics without having to recreate my Alma search (if I can) in Analytics. This would also be very helpful for working on sets of records that other people at my institution have created!