Page Comparison

Item

Desired Outcome

Time

Who

Notes

Discussion

Actions

Announcements

Share short pieces of need-to-know information

10 min

All

• Next Weekly project update meeting on RLFs (URL)

• Ex Libris Meeting Records (URL)

• SILS Vanguard October Workshop, October 2-9 (full schedule)

Migrated data review by Vanguard libraries

Share observation and learn about Vanguard migration results

30 min

Catherine Busselen Cathleen Lu Ryan Finnerty Kathleen Garvey-Clasby (Unlicensed) Kevin Balster

• Kevin / UCLA

  • Multi-match report (IZ matches 2+ NZ many of them are EEBO issues or may be CZ issues) Other issues may also be due to the way the records were loaded into NZ then IZ.

    • Multi-matches: CZ matches were not intended, so may be reconciled by go-live (hopefully)

    • Catherine: perhaps check for percentages of multi-match reports from Vanguard Libraries to see differences and rates of duplication.

    • For Multi-Matches: Create a sub-set of records to link to the NZ and then reduce list to a more manageable number. Potential post-migration clean up for campuses.

• Catherine / UCSB

  • Suppressed records, things that came out of extract that we’d perhaps have to develop pre- or post-migration clean up actions.

  • MMS ID: NZ and IZ MMS IDs are different but are in similar places, based on when you are viewing in NZ or IZ. This can be confusing for Alma users.

  • The NZ tab is missing (ticket to ExL has been sent)

  • Sets came over for individual members, but Admin sets did not migrate correctly.

  • E-resources migrating strange in NZ but not migration issue; RM and E&A groups may need to investigate.

  • Create list of data fields or types where other library’s IZ information is in local IZ. Were these marked properly and migrated wrong? Or were not marked properly as local IZ data? We can check local coding first to ensure local IZ data was updated, and is a true migration issue.

  • Total record/Alma data counts came in as expected, but analytics did not migrate as expected, but hoping will migrate for go-live.

  • Possible to ask EXL to exclude any records with specific 9xx as requested, for any suppressed, SCP, or other records that you don’t want to migrate to NZ.

• Ryan / UCSD

  • E-portfolios that are “blank” which were hybrids that did not migrate properly. Will review to possibly de-duplicate.

  • Issue with 10,000 linked item records that they need to “unlink” to avoid this problem - aka boundwiths

  • Leader and resource type issue.

  • Holdings issues with 866 and other data not matching; will need to be cleaned up.

  • Holdings with same Location: all holdings were made for all locations, but items only set to “first” holding - will also have to be cleaned up either pre-migration or post.

  • Fields not coded into local areas, e.g. 790 needs to be migrated to local field to not be lost.

• Kate / SCP

  • One file of data that not all files migrated, several thousand records missing.

  • Duplicate analysis:

  • Some e-resources were migrated as a database that should be portfolio instead, will review the e-resources.

  • Will try to work on getting legacy data in NZ (with ExL).

• Kathleen / UCSF

  • Material and resource types not showing up correctly (correcting leader)

  • Serials with holdings available, but no items available, will need to find way to add inventory.

  • Some data was not given local status but UCSF lost the data in IZ: e.g. 541, 793, even though they were the only IZ and NZ record -the data was still lost. Issue may be sent to ExL via Basecamp.

  • Large number of multi-matches (double UCLA numbers), perhaps due to being a later campus, but it may a different issue

TJ Kao may develop some kind of google doc with Vanguard issues found, to share found and noted issues for all campuses (tent)