Add taxon IDs to the model

[thomasstjerne]

It would be really useful to not only have the taxon names but also the IDs in the data packages.

Please add the following fields that are also available through the current v4 API:

phylum_taxID, class_taxID, order_taxID, family_taxID, subfamily_taxID, genus_taxID, species_taxID, subspecies_taxID

[DNAdiversity]

That's not a bad idea but it might become excessive. I believe it would be better to have a separate registry of the full taxonomy with ids. Would that address needs?

[rdmpage]

Having a separate file with the complete BOLD taxonomy and associated taxonomy ids would be very useful to those of us building on top of the data packages. It would likely also simplify GBIF's parsing of BOLD data (at present they try and infer the BOLD taxonomy from the files returned by the previous API).

Perhaps a solution would be to have a separate taxonomy file in the package, but also include the taxonomy id of the identification assigned to each barcode in the main file. That way there is no ambiguity when linking the identification to the larger taxonomy.

[DNAdiversity]

I put a plan in place to transition BOLD taxonomy to COL. The transition should be completed in the next couple of months. I believe it would best to make the taxonomy registry broadly available at that point. Note that there is already a taxonomy id (TAXID) in the BCDM definition and data packages as a result.

[thomasstjerne]

Happy to see some thoughts on this!

Yes, a full export of the BOLD taxonomy would definitely be preferable to having to assemble it manually.
I agree with @rdmpage that including a separate file in the data package would be a good solution.

However, an even better approach might be a scheduled export directly to ChecklistBank in CoLDP format. This would reduce the workload on the GBIF side, as any dataset in ChecklistBank can be used as a source for compiling the Catalogue of Life. It would also make the taxonomy easily accessible via the ChecklistBank API, which I believe would benefit many users.