INM7 simplified data models for manual metadata entry
The classes and slots in this schema have the (sole) purpose of informing the auto-generation of UIs for data entry. Consequently, the simplify and lump-together concepts and constructs that will eventually be represented with more appropriate data structures from the `base` schema. More information is available on the schema's [about page](about). The schema definition is available as - [JSON-LD context](../unreleased.jsonld) - [LinkML YAML](../unreleased.yaml) - [OWL TTL](../unreleased.owl.ttl) - [SHACL TTL](../unreleased.shacl.ttl)
ALL CONTENT HERE IS UNRELEASED AND MAY CHANGE ANY TIME
An unambiguous reference to the subject within a given context.
A tag/value pair with the semantics of OWL Annotation.
A `Thing` that is a value of some kind. This class can be used to describe an outcome of a measurement, a factual value or constant, or other qualitative or quantitative information with an associated identifier. If no identifier is available, an `AttributeSpecification` can be used within the context of an associated `Thing` (`attributes`).
Mix-in for a (structured) value specification. Two slots are provided to define a (literal) value (`value`) and its type (`range`).
A record of properties of the metadata record on a subject, a collection of tag/text tuples with the semantics of OWL Annotation.
Declares a relation that associates a `Thing` (or another attribute) with an attribute, where an attribute is an intrinsic characteristic, such as a quality, capability, disposition, function, or is an externally derived attribute determined from some descriptor (e.g. a quantity, position, label/identifier). Technically, this declaration is done via an `AttributeSpecification` that combines a `predicate` with a value declaration and the attribute-related slots of a `Thing`. Importantly, such attributes are declared inline, because they do not have a unique identifier. If an identifier is available, a `Thing` declaration (see `relation`), and a qualification of that relationship via a `Statement` (see `characterized_by`) should be preferred.
A list of terms from different schemas or terminology systems that have broader meaning.
Qualifies relationships between a subject `Thing` and an object `Thing` with a `Statement` declaring a `predicate` on the nature of the relationship.
A list of terms from different schemas or terminology systems that have close meaning.
A list of terms from different schemas or terminology systems that have identical meaning.
A list of terms from different schemas or terminology systems that have narrower meaning.
A list of terms from different schemas or terminology systems that have related meaning.
Declares an unqualified relation of the subject `Thing` to another `Thing`. This schema slot is used to define related things inline. If such a definition is not needed. A qualified relationship can be declared directly using the `characterized_by` slot.
Additional name(s) associated with the subject, such as one or more middle names, or a nick name.
A person to whom an assignment to the subject is made. For example, a person appointed or deputed by another to perform some task, or enjoy some privilege.
Persons that are working together on a project.
A comment about a metadata record either providing additional information for a record curation, or leaving a comment after curation occurred. This can be used to include information that is deemed relevant, but could not be expressed in the provided fields.
Grant that provides resources for a project.
Administrative contacts at the local organization.
The subject is a member of an organization.
Room(s) that are the office(s) of the subject.
Organizations that contribute to a project.
Deliverable requirements of the subject.
Administrative contacts at the sponsoring organization.
A Checksum is a value that allows to check the integrity of the contents of a file. Even small changes to the content of the file will change its checksum. This class allows the results of a variety of checksum and cryptographic message digest algorithms to be represented.
Digital Object Identifier (DOI; ISO 26324), an identifier system governed by the DOI Foundation, where individual identifiers are issued by one of several registration agencies.
An agent responsible for making an entity.
The `range` is only `uriorcurie` here (and not `Thing`), because we have an `ifabsent` declaration for DOIs that only work with this type. And even for that it needs a patch.
Name of the agency that issued an identifier.
An RDF statement that links a `predicate` (a `Property`) with an `object` (a `Thing`) to the subject to form a triple. A `Statement` is used to qualify a relation to a `Thing` referenced by its identifier. For specifying a qualified relation to an attribute that has no dedicated identifier, use an `AttributeSpecification`.
Reference to a `Thing` within a `Statement`.
We do not declare a range here to be able to tighten the range in subclasses of class that need a particular range. This appears to be working around a linkml limitation.
Persistent and globally unique identifier of a `Thing`.
Declares that the value of a `Thing` or `AttributeSpecification` are instances of a particular class.
An award, prize, or other honor received in recognition of an achievement.
A report that is published in a journal.
Building level where the subject is located.
Timepoint at which the subject must have been completed at the latest.
Timepoint at which the subject was (last) published.
Timepoint at which the subject was received.
Name to shown when the record is displayed as an item.
Associated Digital Object Identifier (DOI; ISO 26324; see https://doi.org). The value must be just the DOI without the URL project. So just `10.1038/s41597-022-01163-2` and not `https://doi.org/10.1038/s41597-022-01163-2`.
The (inherited) family name of the subject. In many Western languages this is the "last name".
The given (non-inherited) name of the subject.
The honorific prefix(es) of the subject's name. For example, (academic/formal) titles like "Mrs", or "Dr", "Dame".
The honorific suffix(es) of the subject's name. For example, generation labels ("III"), or indicators of an academic degree, a profession, or a position ("MD", "BA").
Associated International Standard Serial Number (ISSN) identifier (see https://www.issn.org).
Local budget awarded by the sponsor in Euros.
SAP PSP element associated with the subject.
Associated ORCID identifier (see https://orcid.org).
An organization the subject is a part of.
Total budget provided by the sponsor in Euros.
Identifier for a grant issued by the sponsor.
An identifier that has been derived from information on the identified entity.
An identifier that was issued by a particular agent with a notation that has no (or an undefined) relation to the nature of the identified entity.
String of characters such as "T58:5" or "30:4833" used to uniquely identify a concept within the scope of a given concept scheme.
An attribute is conceptually a thing, but it requires no dedicated identifier (`pid`). Instead, it is linked to a `Thing` via its `attributes` slot and declares a `predicate` on the nature of the relationship.
Mix-in with the common interface of `Thing` and `AttributeSpecification`. This interface enables type specifications (`rdf:type`) for things and attributes via a `type` designator slot to indicate specialized schema classes for validation where a slot's `range` is too generic. A thing or attribute can be further describe with statements on qualified relations to other things (`characterized_by`), or inline attributes (`attributes`). A set of `mappings` slots enables the alignment for arbitrary external schemas and terminologies.
People that contributed to a document in the author role.
Projects that have contributed to the subject.
Person(s) that are formal or informal leaders of the subject.
A list of terms from different schemas or terminology systems that have comparable meaning. These may include terms that are precisely equivalent, broader or narrower in meaning, or otherwise semantically related but not equivalent from a strict ontological perspective.
A single level or floor of a (multilevel) building.
An entity that needs to be provided to another party, typically requiring to perform a specific task. For example, a write-up on a specific development, a software tool ready for download, a dataset acquired.
A grant, typically financial or otherwise quantifiable, resources.
A periodical that publishes (peer-reviewed) academic articles.
A place or region where entities (building, office, etc.) reside.
An RDF property, a `Thing` used to define a `predicate`, for example in a `Statement`.
Reference to a `Property` within a `Statement`.
A collection of data, published or curated by a single agent.
An area within a building enclosed by walls and floor and ceiling.
A description of how the subject should be acknowledged.
Timepoint at which the subject ends or ended.
Timepoint at which the subject starts or started.
An identifier is a label that uniquely identifies an item in a particular context. Some identifiers are globally unique. All identifiers are unique within their individual scope.
A collective endeavour of some kind. Typically it is a planned process that is undertaken or attempted to meet some requirement, or to achieve a particular goal.
A social or legal institution such as a company, a society, or a university.
Technical helper providing curation-related slots.
A shortened name for the subject. For example, an acronym, initialism, nickname, or other abbreviation of the name or title.
A summarily description of the subject. It is closely related to a `name`, but often less compact and more descriptive. Typically used for documents.
The most basic, identifiable item. In addition to the slots that are common between a `Thing` and an `AttributeSpecification` (see `ThingMixin`), two additional slots are provided. The `pid` slot takes the required identifier for a `Thing`. The `relation` slot allows for the inline specification of other `Thing` instances. Such a relation is unqualified (and symmetric), and should be further characterized via a `Statement` (see `characterized_by`). From a schema perspective, the `relation` slots allows for building self-contained, structured documents (e.g., a JSON object) with arbitrarily complex information on a `Thing`.
State that the subject is an instance of a particular schema class. Typically, no explicit value needs to be assigned to this slot, because it matches the class type of a particular record. However, this slots can be used as a type designator of a schema element for validation and schema structure handling purposes. This is used to indicate specialized schema classes for properties that accept a hierarchy of classes as their range.