Skip to content

🗂 VCell — Zenodo release archiving #1718

Description

@jcschaff

🗂 Master issue — VCell Zenodo release archiving · on the VCell board.

Why — Every important VCell-family release should have a stable, citable DOI with correct attribution, so papers and reuse can point at an exact version. Historically releases weren't archived consistently, and some landed under fragmented concepts with mismatched authors.

What — Reproducibly archive VCell-family releases to Zenodo with correct titles, version lineage (continues across versions), and curated per-era author lists (contributors reflected accurately, PI credited last). Backfill the history, keep new releases archived going forward.

Scope — vcell, pyvcell, vcell-solvers, cam-center/SpringSaLaD.

How — driven by the shared zenodo-maint tool (reusable GitHub Actions: archive-on-release + drift monitor) rather than the fragile native Zenodo↔GitHub webhook; author lists come from a curated authorship pipeline.

Status

  • ✅ Historical releases backfilled; vcell-solvers onboarded (native webhook disabled).
  • 🔲 SpringSaLaD author-list correction — pending PI sign-off, targeted 2026-07-07.

Per-repo archiving PRs (evidence)

Coordination inbox: comment with progress/handoffs (what moved + PR/commit links); the lead posts a periodic status summary.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions