ID | Property | Obligation | Occ | Definition | Allowed values, constraints, remarks |
1 | Identifier | M | 1 | Unique string that identifies the instrument instance | |
1.1 | identifierType | M | 1 | Type of the identifier | [1] |
2 | SchemaVersion | M | 1 | Version number of the PIDINST schema used in this record | Fixed value [2] |
3 | LandingPage | M | 1 | A landing page that the identifier resolves to | URL |
4 | Name | M | 1 | Name by which the instrument instance is known | Free text |
5 | Owner | M | 1-n | Institution(s) responsible for the management of the instrument. This may include the legal owner, the operator, or an institute providing access to the instrument. | |
5.1 | ownerName | M | 1 | Full name of the owner | Free text |
5.2 | ownerContact | O | 0-1 | Contact address of the owner | Electronic mail address |
5.3 | ownerIdentifier | O | 0-1 | Identifier used to identify the owner | Free text, should be a globally unique identifier. |
5.3.1 | ownerIdentifierType | O | 1 | Type of the identifier | Free text |
6 | Manufacturer | M | 1-n | The instrument's manufacturer(s) or developer. This may also be the owner for custom build instruments | |
6.1 | manufacturerName | M | 1 | Full name of the manufacturer | Free text |
6.2 | manufacturerIdentifier | O | 0-1 | Identifier used to identify the manufacturer | Free text, should be a globally unique identifier. |
6.2.1 | manufacturerIdentifierType | O | 1 | Type of the identifier | Free text |
7 | Model | R | 0-1 | Name of the model or type of device as attributed by the manufacturer | |
7.1 | modelName | R | 1 | Full name of the model | Free text |
7.2 | modelIdentifier | O | 0-1 | Identifier used to identify the model | Free text, should be a globally unique identifier. |
7.2.1 | modelIdentifierType | O | 1 | Type of the identifier | Free text |
8 | Description | R | 0-1 | Technical description of the device and its capabilities | Free text |
9 | InstrumentType | R | 0-n | Classification of the type of the instrument | |
9.1 | instrumentTypeName | R | 1 | Full name of the instrument type | Free text |
9.2 | instrumentTypeIdentifier | O | 0-1 | Identifier used to identify the type of the instrument | Free text, should be a globally unique identifier |
9.2.1 | instrumentTypeIdentifierType | O | 1 | Type of the identifier | Free text |
10 | MeasuredVariable | R | 0-n | The variable(s) that this instrument measures or observes | Free text |
11 | Date | R | 0-n | Dates relevant to the instrument | ISO 8601 |
11.1 | dateType | R | 1 | The type of the date | Controlled list of values: Commissioned, DeCommissioned |
12 | RelatedIdentifier | R | 0-n | Identifiers of related resources | Free text, must be globally unique identifiers. |
12.1 | relatedIdentifierType | R | 1 | Type of the identifier | Controlled list of values: ARK, arXiv, bibcode, DOI, EAN13, EISSN, Handle, IGSN, ISBN, ISSN, ISTC, LISSN, PMID, PURL, RAiD, RRID, UPC, URL, URN, w3id |
12.2 | relationType | R | 1 | Description of the relationship | Controlled list of values: IsDescribedBy, IsNewVersionOf, IsPreviousVersionOf, HasComponent, IsComponentOf, References, HasMetadata, WasUsedIn, IsIdenticalTo, IsAttachedTo |
12.3 | relatedIdentifierName | O | 0-1 | A name for the related resource, may be used to give a hint on the content of that resource | Free text |
13 | AlternateIdentifier | R | 0-n | Identifiers other than the PIDINST pertaining to the same instrument instance. This should be used if the instrument has a serial number. Other possible uses include an owner's inventory number or an entry in some instrument data base. | Free text, should be unique identifiers |
13.1 | alternateIdentifierType | R | 1 | Type of the identifier | Controlled list of values: SerialNumber, InventoryNumber, Other |
13.2 | alternateIdentifierName | O | 0-1 | A supplementary name for the identifier type. This is mostly useful if alternateIdentifierType is Other. | Free text |
[1] | The type of the identifier depends on the provider being used to register the instrument PID. In the case of ePIC, the value of identifierType would be "Handle". |
[2] | The value of SchemaVersion is defined to be equal to the version number for each release version of the schema. |