Show provenance for annotations in web app #1095
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a proof of concept showing that we can propagate information about where a field displayed on the Bioregistry came from. This is important because the Bioregistry imports data from other registries, so it's useful to know where an annotation (e.g., the name associated with a prefix) came from, and under what license it's being reused.
For simple fields like name and description, this PoC shows that we can update the functions that get the data to return extra information. However, for more complex fields, it might be better to have a wrapper data structure (e.g., a 2-tuple, a dataclass) that incorporates the source information and the actual data