UA Research Data Repository

Access to the ReDATA service is currently by request only. To obtain access, please contact us at data-management@email.arizona.edu. This page, ReDATA policies, and functionality of the ReDATA platform may change without notice.

What is the UA Research Data Repository?

The UA Research Data Repository (ReDATA) serves as the institutional repository for non-traditional scholarly outputs resulting from research activities by University of Arizona researchers. Depositing research materials (datasets, code, images, videos, etc.) associated with published articles and/or completed grants and research projects, into ReDATA helps UA researchers ensure compliance with funder and journal data sharing policies as well as University data retention policies. ReDATA is designed for materials intended for public availability. All published materials will receive a DOI for citation purposes.

Why Should I Deposit Data Here?

  • To fulfill funder or publisher public data sharing mandates
  • To make your data citable
  • To make your papers more reproducible
  • Comply with UA data retention policy

How do I Use It?

To deposit, please follow the step-by-step tutorial

In brief:

  1. Familiarize yourself with ReDATA's policies. You may deposit any kind of research output except
    • sensitive or restricted data
    • deposits consisting solely of standalone manuscripts (e.g., journal articles, theses/dissertations, reports). These should go in our sister repository: the UA Campus Repository
  2. Ensure your dataset complies with the deposit guidelines 
  3. Log in with your NetID
  4. Create a new submission
  5. On the submission page, complete the required metadata fields and upload your dataset
  6. Submit your dataset
    • You may pre-reserve a DOI upon submission. This will allow you to insert the DOI in a publication prior to the completion of the review (the DOI won't actually become active until the dataset becomes public)

After submission, your dataset will be reviewed and curated for adherence to the guidelines and policies. If additional information is needed, you will be contacted. At the same time, you will be asked to complete the Deposit Agreement. Upon completion of the review and receipt of the signed Deposit Agreement, your dataset will be published.

For more detailed, step-by-step instructions, see our Help & How-tos below.

Help & How-tos 

Need More Help? Please get in touch with us by scheduling a consultation using the button at the top of the page or you may email us directly at data-management@email.arizona.edu 

Deposit Guidelines Checklist 

To improve the quality and reusability of datasets deposited into the Repository, completion of this checklist is required prior to submission. You may create a draft submission in ReDATA to enter/upload information as you progress through each section. Some steps are optional or may not apply to every case.

Select Name & License
1. Name the dataset (required)

Select a descriptive name for the dataset. 

  • For datasets associated with publications, we recommend the format Data for "[insert title of associated publication]". Example: Data and Code for "Beyond greenness: detecting temporal changes in photosynthetic capacity with hyperspectral reflectance data"
  • For datasets not associated with publications, we recommend selecting a title that describes what it is and includes temporal (dates, date ranges) and/or geospatial information, as appropriate. Example: Survey of Carbonyl Sulfide in Soils at 38 Sites in Europe
2. Select an appropriate license (required)

See the license selection matrix for allowable licenses and guidance for which to select. You will record your selection upon deposit (and in the dataset's README.txt file).

Note: if different parts of the deposit have different license requirements, we recommend creating two separate deposits. We can link them together in the repository upon submission.

Organize Files and Folders
3. Name files appropriately (recommended)

Files should be clearly named so others can understand. Any naming conventions should be documented in the README.txt or elsewhere.

File naming best practices

4. Structure folders appropriately (recommended)

If possible, a flat structure without folders is recommended. If the dataset is more complex and would benefit from the use of folders, then they are allowed, as long as they are named appropriately

Folder structure best practices

5. Create ZIP archives (if needed)

Bundling together data in ZIP files is needed if your dataset has folders (folders cannot be uploaded to the repository, only files). Therefore, if the dataset is to be compressed we recommend the following

  • Use the ZIP file format only

  • One ZIP file per downloadable "chunk" of information. For example, if you dataset contains three folders, Data, Code, and Figures, you could create three zip files: Data.zip, Code.zip, Figures.zip. That way, each part of the project can be downloaded separately without having to download everything.

  • Keep the README.txt outside of any ZIP files.

Add Documentation
6. README.txt (required)

Please complete the README.txt template prior to submission to the extent that you can, and add it to the deposit outside of any Zip files (as shown in the figure above). You may re-use the information from the README.txt to fill in the required metadata fields in the repository during the submission phase.

  • If you submit your dataset for review and do not include a README.txt, we will send you a partially filled out one for you to finish.
    • Before final publication, you will have an opportunity to approve any changes we make.
  • Even if you include other documentation, a README.txt in the format specified by the preceding template is still required.

A sample README.txt is available for reference purposes.

7. Attach license text (if needed) Apart from stating the license in the README.txt file, be sure to attach the license where applicable (e.g., add it to source code files as dictated by the license, or include a copy of the license).
8. Generate preview images (optional)

If your files are not automatically previewable by the data repository platform, you may generate one or more preview images (e.g., screenshots, plots). As an example, in the figure above, ‘timeseries.png’ represents a self-created image which will appear as the dataset thumbnail image in the repository.

9. Add additional documentation 

If you already have developed documentation for your dataset please include it. Examples of documentation include: readme files, user manuals, code books, flowcharts, etc. See Data Documentation for help with what kind of information to include. If documentation is for specific parts of the dataset, be sure to indicate which parts/files/folders the documentation is for, either by indicating it within the file or by naming the file appropriately (e.g., README_software.txt)

De-identified human subjects research (e.g., surveys, observational studies, etc.): in order to publish this kind of data, we require the IRB-approved consent form used for the study. You may include it with the dataset or, if you do not wish to make it public, you may email it directly to us.

Include Related Materials
10. Add source code repository (optional) You may link to any appropriate source code repository using the References box (Github, Bitbucket, etc). Additionally, the Repository platform provides a direct integration with GitHub.
11. Add other materials (optional) You may link to any other related materials using the References box in the submission form in order to give additional context to the dataset.
12. Exclude journal articles (required) Do not include copies of published journal articles alongside the dataset. Instead you may link to them from the README.txt and/or by adding them to the References box during the submission process .

After completing the checklist, you may submit the dataset and it will be reviewed.

Policies   

Use of the repository is governed by the

 

Javascript required to display embed.

Direct link: https://osf.io/7qmxw/

 

Javascript required to display embed.

Direct link: https://osf.io/n64zp/

All datasets will undergo curatorial review by an authorized curator. The review may include (but is not limited to) the following: 

  • Adherence to the deposit guidelines
  • Ensuring that files referenced in the data and documentation are accounted for
  • Opening files to ensure they can be read
  • Copy editing of text in the metadata (title, description, etc.)
  • Adding links to associated publications/materials
  • Examining tabular datasets for adherence to best practices
  • Virus check
  • Check for sensitive data
  • Unpackaging/re-packaging of materials when appropriate

Additional Information  

Who Can Deposit Materials?

Anyone with a valid UA NetID login and Library privileges.

 

How Much Does it Cost to Deposit?

At this time, there is no cost to individual researchers for depositing materials.

 

What Kinds of Materials Can I Deposit?

The data repository will only accept datasets, software, media files (and associated documentation) developed or used in support of research activities at UA. Deposits consisting solely of document-oriented materials such as reports, pre-prints, post-prints, journal articles, reports, theses, and dissertations will not be accepted (these materials should be deposited in the UA Campus Repository). See the Deposit policy for more information.

 

Do materials have to be associated with a published article?

No. As long as the dataset, code, etc. is "final", it is acceptable.

 

What Size/Amount of Materials Can I Deposit?

The amount of materials that can be deposited are limited by your individual quota allocation. See the policy document for more information about quotas.

 

What Happens After I Submit and Publish my Dataset?

After uploading your files, entering the appropriate metadata, and submitting the dataset, it will not be published immediately. Instead it will undergo curatorial review and you (or a designated corresponding author) will be required to sign a deposit agreement. Once the curatorial review has been completed, your dataset will be made public and the DOI will become active. After publication, you may make changes to the dataset or metadata at any time (this will generate a new version of the dataset, the old version remains available).

 

What Happens if ReDATA Goes Away?

Published materials will be transferred to the public Figshare instance where possible. In all cases, an archival copy of published materials will be retained for 10 years from the date of deposit. Access to this copy will be by request only (contact data-management@email.arizona.edu). See the Retention policy for more information.

 

Javascript required to display embed.

Direct link: https://osf.io/f57nz/