5,887
edits
Data Ingestion Guidance: Difference between revisions
→Data recommendations for optimal searchability and applicability in the aggregate
| Line 143: | Line 143: | ||
*'''Dates''': put dates in [http://www.w3.org/TR/NOTE-datetime ISO 8601] format, i.e., YYYY-MM-DD, e.g., 2014-06-22. The critical element in this date is a four character year. e.g., http://rs.tdwg.org/dwc/terms/#eventDate. | *'''Dates''': put dates in [http://www.w3.org/TR/NOTE-datetime ISO 8601] format, i.e., YYYY-MM-DD, e.g., 2014-06-22. The critical element in this date is a four character year. e.g., http://rs.tdwg.org/dwc/terms/#eventDate. | ||
*'''Meters''': put elevation in METERS units in the elevation field without the units (e.g., the fields ''dwc:minimumElevationInMeters'' and ''dwc:maximumElevationInMeters'' already assume the numeric values are in meters, so there no need to include the units with the data). | *'''Meters''': put elevation in METERS units in the elevation field without the units (e.g., the fields ''dwc:minimumElevationInMeters'' and ''dwc:maximumElevationInMeters'' already assume the numeric values are in meters, so there no need to include the units with the data). | ||
*'''Escapes''': do not use unescaped newline characters. | *'''Escapes''': do not use unescaped newline characters in text fields. | ||
*'''Data uncertainty''': use the remarks fields to express doubt or missing values in data, Something like '?' is not a helpful value, and cannot be searched for | *'''Data uncertainty''': use the remarks fields to express doubt or missing values in data, Something like '?' is not a helpful value, and cannot be searched for | ||
*'''No '0'''': do not export '0' in fields to represent no value, e.g., lat or lon. This caution applies to '?', 'NA', '00/00/0000' and any other placeholder value. | *'''No '0'''': do not export '0' in fields to represent no value, e.g., lat or lon. This caution applies to '?', 'NA', '00/00/0000' and any other placeholder value. | ||