2017-02-23 Meeting notes

Owned by Nikki DeMoville (Unlicensed)
Mar 06, 2017

Date

Attendees

Discussion items

  • Meeting schedule
    • Thursday was a great day when we started but many of us are now swamped with meetings/training on Thursdays and find it difficult or impossible to attend at the original time
    • Karen Schlesser will send out a Doodle poll so we can find a meeting time that a majority of the group can attend
  • Analytics needs check-up
    • Does everyone have the Alma/Primo roles they need to do the work associated with this working group?
      • Alma roles: 
        • Designs Analytics (create reports/dashboards, use configuration menu to share reports/dashboards)
        • (optional) API Analytics Read (use API to pull Analytics reports into websites, etc.)
      • Primo role (Back Office account required)
        • Any Back Office role
        • OR Reporting role (limits user to Primo Analytics only)
  • Serials Solutions 360 Counter / Intota Assessment update
    • 360 Counter customers are waiting for guidance from Ex Libris regarding data migration and setting up vendors
    • Nikki DeMoville posted to Base Camp to request an update (see 2/22/17 status report for details)
    • Dolph Chaney responded 2/23/17:
      • "We are continuing to pursue answers to these and other related questions with the Migration Team but do not have more detail to share at this time.  We recognize and understand the importance and time-sensitivity of the answers to your questions."
  • Analytics vs. Repository Search (needed soon)
    • This is an area of confusion--Innovative Systems used Create List for all functions, while Alma has two different systems
    • It seems like it would be within the scope of this group to provide guidance on which system to pick for which needs
      • CALL FOR VOLUNTEER(S) FROM THIS GROUP!  Please respond to the group if interested!
        • Build a wiki page to list and advise regarding the following:
          • what fields (or which type at least, or link to documentation) are indexed in Repository Search and which are in Analytics
          • strengths and weaknesses of each system (better searching?  better output?  directly actionable?   can schedule/display/email?)
          • maybe recommendations on which system to use for which type of work
  • Sets and Indication Rules (long time-line -- summer/fall)
    • Sets created using Repository Search can be filtered in very sophisticated ways using Indication Rules, which are similar to normalization rules
    • The Norm Rules Task Force is concentrating on policy, and training on this function is not part of their charge (per consultation with TF member J. Hobbs, SLO)
    • This appears to be a training gap that falls within the purview of "Reporting"
    • CALL FOR VOLUNTEER(S) FROM THIS GROUP!  Please respond to the group if interested!
      • Learn about Indication Rules
      • Build a wiki page with a brief explanation of what they are and how they work, and links to documentation and presentations by ExL and others
      • Liaise with Brandon Dudley, Mallory and Sarina, and possibly the Tech Services WG regarding hosting a possible webinar on this topic in late summer or next fall (when campuses are caught up and ready for more sophisticated training)
  • Goals
    • Postponed most goals until next meeting when it's hoped more of us can attend
    • Updated goal:  Primo Analytics
      • Karen has volunteered to take lead
      • Karen and Nikki attended the Primo Analytics training webinar
      • Can't do anything else until Analytics is activated for CSU Primo instances
    • Discussed goal:  "Develop a communications plan to alert the campus libraries and the implementation of the work of this group."
      • Ways to communicate our work include the listserv, the wiki, Slack, and working group open forums
      • Technical Services group has been generous in putting us on the agenda to get the word out about things like the 9xx fields
      • Nikki will check with Access Services to see if they have a similar forum we might use in future
      • Nikki will take responsibility for posting to and reporting back from Base Camp on Analytics issues
      • Karen will take responsibility for the Slack Analytics channel
      • Karen is working on a form whereby campuses can request help with specific reports
      • All:  keep monitoring the different listservs and jump in where needed (thanks to all who have been doing so already!)
      • All:  let's talk at another meeting whether we want to host an open forum of our own to answer, or at least collect, Analytics questions