¶ dcr:administrativeData
The element dcr:administrativeData contains all essential administrative information, which describes various details of the certificate request, e. g. also details of the manufacturer, client, laboratory, time agreements etc
¶ Tree structure
The tree structure of the element dcr:administrativeData has the following appearance:
¶ Extract from the XML schema: Element definition "dcr:administrativeData"
...
<xs:element name="administrativeData">
<xs:complexType>
<xs:sequence>
<xs:element name="software" type="dx:softwareType"/>
<xs:element name="identicationList" type="dx:identificationListType"/>
<xs:element name="customer" type="dcr:extendedContactListType"/>
<xs:element name="laboratory" type="dcr:extendedContactListType"/>
<xs:element name="requestedCertificate"
type="dcr:requestedCertificateType"/>
<xs:element name="requirements" type="dcr:requirementsType"/>
<xs:element name="contractList" type="dcr:contractListType" minOccurs="0"/>
<xs:element name="dataProcessingList" type="dcr:dataProcessingListType"
minOccurs="0"/>
<xs:element name="serviceFeatureList" type="dcr:serviceFeatureListType"
minOccurs="0"/>
</xs:sequence>
</xs:complexType>
</xs:element>
...
¶ Description of the elements
See the list of abbreviations here
| Element Element type |
Use | Description |
|---|---|---|
| dcr:software (dx:softwareType) |
[M] | Essential information to identify the software used to create the DCR is stored here. |
| dcr:uniqueIdentifier (dx:identifierType) |
[M] | A worldwide unique identifier for the certificate or report shall be specified here. A necessary condition is that the identifier is unique in the organisation where the calibration laboratory is located. |
| dcr:identificationList (dx:identificationListType) |
[M] | Specification of identifications used in the DCR. |
| dcr:requestedCertificate (dcr:requestedCertificateType) |
[M] | Information regarding the certificate being requested. This allows the user to specify whether they desire a Digital Calibration Certificate (DCC), Digital Test Certificate (DTC), Digital Verification Certificate (DVC), or another. |
| dcr:requirements (dcr:requirementsType) |
[M] | This element specifies the requirements for the measurement procedure set out in the DCR. |
| dcr:customer (dcr:extendedContactListType) |
[O] | Responsible persons and a general contact typically found on the customer side. Often, this involves the supplier of the DCR. |
| dcr:laboratory (dcr:extendedContactListType) |
[O] | Responsible persons and general contact typically found within the laboratory. Often, these contacts should be addressed when sending out a DCR. |
| Details about the requirements for a certificate request. This includes specifying the desired human-readable formats or indicating whether the customer requires one certificate per measurement or conformity statements or something else. | ||
| dcr:contractList (dcr:contractListType) (In Discussion) |
[O] | Contracts offered with the DCR. This elements include time agreements as a part of a contract of the DCR. |
| dcr:dataProcessingList (dcr:dataProcessingListType) |
[O] | Definition of distinct categories of data transformations or analysis procedures needed in the data processing phase. Customers are provided with flexibility by enabling them to outline each specific procedure through a predefined list of options such as linearization, interpolation coefficient calculation, trend analysis, utilizing previous calibration data, among others. Additionally, supplementary details about each are provided via an optional description field. |
| dcr:serviceFeatureList (dcr:serviceFeatureListType) |
[O] | Documention for different services that might be required to be done in a laboratory. It supports detailed documentation for each service feature, including descriptions, responsibilities, and scheduling details, thereby facilitating clear communication and management within the laboratory or with external stakeholders. |