Space menu
Curation Status Labels
# Curation Status Labels
## What are Curation Status Labels?
DataverseNO uses **Curation Status Labels** to support the management of datasets undergoing curation.
Combined with automatically assigned publication-status labels, Curation Status Labels help curators communicate and track the status of dataset drafts throughout the curation process.
Curation Status Labels are:
- Assigned manually by curators.
- Only available for dataset drafts.
- Visible to curators and depositors with access dataset drafts.
- Automatically removed when a dataset is published.
- Mutually exclusive, meaning that only one Curation Status Label can be active at a time. Assigning a new label automatically removes the previous one.
The [Curation Guidelines](wiki:/s/dataverseno-brukarforum/wiki/55/curation-guidelines "Curation Guidelines") explain how the most common Curation Status Labels are used during the normal curation workflow. This page complements those guidelines by providing detailed information about each available Curation Status Label, including its purpose, appropriate use cases, and relationship to other dataset statuses.
## Assigning a Curation Status Label
To assign or change a Curation Status Label:
1. Open the dataset draft.
2. Click **Curation Status**.
3. Select **Change Curation Status**.
4. Select the desired label.
To remove a label without assigning a new one:
1. Click **Curation Status**.
2. Select **Change Curation Status**.
3. Select **Remove Current Status**.
# Available Curation Status Labels
## `Curator Assigned`
### Purpose
Indicates that responsibility for curating the dataset has been assigned.
### When to use
Assign when it has been decided who will curate a dataset that has been submitted for review but curation for some reason has not started yet.
## `In Curation`
### Purpose
Indicates that the dataset is currently being curated.
### When to use
Assign when curation begins.
### Notes
**`In Curation` is the primary Curation Status Label used during routine curation in DataverseNO.** Most datasets that are undergoing review will have this label assigned unless a more specific workflow label is needed.
If a dataset is returned to the depositor and later resubmitted for review, the label `In Curation` will normally remain associated with the dataset throughout the curation process.
## `Awaiting Reply`
### Purpose
Indicates that the curator is waiting for input from the depositor or another stakeholder.
### When to use
Assign when additional information, clarification, or action is required before curation can proceed, but the dataset has not been returned to the depositor.
## `Legal or Ethical Concerns`
### Purpose
Indicates that legal and/or ethical issues require clarification.
### When to use
Assign when concerns arise regarding topics such as:
- Rights and permissions
- Copyright
- Personal data
- Confidential information
- Ethical approval
## `Awaiting Final Approval`
### Purpose
Indicates that curation has been completed and that the curator is waiting for the depositor to confirm publication.
### When to use
Assign after all curation activities have been completed and the dataset is ready for publication.
## `In Double-Blind Review`
### Purpose
Indicates that the dataset is associated with a manuscript undergoing double-blind peer review.
### When to use
Assign once an anonymized review copy has been created.
### Notes
The label should be assigned to the **original** dataset while the anonymized review copy is being used during peer review.
See the [Double-blind peer review](wiki:/s/dataverseno-brukarforum/wiki/57/double-blind-peer-review "Double-Blind Peer Review") page for guidance.
## `Awaiting Article Publication`
### Purpose
Indicates that curation has been completed but publication of the dataset is being postponed until a related article, book chapter, or other publication has been accepted or published.
### When to use
Assign this label when:
- Curation has been completed.
- The dataset is ready for publication.
- The depositor does not yet wish the dataset to be published.
- A related article, book chapter, book, dissertation, or other scholarly publication is still undergoing editorial or peer review, or awaits publication.
### Curator action
Before assigning this label, verify that the dataset:
- Aligns with the DataverseNO Deposit Guidelines.
- Has completed the normal curation process.
- Is ready for publication once the depositor gives final approval.
After assigning this label:
- Keep the dataset under curator control.
- Do not return the dataset to the depositor for editing.
- If editors, reviewers, or other stakeholders need access to the dataset, follow the guidance in section **Reading access to unpublished datasets** in the [Curation Guidelines](wiki:/s/dataverseno-brukarforum/wiki/55/curation-guidelines "Curation Guidelines").
- If the publication process involves double-blind peer review, follow the dedicated [Double-blind peer review](wiki:/s/dataverseno-brukarforum/wiki/57/double-blind-peer-review "Double-Blind Peer Review") workflow instead.
### Notes
This label helps curators identify datasets that are effectively publication-ready but are being temporarily withheld from publication for publication-related reasons.
The label also signals that the dataset should remain stable while it is being shared with editors or reviewers.
A dataset assigned `Awaiting Article Publication` should normally not be modified. If changes become necessary during the publication review process, they should be coordinated through the curator and handled according to the normal DataverseNO curation workflow.
## `Cited but Unpublished`
### Purpose
Indicates that a dataset draft has been cited or otherwise referred to publicly but has never been formally submitted for review and publication in DataverseNO.
### When to use
Assign this label when a curator becomes aware of a dataset draft that:
- Has been cited in a publication, manuscript, report, thesis, website, or other public context.
- Has not been submitted for review through the normal DataverseNO curation workflow.
- Remains unpublished despite having entered the scholarly record.
### Curator action
The curator should make reasonable efforts to clarify the status of the dataset.
As a first step, the curator should contact the depositor and encourage them to either:
- Submit the dataset for review and publication;
- Continue maintaining the dataset draft; or
- Withdraw the dataset.
If the curator is unable to reach the depositor, or if the depositor does not follow up on the request within a reasonable period of time, the curator should contact the publisher and explain the situation, while keeping the depositor copied on the correspondence.
Where possible, curators should support the depositor in bringing the dataset into alignment with the DataverseNO Deposit Guidelines and completing the publication process.
DataverseNO has established a dedicated routine for handling datasets with the status `Cited but Unpublished`. Curators are encouraged to follow this routine when available. For further information and the most recent version of the procedure, contact the Dataverse Repository Management team at [support@dataverse.no](mailto:support@dataverse.no).
### Notes
Datasets that have been cited but remain unpublished can create uncertainty for readers because the cited dataset cannot be accessed through the DOI or repository record in the way normally expected for published research outputs.
Curators should therefore follow up such cases as soon as practicable.
If the depositor or publisher does not take the necessary actions after being given appropriate time to respond, the dataset may later be assigned the label `Candidate for Deletion` and handled in accordance with the DataverseNO Policy Framework.
The `Cited but Unpublished` label is intended to support follow-up and resolution. It should normally be regarded as a temporary status rather than a final outcome for a dataset.
## `Candidate for Deletion`
### Purpose
Indicates that the curator believes a **dataset draft** should be considered for deletion.
### When to use
Assign this label when there are reasonable grounds for deleting a dataset draft and further curator action is required before a final decision can be made.
Typical situations include:
- Dataset drafts that have remained unpublished for a long period and where curators will need to make reasonable efforts to clarify their status with the depositor.
- Dataset drafts that have been cited but have never been formally submitted for review and publication, and where neither the depositor nor the publisher has taken the necessary actions after being given appropriate time to respond. Such datasets will often previously have been assigned the label `Cited but Unpublished`.
- Dataset drafts that were mistakenly created in the DataverseNO production environment when they should have been created in the training environment (**[demo.dataverse.no](http://demo.dataverse.no)**).
### Notes
Possible deletion should always be considered in light of the DataverseNO Policy Framework.
In particular, the DataverseNO Deposit Agreement states:
> "You grant to DataverseNO the right to delete unpublished dataset drafts that have not been submitted for review after more than one year after creation. Before deleting an unpublished dataset draft, DataverseNO support staff will make a reasonable effort to contact you to clarify the status of the draft."
Before proceeding with deletion, curators should therefore ensure that reasonable efforts have been made to clarify the status of the dataset with the depositor.
DataverseNO has established a dedicated routine for handling datasets with the status `Candidate for Deletion`. Curators are encouraged to follow this routine when available. For further information and the most recent version of the procedure, contact the Dataverse Repository Management team at [support@dataverse.no](mailto:support@dataverse.no).
This label applies only to **dataset drafts**. Deletion is only possible while a dataset remains in draft status.
The removal of **published datasets** is handled through the DataverseNO deaccessioning process rather than deletion.
If you have questions about deaccessioning, contact the Dataverse Repository Management team at [support@dataverse.no](mailto:support@dataverse.no).
# Relationship to publication-status labels
Dataverse automatically assigns a number of publication-status labels to indicate the technical status of a dataset.
Examples include:
- `Draft`
- `In Review`
- `Unpublished`
- `Deaccessioned`
In addition, DataverseNO curators may assign a single Curation Status Label to indicate the current curation status of a dataset.
Example:
- `In Curation`
Curators should consider both the automatically assigned publication-status labels and any manually assigned Curation Status Label when determining the current status of a dataset.
### Common dataset statuses
The table below illustrates common dataset statuses in DataverseNO and how they are typically represented through a combination of publication-status labels and Curation Status Labels.
The overview is intended as a quick reference. Not all datasets will pass through every status, and some statuses may be skipped depending on the nature of the dataset and the curation process.
| \# | Dataset status | Publication-status labels | Curation Status Label |
| - | -------------- | ------------------------- | --------------------- |
| 1 | Draft of new unpublished dataset | `Draft` `Unpublished` | – |
| 2 | Dataset submitted for review | `Draft` `In Review` `Unpublished` | – |
| 3 | Curator assigned | `Draft` `In Review` `Unpublished` | `Curator Assigned` |
| 4 | Active curation in progress | `Draft` `In Review` `Unpublished` | `In Curation` |
| 5 | Awaiting feedback from depositor or another stakeholder | `Draft` `In Review` `Unpublished` | `Awaiting Reply` |
| 6 | Legal or ethical issues require clarification | `Draft` `In Review` `Unpublished` | `Legal or Ethical Concerns` |
| 7 | Dataset returned to depositor for revision | `Draft` `Unpublished` | `In Curation` |
| 8 | Dataset resubmitted after revision | `Draft` `In Review` `Unpublished` | Typically: `In Curation` |
| 9 | Awaiting depositor approval for publication | `Draft` `In Review` `Unpublished` | `Awaiting Final Approval` |
| 10 | Double-blind peer review in progress | `Draft` `In Review` `Unpublished` | `In Double-Blind Review` |
| 11 | Awaiting publication of related article or book | `Draft` `In Review` `Unpublished` | `Awaiting Article Publication` |
| 12 | Dataset published | Published dataset (all draft and Curation Status Labels automatically removed) | – |
| 13 | Draft of new version of published dataset | `Draft` | – |
| 14 | New version submitted for review | `Draft` `In Review` | – |
| 15 | Curator assigned to new version | `Draft` `In Review` | `Curator Assigned` |
| 16 | Active curation of new version | `Draft` `In Review` | `In Curation` |
| 17 | New version published | Published dataset (all draft and Curation Status Labels automatically removed) | – |
| 18 | Dataset cited but not submitted for review or publication | `Draft` `Unpublished` | `Cited but Unpublished` |
| 19 | Dataset draft considered for deletion | Typically: `Draft` and/or `Unpublished` | `Candidate for Deletion` |
| 20 | Published dataset deaccessioned | Deaccessioned | – |
# Recommended practice
- Assign labels consistently across datasets and collections.
- Ensure that the assigned label reflects the current status of the dataset.
- Update labels when the curation status changes.
- Use `In Curation` as the default label when actively reviewing a dataset.
- Use `In Double-Blind Review` whenever an anonymized review copy has been created.
## Need help?
If you are uncertain which label should be applied:
1. Consult your local curation team.
2. If needed, contact the Dataverse Repository Management team at [support@dataverse.no](mailto:support@dataverse.no).
Powered by HumHub