Closed seltmann closed 6 months ago
@seltmann was just looking at adding subspecies to DiscoverLife taxonomic alignment.
curl --insecure "https://www.discoverlife.org/mp/20q?search=Bombus+vosnesenskii&guide=1&flags=HAS:"\
tee Bombus+vosnesenskii.html
yielded attached file. Bombus+vosnesenskii.html.txt
and the subgenus appears present -
cat Bombus+vosnesenskii.html | grep Pyro
<br><small>Subgenus: <a href="/mp/20p?see=Pyrobombus&name=Bombus&guide=1&flags=HAS:subgenus:"><i>Pyrobombus</i></a></small>
This would mean that I'd have to ask discoverlife 20k times for their separate species pages. Is there a more efficient way to get this?
also, note that DiscoverLife keeps associations with specimen records that appear to contain more information (e.g., associatedTaxa) that those shared with GBIF, or some not shared at all. Is this a known issue?
For instance, https://www.discoverlife.org/mp/20l?id=BBSL154071;BBSL154070;BBSL__BBSLID87119 (see attached screenshot) contains associatedTaxa (i.e. Arnica sp.
) information.
However, on the associated GBIF occurrence page at https://www.gbif.org/occurrence/658974260 (see attached screenshot) no such associatedTaxa can be found.
duplicate of #161 .
Discoverlife catalog does not include subgenera because they are located on a different webpage than the indexed catalog.
From the online version of the checklist found here https://www.discoverlife.org/mp/20q?act=x_checklist&guide=Apoidea_species&flags=HAS:
Subgenus is only located on a different webpage. So for Bombus vosnesenskii Radoszkowski, 1862 should equal Bombus (Pyrobombus) vosnesenskii Radoszkowski, 1862