We need to decide on what tags the target loader is supposed to create. Currently there are 4 categories of tags (Sites, Series, Forum and Other) and the target loader is assigning a single tag of type Site to a site_observation that looks like this: A/144,A/45,B/191. This correspond to the first 3 residues in the site.
We need to decide on a more complete handling of tags.
do we need tags for canonical site and conformer site (currently I think it's just conformer site that is used).
do we want tags for crystal form (and a new tag category).
do we want tags for macromolecular assembly (and a new tag category).
How do we visually distinguish these different tags. Should the type be used as a prefix e.g. conf_site:A/144,A/45,B/191.
Is the user able for rename a site e.g. change it to active site. Probably out of scope for this discussion, as it involves front end work and policy for who can do this.
Frontend needs to be changed to handle tag categories dynamically (it was decided waaay back that tag categories are going to be hardcoded in the backend and frontend)
We need to decide on what tags the target loader is supposed to create. Currently there are 4 categories of tags (Sites, Series, Forum and Other) and the target loader is assigning a single tag of type Site to a site_observation that looks like this:
A/144,A/45,B/191
. This correspond to the first 3 residues in the site.We need to decide on a more complete handling of tags.
conf_site:A/144,A/45,B/191
.active site
. Probably out of scope for this discussion, as it involves front end work and policy for who can do this.