Skip to content

Class: StudyResult (Abstract)

Description: A collection of data items from a study that are about a particular study subject or experimental unit (the 'focus' of the Result) - optionally with context/provenance metadata that may be relevant to the interpretation of this data as evidence.

Notes: The data/metadata included in a Study Result object are typically a subset of data from a larger study data set, that are selected by a curator because they may be useful as evidence for deriving knowledge about a specific focus of the study. The notion of a 'study' here is defined broadly to include any research activity at any scale that is aimed at generating knowledge or hypotheses. This may include a single assay or computational analyses, or a larger scale clinical trial or experimental research investigation.

classDiagram class StudyResult InformationContentEntity <|-- StudyResult StudyResult <|-- ConceptCountAnalysisResult StudyResult <|-- ObservedExpectedFrequencyAnalysisResult StudyResult <|-- RelativeFrequencyAnalysisResult StudyResult <|-- TextMiningResult StudyResult <|-- ChiSquaredAnalysisResult StudyResult <|-- LogOddsAnalysisResult StudyResult : category StudyResult : creation_date StudyResult : deprecated StudyResult : description StudyResult : format StudyResult : full_name StudyResult : has_attribute StudyResult --|> Attribute : has_attribute StudyResult : id StudyResult : iri StudyResult : license StudyResult : name StudyResult : provided_by StudyResult : rights StudyResult : synonym StudyResult : type StudyResult : xref

Inheritance

Slots

Name Cardinality and Range Inheritance Examples
license:
None
0..1
String		 InformationContentEntity
rights:
None 		0..1
String		 InformationContentEntity
format:
None 		0..1
String		 InformationContentEntity
creation_date:
date on which an entity was created. This can be applied to nodes or edges 		0..1
Date		 InformationContentEntity
provided_by:
The value in this node property represents the knowledge provider that created or assembled the node and all of its attributes. Used internally to represent how a particular node made its way into a knowledge provider or graph. 		0..*
String		 NamedThing
xref:
A database cross reference or alternative identifier for a NamedThing or edge between two NamedThings. This property should point to a database record or webpage that supports the existence of the edge, or gives more detail about the edge. This property can be used on a node or edge to provide multiple URIs or CURIE cross references. 		0..*
Uriorcurie		 NamedThing
full_name:
a long-form human readable name for a thing 		0..1
LabelType		 NamedThing
synonym:
Alternate human-readable names for a thing 		0..*
LabelType		 NamedThing
id:
A unique identifier for an entity. Must be either a CURIE shorthand for a URI or a complete URI 		1..1
String		 Entity
iri:
An IRI for an entity. This is determined by the id using expansion rules. 		0..1
IriType		 Entity
category:
Name of the high level ontology class in which this entity is categorized. Corresponds to the label for the biolink entity type class. In a neo4j database this MAY correspond to the neo4j label tag. In an RDF database it should be a biolink model class URI. This field is multi-valued. It should include values for ancestors of the biolink class; for example, a protein such as Shh would have category values biolink:Protein, biolink:GeneProduct, biolink:MolecularEntity. In an RDF database, nodes will typically have an rdf:type triples. This can be to the most specific biolink class, or potentially to a class more specific than something in biolink. For example, a sequence feature f may have a rdf:type assertion to a SO class such as TF_binding_site, which is more specific than anything in biolink. Here we would have categories {biolink:GenomicEntity, biolink:MolecularEntity, biolink:NamedThing} 		1..*
Uriorcurie		 Entity
type:
None 		0..*
String		 Entity
name:
A human-readable name for an attribute or entity. 		0..1
LabelType		 Entity
description:
a human-readable description of an entity 		0..1
NarrativeText		 Entity
has_attribute:
connects any entity to an attribute 		0..*
Attribute		 Entity
deprecated:
A boolean flag indicating that an entity is no longer considered current or valid. 		0..1
Boolean		 Entity

LinkML Source

name: study result
description: A collection of data items from a study that are about a particular study
  subject or experimental unit (the 'focus' of the Result) - optionally with context/provenance
  metadata that may be relevant to the interpretation of this data as evidence.
notes:
- The data/metadata included in a Study Result object are typically a subset of data
  from a larger study data set, that are selected by a curator because they may be
  useful as evidence for deriving knowledge about a specific focus of the study. The
  notion of a 'study' here is defined broadly to include any research activity at
  any scale that is aimed at generating knowledge or hypotheses. This may include
  a single assay or computational analyses, or a larger scale clinical trial or experimental
  research investigation.
from_schema: https://w3id.org/biolink/biolink-model
is_a: information content entity
abstract: true