Vanguard Testing Policies and Procedures

Legend: not started IN PROGRESS STALLED decided

Recommended Process

Timeline:

• Sept 4th: ExL releases the vanguard (VG) environment; VG ICs will get sysadmin accounts to start making new accounts as needed. (Update: Some instance were delayed until Sep 8.)

• Sept 7th holiday

• Sep 4-21: Moratorium on any type of bibliographic and holdings records work by vanguard campus or SILS groups that could impact data in the NZ until 9/21/2020.This would preserve the data in its migrated state and allow for Resource Management FG to do their data review.

• Sept 10th: ExL presentation on evaluating data in the VG

• Sept 16th: ExL releases the Primo VE environments

• Sept 17th: ExL presentation on “First look at Primo VE” in vanguard

• Sept 21st: Provided migration was successful, Vanguard campuses will begin creating FG Test accounts. Roles will be assigned based upon requested test function.

• After September, non-Vanguard local campus SILS teams can request access through their IC.

• Oct 5-9: Vanguard Alma Workshop

• End of October: Lessons learned show and tell

• Nov 5: Implementation kickoff

• End of Dec: Vanguard environments decommissioned

Accounts:

• Sysadmin (high privilege) accounts will be given to VG campus ICs at the same time as the environment is released. Those sysadmins will create new local accounts with appropriate privileges to manage system needs and do local testing.

• Local VG campus SILS testers will be given accounts as coordinated by the IC.

• SILS Cohort testers (whether VG or non-VG) will be given accounts as needed by the ICs, as requested from this form: (SILS group chairs fill this request form out): https://docs.google.com/spreadsheets/d/1TdOXbR7E13UUZPWsx2NYkfP-jCkNq3TDgsmxZQYOKQo/edit#gid=0

• The appropriate permission levels will be provided for the test expectation.

• All accounts will be for named staff members and associated with a UC email account (for data privacy tracking concerns); no accounts will be shared.

• Before receiving an account, everyone must complete the Acknowledge of Data Security Responsibilities form.

Project Test Plan:

Test plan overview

1. ICs will be spearheading local testing and distributing local accounts in the VG instances.

   1. Each IC/local VG campus is in charge of their own test plan(s) and accounts

2. FG Chairs will be spearheading systemwide testing, and will be requesting VG instance accounts for non-VG FG members as needed on this form https://docs.google.com/spreadsheets/d/1TdOXbR7E13UUZPWsx2NYkfP-jCkNq3TDgsmxZQYOKQo/edit#gid=0

   1. FG members who are from VG campuses will have accounts at their home campus in addition to any other necessary accounts.

3. Non-VG local campus staff who wish to view VG data can request an account after September 2020. Host VG campus will request that the guest provide assistance as requested in exchange for access.

Specific Test Plans:

Local campuses are responsible for their own test plans, focusing on local campus data and configuration needs, and vanguard local testing will not be coordinated at the SILS IC level. Local campus testers can take advantage of shared resources and examples here: https://uc-sils.atlassian.net/wiki/spaces/IC/pages/644907623

In addition, the unified Recommendations for Vanguard data migration testing plan has been approved by the ILSDC (8/14), the Patron Data group (8/17), and the PPC (8/21) and represents a basic UC data validation checklist that each local campus should use as a baseline (and add or subtract as needed.)

SILS Functional Groups are responsible for their own test plans as well, focusing on systemwide workflows and policies, and FG testing will not be strictly coordinated at the SILS PPC level. FG members can find their test plans in their specific Google Drive folders.

Network Zone testing:

• Alison Ray (CDL IC) will be the primary point person for accounts and basic configuration in the NZ.

• The CDL Data in the Network Zone SILS group will be primarily responsible for testing shared data in the Network Zone.

• The Discovery FG will be primarily responsible for configuring and testing the NZ Primo VE instance.

• Accounts to test other functionality in the NZ can be requested as needed on the spreadsheet.

Coordination between local campus testing and FG testing:

Where coordination is needed between local testers and FG testers (for example because of potential overwriting of data, or overlapping work), the campus FG member is primarily responsible for coordinating between the needs of the Functional Group and the local testing, and can loop in the campus IC and FG Chair as needed.

Moratorium on bibs/holdings work until 9/21:

The ICs are recommending a moratorium on any type of bibliographic and holdings records work by vanguard campus or SILS groups that could impact data in the NZ until 9/21/2020.This would preserve the data in its migrated state and allow for Resource Management FG to do their data review. This moratorium would not apply to local vanguard testing on Fulfillment and Resource Sharing, or Acquisitions, whose testing would not result in changes to bibs and holdings data in the NZ.

Dependencies

• Testing cannot begin until the data security subgroup (WG) delivers a statement for testers to acknowledge they will abide by data security policies during phase 4 implementation for testing and configuring. See Acknowledgement of Data Security Responsibilities form under “Links” below.

Links

Account Request sheet

Acknowledgement of Data Security Responsibilities form

Recommendations for Vanguard data migration testing worksheet

Alma campus IC recommendations for Data Testing

Action Log