<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Dear Eric,<br>
<br>
it depends which kinds of data field your database offers for date
entries. Paul's recommendations are very reasonable, as this
convention provides a clear indicator that specific information
was not available (but that this information was checked to best
knowledge when datasets were migrated into the new database, or
entered directly). Recording that something was unknown at a
specific point or recorded inadequately or vaguely is very
helpful, especially if a successor wants to evaluate specific
datasets in the future.<br>
<br>
In our database, any edits are marked with [squared brackets], for
example alternative locality spellings, locality data that got
edited to be more accurate, etc. Usually we add initials and date
of the person that did the edits.<br>
<br>
If your database has only one field for date entries and this is
numerical, it might be worth to move the information into the
remarks. Because the remarks field is a collector for everything
that fits nowhere else, it is worth to introduce a strict syntax
to separate these bits (e.g. a semicolon).<br>
<br>
Hope this helps<br>
Dirk<br>
<br>
Am 18.09.2018 um 03:21 schrieb Schultz, Eric:<br>
</div>
<blockquote type="cite"
cite="mid:BN6PR05MB3489B8C55DB219132EADE7CC851D0@BN6PR05MB3489.namprd05.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<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:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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]-->
<div class="WordSection1">
<p class="MsoNormal">We are cleaning up entries in a legacy
database so that our data can be imported into a properly
configured collections database. Exact dates will be imported
in a text string mm/dd/yyyy. But how to render a vague date
referring only to season, such as ‘Spring 1984’, or if only
the year was recorded? Is it better to record as missing data,
record as an erroneous but exact date such as 01/01/1984, or
place at the midpoint of the season? Whatever we do we will
have a ‘verbatim’ field that preserves the original entry, but
we want to have a version of collection date that is useful
and searchable. Thanks for any assistance!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Eric T. Schultz<o:p></o:p></p>
<p class="MsoNormal">Professor, Department of Ecology and
Evolutionary Biology<o:p></o:p></p>
<p class="MsoNormal">Coordinator, Joint BS-MS Degree in
Biodiversity and Conservation Biology<o:p></o:p></p>
<p class="MsoNormal">Director, Vertebrate Biodiversity
Collections<o:p></o:p></p>
<p class="MsoNormal">Chair, General Education Oversight
Committee<o:p></o:p></p>
<p class="MsoNormal">University of Connecticut<o:p></o:p></p>
<p class="MsoNormal">Storrs, CT 06269-3043<o:p></o:p></p>
<p class="MsoNormal"><a href="mailto:eric.schultz@uconn.edu"
moz-do-not-send="true">eric.schultz@uconn.edu</a><o:p></o:p></p>
<p class="MsoNormal">860.486.4692<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Nhcoll-l mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Nhcoll-l@mailman.yale.edu">Nhcoll-l@mailman.yale.edu</a>
<a class="moz-txt-link-freetext" href="https://mailman.yale.edu/mailman/listinfo/nhcoll-l">https://mailman.yale.edu/mailman/listinfo/nhcoll-l</a>
_______________________________________________
NHCOLL-L is brought to you by the Society for the Preservation of
Natural History Collections (SPNHC), an international society whose
mission is to improve the preservation, conservation and management of
natural history collections to ensure their continuing value to
society. See <a class="moz-txt-link-freetext" href="http://www.spnhc.org">http://www.spnhc.org</a> for membership information.
Advertising on NH-COLL-L is inappropriate.
</pre>
</blockquote>
<p><br>
</p>
<pre class="moz-signature" cols="72">--
Dirk Neumann
Tel: 089 / 8107-111
Fax: 089 / 8107-300
*new email: neumann(a)snsb.de*
Postanschrift:
Staatliche Naturwissenschaftliche Sammlungen Bayerns
Zoologische Staatssammlung München
Dirk Neumann, Sektion Ichthyologie / DNA-Storage
Münchhausenstr. 21
81247 München
Besuchen Sie unsere Sammlung:
<a class="moz-txt-link-freetext" href="http://www.zsm.mwn.de/sektion/ichthyologie-home/">http://www.zsm.mwn.de/sektion/ichthyologie-home/</a>
---------
Dirk Neumann
Tel: +49-89-8107-111
Fax: +49-89-8107-300
*new email: neumann(a)snsb.de*
postal address:
Bavarian Natural History Collections
The Bavarian State Collection of Zoology
Dirk Neumann, Section Ichthyology / DNA-Storage
Muenchhausenstr. 21
81247 Munich (Germany)
Visit our section at:
<a class="moz-txt-link-freetext" href="http://www.zsm.mwn.de/sektion/ichthyologie-home/">http://www.zsm.mwn.de/sektion/ichthyologie-home/</a>
</pre>
</body>
</html>