AdamWoodsAM
commented
3 years ago @cdausmus I have come across the same issues and the problem is pretty likely related to same DwC fields and the classifiers not working. Would be good to get this one sorted.
cdausmus
There is an issue with templates that have fields with the same field type and different classifier, see below:
We've been testing the State Herbarium of South Australia 1 template (https://digivol-test.ala.org.au/template/preview/1554706), and there are some problems with the phenology checkboxes. When one or more are checked by a transcriber and the task is saved, all the phenology options become checked for that task. We’ve also noticed that even if none are checked by the transcriber (ie no evidence of flowers or fruit on the specimen), all become checked after the task is saved. We have experimented with adding a couple of additional checkboxes based on different elements (because we noticed the original set were all based on one), and also by varying the type of one of the original set. It appears that all of the original phenology fields become set to ‘true’ whenever a task is saved, regardless of what the transcriber has done. There’s nothing obvious in the field edit screen like a default value. It may be a setting(s)/background script that we can’t see.