Class: PermanentID
Represents a persistent unique identifier for an entity and its relationship to some other entity.
__
The 'id' field and 'relationship_type' fields are required.
__
The values in the 'relationship_type' field come from controlled vocabularies maintained by DataCite and Crossref. See the documentation links below for more details.
__
DataCite relation types: https://support.datacite.org/docs/datacite-metadata-schema-v44-recommended-and-optional-properties#12b-relationtype
__
Crossref relation types: https://www.crossref.org/documentation/schema-library/markup-guide-metadata-segments/relationships/
__
URI: dcm:PermanentID
classDiagram
class PermanentID
click PermanentID href "../PermanentID"
PermanentID : description
PermanentID : id
PermanentID : relationship_type
PermanentID --> "0..1" RelationshipType : relationship_type
click RelationshipType href "../RelationshipType"
Slots
Name | Cardinality and Range | Description | Inheritance |
---|---|---|---|
id | 1 Uriorcurie |
Persistent unique ID for an entity | direct |
description | 0..1 String |
Description of that entity | direct |
relationship_type | 0..1 RelationshipType |
The relationship between the ID and some other entity | direct |
Usages
used by | used in | type | used |
---|---|---|---|
CreditMetadata | related_identifiers | range | PermanentID |
Identifier and Mapping Information
Schema Source
- from schema: https://kbase.github.io/credit_engine/linkml/credit_metadata
Mappings
Mapping Type | Mapped Value |
---|---|
self | dcm:PermanentID |
native | dcm:PermanentID |
LinkML Source
Direct
name: PermanentID
description: 'Represents a persistent unique identifier for an entity and its relationship
to some other entity.
The ''id'' field and ''relationship_type'' fields are required.
The values in the ''relationship_type'' field come from controlled vocabularies
maintained by DataCite and Crossref. See the documentation links below for more
details.
DataCite relation types: https://support.datacite.org/docs/datacite-metadata-schema-v44-recommended-and-optional-properties#12b-relationtype
Crossref relation types: https://www.crossref.org/documentation/schema-library/markup-guide-metadata-segments/relationships/
'
from_schema: https://kbase.github.io/credit_engine/linkml/credit_metadata
attributes:
id:
name: id
description: Persistent unique ID for an entity. Should be in the format <database
name>:<identifier within database>.
examples:
- value: DOI:10.46936/10.25585/60000745
- value: GO:0005456
- value: HGNC:7470
from_schema: https://kbase.github.io/credit_engine/linkml/components
slot_uri: schema:identifier
domain_of:
- License
- PermanentID
range: uriorcurie
required: true
pattern: ^[a-zA-Z0-9.-_]+:\S
description:
name: description
description: Description of that entity.
examples:
- value: Amaranthus hypochondriacus genome
- value: This data analysis workflow demonstrates how to process a metagenome
to identify viruses using VirSorter. Then, provides taxonomic classification
using vConTACT2.
from_schema: https://kbase.github.io/credit_engine/linkml/components
rank: 1000
slot_uri: schema:description
domain_of:
- PermanentID
relationship_type:
name: relationship_type
description: The relationship between the ID and some other entity. For example,
when a PermanentID class is used to represent objects in the CreditMetadata
field 'related_identifiers', the 'relationship_type' field captures the relationship
between the resource being registered and this ID.
from_schema: https://kbase.github.io/credit_engine/linkml/components
rank: 1000
domain_of:
- PermanentID
range: RelationshipType
Induced
name: PermanentID
description: 'Represents a persistent unique identifier for an entity and its relationship
to some other entity.
The ''id'' field and ''relationship_type'' fields are required.
The values in the ''relationship_type'' field come from controlled vocabularies
maintained by DataCite and Crossref. See the documentation links below for more
details.
DataCite relation types: https://support.datacite.org/docs/datacite-metadata-schema-v44-recommended-and-optional-properties#12b-relationtype
Crossref relation types: https://www.crossref.org/documentation/schema-library/markup-guide-metadata-segments/relationships/
'
from_schema: https://kbase.github.io/credit_engine/linkml/credit_metadata
attributes:
id:
name: id
description: Persistent unique ID for an entity. Should be in the format <database
name>:<identifier within database>.
examples:
- value: DOI:10.46936/10.25585/60000745
- value: GO:0005456
- value: HGNC:7470
from_schema: https://kbase.github.io/credit_engine/linkml/components
slot_uri: schema:identifier
alias: id
owner: PermanentID
domain_of:
- License
- PermanentID
range: uriorcurie
required: true
pattern: ^[a-zA-Z0-9.-_]+:\S
description:
name: description
description: Description of that entity.
examples:
- value: Amaranthus hypochondriacus genome
- value: This data analysis workflow demonstrates how to process a metagenome
to identify viruses using VirSorter. Then, provides taxonomic classification
using vConTACT2.
from_schema: https://kbase.github.io/credit_engine/linkml/components
rank: 1000
slot_uri: schema:description
alias: description
owner: PermanentID
domain_of:
- PermanentID
range: string
relationship_type:
name: relationship_type
description: The relationship between the ID and some other entity. For example,
when a PermanentID class is used to represent objects in the CreditMetadata
field 'related_identifiers', the 'relationship_type' field captures the relationship
between the resource being registered and this ID.
from_schema: https://kbase.github.io/credit_engine/linkml/components
rank: 1000
alias: relationship_type
owner: PermanentID
domain_of:
- PermanentID
range: RelationshipType