yroskov
commented
1 year ago I have mentioned undetected "orphan decisions" as a problem earlier: CoL may have a set of decisions which are not actual after GSD provider resolved the issue in a new version of its dataset. You gave an example of "orphan decisions" above.
We need to find a solution to this problem. Perhaps, TASKS reports should have preceding check for names with Name Status decisions, and include names with decision to change status but without its contra-partner in the list of broken decisions.
I saw in logs that there are update decisions to make some names in WCVP ambiguous synonyms. For example Angelica major Lag.
This likely is still based on the older version 10 of WCVP. In the current v11 at least there are 2 species with different authors and A. major Lag. being accepted: https://www.checklistbank.org/dataset/2232/names?facet=rank&facet=issue&facet=status&facet=nomStatus&facet=nameType&facet=field&facet=authorship&facet=authorshipYear&facet=extinct&facet=environment&facet=origin&limit=50&offset=0&q=Angelica%20major&sortBy=taxonomic
The name ids in WCVP are the same though, so the decisions are not broken and still apply - wrongly now:
@yroskov do we have a procedure in place that would detect such changes and remove the now superfluous decisions? Or would these go unnoticed as they are not broken? The syncs do not allow status changes from accepted to synonym and vice versa, so for the accepted species at least nothing seriously happens. But the synonym would be changed to ambiguous indeed still.