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

Selective case update #4808

Open
dnil opened this issue Sep 2, 2024 · 0 comments
Open

Selective case update #4808

dnil opened this issue Sep 2, 2024 · 0 comments

Comments

@dnil
Copy link
Collaborator

dnil commented Sep 2, 2024

From discussion with @rannick:

Is your feature request related to a problem in the current program to new available techology or software? Please describe and add links/citations if appropriate.
When cases are updated, either a long time is spent loading, or if extra keys are given on CLI to samples or cases, this is only stored in the scout db, not in e.g. housekeeper for future updates. This is made apparent by the current effort to update DNA cases with tomte RNA data.

Describe the solution you'd like
Instead of the current model with either cleanly loading everything from config, or adding extra files/keys, parse an update config and only adjust/load for values that actually changed.

At the same time as adding this, deprecate a bunch of odd separate and partially non-functional options on scout update case - e.g. all the vcf options.

Describe alternatives you've considered
Explicit field tags in the config, like update on the row. Checksums on each data file, reloading on update only if the checksum has changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant