RFC 091: scope the merge-behaviour notes to library material - #165
Merged
Conversation
Cross-reference RFC 092 and qualify the two statements that read as covering all digitised content; the archive path has a CALM/Axiell merge target and no Folio record. Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
RFC 091 states that the Sierra work is always the merge target for digitised content and that post-migration digitisations attach to Folio-sourced records. Both hold for library material only: digitised archive material merges into a CALM (later Axiell) target and deliberately has no Folio record, the path now recorded in RFC 092 (rfcs/092-digitised-archive-links).
This amendment qualifies those two statements and adds RFC 092 to the related list, so the two documents no longer disagree about the archive path. It changes no decisions. Amending RFC 091 was a named next step of RFC 092 (#164).
Preview the amended RFC: https://github.com/wellcomecollection/docs/blob/rk/rfc-091-archive-scope/rfcs/091-digitisation-ingest-identifiers/README.md