Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel7
stylecircle

...

Expand
titleOption 1: Anyone adding to this dataverse needs to be given access.

Option 1: Anyone adding to this dataverse needs to be given access.

The admin of this dataverse is the only person permitted to add new sub-dataverses and datasets. If another user would like to add to this dataverse, the admin will need to assign a role to that user. This is the most restricted level of access to a dataverse and is recommended for users creating personal or individual project dataverses, or groups creating a dataverse that will only require approved users to contribute content. Odum Institute Data Archive recommends most dataverses use this option.

Expand
titleOption 2: Anyone with a Dataverse account can add sub dataverses.

Option 2: Anyone with a Dataverse account can add sub dataverses.

Users with a UNC Dataverse account are permitted to contribute sub dataverses to this project dataverse. They will be assigned the role of admin to any sub dataverse they create and can then add datasets to their sub dataverse.

Expand
titleOption 3: Anyone with a Dataverse account can add datasets.

Option 3: Anyone with a Dataverse account can add datasets.

Users with a UNC Dataverse account may only contribute datasets to the dataverse. Users who create new datasets will be assigned as a ‘Dataset Creator’ and will only be able to edit their datasets. This is a particularly useful designation for groups who seek contributions, but only within the scope of their project. It is also the recommended permission level for journals who require data sharing as part of their publication process.

Expand
titleOption 4: Anyone with a Dataverse account can add sub dataverses and datasets.

Option 4: Anyone with a Dataverse account can add sub dataverses and datasets.

This is a combination of options 2 and 3. Users are permitted to create sub-dataverses and add datasets to those sub-dataverses, or they may contribute to the project dataverse directly by adding new datasets. This gives your contributors more options in how they share and organize the data and supporting materials within your project dataverse; however, it opens your dataverse to contributions from anyone with a UNC Dataverse account.

...

The second question works in combination with the first. These options determine what roles are assigned to your users once they are permitted access to create new content. The two designations are ‘Contributor’ or ‘Curator’. UNC Dataverse provides a description of the types of actions each role can make.

Expand
titleContributors

Contributors can edit metadata, upload files, and edit files, edit Terms, enable a guestbook, and submit their datasets for review. Contributors are not able to publish a dataset within your project dataverse. Instead, they can submit the dataset for review and an admin or curator may publish the dataset. See Submit for Review & Return to Author Feature for more information.

Info

The Contributor role is the recommended choice for those dataverses using Option 3: Anyone with a Dataverse account can add datasets. This combination permits admins the ability to review all dataset records before publication, make any necessary edits, and then approve or deny the publication.

Expand
titleCurators

Curators can edit metadata, upload files, and edit files, edit Terms, enable and create a guestbook, enable file restrictions and grant file access, edit permissions, assign roles, and publish a dataset record. Curators can do most things within a dataverse and is a good designation to assign to project team members responsible for sharing data such as project managers, data archivists, or research assistants.

Info

The Curator role is the recommended choice for those dataverses using Option 1: Anyone adding to this dataverse needs to be given access. This permits the Admin the ability to grant access to additional team members who will assist in making the research data available within the project dataverse.

Please keep in mind that once a role is assigned it can be removed at any time by an admin or curator. To learn more about assigning and revoking roles, please see Permissions – Users/Groups.

...