2017-04-18 Meeting notes

Date

Attendees

Discussion items

  • 360 Counter customers
    • Nikki shared Basecamp discussion regarding 360 Counter customers (Fresno, Long Beach, San Diego, San Luis Obispo)
    • 360 Counter customers will continue to have the service until Oct. 1 (SLO) or Dec. 31 (Fresno, LB, SD)
    • Ex Libris will not migrate ANY data or configuration for 360 Counter customers
      • Expectation is to use a combination of SUSHI and manual gathering from publishers/uploading to Alma
      • Group consensus is this apparently unavoidable but is not good news
      • Per Karen, the initial SUSHI harvest will retrieve the last 12 months, so setting up SUSHI will at least bring in a block of recent data
      • Campuses can set up SUSHI starting now (however, SLO and SD should probably wait due to 360 RM migration)
      • Usage data will be wiped; however, campuses that have switched over from USTAT will retain their migrated data or receive a fresh copy
  • Status Report on Centralized Analytics
    • At the previous meeting and via emails over the past weeks, the group drafted a statement that contained a number of policy and governance questions and forwarded it to the Implementation Team through Patrick.
    • Nikki met with the Implementation Team on 4/17/17 to clarify and answer follow-up questions
    • Important points:
      • Post-implementation status of this group:  Some version of the Analytics Group will exist, although its exact make-up and charge is still TBD.
      • Will SDLC/CO help campuses with analytics reports/dashboards?  No. The Analytics Group may have a support role.
      • How will NZ/IZ statistics gathering/reporting be handled?  Implementation Team meeting to consider NZ/IZ workflows this week, and will include analytics questions
        • It may be better to keep all usage stats in the IZ to avoid duplication, since the NZ can report on IZ analytics
      • Is there any chance of CO support for usage data gathering since all usage will now be either SUSHI or manually gathered and staffing/expertise is unequal across campuses
        • It remains to be seen ... the idea was not rejected out of hand, but the level of support from the CO for various Alma functions is still under discussion
      • Curation/policies for the shared Calstate community folder
        • Implementation team suggests that the Analytics WG put forth some policies regarding naming, file structure, appropriate sharing
        • Lauren volunteered to start a draft
  • Alma Health Check
    • We're concerned about campuses not feeling confident about the Analytics questions
    • The Implementation Team agreed that a webinar covering just those four checkbox items might be a good idea
    • Karen volunteered to lead the webinar; Nikki volunteered to assist
  • Status Reports
    • Lisa is working on new training videos and updated versions of some previous videos; 5pm publishing schedule from Alma to Analytics is problematic for many reporting functions
    • Karen updated status on SUSHI set-up and harvesting for the USTAT campuses
    • Carol:  EAR analytics committee update; some discussion around EAR analytics committee being an important user of Analytics but not having responsibility to gather or manage usage stats
    • Stephanie and Carol:  working on a wiki page detailing Analytics vs. Repository Search; meeting weekly; have decided on an approach that centers on earlier survey data regarding common reports
    • Lauren:  added information regarding data that will or won't be kept; discussion regarding how campuses may use the shared folder to retain important queries that would be lost during migration
    • Marc:  recently joined group; working through the Ex Libris training videos; will test some of the IPEDS queries soon
    • Nikki:  IPEDS/ACRL:  not much action right now, sense that campuses have other things to worry about.  Need to learn more about NZ Analytics–potential to answer IPEDS queries for all campuses at once from the NZ.

Action items