| Goal | Action | Due Date |
|---|
| Establish an email alias for the Analytics group communication (to allow CSU library personnel to ask questions as needed) | Request to Brandon Per Brandon, we can set this up closer to go live. | 6/15/17 |
| Determine how CSU campuses need to configure their local fields to be mapped for analytics (LOCAL PARAMS = 9xx fields; up to five can be mapped by EL for use in analytics). | Documentation created: 9xx Local Params, discussed at February 9, 2017 Technical Services Open Forum. | 2/28/17 |
| Develop a communications plan to alert the campus libraries and the implementation of the work of this group. | Divided communication responsibilities See communications page | 2/28/17 |
| Establish the role for this work group post-implementation, including composition and work goals. | Discuss at future meetings | 3/28/17 |
| Develop a division of labor among the Analytics group members and other campus experts to create the reports needed by the CSU system and establish mechanisms for sharing completed queries for the use of all | Discuss at future meetings | 4/30/17 |
| Establish division of labor to work cooperatively and effectively alongside the EAR Committee's Electronic Resources – Analytics Subgroup | C. Perruso is member of the EAR group | 4/30/17 |
| Explore advanced Alma analytics features such as link resolver analytics to meet CSU library reporting needs | K. Schlesser will explore Usage via Alma Link Resolver | 9/30/17 |
| Establish a joint task group with the ULMS Discovery Group to explore use of Primo Analytics | K. Schlesser will liaise with Discovery group | 9/30/17 |
| Establish policies/procedures for working in the NZ Analytics instance | Discuss at future meeting | 3/28/17 |