<HTML dir=ltr><HEAD><TITLE>RE: [tdwg-guid] First step in implementing LSIDs?[Scanned]</TITLE>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.2900.3059" name=GENERATOR></HEAD>
<BODY>
<DIV id=idOWAReplyText46148 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Yes Rich, our plan is to apply the LSID to the accession 'number' (actually an accession 'code' as we have an historical legacy of suffix 'a', 'b', etc for subdivisions of the original collection which in many cases is a collection of objects rather than one physical object - a bag of leaves for example). And yes, there are some possible problems with errors associated with the metadata but ... in the cotenxt of a DBMS where the accession number is set to unique values only, duplications are in reality impossible, and yes there are far more important challenges to address than this ... ;-)</FONT></DIV>
<DIV dir=ltr><FONT size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>I assume you are correct about the 001100010011001000110011001101000011010100110110 ... I'm a systematist leaning towards nomenclature rather than an IT person.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>I guess the 'change of ownership' comment was directed at the importance of retaining the accession number as this is cited in the literature, and the utility of keeping this as a resolvable LSID.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>A rather complex model is required for 'managing' the objects of a collecting event and what subsequently happens to those objects, which others have more experience of and valid opinions on - I refer, for example, to a pit trap for insects where multiple objects are assigned an initial accession number, the objects are subsequently divided and divided again and again and finally a few may end up on pins as name bearing types.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Cheers,</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Paul</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Richard Pyle [mailto:deepreef@bishopmuseum.org]<BR><B>Sent:</B> Sat 02/06/2007 10:08<BR><B>To:</B> 'Paul Kirk'; 'Jason Best'; tdwg-guid@lists.tdwg.org<BR><B>Subject:</B> RE: [tdwg-guid] First step in implementing LSIDs?[Scanned]<BR></FONT><BR></DIV>
<DIV><BR>
<P><FONT size=2>Paul and List,<BR><BR>First, I should clarify something about my earlier post. I wrote at the<BR>start of Scenario 3:<BR><BR>"3) Issue data-less LSIDs without using the revision ID feature, and track<BR>data change history separately from the LSIDs"<BR><BR>That should have been "...and track *metadata* change history separately<BR>from the LSIDs" (metadata, not data).<BR><BR>> So, without making things too complicated as we 'start to walk'<BR>> in this domain of biodiversity informatics my vote is for a<BR>> variation of scenario 3) from Rich. The reason I vote for this<BR>> is that in the fullness of time, and the 'herb.IMI' database<BR>> has already started this, much of the metadata with be<BR>> LSIDs and it's correctness (i.e. sorting out typos etc) will<BR>> be delegated to the entities who issue those LSIDs. As IPNI<BR>> improves the quality of the metadata associated with the<BR>> LSIDs they issue (and if I understand correctly they do use<BR>> the scenario 3) from Rich) so the quality of the metadata<BR>> associated with a 'herb.IMI' LSID improves. The reason I<BR>> prefer the data + metadate 'model' is that in this instance<BR>> the data is fixed ... who changes collection/accession<BR>> numbers? ... so perfect for this role. Even if a collection<BR>> moves to a new owner the original data need not 'disappear'<BR>> in the same way that DOI's move with the objects as book and<BR>> journal titles change from one publisher to another.<BR><BR>So...if I understand correctly, you differ from my scenario 3 in that you do<BR>generate data-bearing LSIDs for specimens, but the data part is limited to<BR>only the Accession number, not the complete set of data fields associated<BR>with the record -- correct? So, in effect, the object LSID actially applies<BR>to is the binary accession number, not the "concept" of the specimen. I can<BR>imagine in this case that the LSID can be thought of as representing the<BR>"concept of the specimen" because the accession number itself is a surrogate<BR>for the physical specimen. The only thing that concerns me about this<BR>approach is that there is a non-zero incidence of accidental duplicate<BR>catalog numbers within a given collection, and possibly errors in<BR>associating catalog numbers. For example, if the computer database for a<BR>collection had an error created by a technician who, for example, entered<BR>the metadata for accession number IMI1234569 by mistake, when it should have<BR>been IMI1234596 (and vice versa), then branding the accession number as<BR>"data" for the LSID means that the LSID technically *must* stay with the<BR>accession number (not the specimen associated with the metadata for that<BR>LSID), after the error is discovered. Not a huge problem, but could<BR>surprise people who had indexed the LSID before the error was discovered,<BR>who then came back to resolve it again after the error was fixed (i.e., they<BR>would get totally wrong information). Given how rare this problem is likely<BR>to be (against a backdrop of many far more likely problems we will have to<BR>overcome), I don't see this as a strong reason not to proceed with your<BR>plan.<BR><BR>> Final point, the 'data' is the 'herb.IMI' accession number;<BR>> in context this is a GUI because of the existence of Index<BR>> Herbariorum. So, our data will be 123456 not IMI123456<BR>> because ... in the fullness of time we will include an<BR>> Index Herbariorum LSID to 'identify' the 'institutional<BR>> acronym' element of the metadata.<BR><BR>Is the binary data for the accession number in 8-bit, or 16-bit? I'm<BR>assuming 8-bit would be fine, as I suspect all collections would have<BR>accession numbers that can be rendered with 256-character ASCII. Is there<BR>any "wrapper" to the number as binary data, or is it a straight ASCII binary<BR>representation (e.g.: 001100010011001000110011001101000011010100110110 for<BR>"12345")?<BR><BR>I'm not sure I follow the logic of how embedding the accession number as<BR>data for the LSID allows the LSID to move to a new owner. I would think the<BR>opposite. Isn't it likely that the new owner would create their own<BR>accession number for the specimen? In this case, they would be forced to<BR>generate a new LSID if they were following the same practice of encoding the<BR>accession number as "data", rather than metadata.<BR><BR>Also, wouldn't it make more sense to include the acronym (IMI) as part of<BR>the data for the LSID? At least that way the "12345" would have *some*<BR>context.<BR><BR>Finally, this approach would work only for collections where there is a<BR>strict 1:1 correlation between accession numbers and specimen objects for<BR>which an LSID is desired.<BR><BR>Thanks for your comments -- this thread is already forcing me to think about<BR>things in a way I hadn't thought of them before.<BR><BR>Aloha,<BR>Rich<BR><BR>Richard L. Pyle, PhD<BR>Database Coordinator for Natural Sciences<BR> and Associate Zoologist in Ichthyology<BR>Department of Natural Sciences, Bishop Museum<BR>1525 Bernice St., Honolulu, HI 96817<BR>Ph: (808)848-4115, Fax: (808)847-8252<BR>email: deepreef@bishopmuseum.org<BR><A href="http://hbs.bishopmuseum.org/staff/pylerichard.html">http://hbs.bishopmuseum.org/staff/pylerichard.html</A><BR><BR><BR><BR></FONT></P></DIV><p><font face="Arial" size="1">************************************************************************<br>
The information contained in this e-mail and any files transmitted with it is confidential and is for the exclusive use of the intended recipient. If you are not the intended recipient please note that any distribution, copying or use of this communication or the information in it is prohibited. <br>
<br>
Whilst CAB International trading as CABI takes steps to prevent the transmission of viruses via e-mail, we cannot guarantee that any e-mail or attachment is free from computer viruses and you are strongly advised to undertake your own anti-virus precautions.<br>
<br>
If you have received this communication in error, please notify us by e-mail at cabi@cabi.org or by telephone on +44 (0)1491 829199 and then delete the e-mail and any copies of it.<br>
<br>
CABI is an International Organization recognised by the UK Government under Statutory Instrument 1982 No. 1071.<br>
<br>
**************************************************************************</font><br>
</p>
</BODY></HTML>