2020-06-10 ACQ/ERM FG Meeting notes
Date
Jun 10, 2020 11AM-12:30
Zoom:
See calendar item or inquire with Chair for Zoom details.
Attendees
@Mark Hemhauser (Unlicensed) , UC Berkeley
@Lisa Spagnolo , UC Davis (chair)
@Paula Pascual , UC Irvine
@Stacy McKenna , UCLA
@Sarah Sheets , UC Merced
@Carla Arbagey , UC Riverside
@Judy Keys , UC San Diego
@Lisa Wong , UC Santa Cruz (timekeeper)
@Holly Eggleston (Unlicensed) , California Digital Library (notetaker)
@Susan Boone , UC San Francisco
@Maricel Cruz (Unlicensed) , UC Santa Barbara
Not attending
Future agenda items
Discussion items
Item | Desired Outcome | Time | Who | Notes | Decisions | Actions | |
---|---|---|---|---|---|---|---|
1 | Assemble | Getting settled, reviewing agenda | 5 | Lisa |
| ||
2 | Admin Items |
| 5 | Lisa | Lisa S doing review of confluence space for publicity review and also general cleanup (RACI, etc) Lisa S will record meetings when partial attendence Moved open questions off meeting minutes (where did these go?) Basecamp archiving (general from multiple points):
What do we do with questions we have but it's not the right time to ask. |
Decision: Archive original Basecamp thread, post any followups as new thread. Decision: Followup thread should reference source of initial answer. Decision: Retain Google Doc. |
ACTION: Lisa S start spreadsheet for tracking queued questions. |
3 | Updates: specifically from PPC | Shared understanding of PPC activities, including what is routing to our FG. | 10 | Lisa |
|
| Lisa S. will followup on whether there is a benefit to having SCP data in ILS records. And clarify how IZ records link to the NZ. / 5/27 ACTION: FG asked to finalize vision statements and post to wiki - Lisa S prepare for next meeting review ACTION: Lisa check on details of certification process - are these materials available to us now.
|
4 | Follow-up from 6/3 Ex Libris Call | Debrief for follow-up items from ExL- Q&A 6/3 - determining actions needed between now and 6/10 | 10 | All | Review Q&A and responses for any additional information needed. | Decision: Archive 6/3 Q&A and we'll follow up in separate thread as needed | ACTION: all what followup needed from our Q&A?
|
5 | Decision Page - Vendors Discussion | Approve closure of ILSDC Vendors Decision Page; Develop migration-related Vendors Decision Page (to route to IC) | 15 | All | Decision Page Vendor Records in the Network Zone Sharing Vendor Info in NZ (ExL doc) NEW: Vendor Data for Migration to Test Global Vendor File in Vanguard Discussing Vendor Data: CDL would load all vendors, use suffix to prevent unintentional matching. CDL share all vendors to all campuses Would identify subset (1 or 2) of vendors for IZ to link to. Looks like proposal is only for a subset of campuses to link to selected vendor. Should all vanguard campuses link to same vendors? Would make more sense for how we'd apply this as a policy? Q: If we wish to use NZ vendors, does an institution migrate the same vendor code in their vendor file? Q: If we use an NZ vendor, does an institution migrate their POL w/the NZ vendor code in the POL vendor code field? Q: Followup from 6/3 - ExL response to Q8. Their recommended workflow says not to share the vendor. Why not? This feeds back to our core vendor question of "what do we gain by sing shared vendors, what do we lose if we do not" 360RM - CDL, UCLA, UCSB (only uses PRV prefixed vendors for holding Sushi credentials)
| Decision: Close for decision, acknowledge more specific discussion continuing | Everyone: continue to look at vendor records in the NZ and think about answers to the questions on the decision page so we can make a decision for next week’s meeting ACTION: Lisa add vendor followup questions (to vendor basecamp thread or to new thread? |
6 | Vendors Basecamp Item | Identify what is needed for follow-up Q to Ex Libris (vs. exploration in Sandbox or in Vanguard) - what do we need to know now? If OK, time to archive Basecamp item? | 10 | All |
| Decision: Archive thread, post followups as new thread, retain google doc. (Not closing in light of extra questions resulting from discussion on Vendor Data page. | Everyone review for items needing additional followup. |
7 | Decision Page on P2E | Developing a quick turnaround recommendation for P2E data due in next week; beginning of testing plan for Vanguard. | 15 | All
| Decision Page: P2E Recommendations for Vanguard Brief recommendations knowing that people are preparing P2E data Concern with records that contain both P and E (acknowledgement) What recommendations do we have at this stage? P2E Lessons Learned Google Document Carla to present from UCR experience. Summary: Records with multiple links and multiple 793 used to identify portfolio resulted in multiple portfolios with the value from first 793. Had to export list of records and reingest to the system (using public note for portfolio name?). Delete old portfolios afterwards (do not delete bib records). Replicating the P2E process manually post-migration but with different values in import profile.
|
| |
8 | Wrap-up | Identify next actions | 5 | Lisa | Propose meeting of III campuses (both new and already-alma) to discuss migration issues prior to next meeting. Request to record to share with SCP? |
| |
9 | Parking Lot | To save for future discussion (after 6/3 call - identify what to bring in next) | 75/75 |
|
|
|
|
The SILS mission is to transform library services and operations through innovation and collaboration. The future is shared!
Question? Contact AskSILS-L@ucop.edu