Analytics & Reporting Status Reports

Goal: Establish an email alias. In progress. Per Brandon, an email alias can be established closer to go live. (Status = pending)

Goal: Configuring local fields. Established which fields are available and how to request; confirmed that campuses can change their choices but should avoid doing so. Karen/Nikki communicated to campuses via the Tech Services working group weekly open forum. Karen added documentation to the wiki. (Status = complete)

Goal: Communications plan. See new communications page. (Status = nearly complete)

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. Update: Carol Perruso is in both groups and has agreed to be liaison. Further updates to come as EAR group is just getting started. (Status = pending)

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. Update: Karen/Nikki attended Ex Libris functional call re: Primo Analytics. Note that Analytics is not yet configured in the Cal State Primo Back Office instances. Update 3/3/2017: Primo Analytics still non-functional.

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.

Outstanding issues:

• Status of 360 Counter customers
  • Ex Libris has given assurance that contracted services will continue as needed until data is migrated, regardless of renewal status
  • Brandon is working with Ex Libris PM Dolph Chaney to formalize this assurance. Dolph is working with others at Ex Libris to get formal agreements for us.
• Status of USTAT customers
  • Not all campuses seem to be able to set up SUSHI
• Primo Analytics
  • Still non-functional

New activity:

• Cross-posted to Tech Services, Access, and Analytics listservs: communication regarding immediate Analytics & Reporting needs at campuses.
  • Particular concerns:
    • The Analytics questions on the Alma and Primo Health Checklist
    • Setting up usage statistics, SUSHI configuration, and USTAT or 360 Counter migration
    • Advanced Repository Search, logical, itemized, and combined sets
    • Creating and managing Fulfillment Sets and using them in your daily work
    • Using Analytics reports to create sets in Alma
      
      

• Further 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.
• Pending update by Ex Libris, draft recommendations for 360 Counter customers regarding usage data migration and when to start loading reports and configuring SUSHI in Alma.
• Page with detailed comparisons and recommendations regarding Repository Search vs Analytics. Stephanie Alexander and Carol Perruso have volunteered to work on this over the next 4 to 6 weeks.
• New meeting time: monthly meetings rescheduled to Tuesday mornings to resolve attendance conflicts

Goal: Establish an email alias. In progress. Per Brandon, an email alias can be established closer to go live. (Status = pending)

Goal: Configuring local fields. Established which fields are available and how to request; confirmed that campuses can change their choices but should avoid doing so. Karen/Nikki communicated to campuses via the Tech Services working group weekly open forum. Karen added documentation to the wiki. (Status = complete)

Note: Feb.16 meeting postponed to Feb. 23, so the "next meeting" issues below remain pending except as noted.

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. Update: Karen/Nikki attended Ex Libris functional call re: Primo Analytics. Note that Analytics is not yet configured in the Cal State Primo Back Office instances.

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.

Julie Su (SDSU) requested information regarding 360 Counter migration. Nikki posted the following in BaseCamp on Friday, Feb. 27. Ex Libris has not yet responded.

I am hoping for updates and/or confirmation on the following:

• Timeline for migrating usage data
• Amount of usage data to be migrated (is it still 3 years?)

Current customers of Serials Solutions 360 Counter with DRS service have a particularly complex situation with regard to migration:

• Currently configured SUSHI harvests in 360 Counter gather data monthly
• DRS service gathers data twice per year -- in February for Jul-Dec and in August for Jan-Jun
• At least two DRS customers have contracts that expire in June 2017.  These customers will end up with data that is current through a variety of dates--most recent month for SUSHI harvests, December 2016 for DRS loads, or older than December 2016 in cases of DRS load failure (due to account, platform, etc. changes)

Serials Solutions customers urgently need to know when their data will be migrated so they can do the following:

• Know when to start setting up SUSHI in Alma without creating duplicate data loads or waiting till the last minute
• Know how much additional usage data to extract from 360 Counter to reload into Alma, before contracts expire
• Decide how to handle DRS failure cases for the most recent (February 2017) load cycle
• Plan for manual data extract/upload for Jan 2017 forward for platforms handled through DRS
• Extend their contracts with Serials Solutions if necessary

• Further 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.
• Pending update by Ex Libris, draft recommendations for 360 Counter customers regarding usage data migration and when to start loading reports and configuring SUSHI in Alma.

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.

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.