Roles in the Texas Data Repository

Dataverse, the underlying software of the Texas Data Repository (TDR), manages permissions to different parts of the repository through “roles.”

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.

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 datasets.) 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
Dataverse Creator A person who can add subdataverses within a dataverse.  The user can then add (and publish) datasets within that subdataverse. Does NOT have permission to add datasets to the parent dataverse.   Yes
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

Other notes about roles:

  • Users logging in through their institutional authentication systems are assigned to an institutional Group in the TDR with permissions specific to that institution. If you have questions about your permissions level, please contact your institutional library contact or the Texas Digital Library Helpdesk.
  • File level permissions are binary. You simply grant (or restrict) access to published files.  
  • Any user who creates a sub-dataverse is automatically the Administrator for that dataverse.