Providing a Metadata_Creation date and Metadata_Last_Revision date is required in DIF 10. The Metadata_Future_Review and Metadata_Delete fields are optional. Multiple types of Metadata Dates may be provided, if necessary (Cardinality 1..*)
UMM-C Element | DIF 10 Path | Type | Usable Valid Values | Constraints | Required in DIF 10? | Cardinality | Notes |
---|
MetadataDate/Date MetadataDate/Type=CREATE | Metadata_Dates/Metadata_Creation | Date dateTime Enumeration | unknown present unbounded future Not provided | n/a | Yes | 1 | Dates provided in the Metadata_Creation field will be labeled with the MetadataDate/Type of 'CREATE' when translated to UMM. If any of the enumeration values are provided (unknown, present, unbounded, future, Not provided) the date will automatically default to 1970-01-01T00:00:00Z when being translated to UMM. This is because UMM does not currently support any enumeration values in date fields. | MetadataDate/Date MetadataDate/Type=UPDATE | Metadata_Dates/Metadata_Last_Revision | Date dateTime Enumeration | unknown present unbounded future Not provided | n/a | Yes | 1 | Dates provided in the Metadata_Last_Revision field will be labeled with the MetadataDate/Type of 'UPDATE' when translated to UMM. If any of the enumeration values are provided (unknown, present, unbounded, future, Not provided) the date will automatically default to 1970-01-01T00:00:00Z when being translated to UMM. This is because UMM does not currently support any enumeration values in date fields. | MetadataDate/Date MetadataDate/Type=REVIEW | Metadata_Dates/Metadata_Future_Review | Date dateTime Enumeration | unknown present unbounded future Not provided | n/a | No | 0..1 | Dates provided in the Metadata_Future_Review field will be labeled with the MetadataDate/Type of 'REVIEW' when translated to UMM. If any of the enumeration values are provided (unknown, present, unbounded, future, Not provided) the date will automatically default to 1970-01-01T00:00:00Z when being translated to UMM. This is because UMM does not currently support any enumeration values in date fields. | MetadataDate/Date MetadataDate/Type=DELETE | Metadata_Dates/Metadata_Delete | Date dateTime Enumeration | unknown present unbounded future Not provided | n/a | No | 0..1 | Dates provided in the Metadata_Delete field will be labeled with the MetadataDate/Type of 'DELETE' when translated to UMM. If any of the enumeration values are provided (unknown, present, unbounded, future, Not provided) the date will automatically default to 1970-01-01T00:00:00Z when being translated to UMM. This is because UMM does not currently support any enumeration values in date fields. |
Value needed for translations: Not provided - The value of 'Not provided' might appear in the Metadata_Dates/Metadata_Creation and/or the Metadata_Dates/Metadata_Last_Revision fields as a result of software used to convert older versions of DIF to newer versions of DIF (such as 10.2 or 10.3). Required fields that are left empty in older versions of a DIF record are automatically populated with 'Not provided' when being converted to a new version, and both Metadata_Dates/Metadata_Creation and Metadata_Dates/Metadata_Last_Revision are required in the latest version of DIF. This value should not be used by metadata providers. Example Mapping
Section |
---|
Column |
---|
| DIF 10 No Format |
---|
<Metadata_Dates>
<Metadata_Creation>2014-01-13</Metadata_Creation>
<Metadata_Last_Revision>2018-11-06</Metadata_Last_Revision>
<Metadata_Future_Review>2100-01-01</Metadata_Future_Review>
</Metadata_Dates> |
|
Column |
---|
| UMM No Format |
---|
DataDates: [
{
Date: "2014-01-13T00:00:00.000Z",
Type: "CREATE"
},
{
Date: "2018-11-06T00:00:00.000Z",
Type: "UPDATE"
},
{
Date: "2100-01-01T00:00:00.000Z",
Type: "REVIEW"
},
] |
|
|
|