DIF 10Data Date is an optional field. Multiple Data Dates may be provided, if necessary (Cardinality 0..*)
UMM-C Element | Path | Type | Usable Valid Values | Constraints | Required in DIF 10? | Cardinality | Notes |
---|
DataDate/Type = CREATE DataDate/Date | Metadata_Dates/Data_Creation | Date dateTime Enumeration | unknown present unbounded future Not provided | n/a | No | 0..1 | Dates provided in the Data_Creation field will be labeled with the DataDate/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. | DataDate/Type = UPDATE DataDate/Date | Metadata_Dates/Data_Last_Revision | Date dateTime Enumeration | unknown present unbounded future Not provided | n/a | No | 0..1 | Dates provided in the Data_Last_Revision field will be labeled with the DataDate/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. | DataDate/Type = REVIEW DataDate/Date | Metadata_Dates/Data_Future_Review | Date dateTime Enumeration | unknown present unbounded future Not provided | n/a | No | 0..1 | Dates provided in the Data_Future_Review field will be labeled with the DataDate/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. | DataDate/Type = DELETE DataDate/Date | Metadata_Dates/Data_Delete | Date dateTime Enumeration | unknown present unbounded future Not provided | n/a | No | 0..1 | Dates provided in the Data_Delete field will be labeled with the DataDate/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/Data_Creation and/or the Metadata_Dates/Data_Last_Revision fields as a result of software used to convert older versions of DIF to DIF version 10.2. Required fields that are left empty in older versions a DIF record are automatically populated with 'Not provided' when being converted to a new version, and both Metadata_Dates/Data_Creation and Metadata_Dates/Data_Last_Revision are required in DIF version 10.2. Both Data_Creation and /Data_Last_Revision were changed from required to optional in DIF version 10.3. Therefore, no DIF 10.3 records should have 'Not provided' as a value in the Data_Creation or Data_Last_Revision fields. This value should not be used by metadata providers. Example Mapping
Section |
---|
Column |
---|
| DIF 10 No Format |
---|
<Metadata_Dates>
<Data_Creation>2012-12-12</Data_Creation>
<Data_Last_Revision>2018-10-03</Data_Last_Revision>
<Data_Future_Review>2100-01-01</Data_Future_Review>
</Metadata_Dates> |
|
Column |
---|
| UMM No Format |
---|
DataDates: [
{
Date: "2012-12-12T00:00:00.000Z",
Type: "CREATE"
},
{
Date: "2018-10-03T00:00:00.000Z",
Type: "UPDATE"
},
{
Date: "2100-01-01T00:00:00.000Z",
Type: "REVIEW"
},
] |
|
|
|