Page Comparison

Versions Compared

Key

This line was added.
This line was removed.
Formatting was changed.

Google Doc worksheet for meeting minutes

May 9, 2018

Attendees:

Several campuses have no usage data at all in Analytics

Discuss best approach to help them

Some campuses are still setting up collections, POLs, and general Alma data and infrastructure, aren’t at the point yet where they can set up SUSHI or usage data infrastructure, may not know their account information or how to get started
SDLC account information and setup for other institutions

Nikki will ask Ying to contact SDLC package vendors for to ensure that accounts are setup for each institution and compile a list of usernames that institutions can use to reset their passwords (may need institutional emails for this?)

Action item: Craft an email with instructions for getting started and send to ERM group to distribute, gather pain points and get a sense of how we can help them; see how to identify campus primary contacts? See https://calstate.atlassian.net/wiki/spaces/URM/pages/151453722/CSU+Cataloging+Contacts for example (Lauren)

Action item: Prep example report that institutions can use to see exactly what may have already been migrated for you or already exists in Alma (could also help with iterative setup) - dashboard that would show platforms and usage data in one view to look at data as it’s harvested
- Create instructions for setting up a single vendor / manual upload and check results in Analytics (Link to/update existing Tips and Tricks)

Recommendation that we standardize reporting codes, item types - campuses are using these in different ways

This would help with ACRL reports and other systemwide comparisons/reports
Should define POL types/standardized Alma fields for use systemwide
Start with Acquisition data? Develop example reports?
Want to avoid forcing people to redo work

Action item: Ask Acq/ERM group whether they would explore and recommend some standardized fields based on how people are currently using their reporting codes (Lauren)

2. ELUNA

SWIG meeting updates (Moon)
- Working on evidence document to outline issues that Alma/Primo/Leganto users are experiencing
- Ex Libris expressed commitment to moving issues forward; plans discussed:
  - No SQL access to live or copies of anyone’s data ever
  - No plans for analytics connected to sandboxes (v. expensive)
  - Supportive of institutions building their own data warehouses of Alma data
  - Random Analytics timeout - Ex L assured it’s been fixed; should be extended to 59 minutes - will not extend past an hour for security reasons
  - Added 9 new subject areas since January 2017 and will continue adding more
  - If you want new fields added put in enhancement request or work with SIWG to get them added
  - Certain fields are named differently between Analytics and Alma - Ex Libris is committed to fixing those discrepancies - submit support request
  - Cost Per Use is being completely revamped (!)
  - Many data elements will move to einventory subject area

Useful things we learned and how best to share these (all)

3. Summer training

Developing plans (Brandon, whatever can be shared)

4. Any other TF updates anyone wants to share, as time allows

April 11, 2018

Attendees

...