Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Effective November 1st, 2022, UNC Dataverse has changed its user policy to permit only UNC faculty, students, staff, and approved affiliates the ability to create new sub-dataverses and share data within UNC Dataverse. This change is to promote UNC-based research initiatives and ensure a more secure user experience for the research community.

With this change, we have implemented new user permissions as described below:

UNC Shibboleth: A faculty, student, or staff member of UNC Chapel Hill that logs in with their onyen. UNC Shibboleth users have permissions to create new dataverses within UNC Dataverse and share their data within those dataverses.

Non-UNC Shibboleth: An affiliate who logs into UNC Dataverse using their institution’s Shibboleth single sign-on. Non-UNC Shibboleth users may contribute to pre-existing dataverses they are Admins of or may request access to contribute to someone else’s dataverse. To request access to share data within an existing dataverse, please click on the Contact link of that dataverse and request permissions from the dataverse Admin.

Local: A user who logs into UNC Dataverse using a Dataverse-specific username and password. If you had a local account before November 1st, you are still able to access any dataverses and datasets you own. You may continue to add datasets to your pre-existing dataverse(s). If your institution does not use Shibboleth single sign-on and you need to contribute to a UNC researcher’s dataverse, you may request a local account be created.

Oauth: A user who logged in via Gmail or Github. This feature has been disabled. Any user who logged in via Gmail or Github will need to convert their account to a Shibboleth account or may request a local account if they require access to a pre-existing dataverse. The Odum Institute Data Archive will consider all requests and reserves the right to deny any request deemed outside of the scope of our current Terms of Use.

Please see our FAQs if you have questions about User Accounts and Permissions.

  • No labels