Skip to content

Zenodo deposition for iSamples query substrate — 202601 snapshot #139

@rdhyee

Description

@rdhyee

Context

Plan file at the iSamples monorepo root: ZENODO_DEPOSITION_PLAN.md. Drafts a one-deposition-per-snapshot structure for archiving the query substrate to Zenodo — roughly 1.52 GB across 10 files for the 202601 snapshot.

Currently these files live on Cloudflare R2 (pub-a18234d962364c22a50c787b7ca09fa5.r2.dev). Zenodo gives us DOI-citable, versioned, long-term-archival storage for grant deliverables and reproducibility of the June 2026 keynote / workshop materials.

Credentials

Zenodo API key is durably stored at op://Automations/Zenodo API Key 2025.04.24/credential (verified working).

Scope

  • Narrow parquet (106M rows, ~844 MB)
  • Wide parquet (20M rows, ~282 MB)
  • samples_map_lite.parquet (for Explorer)
  • H3 tier parquets
  • README + schema docs
  • Total ~1.52 GB, 10 files

Open decisions (5)

  • Creator list + ORCIDs — who's listed as creator? Raymond, Hana, Stephen, Kerstin, Bill, Dave? ORCIDs for each.
  • License — CC-BY-4.0 recommended; verify compatibility with source data licenses (OpenContext, SESAR, GEOME, Smithsonian)
  • Narrow-snapshot label mismatch — narrow file is dated 2025-12-12 (zenodo_narrow_2025-12-12.parquet, labeled 202512); wide is 2026-01-09 (202601). Do we rename, re-snapshot, or annotate?
  • Stale draft handling — prior Zenodo drafts from earlier iSamples work: delete, supersede, or ignore?
  • isDerivedFrom phrasing — how to express upstream provenance (source collection DOIs where available) in Zenodo metadata

Acceptance

  • Deposition published with DOI (or reserved DOI, if we want to land site changes against it first)
  • Landing page on isamplesorg.github.io cites the DOI as canonical archival location
  • R2 URLs remain the live access path; Zenodo is the archival mirror

Related

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions