Open mdoering opened 2 years ago
My favorite would be the last as it keeps consistency with the COL checklist and its implemented hierarchy. @thomasstjerne we might want to create a dedicated, tabular estimate page for this to be managed best. But you can manage estimates already in the assembly tree:
Current gaps in COL should be documented in the portal to raise awareness. It helps is finding people and datasets to fill these gaps, but also helps in justifying the current state and respond to user feedback such as "why is species X not in COL?".
There are several options to manage a gap list: