Topic 2: GUIDs for Collections and Specimens

Donald Hobern dhobern at GBIF.ORG
Thu Oct 20 08:37:58 CEST 2005


 [ Another topic for comments.  Please keep the Topic number in responses ]



Topic 2: GUIDs for Collections and Specimens



Identifiers to assist with management of collection data have been at the
centre of TDWG's GUID investigation from the beginning.  A primary
motivation for this work has been the need to recognise where two data
providers are offering access to information on the same specimen.  Two very
basic scenarios for specimen identifiers are described on the wiki at
http://wiki.gbif.org/guidwiki/wikka.php?wakka=GUIDUseCases. However we do
need to make sure we understand the actual scenarios requiring such
identifiers across the range of biological collections.  I am therefore
looking for descriptions of the situations in which your current processes,
systems and applications already use identifiers for specimens (and where
perhaps genuinely globally unique identifiers may help), and of any policies
and processes around collection management which might affect how we are
able to assign, manage or resolve identifiers.



When I speak of 'specimens' I am primarily thinking of organisms (living or
dead, including subsamples) held in collections (including zoos, aquaria,
culture collections and seed banks), but I am also very interested in
parallel situations involving the assignment of identifiers to observation
events in the field.



Some more specific questions to try to shape discussion:



1.      What identifiers (how many per specimen) get assigned to specimens
in your organisation or domain (field numbers, catalogue numbers, etc.)?
2.      What is the scope of uniqueness for each of these identifiers
(notebook page, collector, database, institution, global, etc.)?
3.      Can you explain the life cycle of each of these identifiers (who
assigns them, how they are subsequently tracked)?
4.      Can you give examples of how these identifiers are used to retrieve
the specimen and/or information on the specimen?
5.      Would there be any social or technical roadblocks to replacing these
identifiers with a single identifier that was guaranteed to be unique?
6.      In the case of subsamples from a specimen, can you identify issues
around associating the sample and associated information with the source
specimen and associated information?



The subject of specimen identifiers is somewhat linked to that of collection
identifiers, since Darwin Core and the ABCD Schema have used institution and
collection codes together with catalogue numbers to identify specimens in
the absence of GUIDs.  It would also be useful here to collect information
on the following:



7.      How are your specimens organised into larger identifiable sets
(collections, named collections, databases, institutions, etc.)?
8.      What identifiers get assigned to each of these sets in your
organization or domain (institution codes, collection codes, Index Herbarium
acronyms, etc.)?
9.      Can you explain the life cycle of each of these identifiers (who
assigns them, how they are subsequently tracked)?
10.     Can you give examples of how these identifiers are used to locate
the set and/or information on the set?
11.     Would there be any social or technical roadblocks to replacing these
identifiers with a single identifier that was guaranteed to be unique?



To help you a little, my aim is to use this information to develop
additional scenarios as use cases which will complement those already on the
wiki (and yes, I do realise that the existing "use case" pages are not
formal use cases!).  If you feel able simply to add pages to the wiki which
describe scenarios for using identifiers to manage specimen and collection
data, please go ahead (and include links to your new scenarios from the
GUIDUseCases page).



Thanks,



Donald

---------------------------------------------------------------
Donald Hobern (dhobern at gbif.org)
Programme Officer for Data Access and Database Interoperability
Global Biodiversity Information Facility Secretariat
Universitetsparken 15, DK-2100 Copenhagen, Denmark
Tel: +45-35321483   Mobile: +45-28751483   Fax: +45-35321480
---------------------------------------------------------------




------=_NextPart_000_0003_01C5D551.92C294A0
Content-Type: text/html;
        charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place" downloadurl=3D"http://www.5iantlavalamp.com/"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City" =
downloadurl=3D"http://www.5iamas-microsoft-com:office:smarttags"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"country-region" downloadurl=3D"http://www.5iantlavalamp.com/"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman";}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:purple;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal;
        font-family:Arial;
        color:windowtext;}
span.EmailStyle18
        {mso-style-type:personal-reply;
        font-family:Arial;
        color:navy;}
@page Section1
        {size:612.0pt 792.0pt;
        margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
        {page:Section1;}
 /* List Definitions */
 @list l0
        {mso-list-id:256908390;
        mso-list-type:hybrid;
        mso-list-template-ids:1073485238 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
        {mso-level-tab-stop:36.0pt;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level2
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:72.0pt;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level3
        {mso-level-tab-stop:108.0pt;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level4
        {mso-level-tab-stop:144.0pt;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level5
        {mso-level-tab-stop:180.0pt;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level6
        {mso-level-tab-stop:216.0pt;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level7
        {mso-level-tab-stop:252.0pt;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level8
        {mso-level-tab-stop:288.0pt;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level9
        {mso-level-tab-stop:324.0pt;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l1
        {mso-list-id:1008168421;
        mso-list-template-ids:-2037632138;}
@list l1:level2
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:72.0pt;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l2
        {mso-list-id:1072695626;
        mso-list-type:hybrid;
        mso-list-template-ids:251168318 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l2:level1
        {mso-level-tab-stop:36.0pt;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l3
        {mso-list-id:2108186681;
        mso-list-type:hybrid;
        mso-list-template-ids:-1955844692 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l3:level1
        {mso-level-tab-stop:36.0pt;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
ol
        {margin-bottom:0cm;}
ul
        {margin-bottom:0cm;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>&nbsp;<span lang=3DEN-GB>[ <font color=3Dnavy><span
style=3D'color:navy'>Another </span></font>topic<font color=3Dnavy><span
style=3D'color:navy'> </span></font>for comments. &nbsp;Please keep the =
Topic
number in responses ]<o:p></o:p></span></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'>Topic <font color=3Dnavy><span =
style=3D'color:navy'>2</span></font>:
<font color=3Dnavy><span style=3D'color:navy'>GUIDs for Collections and =
Specimens</span></font><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Identifiers to assist with =
management of
collection data have been at the centre of TDWG&#8217;s GUID =
investigation from
the beginning. &nbsp;A primary motivation for this work has been the =
need to
recognise where two data providers are offering access to information on =
the
same specimen. &nbsp;Two very basic scenarios for specimen identifiers =
are
described on the wiki at <a
href=3D"http://wiki.gbif.org/guidwiki/wikka.php?wakka=3DGUIDUseCases">htt=
p://wiki.gbif.org/guidwiki/wikka.php?wakka=3DGUIDUseCases</a>.
However we do need to make sure we understand the actual scenarios =
requiring
such identifiers across the range of biological collections.&nbsp; I am
therefore looking for descriptions of the situations in which your =
current processes,
systems and applications already use identifiers for specimens (and =
where
perhaps genuinely globally unique identifiers may help), and of any =
policies
and processes around collection management which might affect how we are =
able
to assign, manage or resolve identifiers. <o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>When I speak of =
&#8216;specimens&#8217; I
am primarily thinking of organisms (living or dead, including =
subsamples) held
in collections (including zoos, aquaria, culture collections and seed =
banks), but
I am also very interested in parallel situations involving the =
assignment of identifiers
to observation events in the field.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Some more specific questions to try =
to
shape discussion:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<ol style=3D'margin-top:0cm' start=3D1 type=3D1>
 <li class=3DMsoNormal style=3D'color:navy;mso-list:l3 level1 =
lfo4'><font size=3D2
     color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>What
     identifiers (how many per specimen) get assigned to specimens in =
your organisation
     or domain (field numbers, catalogue numbers, =
etc.)?<o:p></o:p></span></font></li>
 <li class=3DMsoNormal style=3D'color:navy;mso-list:l3 level1 =
lfo4'><font size=3D2
     color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>What
     is the scope of uniqueness for each of these identifiers (notebook =
page, collector,
     database, institution, global, etc.)?<o:p></o:p></span></font></li>
 <li class=3DMsoNormal style=3D'color:navy;mso-list:l3 level1 =
lfo4'><font size=3D2
     color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Can
     you explain the life cycle of each of these identifiers (who =
assigns them,
     how they are subsequently tracked)?<o:p></o:p></span></font></li>
 <li class=3DMsoNormal style=3D'color:navy;mso-list:l3 level1 =
lfo4'><font size=3D2
     color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Can
     you give examples of how these identifiers are used to retrieve the
     specimen and/or information on the =
specimen?<o:p></o:p></span></font></li>
 <li class=3DMsoNormal style=3D'color:navy;mso-list:l3 level1 =
lfo4'><font size=3D2
     color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Would
     there be any social or technical roadblocks to replacing these =
identifiers
     with a single identifier that was guaranteed to be =
unique?<o:p></o:p></span></font></li>
 <li class=3DMsoNormal style=3D'color:navy;mso-list:l3 level1 =
lfo4'><font size=3D2
     color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>In
     the case of subsamples from a specimen, can you identify issues =
around associating
     the sample and associated information with the source specimen and
     associated information?<o:p></o:p></span></font></li>
</ol>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>The subject of specimen identifiers =
is
somewhat linked to that of collection identifiers, since Darwin Core and =
the
ABCD Schema have used institution and collection codes together with =
catalogue
numbers to identify specimens in the absence of GUIDs. &nbsp;It would =
also be
useful here to collect information on the =
following:<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<ol style=3D'margin-top:0cm' start=3D7 type=3D1>
 <li class=3DMsoNormal style=3D'color:navy;mso-list:l3 level1 =
lfo4'><font size=3D2
     color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>How
     are your specimens organised into larger identifiable sets =
(collections, named
     collections, databases, institutions, =
etc.)?<o:p></o:p></span></font></li>
 <li class=3DMsoNormal style=3D'color:navy;mso-list:l3 level1 =
lfo4'><font size=3D2
     color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>What
     identifiers get assigned to each of these sets in your organization =
or
     domain (institution codes, collection codes, Index Herbarium =
acronyms,
     etc.)?<o:p></o:p></span></font></li>
 <li class=3DMsoNormal style=3D'color:navy;mso-list:l3 level1 =
lfo4'><font size=3D2
     color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Can
     you explain the life cycle of each of these identifiers (who =
assigns them,
     how they are subsequently tracked)?<o:p></o:p></span></font></li>
 <li class=3DMsoNormal style=3D'color:navy;mso-list:l3 level1 =
lfo4'><font size=3D2
     color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Can
     you give examples of how these identifiers are used to locate the =
set
     and/or information on the set?<o:p></o:p></span></font></li>
 <li class=3DMsoNormal style=3D'color:navy;mso-list:l3 level1 =
lfo4'><font size=3D2
     color=3Dnavy face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'>Would
     there be any social or technical roadblocks to replacing these =
identifiers
     with a single identifier that was guaranteed to be =
unique?<o:p></o:p></span></font></li>
</ol>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>To help you a little, my aim is to =
use
this information to develop additional scenarios as use cases which will
complement those already on the wiki (and yes, I do realise that the =
existing &#8220;use
case&#8221; pages are not formal use cases!). &nbsp;If you feel able =
simply to
add pages to the wiki which describe scenarios for using identifiers to =
manage
specimen and collection data, please go ahead (and include links to your =
new
scenarios from the GUIDUseCases page).<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Thanks,</span></font><font size=3D2
face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></p=
>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial'>Donald<br>
&nbsp;<br>
---------------------------------------------------------------<br>
Donald Hobern (<a =
href=3D"mailto:dhobern at gbif.org">dhobern at gbif.org</a>)<br>
Programme Officer for Data Access and Database Interoperability <br>
Global Biodiversity Information Facility Secretariat <br>
Universitetsparken 15, DK-2100 <st1:place w:st=3D"on"><st1:City =
w:st=3D"on">Copenhagen</st1:City>,
 <st1:country-region =
w:st=3D"on">Denmark</st1:country-region></st1:place><br>
Tel: +45-35321483&nbsp;&nbsp; <st1:place w:st=3D"on"><st1:City =
w:st=3D"on">Mobile</st1:City></st1:place>:
+45-28751483&nbsp;&nbsp; Fax: +45-35321480<br>
---------------------------------------------------------------<o:p></o:p=
></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
lang=3DEN-GB
style=3D'font-size:12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>


More information about the tdwg-tag mailing list