Article
None
classDiagram
Publication <|-- Article
Article : authors
Article : category
Article : creation_date
Article : description
Article : format
Article : has_attribute
Article : id
Article : iri
Article : iso_abbreviation
Article : issue
Article : keywords
Article : license
Article : mesh_terms
Article : name
Article : pages
Article : provided_by
Article : published_in
Article : rights
Article : source
Article : summary
Article : type
Article : volume
Article : xref
Parent Classes
Slots
| Name | Description |
|---|---|
| authors | 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. |
| 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, etc. 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} |
| creation_date | date on which an entity was created. This can be applied to nodes or edges |
| description | a human-readable description of an entity |
| format | None |
| has_attribute | connects any entity to an attribute |
| id | A unique identifier for an entity. Must be either a CURIE shorthand for a URI or a complete URI |
| iri | An IRI for an entity. This is determined by the id using expansion rules. |
| iso_abbreviation | Optional value, if used locally as a convenience, is set to the iso abbreviation of the 'published in' parent. |
| issue | issue of a newspaper, a scientific journal or magazine for reference purpose |
| keywords | keywords tagging a publication |
| license | None |
| mesh_terms | mesh terms tagging a publication |
| name | A human-readable name for an attribute or entity. |
| pages | page number of source referenced for statement or publication |
| 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. |
| published_in | The enclosing parent serial containing the article should have industry-standard identifier from ISSN. |
| rights | None |
| source | None |
| summary | executive summary of a publication |
| type | None |
| volume | volume of a book or music release in a collection/series or a published collection of journal issues in a serial publication |
| xref | Alternate CURIEs for a thing |
Mappings
| Mapping Type | Mapped Value |
|---|---|
| self | ['biolink:Article'] |
| native | ['biolink:Article'] |