207 lines
5.9 KiB
Plaintext
207 lines
5.9 KiB
Plaintext
head 1.7;
|
|
access;
|
|
symbols;
|
|
locks; strict;
|
|
comment @# @;
|
|
|
|
|
|
1.7
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next 1.6;
|
|
|
|
1.6
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next 1.5;
|
|
|
|
1.5
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next 1.4;
|
|
|
|
1.4
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next 1.3;
|
|
|
|
1.3
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next 1.2;
|
|
|
|
1.2
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next 1.1;
|
|
|
|
1.1
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next ;
|
|
|
|
|
|
desc
|
|
@Initial revision
|
|
@
|
|
|
|
|
|
1.7
|
|
log
|
|
@Revision 7
|
|
@
|
|
text
|
|
@---+++ AbcdConcept0382
|
|
|
|
---+++++ Identifier
|
|
|
|
<verbatim>DataSets/DataSet/Units/Unit/Identifications/Identification/Date</verbatim>
|
|
|
|
|
|
|
|
---+++++ Group
|
|
|
|
Identification
|
|
|
|
---+++++ Subgroup
|
|
|
|
|
|
---+++++ Full Name
|
|
|
|
|
|
---+++++ Documentation
|
|
|
|
The date of the unit identification event.
|
|
|
|
---+++++ Content
|
|
|
|
The date of the unit identification event. Identification dates are commonly incompletely known (e.g. only the year or year and month) or unknown. Sometimes identification dates are inferred from a researcher's visit or the duration of a loan.
|
|
|
|
The rather complex ABCD <verbatim>DateTime</verbatim> type is used, although many of its elements are not normally needed. As a rule, only the <verbatim>IsoDateTimeBegin</verbatim> element is mapped, which is the one used for searches and which can be used to construct identification histories. Alternatively, the <verbatim>DateText</verbatim> element can also be used, but it provides only for human readability.
|
|
|
|
However, the elements for exact time and periods may be useful for time series in laboratory reports that can be formulated as a series of identification events, or where the result of the identification may be influenced by the duration of a detection process.
|
|
|
|
---++++ Recommended or Prescribed Values
|
|
|
|
---+++++ Example Value
|
|
|
|
---+++++ Example Explanation
|
|
|
|
---+++++ Reviewer
|
|
Berendsohn 12 Apr 2005
|
|
|
|
---++++ Editorial Notes
|
|
@
|
|
|
|
|
|
1.6
|
|
log
|
|
@Revision 6
|
|
@
|
|
text
|
|
@d38 1
|
|
a38 1
|
|
Berendsohn 10 Apr 2005
|
|
a40 4
|
|
|
|
Can you check the English, please? The curly brackets are used to avoid links caused by included uppercase letters.
|
|
|
|
$$Walter$$ Some minor changes - can you review again?
|
|
@
|
|
|
|
|
|
1.5
|
|
log
|
|
@Revision 5
|
|
@
|
|
text
|
|
@d21 1
|
|
a21 1
|
|
Date of the unit identification event.
|
|
d25 1
|
|
a25 1
|
|
Date of the unit identification event. Identification dates are commonly incompletely known (e.g. only the year or year and month) or unknown. Sometimes identification dates are inferred from a researcher's visit or duration of a loan.
|
|
d27 3
|
|
a29 1
|
|
The rather complex ABCD <verbatim>DateTime</verbatim> type is used, although many of its elements are not normally needed. As a rule, only the <verbatim>IsoDateTimeBegin</verbatim> element is mapped, which is the one used for searches and which can be used to construct identification histories. Alternatively, the <verbatim>DateText</verbatim> element can also be used, but it provides only for human readability. However, the elements for exact time and periods may support usage for time series in laboratory reports that can be formulated as a series of identification events or where the result of the identification may be influenced by the duration of a detection process.
|
|
d42 3
|
|
a44 1
|
|
$$YAEL$$ Can you check the English, please? The curly brackets are used to avoid links caused by included uppercase letters.
|
|
@
|
|
|
|
|
|
1.4
|
|
log
|
|
@Revision 4
|
|
@
|
|
text
|
|
@d27 1
|
|
a27 1
|
|
The rather complex ABCD <verbatim>DateTime</verbatim> type is used, although many of its elements are not normally needed. As a rule, only the <verbatim>IsoDateTimeBegin</verbatim> element is mapped, which is the one used for searches and which can be used to construct identification histories. Alternatively, the <verbatim>DateText</verbatim> element can also be used, but it provides only for human readability. However, the elements for exact time may support usage for time series in laboratory or field reports that can be formulated as a series of identification events (including negative identifications).
|
|
@
|
|
|
|
|
|
1.3
|
|
log
|
|
@Revision 3
|
|
@
|
|
text
|
|
@d27 1
|
|
a27 1
|
|
The rather complex ABCD <verbatim>DateTime</verbatim> type is used, although many of its elements are not needed. As a rule, only the <verbatim>IsoDateTimeBegin</verbatim> element is mapped, which is the one used for searches and which can be used to construct identification histories. Alternatively, the <verbatim>DateText</verbatim> element can also be used, but it provides only for human readability.
|
|
d40 1
|
|
a40 1
|
|
$$CHANGE$$ <verbatim>DateTime</verbatim> type could be replaced by the two elements commonly mapped.
|
|
@
|
|
|
|
|
|
1.2
|
|
log
|
|
@Revision 2
|
|
@
|
|
text
|
|
@d25 1
|
|
a25 1
|
|
Date of the unit identification event.
|
|
d27 1
|
|
a27 3
|
|
Identification dates are commonly unknown (element optional), or incompletely known. Missing information reduces the precision of the date (i.e., known only to Year or Year and Month). Sometimes identification dates are inferred from a researcher's visit or duration of a loan.
|
|
|
|
See Date-Type for general usage.
|
|
a30 1
|
|
|
|
a32 6
|
|
1985-07-14
|
|
|
|
July 14
|
|
|
|
July 14, 1985
|
|
|
|
a34 1
|
|
|
|
d36 1
|
|
a36 1
|
|
|
|
d40 1
|
|
a40 3
|
|
We probably don't need IdentificationDate to support the full range of date time elements that are present in the DateTime. It's hard to imagine a realistic case where time of day could be relevant to an identification. If year is unknown, simple text will provide the only function needed -- human readability of the existing information. (Retrieval and sorting by interval in the annual cycle, as we want to support with CollectionDate, is irrelevant in this case.) A single ISO 8061 Date field, along with an IdentificationDate text is sufficient to cover the needs around this concept. -- Blum, 2002-12-10
|
|
|
|
$$Walter$$ Do you want these editorial notes I found in the schema included here?
|
|
@
|
|
|
|
|
|
1.1
|
|
log
|
|
@Initial revision
|
|
@
|
|
text
|
|
@a0 1
|
|
|
|
d11 1
|
|
d21 1
|
|
d25 5
|
|
d36 5
|
|
d50 1
|
|
d52 1
|
|
@
|