FedorSteeman
commented
10 months ago We mapped the "New taxon flag" to the taxon.YesNo1 field in Specify and re-captioned it as such. However, it turned out that the original purpose of the field was to indicate whether a taxon is extinct and a limited amount of taxa across all NHMD collections seem to have ticked this off. There are 546 in total and are the following: SpTaxaMarkedExtinct.csv
The following disciplines are affected:
- Entomology
- Vertebrate Paleontology
- Danekrae
There are 2 possible solutions for this:
- [x] With relevant staff's permission repurpose the "extinct" flag as "new taxon"
- [x] Choose another field and edit the taxon form to show that alongside the "extinct" flag
The problem is that it's unclear how the taxon form can be changed, if at all. If not, then we we're forced to use solution 1. I have asked the question on Discourse here: https://discourse.specifysoftware.org/t/edit-taxon-entry-form/1402
The specimens for Entomology were rove beetles included in amber. Sree was OK with me repurposing it, but recommends I asked Alexey first. I will ask Bent Lindow and Laura Pavesi about their respective discplines.
At the moment, the New Taxon flag in the taxon records in Specify uses a different field for different collections/institutions. It would be helpful if we were consistent.
Right now, to facilitate digitisation, we need this field to be visible (searchable and so collection managers and curators can deselect after taxon has been checked) for NHMD Vascular Plants, NHMD Entomology and NHMA Entomology.
For NHMD entomology, the GREL script is currently being mapped to extinct taxon flag.