340 lines
5.2 KiB
Plaintext
340 lines
5.2 KiB
Plaintext
head 1.15;
|
|
access;
|
|
symbols;
|
|
locks; strict;
|
|
comment @# @;
|
|
|
|
|
|
1.15
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next 1.14;
|
|
|
|
1.14
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next 1.13;
|
|
|
|
1.13
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next 1.12;
|
|
|
|
1.12
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next 1.11;
|
|
|
|
1.11
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next 1.10;
|
|
|
|
1.10
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next 1.9;
|
|
|
|
1.9
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next 1.8;
|
|
|
|
1.8
|
|
date 2007.01.09.00.00.00; author MoinMoin; state Exp;
|
|
branches;
|
|
next 1.7;
|
|
|
|
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.15
|
|
log
|
|
@Revision 15
|
|
@
|
|
text
|
|
@---+++ AbcdConcept0140
|
|
|
|
---+++++ Identifier
|
|
|
|
<verbatim>DataSets/DataSet/Units/Unit/UnitID</verbatim>
|
|
|
|
|
|
|
|
---+++++ Group
|
|
|
|
Meta
|
|
|
|
---+++++ Subgroup
|
|
|
|
|
|
---+++++ Full Name
|
|
|
|
Unit ID
|
|
|
|
---+++++ Documentation
|
|
|
|
A unique identifier for the unit record within the data source.
|
|
|
|
---+++++ Content
|
|
|
|
A unique identifier for the unit record within the data source. The unit ID should provide the key by which a specimen or specimen component can be identified.
|
|
|
|
Preferrably, the unit ID should be stable in the database, so that it also can be used to find the same record again (e.g. for data exchange purposes). The unit ID constitutes the third part of the globally unique record identifier.
|
|
|
|
Equivalent to an accession number which is unique inside the collection; if this is the case, the accession number should be entered both here and under AccessionNumber.
|
|
|
|
In many culture collections, the strain forms the unique identifier and should be entered here (as well as under Strain, AbcdConcept1443).
|
|
|
|
---++++ Recommended or Prescribed Values
|
|
|
|
|
|
---+++++ Example Value
|
|
|
|
|
|
---+++++ Example Explanation
|
|
|
|
|
|
---+++++ Reviewer
|
|
Berendsohn 26 Jun 2005
|
|
|
|
---++++ Editorial Notes
|
|
@
|
|
|
|
|
|
1.14
|
|
log
|
|
@Revision 14
|
|
@
|
|
text
|
|
@d32 1
|
|
a32 1
|
|
In many culture collections, the strain forms the unique identifier and should be entered here (as well as under Strain).
|
|
@
|
|
|
|
|
|
1.13
|
|
log
|
|
@Revision 13
|
|
@
|
|
text
|
|
@d30 3
|
|
a32 1
|
|
Equivalent to an accession number which is unique inside the collection.
|
|
d44 1
|
|
a44 2
|
|
|
|
Berendsohn 14 Jan 2004
|
|
@
|
|
|
|
|
|
1.12
|
|
log
|
|
@Revision 12
|
|
@
|
|
text
|
|
@a45 4
|
|
|
|
How do you want existing standard listed, if at all? Is this ok?
|
|
|
|
No, see 0143, this is done by Neil.
|
|
@
|
|
|
|
|
|
1.11
|
|
log
|
|
@Revision 11
|
|
@
|
|
text
|
|
@d28 3
|
|
a30 1
|
|
Preferrably, the unit ID should be stable in the database, so that it also can be used to find the same record again (e.g. for data exchange purposes). The unit ID constitutes the third part of the record identifier.
|
|
@
|
|
|
|
|
|
1.10
|
|
log
|
|
@Revision 10
|
|
@
|
|
text
|
|
@a29 17
|
|
Existing Standards:
|
|
|
|
HISPID 3: Accession Identifier (=UNIQUEID, =ACCESSIONID, =accid);
|
|
|
|
ITF 2: Accession Identifier (=accid);
|
|
|
|
BioCISE Model: Unit_ID;
|
|
|
|
NBN: Sample_Key-Unit key or Identifying number - can be multiple;
|
|
|
|
Darwin Core 2: Catalog Number;
|
|
|
|
EURISCO: Accession number;
|
|
|
|
FAO/IPGRI MCPD: Accession number;
|
|
|
|
|
|
d47 1
|
|
a47 1
|
|
$$Yael$$ No, see 0143, this is done by Neil.
|
|
@
|
|
|
|
|
|
1.9
|
|
log
|
|
@Revision 9
|
|
@
|
|
text
|
|
@d62 3
|
|
a64 1
|
|
$$Walter$$ How do you want existing standard listed, if at all? Is this ok?
|
|
@
|
|
|
|
|
|
1.8
|
|
log
|
|
@Revision 8
|
|
@
|
|
text
|
|
@d61 2
|
|
@
|
|
|
|
|
|
1.7
|
|
log
|
|
@Revision 7
|
|
@
|
|
text
|
|
@d30 1
|
|
a30 1
|
|
ExistingStandards:
|
|
d38 1
|
|
a38 1
|
|
NBN: Sample_KeyUnit key or Identifying number - can be multiple;
|
|
@
|
|
|
|
|
|
1.6
|
|
log
|
|
@Revision 6
|
|
@
|
|
text
|
|
@d32 2
|
|
a33 1
|
|
HISPID 3: Accession Identifier (=UNIQUEID, =ACCESSIONID, =accid);
|
|
d35 1
|
|
d37 1
|
|
d39 1
|
|
d41 1
|
|
d43 1
|
|
d46 1
|
|
@
|
|
|
|
|
|
1.5
|
|
log
|
|
@Revision 5
|
|
@
|
|
text
|
|
@d33 6
|
|
a38 6
|
|
* ITF 2: Accession Identifier (=accid);
|
|
* BioCISE Model: Unit_ID;
|
|
NBN: Sample_KeyUnit key or Identifying number - can be multiple;
|
|
Darwin Core 2: Catalog Number;
|
|
EURISCO: Accession number;
|
|
FAO/IPGRI MCPD: Accession number;
|
|
@
|
|
|
|
|
|
1.4
|
|
log
|
|
@Revision 4
|
|
@
|
|
text
|
|
@d32 1
|
|
a32 1
|
|
* HISPID 3: Accession Identifier (=UNIQUEID, =ACCESSIONID, =accid);
|
|
@
|
|
|
|
|
|
1.3
|
|
log
|
|
@Revision 3
|
|
@
|
|
text
|
|
@d32 3
|
|
a34 3
|
|
HISPID 3: Accession Identifier (=UNIQUEID, =ACCESSIONID, =accid);
|
|
ITF 2: Accession Identifier (=accid);
|
|
BioCISE Model: Unit_ID;
|
|
@
|
|
|
|
|
|
1.2
|
|
log
|
|
@Revision 2
|
|
@
|
|
text
|
|
@d26 3
|
|
a28 1
|
|
A unique identifier for the unit record within the data source. The unit ID should provide the key by which a specimen or specimen component can be identified. Preferrably, the unit ID should be stable in the database, so that it also can be used to find the same record again (e.g. for data exchange purposes). The unit ID constitutes the third part of the record identifier.
|
|
@
|
|
|
|
|
|
1.1
|
|
log
|
|
@Initial revision
|
|
@
|
|
text
|
|
@a0 1
|
|
|
|
d11 1
|
|
d18 1
|
|
d22 1
|
|
d26 11
|
|
d49 1
|
|
a51 2
|
|
|
|
|
|
@
|