So why Bolitoglossa sombra in TreeBASE?
Well, Googling finds Darrel Frost's Amphibian Species of the World page on this species, which lists the name "Bolitoglossa sombra Hanken, Wake, and Savage, 2005, Copeia, 2005: 234.". Googling again finds a PDF of this paper linked to from David Wake's web site, and by Googling on "Copeia" and "BioOne" I get a DOI to the paper (doi:10.1643/CH-04-083R1.
Reading the paper doesn't make me any the wiser1, until I get the supplementary information for Mueller et al. and discover that Bolitoglossa sp. nov. is specimen MVZ 225875. Searching the PDF of Hanken et al., I find (p. 236)
Three juveniles (MVZ 225875–76, 225878) were generally black but had some obscure whitish patches, which were most evident near the tail base.
So, MVZ 225875 is Bolitoglossa sombra. I confirm this by doing a DiGIR lookup on MVZ 225875 using a script I wrote (doing this is an absolute pain because of the way DiGIR is constructed, and because if doesn't provide resolvable identifiers for specimens). You can view the specimen record directly at MVZ.
1Doh! If I'd read the paper properly, MVZ 225875 is listed as one of the paratypes of Bolitoglossa sombra.
What's your point?
My point is this is a lot of tedium to go through to link up the following items:
- TreeBASE taxon
- NCBI taxonomic record
- NCBI genomic record
- Publication of scientific name
- Specimen sequenced
Each of these records exist and have identifiers (of varying utility), and in the case of all but the TreeBASE record, there are ways to retrieve metadata about the record in XML format. Yet, these records exist in isolation and haven't been linked, which means I cannot easily connect them just by looking at each database. For example, looking at NCBI's record for Bolitoglossa n. sp. RLM-2004, I have no idea that this amphibian has a phylogeny in TreeBASE, or has been described in the scientific literature and is now called Bolitoglossa sombra.
This is just crazy, and is not that hard to fix if we have globally unique identifiers for digital records that are resolvable, and ways to harvest metadata about those records. For more rants and examples on this theme see SemAnt.