1. New Features in Alma Analytics
Presentation September 2017
Yoel Kortick | Senior Librarian

2. Introduction
This presentation will cover selected new developments in Alma Analytics from recent releases.
For a full list of recent developments see the release notes at

3. New Analytics Administrator Role (Sept. 2017)

4. New Analytics Administrator Role (Sept. 2017)
Until now the ‘Design Analytics’ role had permission for both ‘Design Analytics’ and ‘Analytics Configuration’.
The configuration permissions available with the ‘Design Analytics’ role were transferred to the new ‘Analytics Administrator’ role.

5. New Analytics Administrator Role (Sept. 2017)
Users with ‘Analytics Administrator’ role can access the configuration actions in Configuration > Analytics.
Users with only the ‘Design Analytics’ role can create Analytics reports, but do not have access to the Analytics configuration actions.
This allows for more granularity in the assignment of roles to the staff users and therefore more control in managing Alma Analytics.

6. New Analytics Administrator Role (Sept. 2017)
To demonstrate this new functionality we will now look at three users:
Anna Anderson = has only role ‘Analytics Administrator’
Donna Anderson = has only role ‘Design Analytics’
Barbara Anderson = has both roles ‘Analytics Administrator’ and ‘Design Analytics’.

7. New Analytics Administrator Role (Sept. 2017)
User Anna Anderson has only one role and it is ‘Analytics Administrator’

8. New Analytics Administrator Role (Sept. 2017)
User Donna Anderson has only one role and it is ‘Design Analytics’

9. New Analytics Administrator Role (Sept. 2017)
User Barbara Anderson has both roles ‘Analytics Administrator’ and ‘Design Analytics’

10. New Analytics Administrator Role (Sept. 2017)
User Anna Anderson logs in and she can access the Analytics Configuration but she cannot access the Design Analytics

11. New Analytics Administrator Role (Sept. 2017)
User Donna Anderson logs in and she can access the Design Analytics but she cannot access the Analytics Configuration

12. New Analytics Administrator Role (Sept. 2017)
User Barbara Anderson logs in and she can access both the Design Analytics and the Analytics Configuration

13. Removal of outliers in Benchmark Analytics (Sept. 2017)

14. Removal of outliers in Benchmark Analytics (Sept. 2017)
For more information on the usefulness of this feature you may wish to perform an internet search ‘why are outliers excluded’

15. Removal of outliers in Benchmark Analytics (Sept. 2017)
It is now possible to filter out the extreme high and low values (outliers) in benchmark analytics graphs.
This gives a more accurate picture of the situation.
User can put here whatever value he wants

16. Removal of outliers in Benchmark Analytics (Sept. 2017)
This is the graph ‘Num of electronic collections in repository (total), AVG’ in the ‘Inventory Total’ tab.
An ‘outlier’

17. Removal of outliers in Benchmark Analytics (Sept. 2017)
After removing the top and bottom 2% we have a more accurate picture

18. Additional COUNTER report support (Sept. 2017)

19. Additional COUNTER report support (Sept. 2017)
Analytics now supports the following COUNTER type reports in the Usage Data subject area:
BR4 – Platform Access Denied (license limit exceeded)
BR4 – Platform Access Denied (item not licensed)
BR5 - Total Searches
BR5 - Total Searches Federated
MR1 - Multimedia Full Content Unit Requests

20. Additional COUNTER report support (Sept. 2017)
This is of course in addition to the many other COUNTER report types which are supported and listed at:
The additional supported COUNTER report types enable the Alma institution to get an even more in depth picture of the resource usage.

21. Additional COUNTER report support (Sept. 2017)

22. Additional COUNTER report support (Sept. 2017)
For example here we are checking the ‘Platform Access denied (item not licensed)’ measure for ‘Project MUSE’ for 2017

23. Additional COUNTER report support (Sept. 2017)
We can then see the results
Based on the results of a report of this type, the institution may considered changing licensing policies.

24. Usage by COUNTER reports added to benchmark (Sept. 2017)

25. Usage by COUNTER reports added to benchmark (Sept. 2017)
The benchmark analytics default dashboard now includes KPIs related to COUNTER report usage.
This allows the institution to get a perspective on the electronic resource usage in comparisons to other institutions.

26. Usage by COUNTER reports added to benchmark (Sept. 2017)
The institution below (in blue) is about average for Journal usage.

27. Usage by COUNTER reports added to benchmark (Sept. 2017)
The institution below (in blue) is below average for Journal usage.

28. New Usage via COUNTER Reports (Aug. 2017)

29. New Usage via COUNTER Reports (Aug. 2017)
The following reports were added to the Usage via COUNTER Reports dashboard:
Usage Data - Usage amounts for all material types for three calendar years ago until current date
Usage Data - Usage amounts for all measure types for three calendar years ago until current date
By looking at the last three years it is possible for the institution to see long term trends in what kind of COUNTER report data they have been loading.
This is not for measuring usage, but rather for measuring what types of reports have been loaded.

30. New Usage via COUNTER Reports (Aug. 2017)

31. New Usage via COUNTER Reports (Aug. 2017)

32. New Usage via COUNTER Reports (Aug. 2017)

33. New Usage via COUNTER Reports (Aug. 2017)

34. COUNTER Type JR5 Added to Analytics (July 2017)

35. COUNTER Type JR5 Added to Analytics (July 2017)
The JR5 COUNTER report is now supported in Alma and Alma Analytics.
The JR5 measures the usage for YOP (Year of publication).
This allows the institution to measure usage by publication date of the resources.

36. COUNTER Type JR5 Added to Analytics (July 2017)
This institution can see that the majority of the resources used are for very recent years of publication

37. New Bibliographic Details Dimension Fields (June 2017)

38. New Bibliographic Details Dimension Fields (June 2017)
The following fields were added to the shared Bibliographic Details dimension:
Brief Level
Originating System
Originating System ID
Originating System Version
This allows the institution to get a more accurate and in depth picture of the sources of the repository
The following slide shows a pie chart based on the originating system of records added in 2017

39. New Bibliographic Details Dimension Fields (June 2017)

40. Thank you

41. Thank You