Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Date

​​​​10am - 11a

Attendees

  • Ross Anastos, UC Merced

  • Lai Arakawa, UC Irvine

  • Greg Ferguson, UC San Diego

  • Lacey Grawe, UC Riverside

  • Stephen Gurnick, UCLA

  • Marti Kallal, UC Santa Barbara

  • Andy Panado, UC San Francisco

  • Dave Rez, UC Berkeley

  • Ryan Schwab, UC Santa Cruz

  • Derek Sisneros, UC Davis

Not attending

  •  

Discussion items

Item

Desired Outcome

Time

Who

Notes

Decisions

Actions

1

Housekeeping

  • Add any new topics to the agenda

  • Take a temperature check / How is it going?

  • Confirm Minutes Recorder for this meeting - Ryan Schwab

    • In the event that the designated Recorder or Timekeeper is not in attendance, then an alternate volunteer will be requested for that given meeting

 

5 min

Greg

Shared Google drive

Follow-ups:

  • 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.

  • 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.

 

 

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?

Test Scenarios Brainstorming Document posted to Google share

3

Open Forum

  • Opportunity to ask anything

TBD

Greg

4

Homework

  • Document what we need to be working on and questions we may have

 

 

 

 

All - (ONGOING) Add questions for up stream

Alma Sites

  • Share any lessons learned on document to help with future agenda topics

All 

Add post-migration patron data testing ideas to the document in the shared Google Drive.

5

Parking Lot

  • Capture important topics for future discussion

 

 

  • Additional Circulation Data Topics to Think About

  • Alma/Primo Sites - Show and Tell

    • Dedicate some time to “what went wrong or what was great” to mentor “new” campuses.

  • From Governance Charge

    • A register of post-migration quality control tests and results from each campus implementation team. Due late 2021.

      1. To be discussed at a later date

    • A final report of any ongoing post-migration data issues. Due late 2021.

      1. To be discussed at a later date

 

 

6

 

Total

x/x

 

 

 

 

 

  • No labels