Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Help biologists to double check their classification changes #575

Open
SamuelNicaise opened this issue Jan 10, 2023 · 0 comments
Open

Help biologists to double check their classification changes #575

SamuelNicaise opened this issue Jan 10, 2023 · 0 comments
Assignees
Labels
enhancement New feature or request high-priority

Comments

@SamuelNicaise
Copy link
Collaborator

When changing a variant's classification, our biologists systematically add a "to_validate" tag so a second biologist can double-check the change, using a filter on that tag.

However, if the first biologist forgets to add the tag, they risk losing track of it before double checking, especially if it is a "-1" classification that removes the variant from their other filters.

I suggested using the history, but a much simpler solution for users would be:

  • Add an option in settings that activate the following behavior:
    • When a classification is edited, automatically add a custom tag
@antonylebechec antonylebechec added the enhancement New feature or request label May 10, 2023
SamuelNicaise added a commit that referenced this issue Nov 15, 2023
…e check tag and fix concurrency issues

- Add the possibility to automatically add a chosen tag to variants/samples/genotypes after a classification change
- Settings to (de)activate the behavior and select the tags
- Default config change
- Fix concurrency issues: a user could accidentally erase someone else's changes without the warning appearing in some cases
- Improve and uniformize said warning
- Add message while samples are loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request high-priority
Projects
None yet
Development

No branches or pull requests

3 participants