Class: Serial
This class may rarely be instantiated except if use cases of a given knowledge graph support its utility.
URI: biolink:Serial
Identifier prefixes
- issn
- NLMID
Parents
- is_a: Publication - Any published piece of information. Can refer to a whole publication, its encompassing publication (i.e. journal or book) or to a part of a publication, if of significant knowledge scope (e.g. a figure, figure legend, or section highlighted by NLP). The scope is intended to be general and include information published on the web, as well as printed materials, either directly or in one of the Publication Biolink category subclasses.
Referenced by class
Attributes
Own
- id 1..1
- Description: A unique identifier for an entity. Must be either a CURIE shorthand for a URI or a complete URI
- Range: String
- in subsets: (translator_minimal)
- type 0..*
- Range: String
Inherited from entity:
- id 1..1
- Description: A unique identifier for an entity. Must be either a CURIE shorthand for a URI or a complete URI
- Range: String
- in subsets: (translator_minimal)
- iri 0..1
- Description: An IRI for an entity. This is determined by the id using expansion rules.
- Range: IriType
- in subsets: (translator_minimal,samples)
- category 0..*
- Description: 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 featuref
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}- Range: CategoryType
- in subsets: (translator_minimal)
- type 0..*
- Range: String
- description 0..1
- Description: a human-readable description of an entity
- Range: NarrativeText
- in subsets: (translator_minimal)
- has attribute 0..*
- Description: connects any entity to an attribute
- Range: Attribute
- in subsets: (samples)
Inherited from gene product mixin:
- xref 0..*
- Description: Alternate CURIEs for a thing
- Range: Uriorcurie
- in subsets: (translator_minimal)
Inherited from information content entity:
- license 0..1
- Range: String
- rights 0..1
- Range: String
- format 0..1
- Range: String
- creation date 0..1
- Description: date on which an entity was created. This can be applied to nodes or edges
- Range: Date
Inherited from named thing:
- provided by 0..*
- Description: 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.
- Range: String
- category 0..*
- Description: 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 featuref
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}- Range: CategoryType
- in subsets: (translator_minimal)
Inherited from publication:
- authors 0..*
- Description: connects an publication to the list of authors who contributed to the publication. This property should be a comma-delimited list of author names. It is recommended that an author’s name be formatted as “surname, firstname initial.”. Note that this property is a node annotation expressing the citation list of authorship which might typically otherwise be more completely documented in biolink:PublicationToProviderAssociation defined edges which point to full details about an author and possibly, some qualifiers which clarify the specific status of a given author in the publication.
- Range: String
- pages 0..*
- Description: page number of source referenced for statement or publication
- Range: String
- summary 0..1
- Description: executive summary of a publication
- Range: String
- keywords 0..*
- Description: keywords tagging a publication
- Range: String
- mesh terms 0..*
- Description: mesh terms tagging a publication
- Range: Uriorcurie
- id 1..1
- Description: A unique identifier for an entity. Must be either a CURIE shorthand for a URI or a complete URI
- Range: String
- in subsets: (translator_minimal)
- name 0..1
- Description: A human-readable name for an attribute or entity.
- Range: LabelType
- in subsets: (translator_minimal,samples)
- publication type 0..1
- Description: Ontology term for publication type may be drawn from Dublin Core types (https://www.dublincore.org/specifications/dublin-core/dcmi-type-vocabulary/), FRBR-aligned Bibliographic Ontology (https://sparontologies.github.io/fabio/current/fabio.html), the MESH publication types (https://www.nlm.nih.gov/mesh/pubtypes.html), the Confederation of Open Access Repositories (COAR) Controlled Vocabulary for Resource Type Genres (http://vocabularies.coar-repositories.org/documentation/resource_types/), Wikidata (https://www.wikidata.org/wiki/Wikidata:Publication_types), or equivalent publication type ontology. When a given publication type ontology term is used within a given knowledge graph, then the CURIE identified term must be documented in the graph as a concept node of biolink:category biolink:OntologyClass.
- Range: String
Domain for slot:
- id 1..1
- Description: A unique identifier for an entity. Must be either a CURIE shorthand for a URI or a complete URI
- Range: String
- in subsets: (translator_minimal)
- type 0..*
- Range: String
Other properties
Aliases: | journal | |
In Subsets: | model_organism_database |