Difference between revisions of "Verbatim Date"
From BDI Data
(Created claim: example (localized) (P6): Autumn 1805) |
(Changed claim: is part of (P8): Preliminary Concept Pool (Q64)) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| property / is part of | property / is part of | ||
| - | + | ||
| property / example (localized) | |||
| + | 17.05.192? (last digit indistinguishable, could be 5, 9 or 2) (English) | ||
| property / example (localized): 17.05.192? (last digit indistinguishable, could be 5, 9 or 2) (English) / rank | |||
| + | Normal rank | ||
| property / Usage Notes | |||
| + | A text version (alphabetic mixed case and integer) of the date at which the unit identification event took place. This element is meant for use when the date is imprecise, ambiguous or not in a form that satisfies the standard structured date format. It can also be used when it is important to record the verbatim representation of the date or when dates to be recorded are not completely legible. (English) | ||
| property / Usage Notes: A text version (alphabetic mixed case and integer) of the date at which the unit identification event took place. This element is meant for use when the date is imprecise, ambiguous or not in a form that satisfies the standard structured date format. It can also be used when it is important to record the verbatim representation of the date or when dates to be recorded are not completely legible. (English) / rank | |||
| + | Normal rank | ||
| property / Usage Notes | |||
| + | For example the day and month may be decipherable but not the year; the use of this field will allow recording of partially interpreted information.This field can be used to record generalised date ranges and irresolvable ambiguity such as different day/month order conventions (e.g. US/Europe) or to allow for multiple dates and periods. (English) | ||
| property / Usage Notes: For example the day and month may be decipherable but not the year; the use of this field will allow recording of partially interpreted information.This field can be used to record generalised date ranges and irresolvable ambiguity such as different day/month order conventions (e.g. US/Europe) or to allow for multiple dates and periods. (English) / rank | |||
| + | Normal rank | ||
| property / has exact match | |||
| + | |||
| property / has exact match: http://rs.tdwg.org/dwc/terms/verbatimEventDate / rank | |||
| + | Normal rank | ||
Latest revision as of 08:47, 24 October 2018
A date in a free text format.
In more languages
Configure| Language | Label | Description | Also known as |
|---|---|---|---|
| English |
Verbatim Date
|
A date in a free text format.
|
Statements
VerbatimDate
0 references
String
0 references
January 21st, 1900 (English)
0 references
Autumn 1805 (English)
0 references
17.05.192? (last digit indistinguishable, could be 5, 9 or 2) (English)
0 references
A text version (alphabetic mixed case and integer) of the date at which the unit identification event took place. This element is meant for use when the date is imprecise, ambiguous or not in a form that satisfies the standard structured date format. It can also be used when it is important to record the verbatim representation of the date or when dates to be recorded are not completely legible. (English)
0 references
For example the day and month may be decipherable but not the year; the use of this field will allow recording of partially interpreted information.This field can be used to record generalised date ranges and irresolvable ambiguity such as different day/month order conventions (e.g. US/Europe) or to allow for multiple dates and periods. (English)
0 references
