Working in the NZ Analytics instance

Background

It appears that all Analytics fields and data reportable at the IZ level are also available at the NZ level. There are advantages to this but also potential problems.

• Reports can be run at the NZ level that combine the data from multiple campuses or allow comparison of local inventory to the NZ
  
  

• Example reports include:

•  

  • Total physical items or expenditures system-wide, by institution, by material type, etc.

  • Resource sharing or fulfillment statistics system-wide or by institution

  • Duplication between an institution's e-inventory and available e-inventory in the NZ

This has important implications:

• If the data can be kept consistent across campuses, data for surveys such as IPEDS may be generated by reports at the NZ level, rather than by each campus

• User and expenditure data are included and viewable by anyone with the ability to run the Analytics reports; there may be privacy issues that should be explored

  • Regarding user data, it can be anonymized:

    • Per Sarina (email 3/22/17):  I think that we probably want to set the NZ setting ‘analytics_anonymize_user_details’ to true (it was set to false as the default), as described on this page: https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/Alma_Online_Help_(English)/Managing_Multiple_Institutions_Using_a_Network_Zone/Analytics_When_Using_a_Network_Zone/Anonymizing_Member_Details_in_a_Network_Zone.

As a group, we feel that access to NZ Analytics will be an essential tool, especially during the data cleanup immediately after Go Live, so we would like to propose that one person at each campus be assigned a login limited to the Design Analytics role.

• Sarina supports this idea (3/22/2017):  "Thanks for bringing this up, I think that it does make sense for campuses to have access to the read-only Analytics view of the NZ."

• Further information and/or login details (generic or individual) to follow when Brandon returns to the office.