RFC 088: Record the barcode sequence service#158
Open
kenoir wants to merge 1 commit into
Open
Conversation
Resolves Open Question 4's barcode direction. New patrons are now minted a
numeric, sequential card number by a sequence service (a DynamoDB atomic
counter) at first login, instead of receiving the bare Auth0 id. This updates
the question to record that decision and narrow what remains open to the
concrete seed/prefix/width and reader-support sign-off, removing the stale
24-character-format concern.
Also notes the barcode minting in the login-and-enrichment flow, adds the
POST /m2m/sequences/{name}/next route to the API surface, and carries it into
the OpenAPI spec (openapi.yaml + regenerated openapi.md).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
kenoir
changed the title
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.
Preview (rendered on this branch): RFC 088 README · openapi.md
Amends the merged RFC 088 to record how new patrons get a library-card barcode, replacing the now-superseded description.
Why
RFC 088's Open Question 4 (Barcode and role) still described the old approach: new users received the bare Auth0 id as their barcode, with an open task to "verify the 24-character barcode format". That approach was replaced during prototyping. New patrons are now minted a numeric, sequential card number by a small sequence service (a DynamoDB atomic counter) at first login, which keeps the printed and scanned card representation numeric, as it is today. The RFC was therefore wrong on this point; this corrects it and resolves the open question down to the parts that genuinely remain open.
What changed
/m2m/enrichmints the barcode when the FOLIO record has none (allocate-once, best-effort, retried on next login rather than blocking it).POST /m2m/sequences/{name}/next.openapi.yaml, withopenapi.mdregenerated viarender_docs.py. All referenced components already existed, so the addition is self-contained.The RFC index
Last modifieddate is synced via the generator script. No other RFCs are affected.Scope note
The sequence service is a sub-feature of the v2 identity API, not a standalone service: it shares the m2m Lambda, API Gateway and authorizer, lives inside the folio-api spec, and has no consumers outside the identity API. So it belongs in RFC 088 rather than a new RFC.
🤖 Generated with Claude Code