Record date (recommended)
Definition
Export date of the record
Other possible database element names
Timestamp
Status of the information
Export date
Text/URI
Text (date format ISO 8601 required)
Repeatable
No
Obligation level
Recommended
Notes
Dating the data record in accordance with ISO 8601 contributes to transparency and makes it possibe to assess how up-to-date the information provided is. The export date should be provided.
Cataloguing: Additionally, it may be important for cataloguing purposes to specify a date for the creation and for the last modification of the data record. This date can then be provided in a separate element, but must be clearly distinguishable from the export date.
Examples
2023-02-25
2015-09-01T17:21:05
Expression in LIDO (v1.0 and v1.1)
Note on the export creation date:
The type attribute of <lido:recordInfoSet> holds the value "http://terminology.lido-schema.org/lido00470 " (LIDO record)
and
the type attribute of <lido:recordMetadataDate> holds the value "http://terminology.lido-schema.org/lido00472 " (created)
<lido:recordWrap>
<lido:recordInfoSet lido:type="http://terminology.lido-schema.org/lido00470">
<lido:recordMetadataDate lido:type="http://terminology.lido-schema.org/lido00472">2015-09-01T17:21:05</lido:recordMetadataDate>
</lido:recordInfoSet>
</lido:recordWrap>Comparison with relevant standards and database models
Standard | Element name | Text/URI | Repeatable | Obligation level | Comment |
|---|---|---|---|---|---|
German Digital Library: Metadata requirements for data provision | (No match) | Not applicable | Not applicable | Not applicable |
|
Text (controlled format) | No | Recommended | The type attribute of <recordInfoSet> holds the value "http://terminology.lido-schema.org/lido00470 " (LIDO record) and the type attribute of <recordMetadataDate> holds the value "http://terminology.lido-schema.org/lido00472 " (created). | ||
(No match) | Not applicable | Not applicable | Not applicable |
| |
Text (controlled format) | Not specified | Not specified |
| ||
Metadata Record Date | Text (controlled format) | No | Mandatory |
| |
DFG Practical Guidelines on Digitisation: LIDO core metadata | (No match) | Not applicable | Not applicable | Not applicable |
|
Europeana Data Model (EDM) | (No match) | Not applicable | Not applicable | Not applicable |
|
EODEM application profile | Export Date/Timestamp | Text (controlled format) | No | Mandatory |
|
(No match) | Not applicable | Not applicable | Not applicable | An export date is not provided in the CDWA, but a date for data record creation is: 25.5. Cataloging Date | |
CDWA Lite (2006) | (No match) | Not applicable | Not applicable | Not applicable | An export date is not provided in CDWA Lite, but a date for record creation or modification is: 21.4.5 Record Metadata Date |
(No match) | Not applicable | Not applicable | Not applicable |
| |
Text (date format) | No | Recommended | Core element. The creation and each modifikation of the data record is documented in the change history. The obligation level is determined by the institution. | ||
Text (date format) | Not specified | Not specified | Modeling in http://schema.org is sample-based; the flexible data model allows various solutions. For @type, the most generic suitable type is suggested. | ||
(No match) | Text (controlled format) | Yes | Mandatory | Various timestamps are generated automatically in digiCULT, including Metadata-Creation, Metadata-Modification, LIDO-Record-Modification. | |
Status of information | Text (controlled format) | Yes | Mandatory | The record is automatically dated when exported. Different archive versions can be created and retrieved. |
ID data element
mds0026