| Item | Desired Outcome | Time | Who | Notes | Decisions | Actions |
|---|
| 1 | Check-in / updates | Information sharing and problem solving | 2:30-2:55 pm (25 mins) | All | Xiaoli is on vacation this week. FYI: The “Determine the plan for Melvyl” blank decision page has been removed, and the Melvyl and Related Services in SILS page supersedes it. Fulfillment: draft form for fulfillment config due today. Final is due next Friday 8/28. Discovery: received a Q at the TH about branding. EUOS met with someone (confirm who this is with PMs) that they will be meeting with a graphic designer RE branding. Discovery is working on the user interface brand. Would like to rename this as simply user interface since the word branding carries a lot of baggage. Who will be evaluating branding? Josephine’s group has created a checklist for campuses. RMFG- putting together their test template. Maybe discuss this more later
| | |
| 2 | Timeline Review | Awareness of upcoming dates and activities | 2:55 (1 minute) | Christine | Basecamp to-dos: https://3.basecamp.com/3765443/buckets/15553579/todosets/2379093663 Timeline on Confluence: Implementation Timeline Vanguard dates: Sep 4: Vanguard environment with test data is available Sep 16: Primo VE is ready for review and testing Sep 17: Special meeting to introduce Primo VE
Special topics: Aug 27: Shared Vendors (and managing e-resources in NZ) Sep 21: RLFs - This will be an informational meeting for ExL. RSPG presents to ExL and allows ExL to ask questions. All interested FGs are welcome to attend. Sep 24: Authority Control Oct 1: CDL-managed Data subgroup
| | |
| 3 | IC & WG updates | | 2:56-3:00 | Christine | Decision page: Vanguard Testing Policies and Procedures Some points to note: They edited these bullets of the timeline: 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.
They edited this first bullet of the “Accounts” section to say “appropriate” priviledges: They added to the Project Test Plan section that host campuses will request assistance:
In order to get an account for the VG environment, you will need to confirm your compliance with FERPA requirements (data and privacy). This is because staff at member institutions may have logins to other institutions' Alma environment. You should receive something more about this in the next week or two. Qs: Who needs to sign this? everyone? even VG ICs? A: Anyone who is in the VG environment, whether they are testing other campus' data or not, needs to sign. Includes the ICs. Who needs/gets NZ access (outside of CDL)? IZ/NZ coordination for analytics; how is this requested on the form? Make your best case for why access to NZ is needed (what are you testing?)
| | |
| 4 | SILS Chairs | Topics for the agenda | 3:00-3:05 | Christine | Would there be value in presenting testing plans at the next SILS Chairs meeting? Feeling like test plans may not be ready for prime time at that point. Also, testing may be too specific to the group doing the testing and not of much interest broadly speaking. Discovery has a solid enough checklist that could be easily shared. AcqErm could share broad contours. RMFG has an overview doc they could bring to share. Could be a good opportunity to get feedback and other eyes on it. | | |
| 5 | ILS Data Cleanup checklist | Approve the page with any PPC / FG additions. | 3:05-3:30 pm | All | https://docs.google.com/spreadsheets/d/1dFi7lbwbrXzYd4rr_rlvKcQCT0LRGKw7EzzxcuEgBeE/edit#gid=0 This list goes next to ICs for local campus vanguard testing. This is not intended for FG systemwide use - those test plans should be somewhere else. The list is also mostly related to migrated data validation and NOT to workflow or process validation. Those kinds of things should be documented elsewhere… Have PPC members reviewed this list. Anything to add? If PPC has other recommendations for local groups to do - where does this go? How do we disseminate this to the local groups?
To ICs: Please do not use this MASTER copy in your testing - please make a copy and fill out locally. | This was approved by PPC | |
| 6 | Vanguard testing | Clarify expectations around who has permissions to do what | 3:30-3:40 | Claudia / Josephine | Proposal: Discovery FG should be in charge of configuring the NZ Primo VE for their testing purposes. (i.e. not making config requests to CDL / Alison) Makes sense that Discovery should be in charge of configuring NZ in Primo VE for testing. Does Discovery need to fill out config forms? If so, by when? A. Alison has been in charge of the network zone configuration stuff and was told that she didn't / no one has to do that at this time. Ex Libris is going to set up the default config for the network zone and then we just go in the live instance. CDI (central discovery index): is Discovery the ones to evaluate this?
| | |
| 7 | Homework | | | | | | |
| 8 | Parking Lot | | | | | | |
| 9 | | TOTAL | / 80 | | | | |