You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Phase 5: DOI version-mint reconciliation (orphaned reserved DOIs) #900
Problem: In createEzidVersionDoi (backend/src/services/doi.ts), if createIdentifier (status reserved) succeeds but a prior attempt crashed before makePublic, the retry hits the "already exists" branch and returns the still-reserved identifier early without ever calling makePublic. The webhook then writes latest_version_doi to D1 regardless of status. Result: a permanent EZID DOI that does not resolve, recorded as the dataset's latest version. Flagged independently by the backend and data reviews.
Fix:
On the "already exists" path, check status and finish the transition (makePublic + concept HasVersion update) instead of returning early.
Add a mint-progress state column so an interrupted mint is detectable across the request boundary.
Add a reconciliation sweep (mirror archiveRetrySweep) that finds DOIs stuck reserved and completes or reports them.
Activity
Address #900 review: rotation coverage + tombstone guard
Phase 5: DOI version-mint reconciliation (#900) (#940)
neuromechanist commentedon Jul 7, 2026
Shipped in epic #896 (merged to dev via #943).
fix: publish a reserved version DOI with fresh metadata
Phase 5: the code the anonymous fixture needs, and what building it f…