About | UA Research Data Repository

ReDATA service is granted to all members of the University of Arizona with library privileges. If you encounter any trouble while using ReDATA, please contact us at data-management@arizona.edu. Undergraduate students should contact us before uploading content. 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 Digital Object Identifier (DOI) for citation purposes.

Why should I deposit data here?

  • To fulfill funder or publisher public data sharing mandates
  • To make your data citable and FAIR
  • To make your data discoverable (e.g., Google Dataset Search and Web of Science)
  • ReDATA offers free personalized data curation services that helps you comply with University policies and helps make your research more reproducible

How does it work?

Contents

How do I use it? 

This section outlines the process of submitting a data deposit for publication. To make a deposit, please follow the step-by-step tutorial. We strongly recommend that you read the Deposit Guidelines Checklist and our Policies before making a deposit.

In brief:

  1. Familiarize yourself with ReDATA's exceptions & restrictions
  2. Log in to ReDATA and upload your dataset
  3. Complete the required metadata fields
  4. Submit your dataset

What happens after I submit my dataset?

After submission, your dataset will be reviewed and curated for adherence to the guidelines and policies. You will be asked to complete and sign the Deposit Agreement and to complete the README form. The curatorial review process will not start until we receive the signed Deposit Agreement and the completed README form.

Exceptions & restrictions

You may deposit any kind of research output into ReDATA except for:

  • Sensitive, restricted, or legally protected data including but not limited to HIPAA, FERPA, PII, ITAR, CUI, protected species information, etc.
  • Deposits consisting solely of standalone manuscripts (e.g., journal articles, theses/dissertations, reports). These should go in the UA Campus Repository

You may deposit human subjects data as long as:

  • All human subjects data have been de-identified
  • Consent has been obtained for the making this data publicly available or used for future research

The corresponding author (or the authorized depositor) will be asked to confirm adherence to these exceptions and restrictions through the Deposit Agreement.

Tutorials 

  • Step-by-step tutorial: Depositing a dataset
  • Video tutorial: Depositing a dataset Coming Soon
  • Tutorial: requesting a storage quota increase Coming Soon
  • Tutorial: reserving a DOI prior to publication Coming Soon
  • Tutorial: Linking your ORCID with your ReDATA datasets Coming Soon

Need More Help? Please see our Additional information section below and get in touch with us by scheduling a consultation, or you may email us directly at data-management@arizona.edu 

Deposit Guidelines Checklist 

To improve the quality and reusability of the datasets deposited into ReDATA, completion of the Deposit Guidelines Checklist is strongly recommended 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.

You can find the Deposit Guidelines Checklist by opening the drop-down menu below.

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

Select a descriptive title 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 indicate your selection upon deposit.

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

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

Files should be clearly named so others can understand their contents. Any naming conventions should be documented in the README form 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 ReDATA, 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 your 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.

Add Documentation
6. Attach license text (if needed) Apart from stating the license when you create a deposit, 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).
7. Generate preview images (optional)

If your files are not automatically previewable on ReDATA, 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 that will appear as the dataset thumbnail image in ReDATA.

8. Add additional documentation 

If you already have developed documentation for your dataset, please include it. Examples of documentation include readme files, user manuals, codebooks (e.g., jupyter notebooks), 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 to us: data-management@arizona.edu

Include Related Materials
9. Add source code repository (optional) You may link to any appropriate source code repository using the References box (GitHub, Bitbucket, etc.). Additionally, ReDATA platform includes GitHub integration.
10. Add other materials (optional) You may link to any other related materials using the References box in the submission form to give additional context to the dataset.
11. Exclude journal articles (required) Do not include copies of published journal articles alongside the dataset. Instead, you may add them to the References box during the submission process and/or link to them on the README form, which will be provided to you after submitting your dataset.

License Selection Matrix 

As part of the publication process, ReDATA requires one of the following licenses to be assigned to the research outputs involved in the publication process. Datasets that require more than one license (e.g. data and software source code) must include each license in a separate file or, optionally, these datasets may be split into separate deposits. 

We encourage the use of licenses that impose the fewest restrictions on reuse.

You can find the License Selection Matrix in the drop-down menu below or by following this link

 

Javascript required to display embed.

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

Service policies

Terms & conditions 

Use of ReDATA is governed by the

Policies

The UA Research Data Repository Policies outline the mission of ReDATA while ensuring the service remains sustainable. These policies apply to all individuals who are listed as authors for any deposited material as well as individuals or organizations that log in to ReDATA to upload, store, curate, and publish research datasets and software. Among other things, the policies regulate how ReDATA user accounts are created and administered, what kinds of data are accepted, how datasets are made available (i.e., discoverable, accessible, reusable).

The Policies document can be accessed through this link

Community Policy Supplement 

The UA Research Data Repository Community Policy is a supplement to the UA Research Data Repository Policies document. It outlines community norms and expectations for specific use-cases such as custom portals, metadata-only records, linked records, and the use of ReDATA by affiliated organizations/groups such as inter-institutional collaborative research where there is significant UA involvement. 

The Community Policy document can be accessed through this link

Curatorial review 

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

  • Check for sensitive & restricted data
  • 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
  • Unpackaging/re-packaging of materials when appropriate
  • Virus check

Additional information

Questions and answers (Q&A)

  • Who can deposit materials?

    Anyone with a valid UA NetID login and UA Library privileges, specifically, active faculty, staff, designated campus colleagues (DCCs), and undergraduate and graduate students enrolled in an academic program.

  • How much does it cost to deposit?

    At this time, there is no cost to individual UA researchers for depositing materials below one terabyte. Deposits larger than one terabyte will be evaluated on an individual basis.

  • What kinds of materials can I deposit?

    ReDATA will only accept datasets, software, media files (and associated documentation) developed or used to support research activities at UA. ReDATA will not accept deposits consisting solely of document-oriented materials such as reports, pre-prints, post-prints, journal articles, reports, theses, and dissertations. These materials should be deposited in the UA Campus Repository. See the "Deposit Policy" section in the Policies document 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 number of materials that can be deposited is limited by your individual quota allocation. See our Policies 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 and fill out a "README" form via Qualtrics.

    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, UA Research Data Management Services will retain an archival copy of published materials for 10 years from the date of deposit. Access to this copy will be by request only (contact data-management@arizona.edu). See the Retention and Review Policy for more information.

  • When making a deposit...

    • What is the difference between "Title" vs. "Resource title"?

      The "Title" field is the name that you would like your deposit to have. In contrast, the "Resource title" field is reserved for the title of a publication or any other scholarly output (for instance, a journal article) that you want associated with your deposit.

    • What is the difference between "Resource DOI" and "Reserve Digital Object Identifier"?

      As with the "Title vs. Resource title" case above, the Resource Direct Object Identifier (Resource DOI) is the DOI of a publication or any other scholarly output (for instance, a journal article) that you want to associate with your deposit. In contrast, the "Reserve Digital Object Identifier" option allows you to generate a DOI specific to your deposit that others can use to cite your data and link to it. If you would like to know more about the process of reserving a DOI identifier, please refer to our "Tutorial: reserving a DOI prior to publication" in the Tutorials section.

    • What version of the Creative Commons license is assigned to my deposit when I select any of the CC options?

      For the Creative Commons licenses (CC), the following versions apply:

      • CC0: 1.0
      • CC BY: 4.0
      • CC BY-NC: 4.0
      • CC By-NC-SA: 4.0

Other information 

  • Updating your profile on ReDATA

    To update your profile, log in to ReDATA, click on the top-right circle with your initials, and look for the "Profile" option in the drop-down menu. You will also be able to enter your name, job title, fields of interest (you may add more than one), among other information. Don't forget to save the changes!

  • ORCiD

    ORCiD is a nonprofit organization that provides unique identifiers to individual scholars and researchers. ORCiD allows manuscripts, grants, and other scholarship outputs to be more discoverable and integrated within larger research networks, like the ReDATA. You can create and connect your ORCiD directly through the UA ORCiD site and then link your unique identifier to your ReDATA profile after you log in (you may need to log out and log back in for your ORCiD to be captured). For more information, please refer to our video tutorial in the Tutorials section.

  • Requesting a specific site (portal) for your research

    ReDATA consists of portals (pages) that correspond to broad research themes and are defined by the ReDATA team. The creation of additional portals beneath these broad themes can be requested by colleges, departments, or research groups with significant data publication needs; however, approval is at the discretion of the ReDATA team. For more information, please consult the "Requesting Portals" section of the Policies document as well as the Community Policy document.

Contact us

You can contact the ReDATA team by scheduling a consultation or you may email us directly at data-management@arizona.edu

Follow us on Twitter and Instagram