2022-03-04 - Data Migration Subgroup Agenda and Notes

LibMich going live summer 2022; Duke summer 2023; Stanford 2023; Marmot Library still investigating, Western Colorado might go next year

Stanford currently not using old bib identifier as HRID for instance; everyone recommends they start using old bib ID!

deterministic UUID is recommended as well, so don’t have to keep a map for later linkings (orders, loans, boundwiths)

Duke working on deletes, performance issues (need a Jira for this); also importing boundwiths. Deleting with boundwiths tricky

topics for future meetings

• add non-technical topics?

Perhaps general migration planning/strategy? e.g. how to make a plan.  how do we think about how the data is organized in different systems.
how to take advantage of the migration for cleanup. Airflow could lend itself to post-migration cleanup and post-migration workflows.  Lot of potential in that work to compose processes.  We don’t have a lot of toolsets, but there are a lot of principles that you should consider when starting: It’s a collaboration with SMEs and technical folks; understand data; make a mapping

Advertise the agenda on #general or maybe #implementers