<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=iso-8859-1">
<meta name="Generator" content="Microsoft Word 15 (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:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
p.xmsonormal, li.xmsonormal, div.xmsonormal
{mso-style-name:x_msonormal;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle24
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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>
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Hi Andy,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">This is a great topic. We produce a large amount of 2D images (live and preserved) and CT data for our fish collection here at UF. We treat these data as prep types for a collection object. A major reason for this approach and not separating
lots is to conserve collection space. Given the rate that we are imaging our specimens, we wouldn’t be able to also support our future growth of newly acquired collections. Additionally, we see the value of having image data as prep types so that the collection
object can be the one stop for all “metadata” including from other individuals from the same lot. For example, although we try to CT scan individuals from tissued lots to increase data value, we usually don’t scan the individuals that were tissued because
it would be a loss in morphological data captured (e.g. missing fins, epaxial tissue, etc.). One catalog number to rule them all. Guess we’re a bunch of lumpers at heart.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Our system for tracking down the imaged individual in a lot is still being improved (luckily we rarely get those types of requests). When possible, we image lots with only one individual. If we image lots with several individuals, then
we wrap that individual with cheese cloth and/or include tag(s). <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Adding these media as prep types in Specify allows us to query the number of multimedia that we have, similarly to tissues. This number only include files existing in Specify, since derivatives and raw data are a whole other can of worms.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best,<o:p></o:p></p>
<p class="MsoNormal">Zach<o:p></o:p></p>
<p class="MsoNormal">--<o:p></o:p></p>
<p class="MsoNormal">Zachary S. Randall<o:p></o:p></p>
<p class="MsoNormal">Biological Scientist & Imaging Lab Manager <o:p></o:p></p>
<p class="MsoNormal">Florida Museum of Natural History <o:p></o:p></p>
<p class="MsoNormal">1659 Museum Road<o:p></o:p></p>
<p class="MsoNormal">Gainesville, FL 32611-7800<o:p></o:p></p>
<p class="MsoNormal">352-273-1958|Rm. 277 <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">www.zacharyrandall.org<o:p></o:p></p>
<p class="MsoNormal">Twitter: @Zach__Randall<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Nhcoll-l <nhcoll-l-bounces@mailman.yale.edu> <b>
On Behalf Of </b>Schindel, David<br>
<b>Sent:</b> Tuesday, August 25, 2020 11:09 AM<br>
<b>To:</b> Bentley, Andrew Charles <abentley@ku.edu>; nhcoll-l@mailman.yale.edu<br>
<b>Subject:</b> Re: [Nhcoll-l] Digital objects vs. physical objects in collection management databases and how to manage them<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" align="left" width="100%" style="width:100.0%">
<tbody>
<tr>
<td style="padding:0in 0in 0in 0in">
<div>
<p class="MsoNormal" style="mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly">
<b><span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#FA4616">[External Email]</span></b>
<o:p></o:p></p>
</div>
</td>
</tr>
</tbody>
</table>
<div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">Hi, Andy,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">We've had discussions about this in the Interagency Working Group on Scientific Collections (IWGSC; see usfsc.nal.usda.gov). If the digital representations of an object are not published, they
would be archival material directly related to the specimen, and therefore part of the collection. They would be equivalent to field notes, locality maps, audio and video recordings, etc. lf they are submitted to a public database or other open access data
repository (GenBank, CTBase, etc.) then these are publication events that can (and in a perfect world, would be) linked to the specimen record along with scholarly publications in which the specimen is cited. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">In both cases, a comprehensively curated system of specimen digitization would allow users to discover and navigate to all these assets.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">Best regards and stay well -<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">David<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<div id="Signature">
<div id="divtagdefaultwrapper">
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">David E. Schindel, Research Associate<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">Office of the Provost<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">Smithsonian Institution<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">Email: <a href="mailto:schindeld@si.edu">
schindeld@si.edu</a> <o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
</div>
</div>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="98%" align="center">
</div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span style="color:black">From:</span></b><span style="color:black"> Nhcoll-l <<a href="mailto:nhcoll-l-bounces@mailman.yale.edu">nhcoll-l-bounces@mailman.yale.edu</a>> on behalf of Bentley, Andrew Charles <<a href="mailto:abentley@ku.edu">abentley@ku.edu</a>><br>
<b>Sent:</b> Monday, August 24, 2020 4:16 PM<br>
<b>To:</b> <a href="mailto:nhcoll-l@mailman.yale.edu">nhcoll-l@mailman.yale.edu</a> <<a href="mailto:nhcoll-l@mailman.yale.edu">nhcoll-l@mailman.yale.edu</a>><br>
<b>Subject:</b> [Nhcoll-l] Digital objects vs. physical objects in collection management databases and how to manage them</span>
<o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<p class="xmsonormal" style="line-height:12.0pt;background:#FFEB9C"><b><span style="font-size:9.0pt;color:#9C6500">External Email - Exercise Caution</span></b><o:p></o:p></p>
<div>
<div>
<p class="xmsonormal"><a name="x__GoBack"></a><span style="font-size:11.0pt">Hi all</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">I am trying to resolve a philosophical conundrum brought on by the ever-increasing mountain of digital data being produces from and associated with natural history collections. My question is whether digital
representations of an object (images, CT scans, etc.) should be treated as preparations of an object in a collections database similar to other physical preparations or treated differently? For instance, in a fish collection like mine, you have a lot that
has a certain number of specimens. Some of those may be subsequently cleared and stained or have skeletons prepared. These are traditionally handled as preparations of the original lot with the same catalog number (although in some collections they are treated
as separate catalog numbers). Now, however, you have digital representations of those physical objects such as images, CT scans, etc. Should these also be treated as preparations or be treated differently - as digital products or linked as attachments to
the physical objects? To me, they are not physical objects but digital representations of the original object. As such, they are somewhat different to a preparation. This has implications when totaling traditional counts of objects in a collection as well
as when publishing data from a collection to the aggregator community. In some instances, this may be governed by the data model and business rules of the CMS you are using or by your personal preference.</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">I would be interested in hearing your views on this and how you handle this in your collection as I am not sure there is any community consensus as to which way to handle these. I have heard of both methods
being used in various collections.</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">Thanks in advance</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt">Andy</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt"> </span><o:p></o:p></p>
<div>
<p class="xmsonormal"><span style="font-size:11.0pt;color:black"> A : A : A :</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt;color:black"> }<(((_°>.,.,.,.}<(((_°>.,.,.,.}<)))_°></span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt;color:black"> V V V</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt;color:black">Andy Bentley</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt;color:black">Ichthyology Collection Manager</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt;color:black">University of Kansas</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt;color:black">Biodiversity Institute</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt;color:black">Dyche Hall</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt;color:black">1345 Jayhawk Boulevard</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt;color:black">Lawrence, KS, 66045-7561</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt;color:black">USA</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt;color:black"> </span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt;color:black">Tel: (785) 864-3863</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt;color:black">Fax: (785) 864-5335 </span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt;color:black">Email: <a href="mailto:abentley@ku.edu">abentley@ku.edu</a> </span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt;color:black"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__nam02.safelinks.protection.outlook.com_-3Furl-3Dhttp-253A-252F-252Fichthyology.biodiversity.ku.edu-252F-26data-3D02-257C01-257Cschindeld-2540si.edu-257C05bb69872c7b4aa324d208d8486a936a-257C989b5e2a14e44efe93b78cdd5fc5d11c-257C0-257C0-257C637338969870562799-26sdata-3D05wkr90YzamCsPVnBhhcDKJXZOvQO4CCkun82aj8z3s-253D-26reserved-3D0&d=DwMFAw&c=sJ6xIWYx-zLMB3EPkvcnVg&r=BsjUEaAzErVnOJA4kXSO_g&m=djrI-zIT93wiMGeria7qiHeg1OnPwpMDkL1fmqCoeBk&s=z6APnia86i0F27gg3vvbRfIh_HCwEBpFrZWKVObYaYU&e=">http://ichthyology.biodiversity.ku.edu</a></span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt;color:black"> </span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt;color:black"> A : A : A :</span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt;color:black"> }<(((_°>.,.,.,.}<(((_°>.,.,.,.}<)))_°></span><o:p></o:p></p>
<p class="xmsonormal"><span style="font-size:11.0pt;color:black"> V V V</span><o:p></o:p></p>
</div>
<p class="xmsonormal"> <o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>