Repository navigation
RFC 091: record the Folio export path and park the minted id - #176
Merged
Merged
Conversation
Replaces the ingest app that found predecessors through the Identifiers API with the platform export tool scoped under platform#6669: a CSV of bib identifiers in S3, a Folio inventory lookup, MARC from mod-oai-pmh, and marc.xml for Goobi's existing mass import. The predecessor b-number is read from the instance's Sierra system number identifier. Adds a section on Axiell visual and AV material reaching the same path through the RFC 090 stubs, records the independent minted identifier as parked with its revisit triggers, updates the HRID confirmation state, and adds the AV e-bib rule as an open question.
A semicolon in a message label stopped Mermaid rendering the diagram.
…allel Records the 2026-10-13 thread: digital production have Sierra records to work from until March 2027, find the CSV round trip workable and would prefer an in-Goobi pull from Folio, which Intranda are asked to scope alongside the export tool. Trims the closing summary table to the rows that still decide something and notes where Axiell stubs and AV and visual material fall.
paul-butcher
approved these changes
Oct 23, 2026
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
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.
Preview
https://github.com/wellcomecollection/docs/blob/rk/rfc-091-folio-export-path/rfcs/091-digitisation-ingest-identifiers/README.md
What does this change?
Records the wellcomecollection/platform#6669 scoping of 2026-10-13. The ingest app that found predecessors through the Identifiers API becomes a platform export tool: a CSV of bib identifiers in S3, Folio inventory lookup, MARC from mod-oai-pmh through Okapi, marc.xml for Goobi's existing mass import, with the predecessor read from the instance's Sierra system number identifier.
How to test
.scripts/validate_rfc.pyand.scripts/create_table_summary.py --check-readmepass; the preview renders the sequence diagram.How can we measure success?
The export tool in wellcomecollection/platform#6411 can be built from this RFC without reopening the identifier decision.
Have we considered potential risks?
The HRID form still awaits sign-off from Digirati and Internet Archive; the RFC says so rather than claiming it. Companion: #175 for RFC 090.