<div dir="ltr"><div><div><div><div><div><div><div>From the perspective of a terrestrial arthropod collections manager and researcher, I have been thinking about this issue for some time. How a specimen was dispatched, processed, and archived makes a big difference in how it can be used for research. And of course, it could be segregated into several parts that are treated differently. "It's complicated." But the better these things can be documented in a standardized way, the more useful for research. And I like controlled vocabularies, but that would be a long list across disciplines, and there would need to be an "other" option.<br><br></div>Suggested fields:<br></div>- Killing Method (eg. frozen, cyanide, EtOAc, 95% EtOH, 70% EtOH, ethylene glycol, propylene glycol, ...)<br></div>- Fixative (eg. Formalin, EtOH, ...)<br></div>- Preparation (eg. "cleared with KOH, stainied with chlorazol Black & Eosin Y", " ... Mercurochrome", ...)<br></div>- Preparation Notes (eg. "rehydrated in the presence of chlorocresol", "stored/transported with naphthalene", ...)<br>- Preservation (eg. 90% EtOH, 70% EtOH, Euparal, Balsam Resin, Hoyer's solution, ...)<br><br></div>Each of these (and other fields) could have "By" (person) "On Date" (when it happened). And these fields could apply to separate parts (eg. tissues sub-sampled for DNA and preserved separately, genitalia dissections with slide mounts, plants or cultures subdivided among institutions, ...). Quickly the number of fields proliferates. In a one-to-many relational system it would not be too difficult to capture in a structured way. But can GBIF, iDigBio, and others accommodate dimensional data? They generally work in flat file formats, right?<br><br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><font size="1">------------------------------------------------------------<br>Peter T Oboyski, PhD<br>Collections Manager & Curatorial Supervisor<br>Essig Museum of Entomology<br>1170 Valley Life Science Building<br>University of California, Berkeley<br><br>mailing address:<br>1101 VLSB, #4780<br>Berkeley, CA 94720<br><br><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__nature.berkeley.edu_-257Epoboyski_&d=DwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=CLFZJ3fvGSmDp7xK1dNZfh6uGV_h-8NVlo3fXNoRNzI&m=PHpj30ZxQiwuSD-P3QmY-MEa-CLcQvm9q_LF1nBFqco&s=fMpjuBWpDHjXfBAGl-HpwDLfPR7nrPnONvBpsuvZWi4&e=" target="_blank">http://nature.berkeley.edu/~poboyski/</a><br><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__essig.berkeley.edu&d=DwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=CLFZJ3fvGSmDp7xK1dNZfh6uGV_h-8NVlo3fXNoRNzI&m=PHpj30ZxQiwuSD-P3QmY-MEa-CLcQvm9q_LF1nBFqco&s=wY-ItU9xf5QNNtBekH44KTOENxUun3qXQQzWWzfW00U&e=" target="_blank">http://essig.berkeley.edu</a><br><br><a href="mailto:essig.museum@gmail.com" target="_blank">essig.museum@gmail.com</a><br>510.643.0804 (work phone)<br>510.847.0360 (cell phone)<br>--------------------------------------------------------------</font><br></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Fri, Mar 3, 2017 at 9:47 AM, Bentley, Andrew Charles <span dir="ltr"><<a href="mailto:abentley@ku.edu" target="_blank">abentley@ku.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="#0563C1" vlink="#954F72" lang="EN-US">
<div class="m_1235430249551037127WordSection1">
<p class="MsoNormal">Hi all<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">During various conversations I have had over the past couple of months in my capacity as Specify usability consultant and ichthyology collection manager it has become clear to me that one of the major hurdles that is experienced with aggregators
and sharing of data through Darwin Core is the preparation field. Most of the other one-to-many relationships have been taken care of (identifications, measurements, collectors, sequences, media etc.) through similar extensions or other means leaving preparations
as the only one left to tackle. Due to the nature of fish collections and our propensity to utilize the one-to-many relationship between specimens and preparations for all the various preparations we house (ethanol, cleared and stained, skeletal, tissue),
coupled with the fact that there is only a single field in Darwin Core for preparations, mandates that we need to concatenate our preparations into a string (or simply not map them) in order to be able to map them effectively. As such these concatenations
can and do include information about preparation type, counts and various other pieces of information thus littered the field with a huge amount of unique values (160,000 to be exact). With the ever increasing proliferation of tissue collections in all disciplines
this is becoming a more pressing issue for more than just fish collections and is now more widespread across all disciplines.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Given the above, I was thinking of proposing a preparation extension to Darwin Core to accommodate this but as a first step would like to get feedback from the community as to the perceived need and efficacy for such an extension. The
extension need not be very complex and would nominally include fields for preparation type (controlled vocabulary), count (number), prepared by (agent), prepared date and maybe a unique GUID. However, the extension would only be useful if the aggregators
(GBIF, iDigBio etc.) were able to display the data within this extension as part of their portal infrastructure thereby increasing the usefulness of the records for research purposes. Do you think such an extension would be useful? What fields would you
like to see included? Question for the aggregators – would this data be able to be displayed fore efficient use by the ever growing user community?<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Any comments, suggestions, ideas for additional fields etc. are most welcome. Please forward to others who may not be on NHCOLL and who may be interested.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Thanks in advance<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Andy<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-AU"> A : A : A :<br>
}<(((_°>.,.,.,.}<(((_°>.,.,.,<wbr>.}<)))_°><br>
V V V<br>
Andy Bentley<br>
Ichthyology Collection Manager<br>
University of Kansas<br>
Biodiversity Institute<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-AU">Dyche Hall<br>
1345 Jayhawk Boulevard<br>
Lawrence, KS, 66045-7561<br>
USA<br>
<br>
Tel: <a href="tel:(785)%20864-3863" value="+17858643863" target="_blank">(785) 864-3863</a><br>
Fax: <a href="tel:(785)%20864-5335" value="+17858645335" target="_blank">(785) 864-5335</a> <br>
Email: <a href="mailto:abentley@ku.edu" target="_blank"><span style="color:blue">abentley@ku.edu</span></a> <u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-AU"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__ichthyology.biodiversity.ku.edu_&d=DwMFAw&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=CLFZJ3fvGSmDp7xK1dNZfh6uGV_h-8NVlo3fXNoRNzI&m=39WrfUekMrju94v_4HVXBriqB-P3C3JDjHSPlGQ0F10&s=Y-pre1byIqhER5aOPnKwA6RU5zGLWaYvXiaAEpxSCV8&e=" target="_blank"><span style="color:blue">http://ichthyology.<wbr>biodiversity.ku.edu</span></a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-AU"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-AU">SPNHC Past-President<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-AU"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.spnhc.org_&d=DwMFAw&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=CLFZJ3fvGSmDp7xK1dNZfh6uGV_h-8NVlo3fXNoRNzI&m=39WrfUekMrju94v_4HVXBriqB-P3C3JDjHSPlGQ0F10&s=JsEgPq1MVcz4zQakIqqrd9BJT_JYieGi3tH_P58Qgwo&e=" target="_blank"><span style="color:blue">http://www.spnhc.org</span></a><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-AU"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black" lang="EN-AU"> : : <br>
A : A : A :<br>
}<(((_°>.,.,.,.}<(((_°>.,.,.,<wbr>.}<)))_°><br>
V V V</span><span style="color:#1f497d" lang="EN-AU"><u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<br>______________________________<wbr>_________________<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" rel="noreferrer" target="_blank">http://mailman.yale.edu/<wbr>mailman/listinfo/nhcoll-l</a><br>
<br>
______________________________<wbr>_________________<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://urldefense.proofpoint.com/v2/url?u=http-3A__www.spnhc.org&d=DwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=CLFZJ3fvGSmDp7xK1dNZfh6uGV_h-8NVlo3fXNoRNzI&m=PHpj30ZxQiwuSD-P3QmY-MEa-CLcQvm9q_LF1nBFqco&s=QNgVtjcHYXDhXMtFH4eR98KF39q87q87qIR1_GNhrgI&e=" rel="noreferrer" target="_blank">http://www.spnhc.org</a> for membership information.<br>
Advertising on NH-COLL-L is inappropriate.<br>
<br></blockquote></div><br></div>