Regression for BOLD:ADC2696

[ahahn-gbif]

More a question than a bug: in most other cases with BOLD mappings for order=Diptera, I see the previously applied taxon match switch to a BOLD id match - not so in this case though, where a previous BOLD match now switches to taxon match for the accepted name. I cannot identify what makes this case different from all the other ones(?)

{
  "count": 3451,
  "verbatim_kingdom": "null",
  "verbatim_phylum": "Arthropoda",
  "verbatim_class": "Insecta",
  "verbatim_order": "Diptera",
  "verbatim_family": "Chironomidae",
  "verbatim_genus": "null",
  "verbatim_species": "null",
  "verbatim_infra": "null",
  "verbatim_rank": "null",
  "verbatim_verbatimRank": "null",
  "verbatim_scientificName": "Bold:adc2696",
  "verbatim_generic": "null",
  "verbatim_author": "null",
  "current_kingdom": "Animalia",
  "current_phylum": "Arthropoda",
  "current_class": "Insecta",
  "current_order": "Diptera",
  "current_family": "Chironomidae",
  "current_genus": "null",
  "current_subGenus": "null",
  "current_species": "null",
  "current_scientificName": "BOLD:ADC2696",
  "current_acceptedScientificName": "BOLD:ADC2696",
  "current_kingdomKey": 1,
  "current_phylumKey": 54,
  "current_classKey": 216,
  "current_orderKey": 811,
  "current_familyKey": 3343,
  "current_genusKey": "null",
  "current_subGenusKey": "null",
  "current_speciesKey": "null",
  "current_taxonKey": 10051518,
  "current_acceptedTaxonKey": 10051518,
  "proposed_kingdom": "Animalia",
  "proposed_phylum": "Arthropoda",
  "proposed_class": "Insecta",
  "proposed_order": "Diptera",
  "proposed_family": "Chironomidae",
  "proposed_genus": "null",
  "proposed_subGenus": "null",
  "proposed_species": "null",
  "proposed_scientificName": "Chironomidae",
  "proposed_acceptedScientificName": "Chironomidae",
  "proposed_kingdomKey": 1,
  "proposed_phylumKey": 54,
  "proposed_classKey": 216,
  "proposed_orderKey": 811,
  "proposed_familyKey": 3343,
  "proposed_genusKey": "null",
  "proposed_subGenusKey": "null",
  "proposed_speciesKey": "null",
  "proposed_taxonKey": 3343,
  "proposed_acceptedTaxonKey14932": 3343,
  "_key": 4234,
  "changes": {
    "scientificName": true,
    "acceptedScientificName": true,
    "taxonKey": true
  },
  "reviewed": false
}

[mdoering]

interesting case. BOLD:ADC2696 is not part of the new nub, although it appears in the latest iBOL occurrence dataset:
https://www.gbif.org/occurrence/search?dataset_key=040c5662-da76-4782-a48e-cdea1892d14c&taxon_key=10051518

It is not part of the BOLD BIN number checklist though which we include in the backbone.
Maybe @thomasstjerne has an idea how this can happen? https://www.gbif.org/species/search?q=BOLD:ADC2696&dataset_key=4cec8fef-f129-4966-89b7-4f8439aba058&qField=SCIENTIFIC&advanced=1