<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I try to implement a lazy-loading taxonomy tree (as a demo for a open source javascript tree plugin). <div class=""><br class=""></div><div class="">See here for an example:</div><div class=""><a href="http://rawgit.com/mar10/fancytree/master/demo/taxonomy-browser/index.html#key=7348228" class="">http://rawgit.com/mar10/fancytree/master/demo/taxonomy-browser/index.html#key=7348228</a></div><div class=""><br class=""><div class="">What JSON API should use to get the top level nodes (i.e. Kingdoms)?<br class="">Currently I call <br class=""> <a href="http://api.gbif.org/v1/species/search?rank=kingdom" class="">http://api.gbif.org/v1/species/search?rank=kingdom</a><br class="">but this returns much more than the ~7 entries I expect (Animalia, Plantae, Fungi, …)<br class=""><br class="">I seem to get reasonable results, if I only display nodes with key == nubKey.</div><div class=""><br class=""></div><div class="">But the search results retrieved by `species/search?q=homo sapiens` returns multiple hits, and some of them have keys different from nubKey.</div><div class="">Those matches seem to be descendants of an `Animals` kingdom that also has nubKey != key.<br class=""><div class=""><br class=""></div><div class="">I guess my mental model of the data structure is too naïve:<br class=""></div><div class="">- why are there different ‚Animals‘ kingdoms with different keys but identical nubKey?</div><div class="">- does it make sense at all to display a tree (with only one ‚animals‘ node)?</div><div class="">- when I restrict the search results to entries that have a kingdom with key == nubKey, what will the user miss?</div><div class=""><br class=""></div>Thanks<br class="">Martin Wendt</div></div></body></html>