π€ rbotyee (Claude, operated by @rdhyee) β Raymond's intent (2026-08-27): set the deposit's license to the more restrictive option now, as the cautious move in the absence of firm guidance, and flag it here as open to relaxation. His words: "CC-BY is probably the right long-term choice but attaching SA-NC is for the cautious move in the absence of firm guidance." What I did: set Zenodo draft 21288719 ("iSamples Query Substrate β Snapshot 202601") to CC-BY-NC-SA-4.0 via the deposit API (was cc-by-4.0, a placeholder); opened this issue; started a survey of the four sources' data-use terms.
Why NC-SA, and why it is not settled
- The parent record β the April 2025 complete export, 15278211 β is CC-BY-NC-SA-4.0. It was deposited from Raymond's Zenodo account on 2025-04-25 while he was "waiting on Dave and others to tell me how to proceed in terms of license" (his journal, 2025-04-28). No recorded answer to that question has been found (email, Slack, notes). So NC-SA on the parent is a cautious placeholder, not a rights-holder requirement we know of.
- The February 2025 OpenContext-only export (14927593) is CC0.
- The records themselves carry no rights statement (
dc_rights is NULL on all 6.68 M rows across SESAR, OpenContext, GEOME, Smithsonian).
- Rule applied: a derived deposit should not be more permissive than its source without authority from the rights holders. Matching the parent is the defensible floor today.
What would let us relax it
A survey of what each source actually permits for its metadata records (SESAR / IEDA, Open Context per-project licenses, GEOME, Smithsonian Open Access), then a decision by the PIs (@athomer, Kerstin). Survey results will be posted here. Zenodo allows editing the license of a published record without a new version, so publishing now under NC-SA does not lock this in; and since 15278211 is also on Raymond's account, the parent can be relaxed at the same time.
Related
π€ rbotyee (Claude, operated by @rdhyee) β Raymond's intent (2026-08-27): set the deposit's license to the more restrictive option now, as the cautious move in the absence of firm guidance, and flag it here as open to relaxation. His words: "CC-BY is probably the right long-term choice but attaching SA-NC is for the cautious move in the absence of firm guidance." What I did: set Zenodo draft 21288719 ("iSamples Query Substrate β Snapshot 202601") to CC-BY-NC-SA-4.0 via the deposit API (was
cc-by-4.0, a placeholder); opened this issue; started a survey of the four sources' data-use terms.Why NC-SA, and why it is not settled
dc_rightsis NULL on all 6.68 M rows across SESAR, OpenContext, GEOME, Smithsonian).What would let us relax it
A survey of what each source actually permits for its metadata records (SESAR / IEDA, Open Context per-project licenses, GEOME, Smithsonian Open Access), then a decision by the PIs (@athomer, Kerstin). Survey results will be posted here. Zenodo allows editing the license of a published record without a new version, so publishing now under NC-SA does not lock this in; and since 15278211 is also on Raymond's account, the parent can be relaxed at the same time.
Related
pqgcode has no license file yet β README says "see LICENSE" but no LICENSE file exists β which license?Β pqg#25 (separate question: code, not data).