4 | EDITED TO HERE | 5 | Timeline review Post questions in Basecamp as they come up (e. g., config form questions, other concerns). It’s open 24/7! | Stay up to date on timeline / deadlines: Basecamp To-Dos In the works: (reported 8/20) | 15 | Caitlinl or Lena | Config form: PPC will finish config form recommendations Friday 7th - DONE! DRAFT due 14th - DONE!Special meetings upcoming: Vanguard Environment Delivery Sept 4th Special Meeting: Using Alma for Data Review, Sep 10: No questions are needed in advance. The goal of this meeting is to help vanguard institutions understand how to look at their data and to be able to form questions. Primo delivery Sep 16 Special meeting first look at Primo Sep 17
Looking ahead…What defines “completion” for the vanguard? In general, the details below follow along with the Important Project Dates and Key Milestones To Do list on the UCS Basecamp athttps://3.basecamp.com/3765443/buckets/15553579/todolists/2379093736 as to what is accomplished during the Vanguard and when it ends (at the start of the full project implementation)Vanguard completion checklist: | | |
5 | ) https://3.basecamp.com/3765443/buckets/17573560/todolists/2935068623Ex Libris did extracts for the vanguard alma campus (UCSB) but this won’t be the case for the implementation test load. UCM will need to start earlier for WMS.
Major deliverables will be added to the PM Basecamp as additional To Do lists (Test Load, Configs, Primo VE, Integrations, and Cutover/Go Live).
Test Load high level dates provided, rest of line items will be added in over the next month (note change to final date for deliverables)
Configs and Primo VE will be added after being adjusted following the VGs completing their work (and OK of TL dates)
Integrations To Do should be prepped by kickoff
Cutover/Go Live To Dos will be high level until May (look at test load as a starting point) | 6 | Vanguard testing Alma campus IC recommendations for Data Testing | Round-robin with vanguard campuses: Share progress on local implementation test plans; anything you want to share with the group? anything the group can help you with? ICs to review their local implementation test plans and estimate how long testing will take. Report back at the next IC meeting. (Ballpark how long you think testing will take. We are trying to understand what September and October will look like. ) | 20 | Tom | ILSDC and Patron Data testing form https://docs.google.com/spreadsheets/d/1dFi7lbwbrXzYd4rr_rlvKcQCT0LRGKw7EzzxcuEgBeE/edit#gid=1257510643UC instruction begins on Oct 1 for fall quarter, so it would be ideal to get as much testing done as possible by then. UCB and UCM instruction begins August 26. Testing will not be coordinated overall; ICs will manage their own plan. Caitlin started a Vanguard testing decision page. UCLA needs a little time to confirm sysadmin accounts are properly set up before setting up accounts for others. UCB wants to be sure data is not corrupted before granting other accounts. Jeremy noted it's easy to goof things up in Alma. Need the data privacy to be determined before accounts are opened to other campuses. Accounts will be requested using this spreadsheet managed by SILS chairs; Figure out what the vanguard FG members should do sooner before accounts are available for other non-vanguard campuses. Vanguard buddy for Merced? Lynne would like to give accounts but then be able to ask these testers to help answer Alma questions they have. Primo VE will be accessible via a public URL for viewing by anyone. What expectations about setting permissions? Back and forth will likely be needed with requester to determine what they are testing. UCSB provided admin levels for testing but used a strategy for setting more specific roles for go live. For analytics, you can run user reports to see addresses, other private info.
Question: how will campuses communicate to ExL during testing? Basecamp? SalesForce?
Testing dates approved by ICs: By Sep 21, provided the data migrates well, vanguard campuses will open up accounts to FG testers. After September, non-vanguard local campus SILS teams can request access through their IC.
Changed permissions from “highest” level to the “appropriate” level for the testing at hand. | | 7 | | |
8 | Parking lot | Checkin about meeting times in August when we know more about work schedules/school commitments - we may need to shift meeting times/days to better accommodate IC’s schedule.
7 | Parking lot | | | | IC retrospective to share lessons learned (what went well, didn’t go well, do differently next time) - worthwhile? Just the ICs. Do it between the break between vanguard and test load. Invite FGs to present on their test plans at the Sep 3 IC meeting? Thank you, but not needed. | No need to invite FGs to present on their test plans to IC meeting. Many ICs are already familiar with these test plans since FG members are in their local implementation teams. | | 9 | | |