Questions still exist about whether Vanguard sites will be able to grant access to non-Vanguard campuses.
Details are still being worked out as to how this will work, but it is Greg’s understanding that the cohort is discussing how best to make this work for bot the vanguard and non-vanguard campuses. More information to come.
Potential “buddy system” being discussed, for non-vanguard campuses to “buddy up” with a vanguard campus.
Concerns about patron privacy to be addressed.
There was a short discussion about ASCII characters that cause validation errors; [“\”, “&”' “;”]
UCB, UCSD, and UCSF (all Millennium vanguard sites) reported error in their extract file validations with certain special characters within the text of some fields; in particular the back slash character. Removing it from the identified data fields/files seemed to resolve the errors.
Whitespace surrounding the semi-colon was the source of an error, not the semi-colon itself.
Unknown if this is specific to Millenium → Alma migration or general to extracts.
2
Tasks & Deliverables
Revisit Assessment and testing plans for vanguard
10 min
Greg
While our group has accomplished our time driven tasks and deliverables for the front end of the project, as we are now in the vanguard phase, the PMs have asked the Patron Data Cleanup Group to identify potential assessment and testing plans or mechanisms for the vanguard.
From July 6th Minutes: From a Patron Data perspective, what assessment and testing ideas do we have:
Generally, data transfer integrity check.
Did data map to the proper fields? For instance, Note fields; public to public, internal to internal?
Do patron fields display properly?
Can names be searched, including names with special characters.
Barcodes: for campuses with multiple patron barcodes, did they all migrate? Did they migrate properly? Has it caused problems with ILL?
Is there a way to confirm that all of your records actually migrated?
So far testing and validation is a decentralized process.