Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Date

2/3/2017

Working Group

Analytics & Reporting

Task Force
Report Summary

Goal: Establish an email alias. In progress. Per Brandon, an email alias can be established closer to go live.

Goal: Configuring local fields. Nearly complete pending communication to campuses–established that each campus can identify individual fields via a Sales Force case.

Goal: Communications plan. On hold pending discussion at next meeting.

Goal: Post-implementation work of group. On hold pending governance and COLD decisions regarding role of task forces post-implementation. Discussion item for future meeting. Note that group strongly feels that our work will be most useful post-implementation as campuses turn from migration and training to daily use and begin to discover their reporting needs.

Goal: Division of labor among task group and campus experts and ways to share queries. On hold pending future discussion and decisions as above. Community catalog is a useful mechanism for sharing queries.

Goal: Work with EAR Analytics group. On hold pending full implementation of latest EAR subcommittee.

Goal: Advanced analytics features. Karen Schlesser has volunteered to spearhead this, starting with Link Resolver usage. Advanced features will necessarily be secondary to getting campuses fully comfortable with basic reporting, but these powerful features are an important benefit of Alma and leadership in this area is critical.

Goal: Joint task group with Discovery to explore Primo Analytics. Karen Schlesser will liaise with Discovery group. Report and discuss at a future meeting.

Goal: Policies/procedures for the NZ Analytics instance. Discuss at next meeting–high priority. This is an important area for policy and has bearing on many aspects of analytics including working with the EAR subcommittee and reporting on shared resources for surveys such as IPEDS and ACRL.






Description

Other issues the group has recently been consulted about:

  • Provenance Codes–the Analytics group was asked to consider the implications of local campus customization of the Provenance Code field. The group provided a policy statement for use by the Technical Services group in their policy statement for this field.
  • Item Material Types–the Analytics group was asked about the implications of these codes for Analytics. Several responses were offered, with the general response being that these codes should be kept as is and not consolidated. Further advisement on this issue may be necessary.



Action ItemsFurther work on Frequent Queries page. Create page for policy recommendations based on the above recent issues and others that come up. Predict that more issues will begin to come up as campuses dig deeper into Alma.
  • No labels