jlegind
commented
1 year ago Two major changes in the Digi App
- 'Multi specimen container' radio buttons were added to differentiate between Single-Specimen-Object, Multi-Object-Specimens, and Multi-Specimen-Objects. 1
- Alternative NHMA taxonomy was requested where the primary taxonomic identifier is not the Latin name but the NHMA alternative taxonomic ID, as submitted to us in an e-mail containing a file = Aarhus_Dk_lepidoptera2013.xlsx
Instead of using the taxonomic name field to look up names, a digitizer logged in under NHMA Entomology will be presented with a new field "Taxonomic ID" where the alternative taxonomic identifier can be inputted. A valid ID will populate the Taxonomic name field with the taxonomic name from the app taxonomic table.
1
SSO= A single specimen in/on one container
MOS = One specimen taking up several containers
MSO = One container containing multiple specimens
Template for isues/tickets in DigiApp
What is the issue ?
There is a need for having an overview of updates and development from one app state to the next step of evolution.
Detailed description of the issue.
This will give us a better idea of new undesired behavior from one version to the next. It will be a tool for documenting progress and for debugging.
Why is it needed/relevant ?
Tracking this kind of change could give us a shortcut to the section of the code where the problem originates.
Estimate level of effort required.
Easy-ish
What is the expected acceptable result.
A shared document that states the significant changes from version to version of the codebase.
What could be the challenges ?
Determining which characteristic of the code poses a potential risk, in that bugs might actually be unrelated to the new features documented.