<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 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:0cm;
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.gmail-m7966388451846362072msolistparagraph, li.gmail-m7966388451846362072msolistparagraph, div.gmail-m7966388451846362072msolistparagraph
{mso-style-name:gmail-m_7966388451846362072msolistparagraph;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.gmail-m7966388451846362072xmsonormal, li.gmail-m7966388451846362072xmsonormal, div.gmail-m7966388451846362072xmsonormal
{mso-style-name:gmail-m_7966388451846362072xmsonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1809207071;
mso-list-template-ids:1597771446;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></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-NZ" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Here at the NIWA Invertebrate Collection in our Specify database we have the specimen images as attributes of our collection object. We store the image files in our NIWA-wide image management database
(An Atlas database), which creates a unique asset ID for the image that can be shared via a public link. We copy these Atlas asset IDs for each associated image into individual “specimen image” fields in the “Collection Object Attribute” table. These fields
are link fields that are programmed to go to our Atlas image database public link. So we can have multiple asset IDs per collection object.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">We also have a yes/no tickbox labelled as “Photo” on the “preparation” table so that we can use that to flag if we have a photo of that particular preparation. Usually we would register a separate
lot as the photo voucher, but we don’t always do this if the individual is pretty distinct looking in the group of multiple specimens.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Cheers,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US">Sadie<o:p></o:p></span></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Nhcoll-l <nhcoll-l-bounces@mailman.yale.edu>
<b>On Behalf Of </b>Dean Pentcheff<br>
<b>Sent:</b> Wednesday, 26 August 2020 11:03 AM<br>
<b>To:</b> 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></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Speaking from a perspective coming from managing diverse marine invertebrates: we would consider any digital products as being derivatives (and hence "filed with" or linked to) the original specimen. Linking an image or a CT scan back to
a specimen (to be precise: to a specimen record distinguished by a unique specimenID) would be treated just like linking a molecular sequencing extract back to a specimen record.
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The workflow that often goes with marine invertebrates has led us away from the "prep" concept (which seems to come naturally for vertebrate collections where there are a roughly fixed number of kinds of preps for specimens) to a parent/child
concept. A "specimen" can be an unsorted lot (multi-phyletic), or a jar of individuals assumed to be the same species, or one critter in a jar. The moment an individual (or sub-lot) is removed or distinguished in some way, it gets a new specimenID that is
linked as a "child" of the "parent" specimen record. That process can continue (all the worms from an unsorted lot could be given their own specimenID as a lot, and then individuals pulled from the worm jar could each get their own specimenID when they're
isolated for sequencing). The idea is that anything you will want to refer to individually later (in a publication, etc.) should get its own specimenID.
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Now, having said that, and thinking about images, CT scans, and molecular extracts, I hypothesize that I think about those in a way very similar to the way vertebrate people think about "preps". An image never gets its own specimenID, but
always points to a specimenID (yes, there's an imageID for the image record, but that's just the identifier for the image record and does not pretend to be anything else). The same is true for molecular extracts, and would be for CT scans if we had any. Each
of those derived products (images, extracts, CT scans) would probably get its own table in a database, since there are properties unique to it that are irrelevant to the others. But they exist as derivatives of the specimen identified by its specimenID (and
use that specimenID to maintain the linkage). It seems to me that this is analogous to the "prep" idea, which has a defined set of physical derivatives that can come from a specimen, each one of which may have its own properties. Some of these derivatives
(images, CT scans) are electronic-only, and some are physical (molecular extract), but they're treated similarly as defined derivatives of specimens.
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">A field we maintain in the specimen table is "specimen exists (yes/no)". We have situations where there are derivative products but no physical specimen remains in the collection: when the specimen was consumed for molecular analysis, for
example. But that same system would accommodate a situation where there never was a physical specimen, but there only ever was an image, for example. We're mostly specimen-based (not so much observation-based), so in practice almost all the situations like
that existing in our case are situations where we started with a physical specimen.
<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">-Dean<br>
-- <br>
Dean Pentcheff<br>
<a href="mailto:pentcheff@gmail.com" target="_blank">pentcheff@gmail.com</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><a href="mailto:dpentche@nhm.org" target="_blank">pentcheff@nhm.org</a><br>
<a href="https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fresearch.nhm.org%2Fdisco&data=02%7C01%7Csadie.mills%40niwa.co.nz%7C86ec6c523f324a04b20b08d8494b1a4f%7C41caed736a0c468aba499ff6aafd1c77%7C0%7C0%7C637339934272691270&sdata=G19bm6J%2FZUNDbaPEdxlB7REnwdU6W7Ebzr4wCsfWvVc%3D&reserved=0" target="_blank">https://research.nhm.org/disco</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><img border="0" id="_x0000_i1025" src="http://research.nhm.org/images/DISCO_lockup_4color-300.png"><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Tue, Aug 25, 2020 at 2:30 PM Bentley, Andrew Charles <<a href="mailto:abentley@ku.edu">abentley@ku.edu</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><a name="m_7966388451846362072__GoBack"></a><span lang="EN-US">Zach<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Thanks for this articulation of your process. With regard to the issues you raise (which are similar to issues raised in other replies I have received):<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<ol start="1" type="1">
<li class="gmail-m7966388451846362072msolistparagraph" style="mso-list:l0 level1 lfo1">
<span lang="EN-US">Space – not sure this is a valid reason for using preps given that there are other mechanisms of tagging individuals in a lot rather than separating them out as you indicate – wrapping in cheesecloth or tagging. Also, imaged individuals
can usually be discerned simply by visual inspection of distinguishing characteristics – fin damage, body shape, size, etc.<o:p></o:p></span></li><li class="gmail-m7966388451846362072msolistparagraph" style="mso-list:l0 level1 lfo1">
<span lang="EN-US">Searching - not sure this is a valid reason either given that it is just as easy to search a database for those records that have attachments as searching for preps. You could add metadata about the attachment that could facilitate searching
for various kinds of attachments in the same manner.<o:p></o:p></span></li><li class="gmail-m7966388451846362072msolistparagraph" style="mso-list:l0 level1 lfo1">
<span lang="EN-US">Data integration – These attachments are still published to the aggregators as associated with the occurrence record through extensions or otherwise, even though they are not preps. See this example from my collection where Genbank sequences,
images and citations are all published as part of the record of this tissue - <a href="https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.gbif.org%2Foccurrence%2F656980275&data=02%7C01%7Csadie.mills%40niwa.co.nz%7C86ec6c523f324a04b20b08d8494b1a4f%7C41caed736a0c468aba499ff6aafd1c77%7C0%7C0%7C637339934272691270&sdata=WR%2B8x%2FU5%2BbX3BsHOBw93dIcOWP9DpKlKDPLYACXpc%2Fk%3D&reserved=0" target="_blank">
https://www.gbif.org/occurrence/656980275</a>. CT scans would similarly be included as linkages to Morphosource.<o:p></o:p></span></li></ol>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">I am still stuck thinking that an image or a CT scan is simply a digital representation of a specimen and not a prep in the traditional sense but maybe I am thinking
too narrowly. I have yet to see a compelling argument for preps. For instance, if you were to scan a publication or field notebook, would this represent a separate “prep” of the publication or field note page or is it simply a digital representation of the
same thing? Is the distinction that more information can be gleaned from a CT scan than can be gleaned from the specimen itself without dissection? Is that true of an image? What more information is available besides coloration from an image taken while
alive or shortly after euthanizing? I am still worried by the possible confusion with collection stats and digital representations being counted as specimens. I am also worried about the process of publishing data to aggregators where currently digital media
are published as part of an Audubon core extension and not as occurrences (which they would be as preps).<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Still mulling this over in my brain but it would be great if we had some community consensus as to how to treat these things – which there currently is not given
the replies I have been receiving. I will admit that some of my thinking is driven by the Specify data model that we use for our collections. I would be interested in hearing how other CMS’s deal with these or is it similarly all over the map.<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Andy<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="color:black"> A : A : A :</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="color:black"> }<(((_°>.,.,.,.}<(((_°>.,.,.,.}<)))_°></span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="color:black"> V V V</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="color:black">Andy Bentley</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="color:black">Ichthyology Collection Manager</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="color:black">University of Kansas</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="color:black">Biodiversity Institute</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="color:black">Dyche Hall</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="color:black">1345 Jayhawk Boulevard</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="color:black">Lawrence, KS, 66045-7561</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="color:black">USA</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="color:black"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="color:black">Tel: (785) 864-3863</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="color:black">Fax: (785) 864-5335 </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="color:black">Email: <a href="mailto:abentley@ku.edu" target="_blank">abentley@ku.edu</a> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="color:black"><a href="https://aus01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fichthyology.biodiversity.ku.edu%2F&data=02%7C01%7Csadie.mills%40niwa.co.nz%7C86ec6c523f324a04b20b08d8494b1a4f%7C41caed736a0c468aba499ff6aafd1c77%7C0%7C0%7C637339934272701263&sdata=86Tbu44VoiQc2dQj%2BKILyE2GpZLyc3Gdsp919rsH2%2BY%3D&reserved=0" target="_blank">http://ichthyology.biodiversity.ku.edu</a></span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="color:black"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="color:black"> A : A : A :</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="color:black"> }<(((_°>.,.,.,.}<(((_°>.,.,.,.}<)))_°></span><span lang="EN-US"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="color:black"> V V V</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<div style="border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0cm 0cm 0cm;border-color:currentcolor currentcolor">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span lang="EN-US" style="font-size:12.0pt;color:black">From:
</span></b><span lang="EN-US" style="font-size:12.0pt;color:black">"<a href="mailto:zrandall@flmnh.ufl.edu" target="_blank">zrandall@flmnh.ufl.edu</a>" <<a href="mailto:zrandall@flmnh.ufl.edu" target="_blank">zrandall@flmnh.ufl.edu</a>><br>
<b>Date: </b>Tuesday, August 25, 2020 at 3:22 PM<br>
<b>To: </b>"<a href="mailto:SchindelD@si.edu" target="_blank">SchindelD@si.edu</a>" <<a href="mailto:schindeld@si.edu" target="_blank">schindeld@si.edu</a>>, Andrew Bentley <<a href="mailto:abentley@ku.edu" target="_blank">abentley@ku.edu</a>>, "<a href="mailto:nhcoll-l@mailman.yale.edu" target="_blank">nhcoll-l@mailman.yale.edu</a>"
<<a href="mailto:nhcoll-l@mailman.yale.edu" target="_blank">nhcoll-l@mailman.yale.edu</a>><br>
<b>Subject: </b>RE: Digital objects vs. physical objects in collection management databases and how to manage them</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Hi Andy,<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">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></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">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></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">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></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Best,<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Zach<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">--<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Zachary S. Randall<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Biological Scientist & Imaging Lab Manager
<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Florida Museum of Natural History
<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">1659 Museum Road<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Gainesville, FL 32611-7800<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">352-273-1958|Rm. 277
<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"><a href="https://aus01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.zacharyrandall.org%2F&data=02%7C01%7Csadie.mills%40niwa.co.nz%7C86ec6c523f324a04b20b08d8494b1a4f%7C41caed736a0c468aba499ff6aafd1c77%7C0%7C0%7C637339934272711256&sdata=DrKZChoxDX1jMoLZhWMwwFXMRCDkNW41vJNtTUnT4%2F4%3D&reserved=0" target="_blank">www.zacharyrandall.org</a><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US">Twitter: @Zach__Randall<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<div>
<div style="border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0cm 0cm 0cm;border-color:currentcolor currentcolor">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> Nhcoll-l <<a href="mailto:nhcoll-l-bounces@mailman.yale.edu" target="_blank">nhcoll-l-bounces@mailman.yale.edu</a>>
<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 <<a href="mailto:abentley@ku.edu" target="_blank">abentley@ku.edu</a>>;
<a href="mailto:nhcoll-l@mailman.yale.edu" target="_blank">nhcoll-l@mailman.yale.edu</a><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></span></p>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
<table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" align="left" width="100%" style="width:100.0%">
<tbody>
<tr>
<td style="padding:0cm 0cm 0cm 0cm">
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;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" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:12.0pt;color:black">Hi, Andy,</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:12.0pt;color:black"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:12.0pt;color:black">We've had discussions about this in the Interagency Working Group on Scientific Collections (IWGSC; see
<a href="https://aus01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fusfsc.nal.usda.gov%2F&data=02%7C01%7Csadie.mills%40niwa.co.nz%7C86ec6c523f324a04b20b08d8494b1a4f%7C41caed736a0c468aba499ff6aafd1c77%7C0%7C0%7C637339934272711256&sdata=0qnHc2sjvCpuhJJor5snd9sTQHMriqSEZS%2BFZr8S4Tk%3D&reserved=0" target="_blank">
usfsc.nal.usda.gov</a>). 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. </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:12.0pt;color:black"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" 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.</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:12.0pt;color:black"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:12.0pt;color:black">Best regards and stay well -</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:12.0pt;color:black"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:12.0pt;color:black">David</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:12.0pt;color:black"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<div id="gmail-m_7966388451846362072Signature">
<div id="gmail-m_7966388451846362072divtagdefaultwrapper">
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:12.0pt;color:black">David E. Schindel, Research Associate</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:12.0pt;color:black">Office of the Provost</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:12.0pt;color:black">Smithsonian Institution</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:12.0pt;color:black">Email:
<a href="mailto:schindeld@si.edu" target="_blank">schindeld@si.edu</a> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US" style="font-size:12.0pt;color:black"> </span><span lang="EN-US"><o:p></o:p></span></p>
</div>
</div>
</div>
<div class="MsoNormal" align="center" style="text-align:center"><span lang="EN-US">
<hr size="1" width="100%" align="center">
</span></div>
<div id="gmail-m_7966388451846362072divRplyFwdMsg">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span lang="EN-US" style="color:black">From:</span></b><span lang="EN-US" style="color:black"> Nhcoll-l <<a href="mailto:nhcoll-l-bounces@mailman.yale.edu" target="_blank">nhcoll-l-bounces@mailman.yale.edu</a>>
on behalf of Bentley, Andrew Charles <<a href="mailto:abentley@ku.edu" target="_blank">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" target="_blank">nhcoll-l@mailman.yale.edu</a> <<a href="mailto:nhcoll-l@mailman.yale.edu" target="_blank">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><span lang="EN-US">
<o:p></o:p></span></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
</div>
<div>
<p class="gmail-m7966388451846362072xmsonormal" style="line-height:12.0pt;background:#FFEB9C;background-attachment:scroll;background-position-x:0%;background-position-y:0%">
<b><span lang="EN-US" style="font-size:9.0pt;color:#9C6500">External Email - Exercise Caution</span></b><span lang="EN-US"><o:p></o:p></span></p>
<div>
<div>
<p class="gmail-m7966388451846362072xmsonormal"><a name="m_7966388451846362072_x__GoBack"></a><span lang="EN-US">Hi all<o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US">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.<o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US">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.<o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US">Thanks in advance<o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US">Andy<o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
<div>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US" style="color:black"> A : A : A :</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US" style="color:black"> }<(((_°>.,.,.,.}<(((_°>.,.,.,.}<)))_°></span><span lang="EN-US"><o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US" style="color:black"> V V V</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US" style="color:black">Andy Bentley</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US" style="color:black">Ichthyology Collection Manager</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US" style="color:black">University of Kansas</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US" style="color:black">Biodiversity Institute</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US" style="color:black">Dyche Hall</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US" style="color:black">1345 Jayhawk Boulevard</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US" style="color:black">Lawrence, KS, 66045-7561</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US" style="color:black">USA</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US" style="color:black"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US" style="color:black">Tel: (785) 864-3863</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US" style="color:black">Fax: (785) 864-5335 </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US" style="color:black">Email: <a href="mailto:abentley@ku.edu" target="_blank">abentley@ku.edu</a> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US" style="color:black"><a href="https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttps-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%26d%3DDwMFAw%26c%3DsJ6xIWYx-zLMB3EPkvcnVg%26r%3DBsjUEaAzErVnOJA4kXSO_g%26m%3DdjrI-zIT93wiMGeria7qiHeg1OnPwpMDkL1fmqCoeBk%26s%3Dz6APnia86i0F27gg3vvbRfIh_HCwEBpFrZWKVObYaYU%26e%3D&data=02%7C01%7Csadie.mills%40niwa.co.nz%7C86ec6c523f324a04b20b08d8494b1a4f%7C41caed736a0c468aba499ff6aafd1c77%7C0%7C0%7C637339934272721250&sdata=VEnn%2BvDf8yzGc6JFwEBii7iGvwnlKlnX9Sx4zalrX64%3D&reserved=0" target="_blank">http://ichthyology.biodiversity.ku.edu</a></span><span lang="EN-US"><o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US" style="color:black"> </span><span lang="EN-US"><o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US" style="color:black"> A : A : A :</span><span lang="EN-US"><o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US" style="color:black"> }<(((_°>.,.,.,.}<(((_°>.,.,.,.}<)))_°></span><span lang="EN-US"><o:p></o:p></span></p>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US" style="color:black"> V V V</span><span lang="EN-US"><o:p></o:p></span></p>
</div>
<p class="gmail-m7966388451846362072xmsonormal"><span lang="EN-US"> <o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
Nhcoll-l mailing list<br>
<a href="mailto:Nhcoll-l@mailman.yale.edu" target="_blank">Nhcoll-l@mailman.yale.edu</a><br>
<a href="https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.yale.edu%2Fmailman%2Flistinfo%2Fnhcoll-l&data=02%7C01%7Csadie.mills%40niwa.co.nz%7C86ec6c523f324a04b20b08d8494b1a4f%7C41caed736a0c468aba499ff6aafd1c77%7C0%7C0%7C637339934272721250&sdata=7J5QFjNkhsReF28vPkq1cuyU%2BtfMSpVWJlK%2BhfmcVaY%3D&reserved=0" target="_blank">https://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="https://aus01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.spnhc.org%2F&data=02%7C01%7Csadie.mills%40niwa.co.nz%7C86ec6c523f324a04b20b08d8494b1a4f%7C41caed736a0c468aba499ff6aafd1c77%7C0%7C0%7C637339934272731250&sdata=Zy66jSkQrwSy7TY1ld0a4lKZzoac2pot4jnp%2F%2BASKCY%3D&reserved=0" target="_blank">
http://www.spnhc.org</a> for membership information.<br>
Advertising on NH-COLL-L is inappropriate.<o:p></o:p></p>
</blockquote>
</div>
</div>
<table style="width: 600px; font-size: 8pt; font-family: Arial" cellspacing="20">
<tbody>
<tr>
<td><a href="https://www.niwa.co.nz"><img src="https://www.niwa.co.nz/static/niwa-2018-horizontal-180.png"></a>
</td>
<td>
<table style="width: 500px">
<tbody>
<span>Sadie Mills<br>
<font color="#1793d2">Principal Technician - Marine Biology</font><br>
<font color="#1793d2">Group Manager - Collections Curation</font><br>
+64-4-386-0464 | +64-27-447-2343<br>
National Institute of Water & Atmospheric Research Ltd (NIWA)<br>
301 Evans Bay Parade Hataitai Wellington New Zealand<br>
<b>Connect with NIWA:</b> <a href="https://www.niwa.co.nz">niwa.co.nz</a> <a href="https://www.facebook.com/nzniwa">
Facebook</a> <a href="https://www.linkedin.com/company/niwa">LinkedIn</a> <a href="https://twitter.com/niwa_nz">
Twitter</a> <a href="https://www.instagram.com/niwa_science">Instagram</a> </span>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
<font face="Arial" size="1">To ensure compliance with legal requirements and to maintain cyber security standards, NIWA's IT systems are subject to ongoing monitoring, activity logging and auditing. This monitoring and auditing service may be provided by third
parties. Such third parties can access information transmitted to, processed by and stored on NIWA's IT systems</font>
</body>
</html>