You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've added some steps; it's better to deactivate the GB from its ViewEntry (VE). So the user must first look at the GB ViewList (VL), then click on one, see its details, then click "Options", then "Remove genome build", and then get the form.
The form itself can then just contain a warning (are you sure? blabla) and a password field.
When not all variants are also mapped on another genome build, block removal, not just a warning.
Deleting the entry is probably best done by first deleting the entry from the GB table. If done in any other order, the system will be broken for a short time (or a long time, if something goes wrong).
Add button to the GB ViewEntry (VE) to deactivate the genome build (like done on other VEs)
Show form to deactive GB (
/genome_builds/hg19?remove
)Give an error and block removal when:
Delete entry if all variants are safely mapped on another genome build
Related to #550
The text was updated successfully, but these errors were encountered: