Closed mdoering closed 5 months ago
Issues are kept with verbatim records. As projects and its releases don't have verbatim CSV data, there is another verbatimSource entity which tracks both the source identifiers and also the issues.
e.g. https://api.dev.checklistbank.org/dataset/271349/nameusage/~17Bu/source
How can we show issues for both projects and external data best and consistently? If we should the issues on a separate page like the verbatim page we should at least highlight the fact that there are some issues on the main name page.
Seeing issues is important to review the xcol
On usage pages in a release there are no issues shown and there is no way to see them anywhere. It is important to see the issues somewhere. The verbatim link from the issue page should not exist for projects and releases