Skip to content

Phase 5: DOI version-mint reconciliation (orphaned reserved DOIs) #900

Closed

Description

@neuromechanist

Part of epic #896.

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.

Priority: P1 (permanent artifact; narrow crash-window trigger).

Activity

  1. added
    P1High priority - important features, significant bugs
    featureNew feature or enhancement
    on Jul 2, 2026
  2. added 2 commits that reference this issue on Jul 6, 2026
  3. neuromechanist commented on Jul 7, 2026

    @neuromechanist
    ContributorAuthor

    Shipped in epic #896 (merged to dev via #943).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1High priority - important features, significant bugsfeatureNew feature or enhancement

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions