This repository has been archived by the owner on Jan 24, 2018. It is now read-only.
Make referencesets optional when possible #1596
Open
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.
The repo manager requires that a reference set is provided when it is really only a metadata item from the perspective of the variants, features, and RNA. For this reason, we can make it an optional flag at the repo manager.
I am able to add a variant set using just:
python repo_dev.py add-variantset ga4gh-example-data/registry.db brca1 ga4gh-example-data/brca1_1kgPhase3_variants.vcf.gz
Allow nullity for referencesetid field in modelsSafely access the referenceset name in a few placesWe should strongly consider a PR at the schemas that removes the
referenceId
as a required field of a reads search, as that is the only endpoint that can't implement this feature.Works to close #1528, thanks @ejacox for helping us keep focus on usability features.