...
Depending on your own role in relations to a dataverse or dataset in the repository, you may be able to assign roles to other users. The chart below describes the roles available in the repository and the permissions assigned to each. For a description of how liaisons can set up their own Institutional Dataverse permissions in the TDR, see Liaison Administration Options
ROLE | DESCRIPTION | CAN BEASSIGNEDAT DATAVERSELEVEL? | CAN BEASSIGNEDATDATASETLEVEL? |
Administrator | A person who manages the dataverse, including assigning permissions to the dataverse. Can also add sub-dataverses and datasets and edit/publish/deaccession datasets submitted to the dataverse. | Yes | Yes |
Contributor | For datasets submitted to the dataverse, a person who can edit License + Terms, and then submit them for review. (Cannot publish datsets). | Yes | Yes |
Curator | For datasets submitted to the dataverse, a person who can edit License + Terms, edit Permissions, and publish datasets. | Yes | Yes |
Dataverse + Dataset Creator | A person who can add subdataverses and datasets within a dataverse. Datasets submitted to the dataverse are "submitted for review." An Administrator or Curator for the dataverse must approve and publish (or return to the author). If a user with this role creates their own dataverse, they will have the ability to publish dataset within that sub-dataverse. | Yes | No |
Dataverse Creator | A person who can add subverseses within a dataverse. The user can then add (and publish) datasets within that subdataverse. Does NOT have permissions to add datasets to the parent dataverse. | Yes | No |
File Downloader | A person who can download a file (including unpublished files). | Yes | Yes |
Member | A person who can view both unpublished dataverses and datasets, and download files. | Yes | Yes |
...