An open-source repository software application for archiving, sharing, and accessing research data of all kinds.
Yale Dataverse FAQs
General FAQs
Yale research data deposited in Dataverse is openly and freely accessible to everyone, unless it is constrained by security requirements.
To deposit data in Yale’s Dataverse, researchers (faculty, students, postdocs, and staff) must be affiliated with ISPS, EGC, and YLS during the pilot phase (DATES). After (DATE), all Yale researchers using CAS authentication.
Dataverse can accept most file types - please reach out to us if you notice any issues with a particular file type.
In Bytes:
“:ZipUploadFilesLimit”: “8000”
“:MaxFileUploadSizeInBytes”: “2147483648”
“:ZipDownloadLimit”: “11000000000”,
“:MultipleUploadFilesLimit”: “2000”,
The Yale Dataverse is a university funded and supported resource for the Yale research community. At this time there is no cost to deposit data into the Yale Dataverse. If you would like guidance from Archive staff, guided service is available to ensure compliance with common standards and best practices. Researchers may require curatorial assistance that is beyond what the university is able to supply and those costs should be covered by the researcher’s department or grant. For help on budgeting for data management and sharing please see this memo.
Users do not need to log on to access data on the Yale Dataverse. To deposit data, Yale researchers will log in simply by using their institutional account (NetID).
Authors who deposit their works with Yale Dataverse may choose to use a variety of Creative Commons licenses to permit broad re-use of their works, or they may reserve their copyrights and make their work available under default legal rules. In any case, as with all copyrighted works, users are always free to make fair uses and other lawful uses of works downloaded from Yale Dataverse [adapted from UVA].
FAQs for Yale Dataverse Curators
You only need a user account for the Yale Dataverse to upload data. You do not need a user account to download data (with the exception of specific files with restricted access, as noted).
Note: You do not need to be a user (I.e., to have an account) to search, browse, or download from the Yale Dataverse.
To become a user, go to https://dataverse.yale.edu/ and click on the “Log In” button. Select “Yale University” under “Your Institution.” Log in with your Yale netid.
You must be a user (i.e., have an account on the Yale Dataverse) to be able to create a dataverse and upload files to the Yale Dataverse.
As of January 2024, uploads to the Yale Dataverse are by permission only (a “curated model”). Send an email to the admin (dataverseadmin@yale.edu) to start the process.
All “dataverses” need to have “dataverse” in the name, for example: “The Yale Economic Growth Center Dataverse.” The same holds for sub-dataverses, e.g., https://dataverse.yale.edu/dataverse/chirila.
- Include a logo at the top (see relevant FAQ).
- Include description of the Dataverse that includes text and a link to the Dataverse to anchor users using the Description field.
- Include logo in the footer: in Edit Dataverse, under Theme & Widgets.
To display an image or logo as a thumbnail in the list of dataverses and datasets, and / or if the dataverse is a featured dataverse to display the image on main page’s feature collection box:
- Save the logo image on your local disk. (Optional, you may use an existing logo from Dataverse site.) If using an image from dataverse, right click on image to “Save image as” to your local disk (continue to step 6).
- Create a Dataverse, which must be published for all contents to display. (optional, this could be a Featured Dataverse): https://guides.dataverse.org/en/latest/user/dataverse-management.html
- In the relevant Dataverse, click Edit, select “Theme + Widgets.”
- Click “Upload Image” to upload the image from your local disk, keep other options as the default: After you upload the image to dataverse, this image is on dataverse site.
- To display a logo or image at the top of a dataverse page: In the relevant dataverse, right click the uploaded image, and select “Copy image link” for next step to use.
- Select “General Information” from the “Edit” drop down menu.
- In the “Description” box, use following “img” syntax for your logo image, e.g., <img src=”https://dataverse-test.yale.edu/logos/590/yale_isps_logo_cmyk.ai_11.20…” width=”200” height=”500” />
(Copy & paste the relevant URL for the uploaded image)
Please be aware that base urls for production and test server are different.
Production base url: https://dataverse.yale.edu
Test base url: https://dataverse-test.yale.edu
The width and height should be adjusted based on the image size.
To hyperlink the logo, add html code, for example:
<a href=”https://www.yale.edu/” target=”_blank”><img src=”https://dataverse-test.yale.edu/logos/590/yale_isps_logo_cmyk.ai_11.20…” width=”200” height=”500”/></a>
Then click “Save Changes”.
We are still investigating the best process for this. If you need this functionality, please reach out to us.
Yes. Users will need to create an account and you can assign them a role (see relevant FAQ). Note that roles are not inherited by sub-dataverses. That is, someone who is given access to a dataverse (within the Yale dataverse) doesn’t receive permissions to edit datasets in sub-dataverses.
A single file:
If you are uploading a single file (any format):
In your Dataverse, click Add data / New dataset: Follow general guidelines for File Upload here: https://guides.dataverse.org/en/5.13/user/dataset-management.html
SPECIAL CASE: Stata files:
To upload a single Stata file: If you are uploading a single Stata file, follow general guidelines for Tabular Data File Ingest here: https://guides.dataverse.org/en/5.13/user/tabulardataingest/index.html
To upload a Stata file in a folder: Follow guidelines for uploading to display tree view.
Multiple files:
IMPORTANT: If you are uploading more than one file (of any format), zip the files and then upload.
For example,
Zipped_folder/
├── my_data.csv
├── my_script.R
├── README.md
If you are uploading more than one file (of any format), and want to maintain folder structure and file paths, zip the files and then upload.
For example,
Zipped_folder/
├── data
│ ├── my_data.csv
├── analysis
│ └── my_script.R
├── DESCRIPTION
└── README.md
(adapted from: https://the-turing-way.netlify.app/reproducible-research/compendia )
To maintain a folder structure and file paths, you must upload a zipped folder:
- Save your files under one directory (folder); you can choose to have sub-directories, for example,
Zipped_folder/
├── data
│ ├── my_data.csv
├── analysis
│ └── my_script.R
├── DESCRIPTION
└── README.md
(adapted from: https://the-turing-way.netlify.app/reproducible-research/compendia )
- Zip the files to the top level (so that it is one zipped file)
- In your Dataverse, click Add data / New dataset
- Follow general guidelines for File Upload here: https://guides.dataverse.org/en/5.13/user/dataset-management.html
- Upload the zipped file to Dataverse as you would any other single file via “drag and drop” or “select file to add”
- Dataverse will maintain your directory structure
- Dataverse will open the files and read in the relevant information (including tabular data files)
- Uploading a folder will enable “tree view” for end-user to view and download the folder
Notifications appear in the notifications tab on your account page and are also displayed as a number next to your account name. You also receive notifications via email.
Default: You will typically receive a notification or email when:
- You’ve created your account.
- You’ve created a Dataverse collection or added a dataset.
- Another Dataverse installation user has requested access to restricted files in a dataset that you published. (If you submitted your dataset for review, and it was published by a curator, the curators of the Dataverse collection that contains your dataset will get a notification about requests to access your restricted files.)
- A file in one of your datasets has finished the ingest process.
Stakeholders can modify notifications/emails settings.
More information here: https://guides.dataverse.org/en/5.13/api/native-api.html#notifications
All “dataverses” need to have “dataverse” in the name, for example: “The Yale Economic Growth Center Dataverse.” The same goes for a “sub-dataverse,” for example: https://dataverse.yale.edu/dataverse/chirila.
There are multiple packages for interacting with Dataverse through code.
- R package maintained by Shiro Kuriwaki (Yale Political Science): https://cran.r-project.org/web/packages/dataverse/
- pydataverse: https://pydataverse.readthedocs.io/
- Log into the Yale Dataverse.
- Navigate to the Dataverse that needs to have Dataset Metadata auto populated.
- From the Edit menu, select Dataset Templates.
- Select Create Dataset Template.
- Enter a Template Name.
- Enter custom instructions (if needed) and values for the metadata fields that should be auto populated. For example, Template A has custom instructions explaining that an ORCID identifier is recommended for the Author field and auto selects ORCID from the Identifier Type menu.
- After editing has been completed, click Save + Add Terms at the bottom of the page.
- On the next page, add any custom Terms of Use and Access. For example, Template A will have CC-BY 4.0 rather than CC0 1.0, the default value for the top-level Yale Test Dataverse. Skip if not needed.
- Click Save Dataset Template at the bottom of the page.
- The next page displays your Dataset Templates, including the one you just created. To get back to this page later, select Dataset Templates from the Edit menu (Step 3).
- To use a Dataset Template when adding a Dataset, select it from the Dataset Template menu. For example, after selecting Template A, notice that the custom instruction and Identifier Type for the Author field displays as expected. Template values can be edited when adding a dataset.
- You can use an existing Dataset Template as the basis of a new Dataset Template by selecting Copy from the Edit Dataset Templates page. You can modify the Template Name and add custom instructions or auto populated values for metadata fields in addition to those that were copied.
- For additional information, consult the Dataverse Documentation: