Suggest A Dataset¶
We highly welcome additions that can help CUSP grow, whether they come from an unpublished personal collection, a field campaign, a data repository, or a published source. A dataset does not need to be ready for ingestion before it is worth suggesting.
All fields in the dataset-candidate issue form are optional, but it is helpful if you can complete as many as possible.
Information To Include If You Have It¶
Any of the following can help us understand and evaluate a suggested dataset:
- a dataset landing page
- a DOI or other persistent identifier
- a paper with supplementary data
- a project page describing field observations
- a repository record from Arctic Data Center, NSIDC, ORNL DAAC, PANGAEA, Zenodo, Dryad, DataONE, or a similar archive
What We Look For¶
High-priority candidates usually have:
- observation-like rows rather than only gridded or modeled output
- coordinates or site locations
- observation dates or years
- permafrost presence, active-layer thickness, thaw depth, frost-table depth, or depth-to-permafrost information
- enough citation and licensing information to support public reuse
Maintainers use issue status and simple priority labels to track progress. If a candidate is not a fit for CUSP, the issue can be closed with a short reason so the decision remains findable.
Suggest A Dataset¶
Open a dataset candidate issue here: