Conversation
…SP resources for assisting with this process
There was a problem hiding this comment.
Pull request overview
This PR updates the data management documentation to provide clearer, consolidated guidance for creating dataset DOIs and citing/publishing datasets (per ticket #69), including an added graphic to clarify DOI pathways.
Changes:
- Adds a “Navigating DOI Options at LASP” section (with a new DOI options graphic) to the DOI overview page.
- Merges the “creating a DOI” guide content into the “Publishing and Citing Datasets” guide and deletes the standalone page.
- Expands publishing options and quick-start instructions for DataCite/CU resources.
Reviewed changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated 6 comments.
| File | Description |
|---|---|
| docs/source/data_management/digital_object_identifiers.md | Adds DOI option navigation section, promotes registries to subheadings, includes new DOI options graphic. |
| docs/source/data_management/citing_and_publishing_datasets.md | Consolidates DOI creation guidance into the dataset publishing/citation guide; expands options and links. |
| docs/source/data_management/creating_a_doi.md | Deletes the standalone DOI creation guide after merging its content elsewhere. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| 2. **Create a DOI and Landing Page** - Register a persistent identifier that resolves to a landing page with comprehensive dataset information. | ||
| 3. **Maintain Metadata** - Keep DOI metadata accurate and up to date | ||
| 4. **Cite Datasets Properly** - Follow established data citation principles in publications. Reference |
There was a problem hiding this comment.
The workflow list has a numbering mistake (two items labeled "2."). Update the numbering (or use Markdown’s auto-numbering style) so the steps render and read consistently.
| 2. **Create a DOI and Landing Page** - Register a persistent identifier that resolves to a landing page with comprehensive dataset information. | |
| 3. **Maintain Metadata** - Keep DOI metadata accurate and up to date | |
| 4. **Cite Datasets Properly** - Follow established data citation principles in publications. Reference | |
| 3. **Create a DOI and Landing Page** - Register a persistent identifier that resolves to a landing page with comprehensive dataset information. | |
| 4. **Maintain Metadata** - Keep DOI metadata accurate and up to date | |
| 5. **Cite Datasets Properly** - Follow established data citation principles in publications. Reference |
| - [Field Descriptions for DOI Form](https://support.datacite.org/docs/field-descriptions-for-form) | ||
| - [DataCite Metadata Quality](https://support.datacite.org/docs/metadata-quality) | ||
| - [DataCite Community Responsibility](https://support.datacite.org/docs/community-responsibility) | ||
| - [Data Citation Roadmap (Scholarly Repositories)](https://www.biorxiv.org/content/biorxiv/early/2017/10/09/097196.full.pdf) |
There was a problem hiding this comment.
This link entry is duplicated earlier in the same list ("Data Citation Roadmap (Scholarly Repositories)" also appears above). Remove one of the duplicates to avoid redundancy.
| - [Data Citation Roadmap (Scholarly Repositories)](https://www.biorxiv.org/content/biorxiv/early/2017/10/09/097196.full.pdf) |
| - [DataCite Community Responsibility](https://support.datacite.org/docs/community-responsibility) | ||
| - [Data Citation Roadmap for Scholarly Data Repositories](https://www.biorxiv.org/content/biorxiv/early/2017/10/09/097196.full.pdf) | ||
|
|
||
|  |
There was a problem hiding this comment.
The responsibilities sub-list under step 6 is indented, but the image that follows is not, which will end the list and render the image outside of step 6 in Markdown. Indent the image so it remains part of step 6 (or add text clarifying it’s a standalone figure).
|  | |
|  |
| ## Navigating DOI Options at LASP | ||
| There are internal and external options available for creating DOIs for various types of products | ||
| including datasets, software, and presentations. If you're not | ||
| sure where to start, reach out to the LASP Data Management team for guidance by submitting | ||
| a Jira issue with type "DOI" in the [Data Management Jira project](https://jira.lasp.colorado.edu/projects/DATAMAN/). | ||
|
|
There was a problem hiding this comment.
Since creating_a_doi.md was removed, ensure this new section doesn’t leave any stale references behind (the same page’s "Useful Links" section still links to creating_a_doi.md, and the Data Management toctree includes it). Update those links to the merged guide to prevent broken navigation/builds.
| sure where to start, reach out to the LASP Data Management team for guidance by submitting | ||
| a Jira issue with type "DOI" in the [Data Management Jira project](https://jira.lasp.colorado.edu/projects/DATAMAN/). | ||
|
|
||
|  |
There was a problem hiding this comment.
The alt text "DOI_Format" doesn’t describe this image (it’s the DOI options graphic). Use more descriptive alt text so screen readers convey the correct content (and to distinguish it from the existing doi_format.png figure).
|  | |
|  |
| ## Quick Start Guide | ||
| As of 2018, CU Libraries is a member of DataCite. Through this membership, LASP can mint and | ||
| register a limited number of DOIs for datasets housed in our repositories, enabling data to be persistently identified, | ||
| accessed, and cited. For LASP-affiliated datasets, researchers can work with the LASP Data Management team | ||
| to create DOIs and get advice on CU resources available to support publishing datasets. |
There was a problem hiding this comment.
This guide now contains the content that used to live in creating_a_doi.md. Make sure the rest of the documentation no longer links to creating_a_doi.md (e.g., it’s still referenced from the Data Management toctree and digital_object_identifiers.md), otherwise the docs site build/navigation will have broken links after the file deletion.
This PR addresses ticket #69 to provide clearer dataset citation guidance. A graphic was added to clarify options for creating DOIs and two guides were merged into one for simplicity since they overlapped in content
Closes #69