Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Current »

Date

Zoom link in Google Calendar invitation.

Notetaker: Kevin Balster

Attendees

Not attending

Discussion items

Item

Desired Outcome

Time

Who

Notes

Discussion

Actions

Announcements

Share short pieces of need-to-know information

10 min

All

Preread: P2E Recommendations for Vanguard

CB: A&EFG recommending splitting up bib records with separate orders for print and electonic formats. Either cleanup before migration or after migration.
EQ: Cleanup implications if print and electronic orders are not split up.

MB: UCSC encountering 9XX fields that are intended for NZ use in the CZ. Were able to remove most 999 fields, but couldn’t edit if the CZ had some other error that needed attention first.
CB: We can only/should cleanup data that is our own. If it’s originating from the CZ or elsewhere in Alma, we can’t do anything about it.

Review of draft blog post for Harmonization based cleanup for Vanguard, including new recommendations regarding Non-OCLC 035s. 9XX mapping, and records to leave out of the NZ. Contact Catherine if you want to review before it is posted.

  • Erika Quintana to add entry for P2E Recommendations to blog post for Harmonization -Based Cleanup
  • Catherine Busselen to add discussion for Alma specific recommendations to agenda for 7/17 meeting

Review of Task List

Maintain Awareness of Incomplete Tasks

10 min

All

Review of Timeline and Specific Dates

Understand Where Data Cleanup related work fits into the whole migration timeline

20 min

C. Busselen

Swim Lane Timeline

Specific Dates pulled from Basecamp (subject to change)

Vanguard Phase

  • Month of July: upload testing for vanguard campuses

  • July 31: Final date to have all migration-related files and forms delivered to ExLibris and test load preparations completed

  • August 21: Configuration forms due (“final”, fulfillment network, PrimoVE)

  • September 2: load configuration form to Alma

  • September 4: Vanguard Test Load Delivery--Alma environment with UC vanguard test data; begin review of migrated data and initial configurations

  • September 10: Special Meeting topic “Using Alma for Data Review”

  • September 16: Delivery of PrimoVE in Alma Production

  • November 6: Vanguard Completion

Implementation Phase

  • November-December [specific dates unspecified]: Test load data preparation

  • January 3: Test Load start

  • February 5: Delivery of Test Environment

SS: Current thinking seems to be that everybody will be able to see the NZ, but only Vanguard campuses can access IZ, although use-cases may be made by those who need to test but are not part of the vanguard

CB: We need to create legitimate logins for Vanguard, so more people accessing it means more work setting those up. Also, Vanguard is really just to see how migration process goes, not intended for seeing how things display

TJK: for those interesting in just seeing how everything works, the sandbox is available.

ILS DC Recommendations for Vanguard Testing Brainstorming

Brainstorm testing needs for the vanguard

Make assignments for small group to work on fleshing out the testing guidelines

Follow-up assignment to add campus-specific decisions and sample records for testing to draft document

20 min

All

https://docs.google.com/document/d/1a8-DT7KzLMAsW3euLmg--vlbx4ApMIVkG9wTKUrRohg/edit?usp=sharing

CB: Brainstorm a few topics now, then create working group to take first pass at more comprehensive list (made up of non-Vanguard members since Vanguard folks will be busy with that). After Vanguard load, setup another working group (with Vanguard folks).

Up to working group members how to complete work. First pass deadline TBD

Future agenda items

Upcoming deadlines from IC for deliverables

Add recommendations and communicate following harmonization decisions

P to E as future agenda item after vanguard load.

  • No labels