agent_config.yaml

# metamodel_version: 1.7.0# version: 3.0.3id: agent
schema_generating: true
description: person, group, organization or project that provides a piece of information
  (i.e. a knowledge association)
display_name: agent
document_category: agent
weight: 20
fields:
- id: iri
  description: An IRI for an entity. This is determined by the id using expansion
    rules.
  display_name: iri
- id: type
  display_name: type
- id: description
  description: a human-readable description of an entity
  display_name: description
- id: source
  display_name: source
- id: has_attribute
  description: connects any entity to an attribute
  display_name: has attribute
  cardinality: multi
- id: provided_by
  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.
  display_name: provided by
  cardinality: multi
- id: xref
  description: Alternate CURIEs for a thing
  display_name: xref
  cardinality: multi
- id: category
  description: "Name of the high level ontology class in which this entity is categorized.\
    \ Corresponds to the label for the biolink entity type class.\n * In a neo4j database\
    \ this MAY correspond to the neo4j label tag.\n * In an RDF database it should\
    \ be a biolink model class URI.\nThis 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`,\
    \ ...\nIn 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}"
  display_name: named thing_category
  cardinality: multi
- id: affiliation
  description: a professional relationship between one provider (often a person) within
    another provider (often an organization). Target provider identity should be specified
    by a CURIE. Providers may have multiple affiliations.
  display_name: affiliation
  cardinality: multi
- id: address
  description: the particulars of the place where someone or an organization is situated.  For
    now, this slot is a simple text "blob" containing all relevant details of the
    given location for fitness of purpose. For the moment, this "address" can include
    other contact details such as email and phone number(?).
  display_name: address
- id: id
  description: Different classes of agents have distinct preferred identifiers. For
    publishers, use the ISBN publisher code. See https://grp.isbn-international.org/
    for publisher code lookups. For editors, authors and  individual providers, use
    the individual's ORCID if available; Otherwise, a ScopusID, ResearchID or Google
    Scholar ID ('GSID') may be used if the author ORCID is unknown. Institutional
    agents could be identified by an International Standard Name Identifier ('ISNI')
    code.
  display_name: agent_id
- id: name
  description: it is recommended that an author's 'name' property be formatted as
    "surname, firstname initial."
  display_name: agent_name