Resource Management: We have a couple subgroups forming to look at local authorities and testing OCLC updates. FG members are reviewing a test template for our decision pages and will spend next week filling them in and setting priorities.
Discovery: Josephine learned that UCLA created a beta logo to be used for the VG. UCSF web team thought this was pretty straight forward and could be copied to give all the VG libs a standardized logo style. Josephine was surprised to learn that UCLA was working on a logo. This will be put forward as just testing for the VG. Xiaoli believes the word “BETA” may not have enough contrast. This will have to be discussed at campuses.
Marcive: PSELG would like to have just one copy of the record loaded into the NZ. What are the implications in terms of workflow? Who does the work? Should we just get a base file from Marcive so that no one needs to migrate their Marcive records into the system. This will be the cleanest way to move forward. Just collecting ideas, no decisions have been made. We should negotiate with Marcive on a contract if this approach is adopted.
RMFG: subgroup to review documentation on authority controls. Broad consultation is desirable. As long as it’s not a significant amount of their time and they get credit. Ask ExL for the 9/24 meeting date for authority control
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 20: Data cleanup pre-Alma test load regarding Libraries, Locations, Vendors, and Resource Sharing
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.
TBD: Authority Control - Ask ExL for 9/24 meeting date
@Christine Barone (Unlicensed) to contact ExL about having the Authority Control meeting on 9/24
3
Vanguard Testing
Thinking of proposals that allow flexibility in creating of guest accounts for non-VG members, e.g., should we propose that the access to network zone be given out sooner, especially for testing/configuring PrimoVE sitting on NZ?
Brainstorm strategies for testing given non-VG members may not have an account until Oct, e.g., using buddy system.
FG/ELG members who are from VG campuses will have accounts at their home campus in addition to any necessary non-VG accounts.
All accounts will be given “admin” level privileges in the appropriate modules, unless instructed otherwise.
VG campuses are targeting early October for adding non-VG members/guest accounts. They want to give local testers a chance to run tests before giving out guest accounts.
One possible work-around for this is for FG members in the VG to run testing for FG test scenarios.
FG/ELG testing:
Xiaoli’s testing template:
The PPC Steering Committee would like to have all groups complete documenting their testing scenarios by Aug. 28. If it's necessary, the SC will meet with individual groups to prioritize their testing cases after Aug. 28.
From Liz M: I like this, my group will be using a lot of Google docs to let us do more narrative work so having this to pull together a more succinct summary will be helpful this is the template I've drafted for my group to do testing:
How will the “buddy' system work/be utilized in this testing scenario? How will we utilize the “buddy” system well? At the chairs meeting the notion of having a VG campus whose data is ready to go be the campus that becomes everyone’s buddy. This is not confirmed. Would buddies have to work synchronously together? Not necessarily. Create testing scenarios first and then determine if cross group and synchronous testing needs to occur. Maybe it’s ok to buddy as needed rather than pre-determining who should buddy. Fill out the testing worksheet as much as you can and then confer with PPC steering committee.
Does the worksheet viable? yes Anything you would want to change? Is Aug 28th deadline appropriate?
Who is giving out the NZ accounts? CDL? Who is doing the centralized Primo VE (back end accounts for config) accounts?
How long does each FG estimate testing will take? a few hours, a few days, 1 week, more? Will have a better sense when scenarios are generated and depending on buddy system and how well that works. How soon will the NZ be open so that testers can evaluate data? Maybe only one campus does the work and reports back to everyone.
Should PPC meet during testing? Will everyone be too busy? Reconsider this in September. We may be able to cancel some meetings to give time back to testers.
ICs are interested in inviting FGs to present their test plans at an IC meeting (not sure if any action has been taken yet on this.)
Complete the Vanguard SILS Cohort Testing accounts by Aug 28
To perform testing in the VG environment, participants need to have at least completed the relevant Alma essentials training for the modules they are interested in.
@Christine Barone (Unlicensed) find out the process for Primo VE back end accounts for VG testing and how access to NZ is going to work for people to get accounts.
4
Homework
5
Parking Lot
Xiaoli is on vacation next week. Claudia will send out a new zoom link just for that meeting
For September: revisit whether PPC should cancel any meetings in Sep/Oct to accommodate testing.
6
TOTAL
80/ 80
Future agenda items
The SILS mission is to transform library services and operations through innovation and collaboration. The future is shared!
Question? Contact AskSILS-L@ucop.edu