Metadata such as lat, lon, time, volume sampled etc. are critical for science. In a workflow, they should be editable in one place and one place only, otherwise, keeping them in sync becomes a nightmare.
It appears that, often, such metadata is reimported from the source files, hence erasing changes potentially made in EcoTaxa/Part (and being the source of data curation nightmares). If this is indeed the workflow chosen, where the original files are considered to be the source of truth, then metadata that is imported should not be editable anywhere in EcoTaxa/Part. This makes the life of the operators more difficult though.
A middle ground may be to not make it editable from the UI but make it editable from the API, either directly or by re-importing a .tsv file (that may contain only the changed lines+columns).
The point of this issue is to debate the pros and cons and reach a solution.
Metadata such as lat, lon, time, volume sampled etc. are critical for science. In a workflow, they should be editable in one place and one place only, otherwise, keeping them in sync becomes a nightmare.
It appears that, often, such metadata is reimported from the source files, hence erasing changes potentially made in EcoTaxa/Part (and being the source of data curation nightmares). If this is indeed the workflow chosen, where the original files are considered to be the source of truth, then metadata that is imported should not be editable anywhere in EcoTaxa/Part. This makes the life of the operators more difficult though.
A middle ground may be to not make it editable from the UI but make it editable from the API, either directly or by re-importing a .tsv file (that may contain only the changed lines+columns).
The point of this issue is to debate the pros and cons and reach a solution.