Document current gaps

[mdoering]

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:

1. Maintain a static page in the portal with a table of all gaps, very broadly organised by the COL hierarchy.
2. Maintain a new TextTree dataset in github with species estimates given if known
3. Manage species estimates in the COL project and make sure gap areas are existing in the hierarchy, e.g. superfamilies are included

[mdoering]

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:

[mdoering]

We start using https://www.checklistbank.org/about/contribute to document the broad gaps where we seek contributions

[mdoering]

@dhobern I have exported all genera for which we do not have any species and grouped them by their higher parent, mostly the family, to see where COL is weak: empty-families.txt