<div dir="ltr">Lien,<div><br></div><div>My lab has used Specify database for years. I love it. Everything is *finally* in one database - there's a table for scanning and attaching accession paperwork and permits, a table for publications so you can easily link specimens to their citation history, all of our loans are 'in' and we can quickly find who is coming due. Use of authority tables and 'trees' that tie to lookup fields cuts down on misspellings, and helps keep mistakes down to a mild roar (our original database has issues with people putting data into the wrong field, such as in the taxon field, they would put 'Jurassic'). </div><div><br></div><div>It's a complex thing but it's worth it. We make extensive use of wikis to train people, as well as to provide them with a quick reference. (wikis [dot] utexas [dot] edu/display/specify6/Specify+Database)</div><div><br></div><div>Finding the information you need is really quick, too. It's been a learning curve, of course, but we can now generate reports that count number of specimens per locality, how many research loans vs. outreach loans for any given year, and so on. It's nice having good tools to look at the collections with, but it's also a great help for gathering statistical data about how the collection is *used*. </div><div><br></div><div>I find one of the biggest drawbacks is how hard it is to change information once it's in the database. If data got added incorrectly, or even if you just want to refine some information, in many cases each record has to be edited individually. An example would be if a taxa is split, with some saying with the original genus but others getting reassigned. In this case, you would have to first update the taxon 'tree', then open *only* the records that are getting reassigned and edit each of them. Sure, it's a small thing, but if you have a lot to do then it gets really tedious and time consuming. The silver lining is if *all* the specimens get reassigned, you just edit the 'tree' and the individual records tied to that entry all change (this features comes with its own dangers, though!). </div><div><br></div><div>Hope this helps. Feel free to contact me if you have other questions. </div><div><br></div><div>Angie</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 1, 2015 at 6:37 AM, Huong Lien Tran <span dir="ltr"><<a href="mailto:huong.tran@uq.net.au" target="_blank">huong.tran@uq.net.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div style="font-size:12pt;color:#000000;background-color:#ffffff;font-family:Calibri,Arial,Helvetica,sans-serif">
<p><span style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:14.6666669845581px">Hi all, </span></p>
<p><span style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:14.6666669845581px"><br>
</span></p>
<p><span style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:14.6666669845581px">I am posting for my colleague who is working in natural history collection management. Currently her museum in Vietnam is looking to digitise their current specimens
collections and is looking for an affordable management system. </span><span style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:14.6666669845581px">We've done some research and found that the common ones like KEmu or Vernon are a bit too
expensive for their museum to handle. We've come upon Specify (<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__specifyx.specifysoftware.org_specify7_&d=AwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=CLFZJ3fvGSmDp7xK1dNZfh6uGV_h-8NVlo3fXNoRNzI&m=InDsYKRaBducE-o3tDKHCN6uuQ0o7Lm03va1z7qaUrM&s=HI7xEF19TJNrx5S6GJap8u-oro_8dmJyrNXJhL5-zis&e=" target="_blank">http://specifyx.specifysoftware.org/specify7/</a>) and it seems to be very good in the prospect of having local technicians handling the development and maintenance the database, keeping the cost at
affordable level. Nevertheless, we would really want to have some insights from professionals who had experience with Specify. Are there any pitfalls we should look for? Or maybe a contact points where we can get help when using Specify?</span></p>
<p><span style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:14.6666669845581px"><br>
</span></p>
<p><span style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:14.6666669845581px"><span style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:14.6666669845581px">Thanks You,</span><br>
</span></p>
<p><span style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:14.6666669845581px"><span style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:14.6666669845581px"><br>
</span></span></p>
<p><span style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:14.6666669845581px"><span style="color:rgb(31,73,125);font-family:Calibri,sans-serif;font-size:14.6666669845581px">Lien</span></span></p>
<p><br>
</p>
</div>
</div>
<br>_______________________________________________<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="http://mailman.yale.edu/mailman/listinfo/nhcoll-l" rel="noreferrer" 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="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.spnhc.org&d=AwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=CLFZJ3fvGSmDp7xK1dNZfh6uGV_h-8NVlo3fXNoRNzI&m=InDsYKRaBducE-o3tDKHCN6uuQ0o7Lm03va1z7qaUrM&s=5fCB3BH2zmgnBzjEV1MrXV7BgC3t-Hwzrya0TMXcr9g&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></div>