Curation Guidelines
# Curation guidelines
## Introduction
Curation is a support process through which DataverseNO helps researchers prepare datasets for publication, reuse, and long-term preservation.
Curators review datasets against the **[DataverseNO Deposit Guidelines](https://info.dataverse.no/deposit/)** and work with depositors to improve metadata, documentation, file organization, licensing information, and other aspects that contribute to FAIR research data.
The purpose of these guidelines is to support consistent curation practices across the DataverseNO partner institutions.
## Recommended resources
DataverseNO recommends using the **DataverseNO Curation Report Template** to document curation activities and communicate feedback to depositors. The template is available in the following languages:
- English: [https://doi.org/10.5281/zenodo.7453983](https://doi.org/10.5281/zenodo.7453983)
- Norwegian Bokmål: [https://doi.org/10.5281/zenodo.7453986](https://doi.org/10.5281/zenodo.7453986)
- Norwegian Nynorsk: [https://doi.org/10.5281/zenodo.7453988](https://doi.org/10.5281/zenodo.7453988)
In addition, [Curation Status Labels](wiki:/s/dataverseno-brukarforum/wiki/56/curation-status-labels "Curation Status Labels") may be used to indicate different statuses and characteristics of datasets during the curation process. Basic label management is covered in this guide. For detailed guidance on available labels and their use cases, please see the [Curation Status Labels](wiki:/s/dataverseno-brukarforum/wiki/56/curation-status-labels "Curation Status Labels") page.
For detailed guidance on all metadata fields, please see the full **DataverseNO Metadata Guide**.
## The purpose of curation
The purpose of curation is to:
- Support researchers in publishing reusable research data.
- Promote consistent application of DataverseNO policies and guidelines.
- Improve the FAIRness of published datasets.
- Support long-term preservation and reuse.
- Ensure consistent user experience across DataverseNO partner institutions.
## Core curation principles
### Be supportive
Curators help researchers publish and share research data.
The role of the curator is not to act as a gatekeeper but to support depositors in improving datasets where needed.
Use an appropriate level of detail. Not all datasets require the same level of documentation or metadata. Apply the Deposit Guidelines in a manner that reflects the nature, complexity, and disciplinary context of the dataset.
### Be consistent
Similar datasets should receive similar treatment across DataverseNO partner institutions. Curators should follow common DataverseNO policies, guidelines, and agreed practices whenever possible.
### Prioritize reuse
When evaluating a dataset, focus on what future users need in order to understand, evaluate, and reuse the data.
### Document important decisions
Important curation decisions and communications should be documented to support transparency, consistency, and future follow-up.
DataverseNO recommends using the **DataverseNO Curation Report Template** to document curation activities and communicate recommendations to depositors. The template supports consistent curation practices across DataverseNO partner institutions and provides a structured way of recording observations, suggested improvements, and publication decisions.
## Curation workflow
### Overview
The curation process should be guided by the **DataverseNO Deposit Guidelines**. When reviewing a dataset, the curator assesses how well the dataset aligns with the guidance provided to depositors and, where necessary, recommends improvements that support publication, preservation, discoverability, and reuse.
### 1\. Receive and acknowledge the submission
When a depositor clicks **Submit for Review**, the dataset enters the DataverseNO curation workflow.
Curators receive notifications about datasets submitted to the collection(s) they curate
through:
- An **email** notification from the repository platform.
- The **Notifications** tab in DataverseNO.
The responsible collection manager or curation team should then determine who will handle the dataset according to local collection practices.
The curation team should monitor incoming submissions regularly and make initial contact with the depositor as soon as possible, normally within **three working days**.
The purpose of the initial contact is to:
- Confirm that the dataset has been received.
- Introduce the curator.
- Outline the next steps in the review process.
- Establish a communication channel if further dialogue is needed.
As curation starts, the curator should assign the Curation Status Label `In Curation`.
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.
Unless other [Curation Status Labels](wiki:/s/dataverseno-brukarforum/wiki/56/curation-status-labels "Curation Status Labels") are added later, the `In Curation` label normally remains attached to the dataset throughout the review process and helps indicate that the dataset is currently undergoing curation. See [Curation Status Labels](wiki:/s/dataverseno-brukarforum/wiki/56/curation-status-labels "Curation Status Labels") for detailed guidance on available labels and their use cases.
### 2\. Determine whether this is a new dataset or a new version
Before proceeding with the review, determine whether the submitted dataset is:
- A **new dataset** that has not previously been published in DataverseNO; or
- A **new version** of an already published dataset.
#### New datasets
New datasets are normally marked with the automatically assigned publication-status label **Unpublished**. The presence of this label usually indicates that the dataset has not been published previously and should therefore follow the standard curation workflow described below, starting with **3. Obtain an overview of the dataset**.
#### New versions of published datasets
If the **Unpublished** label is not present, the submission may instead be a draft of a new version of an already published dataset.
In such cases, curators should:
- Review the previously published version.
- Identify the changes introduced in the draft version.
- Verify that changes have been documented appropriately in the README file.
- Apply the relevant parts of the curation workflow to the changes introduced in the new version, focusing on the metadata, documentation, files, rights and access conditions, and other aspects that have been modified since the previous version.
### 3\. Obtain an overview of the dataset
It is recommended practice to open a DataverseNO Curation Report for the dataset as soon as the review begins.
Before examining individual files or metadata fields, obtain a general understanding of the dataset. At this stage, no in-depth review is required. The purpose is simply to identify obvious issues that would prevent publication in DataverseNO, even after reasonable safeguards and curation measures have been applied.
Verify that the dataset appears to meet the fundamental requirements described in the DataverseNO Accession Policy. In particular, consider:
- Whether at least one researcher currently or formerly affiliated with a Norwegian research institution has authored or otherwise made a substantive intellectual contribution to the creation of the dataset.
- Whether the dataset appears suitable for open publication in DataverseNO.
- Whether the dataset contains a README file.
Because the README file is mandatory in DataverseNO, a missing README file often indicates that the depositor has not yet consulted the Deposit Guidelines. In such cases, curators will often find it more efficient to **return the dataset immediately and ask the depositor to prepare a README file before detailed curation begins**.
The following wording may be used when contacting the depositor:
> Thank you for submitting your dataset to DataverseNO.
>
> Before we begin the curation process, we kindly ask you to add a README file describing the dataset. A README file is required for publication in DataverseNO and helps both curators and future users understand the data.
>
> Guidance is available in the [Deposit Guidelines](https://info.dataverse.no/deposit/) which also includes a standard README template that can be easily adapted for your dataset.
>
> Once the README file has been added, please re-submit the dataset for review.
Also consider:
- Are there any other obvious issues that require immediate attention?
- Do collaborators or other stakeholders require read or edit access to the dataset during the curation process?
If collaborators or other stakeholders require access to the dataset, the curator should determine which type of access is appropriate and follow the relevant guidance under **Read or edit access to unpublished datasets**.
Particular attention should be paid to datasets associated with publication review workflows, as these may require the use of **Preview URLs** or the dedicated [Double-blind peer review](wiki:/s/dataverseno-brukarforum/wiki/57/double-blind-peer-review "Double-Blind Peer Review") workflow. This is usually indicated by the depositor in the **Related Publication** metadata field or communicated directly to local support services.
### 4\. Review metadata
Review the metadata entered by the depositor:
1. Open the **Metadata** tab.
2. Click **Add + Edit Metadata**.
Focus particularly on the [required](https://info.dataverse.no/deposit/deposit-your-data/#required-metadata) and [recommended](https://info.dataverse.no/deposit/deposit-your-data/#recommended-metadata) metadata fields.
Use the relevant sections of the **[Deposit Guidelines](https://info.dataverse.no/deposit/)** as the primary basis for the review. For detailed guidance on individual metadata fields and metadata schemas, consult the **DataverseNO Metadata Guide**.
Ask:
- Is the dataset sufficiently discoverable?
- Can potential users understand what the dataset contains?
Pay particular attention to:
- The **Point of Contact** field: It is often a good idea that the dataset documentation includes two points of contact, if possible. This is particularly relevant if the first point of contact is a temporary employee (e.g. PhD student or Post Doc). A second point of contact could be a co-author, a PI of the project, a supervisor, or the research group leader.
- The **Related Publication** field: This field often provides the first indication that a dataset is intended for use in double-blind peer review. Where applicable, consult the [Double-blind peer review guidance](wiki:/s/dataverseno-brukarforum/wiki/57/double-blind-peer-review "Double-Blind Peer Review").
- The **Language** of the provided metadata: The DataverseNO Deposit guidelines require that the metadata fields **Title** (or **Alternative Title**), **Description** and **Keyword** are provided in English. If the dataset is described in any additional languages, make sure that these are added in the **Language** field.
Where improvements are needed, document recommendations in the Curation Report. Curators are encouraged to actively use and adapt the detailed metadata-review guidance provided in the DataverseNO Curation Report Template and the DataverseNO Metadata Guide as appropriate for the specific dataset.
### 5\. Review documentation
Documentation is often the most important part of the review.
Review:
- README files
- Codebooks
- Protocols
- Processing documentation
- Analysis scripts
- Additional supporting files
Use the relevant sections of the **[Deposit Guidelines](https://info.dataverse.no/deposit/)** as the primary basis for the review.
Ask:
- Can the dataset be understood without contacting the depositor?
- Are variables, codes, abbreviations, and file relationships adequately explained?
- Are changes from previous versions documented?
Particular attention should be paid to the README file, which should serve as the primary guide to the dataset.
As noted in the README File Template, depositors might need to be reminded that overlap between the methods section of a README file and a related publication is often appropriate and expected. Where relevant, curators may refer depositors to the [Committee on Publication Ethics (COPE) guidance on text recycling](https://doi.org/10.24318/6eWbU5xd).
Curators are encouraged to actively use and adapt the detailed guidance provided in the **DataverseNO Curation Report Template** and the **[DataverseNO README File Template](https://doi.org/10.5281/zenodo.7453999)** when reviewing documentation. This can be particularly useful when the methodological description is sparse or incomplete.
Where improvements are needed, document recommendations in the Curation Report.
### 6\. Review files and file organization
Review the dataset structure and the deposited files. To access the deposited files, open the **Files** tab on the dataset page.
Use the relevant sections of the **[Deposit Guidelines](https://info.dataverse.no/deposit/)** as the primary basis for the review.
Consider:
- File organization and folder structure.
- File naming conventions.
- Presence of file extensions (for example, .txt, .csv, .pdf, .xlsx). File names should normally include a file extension that clearly identifies the file format.
- File integrity.
- Whether the deposited files can be opened and inspected using appropriate software.
- Use of preferred file formats.
- Whether both original and preservation formats are provided where relevant.
- Where both a preferred preservation format and an original working format are included, verify that the file names are identical except for the file extension, making it easy for users and curators to identify corresponding files.
- Presence of embargoed files and whether any embargo appears appropriate and properly configured.
The aim is not necessarily to achieve perfect technical compliance but to ensure that the dataset can be understood, accessed, preserved, and reused.
#### Preferred file formats
DataverseNO accepts all file formats for deposit and publication. However, the file format affects what DataverseNO can commit to preserving over time. Whenever possible, depositors should provide their files in a preferred file format. DataverseNO recommends a range of preferred file formats that are well suited for long-term preservation and reuse.
When reviewing file formats, consider:
- Whether the format is included in the **[DataverseNO File Formats Overview](https://info.dataverse.no/deposit/file-formats/)**.
- Whether an alternative preservation-friendly format would be appropriate.
- Whether both the original format and a preservation format have been provided where relevant.
If the submitted file format is not yet included in the DataverseNO File Formats Overview, or if you are uncertain how to assess a particular file format, consult the Repository Management team at [support@dataverse.no](mailto:support@dataverse.no) or through the relevant DataverseNO Teams channel. Please provide the URL of the dataset(s) containing the file format at stake.
#### Embargoed files
If an embargo has been applied to one or more files, verify that:
- The README file remains openly accessible and is not embargoed.
- The embargo has a valid justification consistent with DataverseNO’s role as a repository for open research data.
- The depositor understands that the embargo will automatically expire on the specified end date.
- The embargo period does not exceed two years.
A temporary embargo may be appropriate, for example, when immediate open publication could adversely affect legitimate commercial or intellectual-property interests.
Embargoes should not be used as a substitute for permanent restricted or controlled access. If the reason for the embargo requires long-term access restrictions, such as the presence of personal or other protected information, the files should normally not be published in DataverseNO.
> **Keep in mind**
>
> The use of non-preferred file formats does not automatically prevent publication. Even where a file format is not well suited for long-term preservation, it is still accepted if the dataset is otherwise suitable for publication. However, DataverseNO cannot commit to converting such files to other formats in the future should the original format become difficult or impossible to use.
### 7\. Review rights, terms of use, and access conditions
Review the rights and access information provided by the depositor. To review licences, terms of use, and access conditions, open the dataset and select the **Terms** tab.
The purpose of this review is to ensure that:
- The depositor has the right to publish the dataset.
- The dataset is suitable for publication in DataverseNO.
- The selected terms of use are appropriate.
- Users receive clear information about how the dataset may be reused.
Use the relevant sections of the **[Deposit Guidelines](https://info.dataverse.no/deposit/)** (and – if needed – the **[Deposit Agreement](https://doi.org/10.5281/zenodo.21850126)**, **[Access and Use Policy](https://doi.org/10.5281/zenodo.21848816)**, and other applicable DataverseNO policies) as the primary basis for the review.
#### Rights and permissions
Verify that the depositor appears to have the right to publish all files included in the dataset.
Particular attention should be paid to datasets containing:
- Material created by third parties.
- Licensed content.
- Copyrighted material.
- Images, audio, video, or text originating from external sources.
- Data generated through collaborative projects involving multiple organizations.
Ask:
- Does the depositor appear to have the necessary rights to publish the content?
- Are there indications that permission from third parties may be required?
- Is additional clarification needed before publication?
Where relevant, request additional information from the depositor.
If the dataset authors have combined data from several sources into a new dataset, curators must verify that the licence applied to the new dataset is compatible with the licences governing all reused data. See the following section for guidance on licence compatibility.
#### Terms of use / license
Review the selected licence or terms of use.
DataverseNO generally recommends the use of **standard licences** wherever possible. Standard licences make it easier for users to understand how data may be reused and support consistent reuse practices across datasets.
Verify that:
- An appropriate standard license has been selected where possible.
- The selected license is consistent with the information provided elsewhere in the dataset.
- Any restrictions or conditions are clearly explained.
- If a standard license cannot be used, customized terms of use have been clearly defined.
- Any customized terms of use are internally consistent and do not conflict with other dataset documentation.
Customized terms of use should only be used when a standard licence is not suitable for the dataset. In such cases, the terms should clearly describe any conditions governing access, use, citation, redistribution, or other forms of reuse.
If the dataset includes data created by others, the curator must check the terms that apply to each source.
If the source data have a standard licence, such as CC BY or NLOD, the curator must verify that the licence selected for the new dataset is compatible with all licences that apply to the reused data. See the **[CC Licence Compatibility Chart](https://wiki.creativecommons.org/wiki/Wiki/cc_license_compatibility)** for an overview of licence compatibility.
- For example, if the researcher has combined one dataset licensed under CC0 with another licensed under CC BY, the new dataset should normally be licensed under CC BY, provided that the terms of both licences and any other applicable rights or restrictions are respected.
If customized terms of use apply instead of a standard licence, the curator must determine whether the proposed licence for the new dataset is compatible with those terms.
- Vague statements such as _“These data can be reused freely”_ may not provide enough information to determine the permitted forms of reuse or the applicable attribution requirements. If the meaning is unclear, the researcher or curator should ask the data provider to clarify the terms before publication.
The following datasets combine data from several sources. Some of the sources did not specify a standard licence or other terms of use. DataverseNO therefore contacted the data providers to clarify the permitted reuse. The confirmations received by email were converted to PDF and uploaded with the relevant dataset:
- Solvang, Øystein; Stein, Jonas; Brattland, Camilla, 2020, “Covid-19 Municipal Level (Norway) Social Science Dataset”, [https://doi.org/10.18710/NMKI2B](https://doi.org/10.18710/NMKI2B), DataverseNO, V1.
- Solvang, Øystein; Eriksen, Kari Elida; Stein, Jonas; Brattland, Camilla, 2020, “Covid-19 Country Level Social Science Dataset”, [https://doi.org/10.18710/VMUP44](https://doi.org/10.18710/VMUP44), DataverseNO, V2.
If the curator is uncertain whether a proposed licence is compatible with the licences or customized terms that apply to the source data, the curator should consult the local curation team. If further guidance is needed, contact DataverseNO Repository Management at [support@dataverse.no](mailto:support@dataverse.no) or through the relevant Teams channel.
#### Access conditions
Confirm that the access conditions are consistent with repository policies:
- The dataset is suitable for open publication.
- No files requiring permanent restricted or controlled access are included.
- Any embargoes are appropriate and properly documented.
#### Document recommendations
Where improvements are needed, document recommendations in the Curation Report.
Curators are encouraged to actively use and adapt the detailed guidance provided in the **DataverseNO Curation Report Template** when reviewing rights, licences, and access conditions. This helps ensure consistent feedback across DataverseNO partner institutions and provides a clear record of the curator’s assessment.
> **Keep in mind**
>
> Whenever possible, DataverseNO seeks to maximize the openness and reusability of research data. At the same time, openness should never override legal, ethical, contractual, or intellectual-property obligations. The curator’s role is to help depositors achieve the most open and reusable solution that is appropriate for the dataset.
### 8\. Assign [Curation Status Labels](wiki:/s/dataverseno-brukarforum/wiki/56/curation-status-labels "Curation Status Labels")
Combined with the automatically assigned publication-status labels, [Curation Status Labels](wiki:/s/dataverseno-brukarforum/wiki/56/curation-status-labels "Curation Status Labels") may be used to indicate different statuses and characteristics of datasets during the curation process.
The most commonly used label during routine curation is `In Curation`, which should normally be assigned when curation begins.
Additional labels may be assigned where relevant.
See [Curation Status Labels](wiki:/s/dataverseno-brukarforum/wiki/56/curation-status-labels "Curation Status Labels") for detailed guidance on available labels and their use cases.
### 9\. Communicate with the depositor
Communication with depositors is a central part of the curation process.
#### Be constructive
Where improvements are recommended, explain why they are beneficial.
Whenever possible, connect recommendations to:
- Reuse
- Documentation
- Preservation
- Discoverability
- FAIR principles
#### Be specific
Clearly describe:
- What should be improved.
- Why the improvement is recommended.
- How the depositor may address the issue.
#### Prioritize important issues
Focus first on issues that substantially affect:
- Understanding
- Reuse
- Preservation
- Compliance with Deposit Guidelines
Avoid overwhelming depositors with unnecessary detail.
DataverseNO recommends using the **DataverseNO Curation Report Template** to structure communication and feedback.
The report should:
- Document observations and recommendations.
- Record curator actions.
- Track depositor responses.
- Provide an audit trail of the review process.
The same report may be updated throughout the review process until publication.
Datasets associated with double-blind peer review may require additional communication with the depositor concerning anonymization, Preview URLs, citation of draft datasets, and the transition from the anonymized review copy to the final published dataset. See the [Double-blind peer review](wiki:/s/dataverseno-brukarforum/wiki/57/double-blind-peer-review "Double-Blind Peer Review") page for details.
### 10\. Confirm readiness for publication
Once the review has been completed, determine whether the dataset is ready for publication.
A dataset is normally ready for publication when:
- It aligns with the DataverseNO Deposit Guidelines.
- Metadata are sufficient.
- Documentation is sufficient.
- Rights and permissions have been clarified.
- Relevant issues identified during review have been addressed.
Document the final assessment in the Curation Report, as appropriate.
In some cases, the depositor may wish to postpone publication because a related article, book chapter, book, or other scholarly publication is still undergoing editorial or peer review.
If the dataset is ready for publication but publication is intentionally postponed for such reasons:
- Assign the Curation Status Label `Awaiting Article Publication`. See [Curation Status Labels](wiki:/s/dataverseno-brukarforum/wiki/56/curation-status-labels "Curation Status Labels") for detailed guidance on available labels and their use cases.
- Keep the dataset under curator control and do not return it to the depositor for editing.
- Follow the guidance under **Read or edit access to unpublished datasets** if editors, reviewers, or other stakeholders need access to the dataset before publication.
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.
### 11\. Obtain depositor approval
Before publication, the depositor should be given the opportunity to review any substantial curator modifications and confirm that the dataset is ready for publication.
The curator and depositor should have a common understanding of the final version that will be published.
### 12\. Publish the dataset
When:
- the curator has confirmed that the dataset is ready for publication; and
- the depositor has confirmed publication,
the curator publishes the dataset.
Publication activates the DOI and makes the dataset publicly available.
The curator should:
- Verify that the DOI has been activated and resolves correctly to the published dataset.
- Inform the depositor that the dataset has been published, including a reference to the published dataset and, where relevant, additional information about any actions that may still be needed (for example updating references to the dataset in related publications).
- Thank the depositor for choosing DataverseNO to archive and publish their data and welcome them back to deposit additional datasets in the future.
Publication marks the completion of the initial curation workflow.
Subsequent updates to the dataset are handled through the versioning workflow described under **New versions of published datasets**.
## Curation checklist
The [Curation Checklist](wiki:/s/dataverseno-brukarforum/wiki/58/curation-checklist "Curation Checklist") provides a practical overview of the most important checks that should normally be carried out during the DataverseNO curation process.
The checklist is intended as a working tool for curators and complements the guidance provided on this page. It follows the normal curation workflow and can be used both during curation and as a final verification before publication.
## Additional curator tasks
### Introduction
In addition to the standard curation workflow described above, curators occasionally perform a range of operational tasks related to access management, dataset administration, preservation, and repository maintenance.
The guidance below covers the most common curator tasks outside the regular curation process.
### Read or edit access to unpublished datasets
In some situations, access to an unpublished dataset needs to be provided before the dataset is published.
The appropriate mechanism depends on the purpose of the access request:
- **Collaborative access**, where collaborators or co-authors need access to a dataset that is still being developed.
- **Review access**, where editors or reviewers need access to a dataset that supports a publication under editorial or peer review.
These two use cases should be handled differently.
### Collaborative access to an unpublished dataset
#### When to use
This workflow should be used when access is needed for collaborators, co-authors, project members, or others who need to inspect the dataset while work on the dataset is still ongoing.
Examples include:
- Collaborators preparing a manuscript.
- Co-authors reviewing research data.
- Project team members checking documentation or metadata.
At this stage, the dataset may still be under active development and may not yet have been curated or be ready for publication.
#### Granting collaborative read or edit access
To grant read or edit access:
1. Log into DataverseNO.
2. Open the unpublished dataset.
3. Click **Edit Dataset**.
4. Select **Permissions**.
5. Select **Dataset**.
6. Click **Assign Roles to Users/Groups**.
7. Under **Role**, select
- **Dataset Viewer** for read access or
- **Contributor** for edit access.
8. Under **Users/Groups**, search for and select the user who needs access.
- If the user cannot be found:
1. Ask the depositor to have the user log into DataverseNO.
2. Once the user confirms they have logged in, repeat step 8.
9. Click **Save Changes**.
10. Inform the depositor (or, where appropriate, the user) that access has been granted.
### Review access to a dataset supporting a publication
#### When to use
This workflow should be used when a dataset needs to be shared as part of the review process of a publication, most often a journal article.
Typical recipients include:
- Journal or book editors.
- Review coordinators.
- In some cases, reviewers directly.
Access is provided using a **Preview URL**.
#### Requirements before creating a Preview URL
A Preview URL should only be created when all of the following conditions are met:
- **The dataset has been curated and is ready for publication.** The curator has completed the curation process and verified that the dataset aligns with the DataverseNO Deposit Guidelines. This is important because:
- It reduces the risk that subsequent curation will reveal issues that prevent publication.
- It helps ensure that datasets participating in editorial or peer review are well documented and reusable.
- It supports the interests of both the depositor and the publication venue.
- **The dataset remains under curator control.** The dataset should not be returned to the depositor before the Preview URL is created. If changes are required during the review process, the depositor should contact the curator. Maintaining curator control helps ensure that:
- The dataset remains stable during the review process.
- Changes are not introduced without curator awareness.
- Any required modifications follow normal DataverseNO curation procedures.
- Good Open Science and transparency practices are maintained.
- **The dataset has been assigned the appropriate Curation Status Label.** Before a Preview URL is created, the dataset should be assigned the Curation Status Label `Awaiting Article Publication`. This helps curators track datasets that are being held back from publication pending publication or acceptance of a related scholarly work.
#### Creating a Preview URL
To create a Preview URL:
1. Log into DataverseNO.
2. Open the unpublished dataset.
3. Click **Edit Dataset**.
4. Select **Preview URL**.
5. Select **Create Preview URL**.
6. Copy the generated Preview URL.
7. Send the Preview URL to the depositor or, if agreed, directly to the person who requires access.
#### Double-blind peer review
Datasets participating in **double-blind peer review** require a separate workflow.
In those cases, the curator should create an anonymized review copy and generate a Preview URL for that anonymized dataset rather than for the original dataset. See detailed guidance on the [Double-blind peer review](wiki:/s/dataverseno-brukarforum/wiki/57/double-blind-peer-review "Double-Blind Peer Review") page.
### Moving datasets
#### Purpose
In some situations, a dataset may need to be moved from one collection to another within DataverseNO.
#### Typical situations
Examples include:
- A dataset has been deposited in the wrong collection.
- A dataset should be associated with a different DataverseNO partner institution.
- Collection structures have been reorganized.
#### Curator guidance
If a dataset needs to be moved, notify the Dataverse Repository Management team at [support@dataverse.no](mailto:support@dataverse.no) and provide:
- A reference to the dataset.
- The current collection.
- The destination collection.
- A brief explanation of why the move is required.
The Repository Management team will assess the request and carry out the move if appropriate.
### Long-term preservation support
#### Purpose
DataverseNO is committed to ensuring that research data published in the repository remain accessible and usable over time.
#### Curator responsibilities
As part of DataverseNO’s long-term preservation activities, curators may be assigned preservation-related tasks by Collection Management.
These tasks are defined in the DataverseNO **Preservation Policy** and **Preservation Plan** and support the repository’s long-term preservation commitments.
### Deleting published datasets (deaccessioning)
Published datasets are part of the scholarly record and are subject to DataverseNO’s long-term preservation commitments.
Once a dataset has been published, its DOI has been activated and DataverseNO has committed to providing enduring access to the dataset in accordance with the DOI Agreement and the DataverseNO Policy Framework.
#### When may access be removed?
In exceptional circumstances, it may become necessary to remove public access to a published dataset.
Examples include:
- Legal concerns identified after publication.
- Ethical concerns identified after publication.
- Copyright or intellectual-property issues.
- Other situations where continued public access is inappropriate.
In such cases, DataverseNO will normally not delete the dataset record itself. Instead, access to the dataset files may be removed through the **deaccessioning** process.
#### What is deaccessioning?
Deaccessioning is the process used to withdraw access to a published dataset while preserving information about the dataset in the repository.
When a dataset is deaccessioned:
- The data files are no longer publicly accessible.
- The dataset metadata remain visible.
- The DOI remains part of the scholarly record.
- The dataset can still be identified and referenced.
The repository platform will indicate the status through the automatically assigned publication-status label **Deaccessioned**.
#### Curator guidance
If a curator becomes aware of circumstances that may justify deaccessioning, the curator should:
1. Document the issue.
2. Consult the local curation team where applicable.
3. Contact the Dataverse Repository Management team at [support@dataverse.no](mailto:support@dataverse.no).
4. Follow the applicable DataverseNO policies, procedures, and decisions regarding deaccessioning.
Curators should not initiate deaccessioning independently unless authorized to do so.
#### Keep in mind
Removing access to a published dataset is an exceptional measure and should only be considered when there are compelling legal, ethical, contractual, or other reasons for doing so.
Whenever possible, issues should be resolved through correction, versioning, or other less restrictive measures rather than deaccessioning.
### Need more information?
For guidance on deaccessioning procedures and specific cases, contact the Dataverse Repository Management team at [support@dataverse.no](mailto:support@dataverse.no).
## Need help?
If you are uncertain how to apply a policy, guideline, or curation practice, consult:
- Your local collection manager
- The DataverseNO curation network
- The Repository Management team
When in doubt, seek a consistent solution that supports the interests of depositors, future users, and the long-term value of the published dataset.
Powered by HumHub
Choose language: