Skip to content
GitHub
Twitter

Study DRAFT Profile

Version: 0.2-DRAFT (16 December 2020)


If you spot any errors or omissions with this type, please file an issue in our GitHub.


Key to specification table

CD = Cardinality

Property Expected Type Description CD Controlled Vocabulary Example
Marginality: Minimum.
@context URL Used to provide the context (namespaces) for the JSON-LD file.
Not needed in other serialisations.		 ONE
@type Text Schema.org/Bioschemas class for the resource declared using JSON-LD syntax. For other serialisations please use the appropriate mechanism.
While it is permissible to provide multiple types, it is preferred to use a single type.		 MANY Schema.org, Bioschemas
@id IRI Used to distinguish the resource being described in JSON-LD. For other serialisations use the appropriate approach. ONE
dct:conformsTo IRI Used to state the Bioschemas profile that the markup relates to. The versioned URL of the profile must be used.
Note that we use a CURIE in the table here but the full URL for Dublin Core terms must be used in the markup (http://purl.org/dc/terms/conformsTo), see example.		 ONE Bioschemas profile versioned URL
author Organization
Person
 Schema:

The author of this content or rating. Please note that author is special in that HTML 5 provides a special mechanism for indicating authorship via the rel tag. That is equivalent to this and may be used interchangeably.


Bioschemas:

Used to indicate the person(s) or organizations that conducted the Study. Please use creator to indicate the Research project
datePublished Date
 Schema:

Date of first broadcast/publication.
description Text
 Schema:

A description of the item.
identifier PropertyValue
Text
URL
 Schema:

The identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links. See background notes for more details.
name Text
 Schema:

The name of the item.
studyDomain PropertyValue
Text
URL
 Schema:

Define the domain of the study. For example, the domain could be astrophysics, functional genomics or earth science. Those domains can also have an ontology reference.


Bioschemas:

For example, in the life sciences we could have Functional Genomics: http://edamontology.org/topic_0085 Protemics: http://edamontology.org/topic_0121

 ONE
studySubject BioChemEntity
MedicalEntity
 Schema:

A subject of the study, i.e. one of the medical conditions, therapies, devices, drugs, etc. investigated by the study.


Bioschemas:

(Reuse of property from MedicalStudy; Expected types extended.)

 MANY
Marginality: Recommended.
about Thing
 Schema:

The subject matter of the content. Inverse property: subjectOf.


Bioschemas:

Use to link to the Protein, Gene, etc that the study is about

 MANY
additionalProperty PropertyValue
 Schema:

A property-value pair representing an additional characteristics of the entitity, e.g. a product feature or another characteristic for which there is no matching property in schema.org.

Note: Publishers should be aware that applications designed to use specific schema.org properties (e.g. http://schema.org/width, http://schema.org/color, http://schema.org/gtin13, …) will typically expect such data to be provided using those properties, rather than using the generic property/value mechanism.


Bioschemas:

Used to provide arbirary properties of a study.

 MANY
citation CreativeWork
Text
 Schema:

A citation or reference to another creative work, such as another publication, web page, scholarly article, etc.
creator Organization
Person
 Schema:

The creator/author of this CreativeWork. This is the same as the Author property for CreativeWork.


Bioschemas:

Used to specify the research project that created the study. Please use author to indicate the organisation, or individuals that conducted the study.

 MANY
dateCreated Date
DateTime
 Schema:

The date on which the CreativeWork was created or the item was added to a DataFeed.
endDate Date
DateTime
 Schema:

The end date and time of the item (in ISO 8601 date format).


Bioschemas:

Used to indicate the end date of the study. (Extension of existing schema.org property)

 ONE
keywords DefinedTerm
Text
URL
 Schema:

Keywords or tags used to describe this content. Multiple entries in a keywords list are typically delimited by commas.
startDate Date
DateTime
 Schema:

The start date and time of the item (in ISO 8601 date format).


Bioschemas:

Used to indicate the start date of the study. (Extension of existing schema.org property)

 ONE
studyLocation AdministrativeArea
Place
 Schema:

The location in which the study is taking/took place.


Bioschemas:

(Reuse of property from MedicalStudy; Expected types extended.)

 ONE
studyProcess PropertyValue
Text
URL
 Schema:

A process performed as part of an experiment or wider study, i.e. intentionally designed. These processes can have ontology URL attached to.


Bioschemas:

For example, in the life sciences we could have RNA-seq of coding RNA from single cells: http://www.ebi.ac.uk/efo/EFO_0005684 case control design: http://www.ebi.ac.uk/efo/EFO_0001427

 MANY

http://www.ebi.ac.uk/efo/EFO_0001433
url URL
 Schema:

URL of the item.
Marginality: Optional.
PPEO:hasGrowthChamber URL
 Schema:

has growth facility


Bioschemas:

The kind of growth facility used in a plant study

 ONE

[ { “PPEO:hasGrowthChamber”: { “PPEO:hasType”: “field” } }, { “PPEO:hasGrowthChamber”: { “PPEO:hasType”: “growth chamber” } }, { “PPEO:hasGrowthChamber”: { “PPEO:hasType”: “greenhouse” } }, { “PPEO:hasGrowthChamber”: { “PPEO:hasType”: “nursery” } } ]
isPartOf CreativeWork
URL
 Schema:

Indicates an item or CreativeWork that this item, or CreativeWork (in some sense), is part of. Inverse property: hasPart.


Bioschemas:

Used to indicate the project that the study is a part of.
relatedStudy Study
 Schema:

A study that is related to this one.


 MANY