Report any major changes in availability / circumstances
15
Chairs
Today’s motto: In the Vanguard there is no try. Only do.
Reminder: There’s a slack channel for the ELUNA Regional User’s Group of California that could be useful for posing questions. Jeremy and a few others are already using it. (ecaug.slack.com)
Formal round robin: how’s it going with your current implementation activities?
UCB: “Furlough Fridays!” suddenly announced, but it’s causing problems for scheduling, obvs. Otherwise SILS wise things are going better than expected. The backslash at the end of data fields was really causing problems with the tool. Now that it’s fixed, it’s going well. Pushing to get decisions made – going well. Working on processor to munge things before going into Alma. In good shape to meet the deadlines.
Not doing a test submission. Aiming to submit July 29.
UCLA: going pretty well, working closely with IT guru who does most of the data work. There are a few questions out on Basecamp. Acquisitions had experienced turnover in past year so doing their best and will tweak as needed.
Internal target is the 25th for final data deadline (no draft, since we have different tool)
UCSD: submitted draft form on Friday with a few things of feedback from Laurie. Our “final” version is ready for July 17th. Final two extract files (suppressed bibs, and P2E) are validated and dropped into shared folder. July 17th: Greg will run all of them through a single validation tool session, and create the mapping form for everything.
Should be able to post tomorrow July 17th as DRAFT.
CDL: After our SCP folks were reporting not enough time, they produced everything today! Then ExL changed the P2E formats… Sp we’re halfway done.
SSM update: communication to ExL → migrate to SalesForce ticket after your data deadline. For now Basecamp is okay.
Start to set expectations for vanguard testing by non-vanguard campuses
25
Caitlin
ExL on 7/9:
One sysadmin account per VG who can then make other accounts as needed
Not everyone needs NZ access, because NZ data is populated out to the IZ Almas and Primo - so better to see it there, not in the actual NZ.
Moving forward:
Note that there’s a patron data / acq data privacy group started in WG for examining how do we address privacy issues in testing and in consortial work.
What is the best “Default” thing to do → make a shared view-only account for Sept, then set up meetings / Q&As for Oct?
Guidelines:
make as few accounts as necessary
Give VG campuses some space to assess in Sept
Set up some template for asking who wants access and why
Plan the culmination of Vanguard and how to show the results of what we learned
Decouple “having access” from “learning lessons”
PMs check in with ExL about what they have planned for lessons learned time at the end of the Vanguard phase
Who does the “lessons learned”? → The VG ICs and the relevant PPC/FG folks. Scope minimum expectations for lessons learned.
