2020-06-09 Meeting notes

Updates

0 mins

Liz

Liz updated on Günter’s message and Deadline issue

From Jane: TJ went UCB and showed and tell about doing analytics

SCP local notes:

• 901 for system number

• 920 participants (same)

• 924 vendor title keys/identifier (from 024/035)

• 930 SCP collection/package titles (from 793)

Q&A debrief and some updates from basecamp

15 mins

Liz: the setup for recording in Zoom lost the question but have audio transcripts.

Sarah: pasted note of Q&A into last meeting notes.

• Having ExL pointed out links to the documents are helpful

• Liz will post some questions from basecamp: for example, you can fake OCLC number(can be any combination, and not mix/match real OCLC#) to force in, as an option to consider; anyone can send question for Liz to post to basecamp.

• One question that 856$3 can’t be used to populate into portfolio, link: http://exl-edu.com/01_Alma/Implementation_and_Migration/Migration_Guides/P2E/#/lessons/df0adM4qZGnbYz5zRrBrP3fNNncNws_T

• PPC is thinking about consolidate basecamp questions and what would be useful and to share in a central place: will need to explore

• When questions being pointed to the same document, wonder if the question is not clear and/or need to rephrase

• Hermine: local concern on deadlines, especially SpecColl, presuss on whether staff are able to do as planned to protect local data

• LIz: the concern is share at UCSD as well; people also want to reassurance. Confluence is open now, agenda can be shared with local group for feedback; tricky on enough time for campus share the agenda ahead of meeting due to PPC meeting on Friday

• ExL mentioned that ExL store the migrated version even not added (due to load & match) and should be a way to see: Vanguard is the place to test it if true. Alma campuses confirmed the migrated version was used for comparison

• Understanding structure of NZ/IZ is helpful too

Liz: Would be helpful to have another one before Go-live?

Yes

Review/update decision pages

Fist-of-five votes for potential Vanguard harmonization

50 mins

Fist-of-five decision making (see page 12)

Group did little exercise to get familiar with the process

For each: let’s look at whether an attempt at standardization for the Vanguard is realistic and to what degree, keeping in mind that localization is always an option.

Question on why to separate 9XX and non-9XX: good question to be discuss whether to consolidate or link between two decision pages

Question on standardization: is decision on level of standardization, all or nothing, or have standardization of a subset: all can be decided, i.e. on which option we would decide, also we make recommendations

Bibliographic records 9xx fields mapping for Vanguard

According to Alma campuses,, ExL will add old system ID into 035 which is searchable. See example Belinda provided [need copy from the chat]

019 vs. 035: migration and post migration process are different. during migration, if 019/035 being matched, will not add; If 019 not matched on 035z, you may have to export; if not matched will fallout

Bibliographic records to leave out of the Vanguard NZ

Non-9XX local data for the Vanguard

Voted recommendations for 973 be used for 793 or collection titles: 9 5s and 2 4s (mainly have not discussed with local yet)

Voted recommendation for campuses if plan to move current system ID, to 996, see decision page linked above.

Voted for added option 5 and campus will write which option used for Vanguard test that can be used to form decision post-Vanguard;

Liz will send the decision page to PCC.

For older system IDs (not the current one), getting feedback from campuses on: one field or two preferable, if one field (996), which subfield to recommend? get feedback by next Monday.

Share and get feedback from campuses to have discussion next week

Share and get feedback from campuses

Sandbox time: Primo and NZ/IZ edits [if time allows]

20 mins

deferred