De-symphonize cocina-models

[mjgiarlo]

NOTE: This issue is not required for the Folio cutover in August 2023 and should not be done until Andrew says it's time. Per @andrewjbtw:

When we discussed this in the spring, the initial plan was to leave the data alone for a while, rather than update the 3.5 million items that have catkeys to remove the catkey/“previous symphony” references.

• [ ] Remove references to Symphony & catkey in openapi.yml and regenerate models (per the README)
  • SymphonyCatalogLink
  • MigratedFromSymphonyIdentifier
  • CatkeyBarcode
• [ ] Remove references to Symphony & catkey elsewhere in cocina-models (e.g., in lib/cocina/models/factories.rb
• [ ] Cut a new cocina-models release and follow existing docs to make sure e.g. symphony references in openapi are removed from downstream apps' openapi configs.
  • [ ] dor-services-app: sul-dlss/dor-services-app/issues/4572
  • [ ] sdr-api: sul-dlss/sdr-api/issues/610

Cutover-Related Questions for Andrew/Arcadia:

1. What do barcodes look like when fully on folio? Currently, we support four different barcode patterns: /^2050[0-9]{7}$/ (for Business), /^[0-9]+-[0-9]+$/ (catkey-based), /^245[0-9]{8}$/ (for Lane), /^36105[0-9]{9}$/ ("standard")
   • Folio is not going to generate barcodes like Symphony did, so no new barcode patterns are needed.
2. Does this list of identifier types (which contains references to Symphony authority file identifier and Symphony catkey, but nothing Folio-related) need updating?
   • It does not, because the Folio instance HRID won't be in the MODS, and Folio doesn't have authority IDs at the moment.
3. Are there any ways outside Argo to trigger metadata refreshes? (If so, we'll need to make sure it is not possible to trigger refreshes from Symphony after cutover.)
   • There's a way in ETD, but that's being planned for elsewhere. Same re: Argo. So we think there's no work specific to cocina-models on this.
4. Should we plan to clean up Cocina metadata to remove Symphony catalog links?
   • Yes, but not until well after the cutover, so we defer for the purposes of this issue.
5. Is it helpful to write and run a report to ensure refresh parity between Symphony and Folio?
   • It could be, but since DSA is already set up to automagically keep catalog links in sync, it is of limited value.

[edsu]

From Planning: @andrewjbtw's understanding is that this can't be done unless we take Symphony out of Cocina. We need to figure out what the impact of not having catkey in the data might be, mostly in Access portfolio.

[mjgiarlo]

This work requires a giant prod data migration to remove all the Symphony catalog links.