Field Names

Field Name	Field Definition
Repository	Official name of repository
Description	A textual description of the repository. Imported from re3data.
Repository contact	Contact information for the repository. Imported from re3data.
Link to re3data record	URL to re3data page for the repository
Re3data ID	A unique string assigned by re3data to identify the repository's metadata entry in re3data. Imported from re3data.
Repository Homepage Link	URL to Repository's homepage
Data Collection Policy Link	URL to the repository’s data collection policy. Data collection policies may cover the research domains, data types, formats, and file types accepted by the repository, in addition to what kind of content is excluded.
Research Area	The disciplinary focus of the repository. Imported from re3data.
Keyword(s)	English keyword(s) describing the subject focus of the repository. Imported from re3data.
Data Type(s )	Types of data accepted by the repository. Accepted data types are sourced from the repository’s website and Data Collection Policy, and manually categorized by JH Data Services curators into one or more of this field’s controlled values.
Data types encourage/permitted-	Text field detailing types of data specifically encouraged for submission by the repository. Encouraged data types are sourced from the repository’s website and Data Collection Policy.
Data type(s) explicitly prohibited	Text field detailing types of data specifically prohibited by the repository. Prohibited data types are sourced from the repository’s website and Data Collection Policy.
Human Data Accepted	Indicates whether the repository accepts data derived from human participants - “Yes” or “No”
Fee for JHU researchers to deposit	Text field detailing the cost for JHU researchers to deposit data to this repository. Includes information about how parameters such as data size or sensitivity impact cost.
Human Participant Data Sharing Policy Link	URL to the repository’s Human Participant Data Sharing Policy, if present, which describes under what conditions they accept data from humans,
Sensitive Data Policy Link	URL to the repository’s Sensitive Data Policy, if separate from the Human Participant Data Sharing Policy, which describes how the repository decides to restrict access to data based on how sensitive it is (which is a combo of identifiability and risk to participants). Often repositories will include information about conditions under which they accept data from humans and how they decide which files from humans to restrict into one policy. In that case, the link to this policy is found in the Human Participant Data Sharing Policy field.
Data Access Policy Link	URL to the repository’s Data Access Policy, which describes who can access data from this repository and how they can access data.
Options for Data Access	Controlled field indicating methods by which data in this repository can be accessed. “Open access” means data is publicly available for anybody to download and use; “Controlled access” indicates one or more controls mediating access (such as authentication of the identity of data requesters, review by a Data Access Committee, etc.), detailed in the “Details on Data Access” field.
Details on Data Access	Text field detailing how access to files works. Information is sourced from policies published on the repository’s website. Where relevant, JHU-specific guidance is included.
Level of De-identification required	Text field detailing how data from human participants should be deidentified prior to deposit. Information is sourced from policies published on the repository’s website. Where relevant, JHU-specific guidance is included.
Submission Policy Link	URL to the repository’s Submission Policy, where you can find information about how to submit/deposit data to the repository.
Required Funder	Occasionally, repositories will limit the data they accept to a specific funder or set of studies. This text field indicates whether the repository only accepts data from a specific funder(s).
Persistent Identifier	Text field indicating what kind of unique identifier the repository uses to distinguish between datasets. The most common is DOI.
Data Retention Period	Text field indicating the duration of time that the repository states they will preserve deposited data and make it accessible.
AI/LLM Policy	Text field describing the repository’s Artificial Intelligence/Large Language Model policy, if present.
Data Limits	Text field describing any limits on either the total size or individual file size for a dataset.
Notes	Additional information about the repository not covered by other fields.