<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:"MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@MS Mincho";
panose-1:2 2 6 9 4 2 5 8 3 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.hoenzb
{mso-style-name:hoenzb;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">One problem with such “cascading” numbers is the high likelihood of errors in earlier, non-digital work. We have about 460,000 catalog numbers in our mollusk
collection, so none is larger than six digits. Over two thirds were generated before computers came into use, and over the years thousands of duplicate numbers (different records with the same number) have been created. Nowadays we are working out of a single
database, so there are safeguards against this kind of error, but finding and fixing the existing duplicates will take years.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="background:white"><b><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black">Paul Callomon</span></b><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black"><br>
<i>Collection Manager, Malacology, Invertebrate Paleontology and General Invertebrates</i></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center;background:white">
<span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal" style="background:white"><b><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black">Academy of Natural Sciences of Drexel University, Philadelphia</span></b><b><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black"><o:p></o:p></span></b></p>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black">1900 Benjamin Franklin Parkway, Philadelphia PA 19103-1195, USA</span><span style="font-size:10.0pt;font-family:"Calibri","sans-serif";color:black"><br>
<i><a href="mailto:callomon@ansp.org" target="_blank">callomon@ansp.org</a> Tel 215-405-5096 - Fax 215-299-1170</i></span><span style="font-family:"Calibri","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> nhcoll-l-bounces@mailman.yale.edu [mailto:nhcoll-l-bounces@mailman.yale.edu]
<b>On Behalf Of </b>Lena Hernandez<br>
<b>Sent:</b> Thursday, August 14, 2014 9:05 AM<br>
<b>To:</b> nhcoll-l@mailman.yale.edu<br>
<b>Subject:</b> Re: [Nhcoll-l] Unique IDs for museum objects versus specimens<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">My Natural Science Collection is relatively small, so I haven’t run into this problem there, but in our History Collection we have a similar issue with portfolios
and the like. The way it is dealt with there is the set as a whole gets a number say 2014.13 (transaction number, 13th transaction of 2014)then an object number 2014.13.1 (first object of transaction 2014.13) and then if it is something like a portfolio is
can be broken down further 2014.13.1.3 (third photo of portfolio 2014.13.1) or alternatively 2014.13.1A-C (first object of 2014.13, three parts). Perhaps you can use something similar, the parent number is always there and you can see how far down the line
this object came out as well as what it came from more recently. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">To use Dean’s example.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">2014.13- Dredge Material<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">2014.13.1-jar o’ crustacea<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">2014.13.1.1-single crustacean from the jar o’ crustacean<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">2014.13.1.1A-D- four parasitic crustacea from your single crustacean<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Or alternatively (Just make sure you are consistent in which way you parse it out)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">2014.13.1.1.1- first parasitic crustacea from your single crustacean<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I hope that make sense, I‘m a bit tired this morning and my brain is not yet up to full speed.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Lena<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Lena Hernandez<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Collections Manager/Registrar<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Museum of Science & History<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">1025 Museum Circle<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Jacksonville, FL 32207<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">(904)396-6674 x212<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><a href="mailto:lhernandez@themosh.org">lhernandez@themosh.org</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
<a href="mailto:nhcoll-l-bounces@mailman.yale.edu">nhcoll-l-bounces@mailman.yale.edu</a> [<a href="mailto:nhcoll-l-bounces@mailman.yale.edu">mailto:nhcoll-l-bounces@mailman.yale.edu</a>]
<b>On Behalf Of </b>Dean Pentcheff<br>
<b>Sent:</b> Wednesday, August 13, 2014 9:12 PM<br>
<b>To:</b> Colin Favret<br>
<b>Cc:</b> <a href="mailto:nhcoll-l@mailman.yale.edu">nhcoll-l@mailman.yale.edu</a><br>
<b>Subject:</b> Re: [Nhcoll-l] Unique IDs for museum objects versus specimens<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">This is an issue that I've raised in the past with the Specify team (and plan to raise again in the near future — fair warning, guys :)<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The precipitating example for us comes from marine specimens. Often an unsorted jar of material will arrive (e.g. from a dredge sample) to be cataloged in the collection — this unsorted lot should get a unique ID — it may be around for
years before it's touched. Then we may pull out (for example) all the crustacea into another jar. This partly-sorted lot also needs a unique ID (it may go to a different room under different staff, so just keeping it with the original jar is not an option).
Then we may pull out a single individual, identify it, and use that in a publication, so that, too, needs an ID. A visiting researcher then examines that individual and pulls off parasitic crustacea, identifying each and putting them into individual vials,
each of which needs an ID. Etc.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">What we have is a clear hierarchical branching parent-child relationship from the initial unsorted lot down to the individual parasites (and their parasites, and their molecular derivatives, etc.). Logically, the way to accommodate this
is to have any "thing" in the collection identified with a unique ID. Any derived or subsorted "thing" gets another unique ID and (and this is critical) is linked to its parent so that all the information from the parent (and on up the chain to the top) is
immediately available via any "child" ID. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Every "thing" gets a first-class ID (no sub-IDs or a limited list of "preps" from an initial object). Key to the concept is retaining the parent-child-grandchild-... chain. At any moment, one should be able to retrieve any ID's entire chain
of parents (and their associated data), or any ID's entire chain of derived children (and their associated data). <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">It is a mystery to me why this scheme is not the standard model for specimen databases where there is a habit of creating chains of derivatives over time. There certainly are implementation details that need careful consideration (for
example with propagation of data down the chain, how "locked" that propagation is, and how to handle things that get completely subdivided so they no longer exist as such, but whose data must persist), but it seems like a very clean, very flexible base model.<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal">-Dean<br>
-- <br>
Dean Pentcheff<br>
<a href="mailto:pentcheff@gmail.com">pentcheff@gmail.com</a><br>
<a href="mailto:dpentche@nhm.org">dpentche@nhm.org</a><o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Wed, Aug 13, 2014 at 4:01 PM, Colin Favret <<a href="mailto:ColinFavret@aphidnet.org" target="_blank">ColinFavret@aphidnet.org</a>> wrote:<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">Has anyone dealt with the distinction between issuing unique IDs (for labels and database records) for museum objects versus specimens? A case in point might be a microscope slide with 100
specimens on it (or a jar, envelope, etc.). These specimens can be of multiple taxa, different sexes, life stages, etc. I believe most collections label the museum object (slide, jar, envelope, etc.) with a unique identifier and then treat the specimens as
a lot, but this doesn't fully parse out the data associated with the various specimens in a specimen database.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">I've developed my own solution (unique ID label for the object, decimal numbers but no label for the individual specimens or specimen lots - e.g. INST123456 for the slide, INST123456.001
for the first specimen lot, INST123456.002 for the second, etc.).<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">But I'm wondering what others have done or if there is anything out there approaching an industry standard.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">Thanks for your input!<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif""><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif"">Colin<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Verdana","sans-serif";color:#888888"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana","sans-serif";color:#888888">Colin Favret</span><span style="font-family:"Verdana","sans-serif";color:#888888"><o:p></o:p></span></p>
</div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Verdana","sans-serif";color:#888888">Université de Montréal</span><span style="font-family:"Arial","sans-serif";color:#888888"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:7.5pt;font-family:"Verdana","sans-serif";color:#888888"><a href="http://favret.aphidnet.org/" target="_blank">Favret.AphidNet.org</a></span><span style="font-family:"Arial","sans-serif";color:#888888"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
Nhcoll-l mailing list<br>
<a href="mailto:Nhcoll-l@mailman.yale.edu">Nhcoll-l@mailman.yale.edu</a><br>
<a href="http://mailman.yale.edu/mailman/listinfo/nhcoll-l" target="_blank">http://mailman.yale.edu/mailman/listinfo/nhcoll-l</a><br>
<br>
_______________________________________________<br>
NHCOLL-L is brought to you by the Society for the Preservation of<br>
Natural History Collections (SPNHC), an international society whose<br>
mission is to improve the preservation, conservation and management of<br>
natural history collections to ensure their continuing value to<br>
society. See <a href="http://www.spnhc.org" target="_blank">http://www.spnhc.org</a> for membership information.<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>