Hi David,<div><br></div><div>Thanks for this heads up. The ITIS ID&#39;s that I have are either from checking manually or mapping on names from one of your downloads.</div><div><br></div><div>In the database that feeds TaxonConcept I try to store both the ITIS ID and the &quot;Scientific Name&quot; that is tied to that ID.</div>
<div><br></div><div>I do this so I know that it&#39;s uses the same or a different name for what I think is the same concept.</div><div><br></div><div>Here is an example of a species concept where my name and the ITIS name differ.</div>
<div><br></div><div><a href="http://lod.taxonconcept.org/ses/sDHAp.html">http://lod.taxonconcept.org/ses/sDHAp.html</a><br><br></div><div>The lexical groups are there to show indicate that there is some association between a given namestring and the concept.</div>
<div><br></div><div>It does not mean that these are true synonyms, these are just to allow pattern matching between namestrings and data that might possibly pertain to the species concept.</div><div><br></div><div>Along the lines of Steve&#39;s earlier email it would be &quot;relatively easy&quot; or perhaps relatively straightforward to create LOD URI&#39;s from your data set with a separate controller that outputs either RDF or RDFa.</div>
<div><br></div><div>URI&#39;s similar to <a href="http://www.itis.gov/tsn/113839">http://www.itis.gov/tsn/113839</a> (ruby on rails likes plural controller so an alternative would be) <a href="http://www.itis.gov/tsns/113839">http://www.itis.gov/tsns/113839</a></div>
<div><br></div><div>I could markup an RDF / RDFa example of one of your records in DarwinCore RDF if that would help people get their head around this.</div><div><br></div><div>RDFa in which the RDF markup exists within the HTML page. Here is a page with links to RDFa examples <a href="http://rdfa.info/wiki/Examples-in-the-wild">http://rdfa.info/wiki/Examples-in-the-wild</a></div>
<div><br></div><div>and a Wikipedia page on RDFa <a href="http://en.wikipedia.org/wiki/RDFa">http://en.wikipedia.org/wiki/RDFa</a></div><div><br></div><div>Respectfully,</div><div><br></div><div>- Pete</div><div><br><div class="gmail_quote">
On Tue, May 31, 2011 at 2:16 PM, Nicolson, David <span dir="ltr">&lt;<a href="mailto:NICOLSOD@si.edu">NICOLSOD@si.edu</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div lang="EN-US" link="blue" vlink="purple"><div><p class="MsoNormal"><span style="font-size:10.0pt;color:#1F497D">Dear Pete and Steve,</span></p><p class="MsoNormal"><span style="font-size:10.0pt;color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#1F497D">I cannot comment on the technical content of your emails (sorry, I&#39;m a content guy!), but I do note this comment by Pete:</span></p><div class="im"><p class="MsoNormal">
<span style="font-size:10.0pt;color:#1F497D">&quot;</span>Most of the plants also have the USDA Plants identifier. In fact you might be able to get the ITIS numbers via the USDA Plants Database.<span style="font-size:10.0pt;color:#1F497D">&quot;</span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#1F497D"> </span></p></div><p class="MsoNormal"><span style="font-size:10.0pt;color:#1F497D">I would not recommend getting ITIS TSNs from any other source than ITIS (see my prior email for some how-to ideas).</span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#1F497D"> </span></p><p class="MsoNormal"><span style="font-size:10.0pt;color:#1F497D">Firstly, the PLANTS Symbol-to-TSN matches were not always well managed due to some technical issues (involving early changes to ITIS, some due to problematic bulk-updates of ITIS from the PLANTS data, or sometimes due to other artifacts). In MOST cases the TSNs they list will be fine, but a silent subset will not.</span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#1F497D"> </span></p><p class="MsoNormal"><span style="font-size:10.0pt;color:#1F497D">Secondly, as I noted, we are mid-stream in a full overhaul of the vascular plant data in ITIS, in almost every case using cooperatively-produced data sets that have also been made available to PLANTS as well. When/whether they use them to update that database is another question, but the ITIS updates are proceeding full-steam, with additional improvements where needed.</span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#1F497D"> </span></p><p class="MsoNormal"><span style="font-size:10.0pt;color:#1F497D">Finally, at least when dealing with non-static data sets, I feel it is just &#39;best practice&#39; to get them from the source wherever feasible, rather than from other places.</span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#1F497D"> </span></p><p class="MsoNormal"><span style="font-size:10.0pt;color:#1F497D">Best,</span></p><div class="im"><p class="MsoNormal"><span style="font-size:10.0pt;color:#1F497D">Dave</span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#1F497D"> </span></p><p class="MsoNormal"><span style="font-size:10.0pt;color:#1F497D">David Nicolson<br>Data Development Coordinator, Integrated Taxonomic Information System<br>
Biologist, USGS Core Science Systems, Biological Informatics Program<br><a href="mailto:nicolsod@si.edu" target="_blank">nicolsod@si.edu</a>    Office <a href="tel:202-633-2149" value="+12026332149" target="_blank">202-633-2149</a>    Fax <a href="tel:202-786-2934" value="+12027862934" target="_blank">202-786-2934</a><br>
<a href="http://www.itis.gov/" target="_blank"><span style="color:#1F497D">http://www.itis.gov/</span></a><br><a href="http://www.cbif.gc.ca/itis/" target="_blank"><span style="color:#1F497D">http://www.cbif.gc.ca/itis/</span></a><br>
&quot;Nihil sumas necesse est...&quot;</span></p><p class="MsoNormal"> </p><p class="MsoNormal"><span style="font-size:10.0pt;color:#1F497D"> </span></p></div><div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt">From:</span></b><span style="font-size:10.0pt"> Peter DeVries [mailto:<a href="mailto:pete.devries@gmail.com" target="_blank">pete.devries@gmail.com</a>] <br><b>Sent:</b> Tuesday, May 31, 2011 2:48 PM<br>
<b>To:</b> Steve Baskauf<br><b>Cc:</b> Nicolson, David; <a href="mailto:tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a>; Gerald Guala; Orrell, Thomas; Alan J Hampson</span></p><div><div></div>
<div class="h5"><br><b>Subject:</b> Re: [tdwg-content] ITIS TSNID to uBio NamebankIDs mapping</div></div><p></p></div><div><div></div><div class="h5"><p class="MsoNormal"> </p><p class="MsoNormal">Hi Steve et al.,</p><div>
<p class="MsoNormal"> </p></div><div><p class="MsoNormal">I agree. This was one of the reasons that I setup TaxonConcept the way I did. It attempts to connect both the LOD entities and the foreign key based entities.</p></div>
<div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">For example:</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">The Racoon <a href="http://lod.taxonconcept.org/ses/CTZ8z.html" target="_blank">http://lod.taxonconcept.org/ses/CTZ8z.html</a></p>
</div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Has links to many other URL&#39;s and URI&#39;s as well as the integer id&#39;s for:</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">
EoL</p></div><div><p class="MsoNormal">NCBI</p></div><div><p class="MsoNormal">ITIS</p></div><div><p class="MsoNormal">BOLD</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">* For some of these it might be best to represent these as a one to many since there are often many names for each concept.</p>
</div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">I have uBio ID&#39;s in GeoSpecies but I thought that would be eventually pulled in via the GNI.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">
I also have a small set of other foreign keys for things like the Hymenoptera name server, FishBase, Mushroom Observer and Tropicos.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Since these are specific to specific subsets of organisms, and came on later in my project I thought it would be best to use a separate RDF file to map to those.</p>
</div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">For instance with Fishbase <a href="http://assets.taxonconcept.org/fb/index.rdf" target="_blank">http://assets.taxonconcept.org/fb/index.rdf</a></p></div>
<div><p class="MsoNormal"> </p></div><div><div><p class="MsoNormal">Insects like this one <a href="http://lod.taxonconcept.org/ses/ICmLC.html" target="_blank">http://lod.taxonconcept.org/ses/ICmLC.html</a> also have the id for bugguide if it exists there and I have found it under the same name or a synonym.</p>
</div></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Of the ~105,000 concepts I have about 47,000 with ITIS ID&#39;s. This may be useful for your plant list and I can send you a spreadsheet if that is easier.</p>
</div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Most of the plants also have the USDA Plants identifier. In fact you might be able to get the ITIS numbers via the USDA Plants Database.</p></div><div><p class="MsoNormal">
 </p></div><div><p class="MsoNormal">I have come to realize that many other groups see the solution to data access is with a custom API, but this requires understanding and debugging your code for each API.</p></div><div>
<p class="MsoNormal"> </p></div><div><p class="MsoNormal">Once the data is available in RDF it is one API for everything. Some issues like what to call each field can be overcome by simply rewriting (converting) the RDF.</p>
</div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">This is easy as long as you have equivalent semantics in the meaning of the field.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">
For instance, it does not really matter if this name is represented as </p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal"><span style="font-family:&quot;Courier New&quot;">&lt;txn:hasScientificName&gt;Procyon lotor&lt;/txn:hasScientificName&gt;</span> or <span style="font-family:&quot;Courier New&quot;">&lt;dwc:scientificName&gt;Procyon lotor&lt;/dwc:scientificName&gt;</span> </p>
</div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">The important thing to understand is that in my model this field does not include the authorship string.</p></div><div><p class="MsoNormal"> </p></div><div>
<p class="MsoNormal">This makes it easier to map this to other datasets and publications that don&#39;t include the authorship string.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal"><span style="font-family:&quot;Courier New&quot;">&lt;txn:scientificNameAuthorship&gt;(Linnaeus 1758)&lt;/txn:scientificNameAuthorship&gt; </span></p>
</div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal"><span> * The scientificNameAuthorship should eventually be mapped to a publication or a list of probable publications. It is too ambiguous.</span></p></div>
<div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">There was a debate about <span>&lt;scientificName&gt;</span> earlier on the list which seemed to go back and forth.  </p></div><div><p class="MsoNormal"> </p>
</div><div><p class="MsoNormal">I got tired of rewriting my examples each time and decided to use my own vocabulary that works in my example queries and has fields that map as closely to dwc as possible.</p></div><div><p class="MsoNormal">
 </p></div><div><p class="MsoNormal" style="margin-bottom:12.0pt">- Pete</p><div><p class="MsoNormal">On Tue, May 31, 2011 at 7:07 AM, Steve Baskauf &lt;<a href="mailto:steve.baskauf@vanderbilt.edu" target="_blank">steve.baskauf@vanderbilt.edu</a>&gt; wrote:</p>
<div><p class="MsoNormal">I had actually written a response to this thread about a week ago in which I tried to clarify why I wanted to connect the ITIS and uBio identifiers.  However, I decided that the email was too cynical and not helpful, so I erased it.  However, I think that a couple of the points I had in that email probably should have been made, so I will try to state them again in a more constructive manner.  <br>
<br>My reason for wanting to connect the uBio and ITIS identifiers really had nothing to do with making use of any of the tools or services that either group provides.  Rather it has to do with my desire to follow the best practices for GUIDs as laid out in the TDWG GUID Applicability Statement (now an official standard).  In particular, I have in mind Recommendations 2 and 8, which I paraphrase here as: &quot;make HTTP URIs out of your identifiers&quot; and &quot;stop making up new identifiers when somebody else already has one for the thing you are talking about&quot;.  I suppose Recommendation 10 should also be mentioned, which I paraphrase as &quot;provide RDF/XML to users that want it&quot;.  <br>
<br>I am actually using ITIS TSNs internally in my database.  However, last time I checked there were no GUIDs based on TSNs that met the recommendations I&#39;ve paraphrased above.  (The ITIS website does mention &quot;LSIDs&quot; in the context of web services, but they don&#39;t follow either recommendation 2 or 10.)  However outdated they are, uBio identifiers do actually meet recommendations 2 and 10 and that is why I wanted to use them (although the http proxied forms are unnecessarily ugly and long).  So that explains in a nutshell the reason for my request.  If ITIS would provide a simple http URI form of their TSNs which could resolve via content negotiation to either HTML or RDF/XML, it would be much easier for me to just use them.<br>
<br>OK, here is where I risk stepping on people&#39;s toes.  So I&#39;ll try to stomp gently.  I think that the area of taxon names is one where the TDWG community fails miserably at recommendation 8.  I&#39;ve lost count of the number of different kinds of identifiers that are available for referring to taxon names (this issue was discussed previously in the thread that starts with <a href="http://lists.tdwg.org/pipermail/tdwg-content/2011-January/002231.html" target="_blank">http://lists.tdwg.org/pipermail/tdwg-content/2011-January/002231.html</a> so I won&#39;t repeat it here).  I don&#39;t know about (nor particularly care about) &quot;turf&quot; in this area, but I would challenge the community to get serious about recommendation 8 and come up with some consensus about a single, universal set of GUIDs for taxon names.  Those identifiers should (in my opinion which stems from the GUID recommendations):<br>
- be http URIs (rec 2)<br>- be based on an existing identifier (rec 8)<br>- return RDF/XML when a client requests it (rec 10)<br>- not change (rec 4)<br>I do not like proxied LSIDs (unnecessarily long with many useless characters) and I despise UUIDs (what is the point of creating a long, un-typeable string to replace a serial number that is already globally unique if appended to a domain name?).  Why not just register something like <a href="http://purl.org/tn/" target="_blank">&quot;http://purl.org/tn/&quot;</a> (with &quot;tn&quot; representing &quot;taxon name&quot;) and stick one of the existing serial numbers onto it?  The domain name would be &quot;turf-neutral&quot; and anybody (GBIF, TDWG, or another organization) could manage the actual resolution through redirection from that domain.  Somebody else could take over the management of the GUIDs if the first group got tired of it or ran out of money.  The result would be a short and simple URI like <a href="http://purl.org/tn/12345" target="_blank">&quot;http://purl.org/tn/12345&quot;</a>.  What would be wrong with that?  This is not rocket science and could be easily accomplished by a few tech-savvy people if the will were there.<br>
<span style="color:#888888"><br>Steve</span></p><div><div><p class="MsoNormal"><br><br>Nicolson, David wrote: </p><pre>Hi Steve (and Dave),</pre><pre> </pre><pre>[NB: After having composed the email below, just before sending it, I re-read your initial email more carefully and realized that you said you already had the ITIS TSNs, and were looking to add the NamebankIDs! Doh! Well, in case you (or anyone else) is interested in methods of matching names to get TSNs, I&#39;ll go ahead and send this anyway. But do note the comments below about the ITIS &quot;versions&quot; and ongoing overhaul of the vascular plant data in ITIS!!! -Dave]</pre>
<pre> </pre><pre>I noticed this just before leaving work last week, and was out yesterday, but I wanted to chime in on this. I&#39;m glad the uBio tools are meeting your needs (they do have some cool stuff!), but it should be noted that those tools are using a static snapshot of ITIS data from January 2009, and we have added about 50,000 additional scientific names, and updated tens of thousands of names beyond that (most of that in the last 6 months, as the frequency of loads dropped off in 2009-2010 due to technical issues).</pre>
<pre> </pre><pre>I also want to note that ITIS is right in the middle of a full update of the vascular plant data in ITIS, and we&#39;re loading updated families on a monthly basis... and at long last we are tackling all the leftover issues from several bulk loads from USDA PLANTS data that left unreconciled bits of ITIS&#39; older vascular plant data in various confusing states... so it is a VAST improvement that is underway.</pre>
<pre> </pre><pre>There are several options for bouncing your names off the current version of ITIS.</pre><pre> </pre><pre>One is to automate a matching process using the live ITIS data, based on the existing ITIS Web Services. I am CC&#39;ing Alan Hampson, our IT fellow who built the Web Services ( <a href="http://www.itis.gov/web_service.html" target="_blank">http://www.itis.gov/web_service.html</a> ), in case you&#39;d like to follow up with him on that option. The advantage is that once you have a process in place it is completely self-serve and can always utilize the current ITIS data. If you have the resources to do this I think it would be greatly to your advantage to use this approach. </pre>
<pre> </pre><pre>You can explore some ideas for client software to use the services at: </pre><pre><a href="http://www.itis.gov/ws_develop.html" target="_blank">http://www.itis.gov/ws_develop.html</a></pre><pre> </pre><pre>
And for more information on ITIS web services try </pre><pre><a href="http://www.itis.gov/ws_description.html" target="_blank">http://www.itis.gov/ws_description.html</a></pre><pre><a href="http://www.itis.gov/ITISWebService.xml" target="_blank">http://www.itis.gov/ITISWebService.xml</a></pre>
<pre> </pre><pre>The ability to flag multiply-matched names (as you noted) should probably be considered, so that appropriate manual steps can be taken. This solution will allow you to take advantage of subsequent updates to ITIS with a minimum of additional effort, and given that the plant data are in the middle of a major overhaul, this bears consideration!</pre>
<pre> </pre><pre>Another possibility is to grab a full snapshot of the ITIS data, and load it into a database so you can do what you wish. The obvious drawback is that it goes out of date, as with the ITIS snapshot uBio is currently using. But it puts you in the driver&#39;s seat re what to do &amp; getting new versions of ITIS. Some general information about the full exports is in the following page, although conspicuously absent is any mention of the MySQL version which (assuming you have the free MySQL properly installed &amp; configured) can be loaded with just a few clicks or a few command lines (depending on your platform):</pre>
<pre><a href="http://www.itis.gov/ftp_download.html" target="_blank">http://www.itis.gov/ftp_download.html</a></pre><pre>And the current ITIS data are all here for downloading:</pre><pre><a href="http://www.itis.gov/downloads/" target="_blank">http://www.itis.gov/downloads/</a></pre>
<pre> </pre><pre>A third option, which I note with some trepidation, is the old &quot;Compare Nomenclature/Taxonomy&quot; function on the ITIS site:</pre><pre><a href="http://www.itis.gov/taxmatch_ftp.html" target="_blank">http://www.itis.gov/taxmatch_ftp.html</a></pre>
<pre>This is a VERY old function that we do plan on replacing (timeframe not yet certain), and it is vulnerable to timeouts, etc., which is why it notes to limit the number of names per pass. But with smaller chunks of names it does work quite well. The caveat is that I would make sure to choose the 4th option in Step 4, as it is at least aware (unlike the 3 other options) of multiply-matched name cases, and lists them separately at the bottom of the report. Just a bare listing of the scientific names, with the word &quot;name&quot; at the top, saved as plain text, is all that is needed for input.</pre>
<pre> </pre><pre>A final option would be to ask someone at ITIS to handle the matching for you (leaving you to decide re the multiply-matched names). This might be simple from your end, but is suboptimal as it leaves you in the same position as you are now should you want or need to compare names again in the future (whether due to acquiring new names in your system, or wanting to check against a later updated version of ITIS), and it pulls someone here (probably me) off of the push to get more updates into ITIS. But in a pinch, I&#39;m certainly willing to try to help you, should it come down to that! I would just ask that you seriously consider the web services option (in particular) or the others above first.</pre>
<pre> </pre><pre>I hope this helps some. If you have already run all your matches against the old &quot;ITIS&quot; data via uBio then you might consider re-running (against the current ITIS data) at least the leftover names that you did not yet get matched. Let us know if you have questions (the <a href="mailto:itiswebmaster@itis.gov" target="_blank">itiswebmaster@itis.gov</a> address goes to myself and Alan and several others, so that might be the best bet for a follow-up unless you have a question specifically for me).</pre>
<pre> </pre><pre>Regards,</pre><pre>Dave</pre><pre> </pre><pre>David Nicolson</pre><pre>Data Development Coordinator, Integrated Taxonomic Information System</pre><pre>Biologist, USGS Core Science Systems, Biological Informatics Program</pre>
<pre><a href="mailto:nicolsod@si.edu" target="_blank">nicolsod@si.edu</a>     Office <a href="tel:202-633-2149" target="_blank">202-633-2149</a>    Fax <a href="tel:202-786-2934" target="_blank">202-786-2934</a></pre><pre>
<a href="http://www.itis.gov/" target="_blank">http://www.itis.gov/</a></pre><pre><a href="http://www.cbif.gc.ca/itis/" target="_blank">http://www.cbif.gc.ca/itis/</a></pre><pre>&quot;Nihil sumas necesse est...&quot;</pre>
<pre> </pre><pre> </pre><pre>-----Original Message-----</pre><pre>Date: Fri, 20 May 2011 05:42:03 -0500</pre><pre>From: Steve Baskauf <a href="mailto:steve.baskauf@vanderbilt.edu" target="_blank">&lt;steve.baskauf@vanderbilt.edu&gt;</a></pre>
<pre>Subject: Re: [tdwg-content] ITIS TSNID to uBio NamebankIDs mapping</pre><pre>To: &quot;David Remsen (GBIF)&quot; <a href="mailto:dremsen@gbif.org" target="_blank">&lt;dremsen@gbif.org&gt;</a></pre><pre>Cc: <a href="mailto:tdwg-content@lists.tdwg.org" target="_blank">&quot;tdwg-content@lists.tdwg.org&quot;</a> <a href="mailto:tdwg-content@lists.tdwg.org" target="_blank">&lt;tdwg-content@lists.tdwg.org&gt;</a></pre>
<pre>Message-ID: <a href="mailto:4DD6457B.2080204@vanderbilt.edu" target="_blank">&lt;4DD6457B.2080204@vanderbilt.edu&gt;</a></pre><pre>Content-Type: text/plain; charset=&quot;iso-8859-1&quot;</pre><pre> </pre><pre>Thanks, all, for the responses.  The &quot;Compare to ITIS&quot; function does </pre>
<pre>just what I want.  I did a test run of 1000 names and it worked like a </pre><pre>charm.  I will need to do a little massaging because sometimes two or </pre><pre>more ITIS IDs come back for each uBio ID.  But I can handle that.</pre>
<pre>Steve</pre><pre> </pre><pre>David Remsen (GBIF) wrote:</pre><pre>  </pre><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><pre>Steve</pre><pre> </pre><pre>Have you tried this?</pre><pre><a href="http://www.ubio.org/clients/ITIS/index.php" target="_blank">http://www.ubio.org/clients/ITIS/index.php</a></pre>
<pre> </pre><pre>or this?</pre><pre><a href="http://www.ubio.org/services/mapper/index2.php" target="_blank">http://www.ubio.org/services/mapper/index2.php</a></pre><pre> </pre><pre>All this ubio talk makes me think we were on to something.  Worth a thought about adopting the new stnadrds and tools and making it really smooth.</pre>
<pre> </pre><pre>DR</pre><pre> </pre><pre> </pre><pre>On 20 May 2011, at 04:46, Steve Baskauf wrote:</pre><pre> </pre><pre>  </pre><pre>    </pre><blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><pre>I have generated a csv spreadsheet of about 39 000 plant names for the </pre>
<pre>U.S. which has the ITIS TSNIDs for the names in a column.  I would like </pre><pre>to have the uBio Namebank IDs in another column of the table.  I have </pre><pre>been looking them up on the uBio website by typing in the names as I </pre>
<pre>need to know the IDs, but after doing about 300 of them, I&#39;m getting </pre><pre>tired of it.  Does anybody have a clever idea of a way to get the other </pre><pre>38 000 Namebank IDs without looking them up.  I&#39;m sure that it would be </pre>
<pre>possible to find this out because uBio gets names from ITIS.  However, I </pre><pre>haven&#39;t seen any clues about how to do it in an automated fashion.  I&#39;m </pre><pre>guessing that there might be some way to use the uBio web services, but </pre>
<pre>if so, it isn&#39;t obvious and I probably don&#39;t have the skills to carry it </pre><pre>out anyway. </pre><pre> </pre><pre>Any ideas?</pre><pre>Steve</pre><pre> </pre><pre>-- </pre><pre>Steven J. Baskauf, Ph.D., Senior Lecturer</pre>
<pre>Vanderbilt University Dept. of Biological Sciences</pre><pre> </pre><pre>postal mail address:</pre><pre>VU Station B 351634</pre><pre>Nashville, TN  37235-1634,  U.S.A.</pre><pre> </pre><pre>delivery address:</pre><pre>
2125 Stevenson Center</pre><pre>1161 21st Ave., S.</pre><pre>Nashville, TN 37235</pre><pre> </pre><pre>office: 2128 Stevenson Center</pre><pre>phone: <a href="tel:%28615%29%20343-4582" target="_blank">(615) 343-4582</a>,  fax: <a href="tel:%28615%29%20343-6707" target="_blank">(615) 343-6707</a></pre>
<pre><a href="http://bioimages.vanderbilt.edu" target="_blank">http://bioimages.vanderbilt.edu</a></pre><pre> </pre><pre>_______________________________________________</pre><pre>tdwg-content mailing list</pre><pre><a href="mailto:tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a></pre>
<pre><a href="http://lists.tdwg.org/mailman/listinfo/tdwg-content" target="_blank">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a></pre><pre> </pre><pre>    </pre><pre>      </pre></blockquote><pre>.</pre><pre> </pre>
<pre>  </pre><pre>    </pre></blockquote><pre>  </pre><p class="MsoNormal"><br><br></p><pre>-- </pre><pre>Steven J. Baskauf, Ph.D., Senior Lecturer</pre><pre>Vanderbilt University Dept. of Biological Sciences</pre><pre> </pre>
<pre>postal mail address:</pre><pre>VU Station B 351634</pre><pre>Nashville, TN  37235-1634,  U.S.A.</pre><pre> </pre><pre>delivery address:</pre><pre>2125 Stevenson Center</pre><pre>1161 21st Ave., S.</pre><pre>Nashville, TN 37235</pre>
<pre> </pre><pre>office: 2128 Stevenson Center</pre><pre>phone: <a href="tel:%28615%29%20343-4582" target="_blank">(615) 343-4582</a>,  fax: <a href="tel:%28615%29%20343-6707" target="_blank">(615) 343-6707</a></pre><pre>
<a href="http://bioimages.vanderbilt.edu" target="_blank">http://bioimages.vanderbilt.edu</a></pre></div></div></div><p class="MsoNormal" style="margin-bottom:12.0pt"><br>_______________________________________________<br>
tdwg-content mailing list<br><a href="mailto:tdwg-content@lists.tdwg.org" target="_blank">tdwg-content@lists.tdwg.org</a><br><a href="http://lists.tdwg.org/mailman/listinfo/tdwg-content" target="_blank">http://lists.tdwg.org/mailman/listinfo/tdwg-content</a></p>
</div><p class="MsoNormal"><br><br clear="all"><br>-- <br>------------------------------------------------------------------------------------<br>Pete DeVries<br>Department of Entomology<br>University of Wisconsin - Madison<br>
445 Russell Laboratories<br>1630 Linden Drive<br>Madison, WI 53706<br>Email: <a href="mailto:pdevries@wisc.edu" target="_blank">pdevries@wisc.edu</a><br><a href="http://www.taxonconcept.org/" target="_blank">TaxonConcept</a>  &amp;  <a href="http://about.geospecies.org/" target="_blank">GeoSpecies</a> Knowledge Bases<br>
A Semantic Web, <a href="http://linkeddata.org/" target="_blank">Linked Open Data</a>  Project<br>--------------------------------------------------------------------------------------</p></div></div></div></div></div></blockquote>
</div><br><br clear="all"><br>-- <br>







------------------------------------------------------------------------------------<br>Pete DeVries<br>Department of Entomology<br>University of Wisconsin - Madison<br>445 Russell Laboratories<br>1630 Linden Drive<br>Madison, WI 53706<br>
Email: <a href="mailto:pdevries@wisc.edu" target="_blank">pdevries@wisc.edu</a><br><a href="http://www.taxonconcept.org/" target="_blank">TaxonConcept</a>  &amp;  <a href="http://about.geospecies.org/" target="_blank">GeoSpecies</a> Knowledge Bases<br>
A Semantic Web, <a href="http://linkeddata.org/" target="_blank">Linked Open Data</a>  Project<br>--------------------------------------------------------------------------------------<br>
</div>