Repository navigation
Conversation
The instance HRID is now assigned by FOLIO from the shared in sequence
rather than computed as AxC-instance-{guid}, because RFC 091 makes the
HRID the preservation identifier for anything digitised after the
migration. The instance is found again through a GUID to instance
mapping table with a self-heal query on the stored bare GUID; holdings
and items keep their computed hrids.
A new section records what a stub has to carry for digital production's
export tool: the identifier set (GUID twice, object number, RefNo under
its own type, predecessor b-number from 035 Bibliographic Number or a
b-number-shaped 907), an instance type per category, the stub marker
that replaces the AxC- prefix, and discovery suppression on create.
Open questions gain the Collections Information decisions these need,
the archivecatalogue restriction on the Axiell feed verified on
production on 2026-10-13, and the dev tenant mismatch.
This was referenced Oct 13, 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-090-digitisation-stubs/rfcs/090-axiell-folio-sync/README.md
What does this change?
RFC 091 makes the FOLIO instance HRID the preservation identifier after migration, and wellcomecollection/platform#6697 put visual and AV material in Axiell, synced to FOLIO. The stubs this sync creates are what the digitisation export resolves, so the RFC now says what they carry.
How to test
.scripts/validate_rfc.pyand.scripts/create_table_summary.py --check-readmepass; the preview renders the new tables.How can we measure success?
The sync change can be built from this RFC and the spec in location-movement-control-docs without reopening the identifier decision recorded in wellcomecollection/platform#6669.
Have we considered potential risks?
The 035 and 024 emission for stubs is inferred from mod-oai-pmh's rules rather than observed; the RFC says so and makes observing it an acceptance step.