Skip to content
This repository has been archived by the owner on Jul 18, 2022. It is now read-only.

/biosamples response is missing a datasetID field #67

Closed
Tom-Shorter opened this issue May 7, 2021 · 5 comments
Closed

/biosamples response is missing a datasetID field #67

Tom-Shorter opened this issue May 7, 2021 · 5 comments
Assignees

Comments

@Tom-Shorter
Copy link

There is currently no way to identify which dataset an individual biosample came from, /individuals and /g_variants both have a datasetID field within the response object for individual results so it seems an oversight that it is missing from /biosamples.

@mbaudis
Copy link
Member

mbaudis commented May 7, 2021

That is probably just an oversight, but in the end related to #63. So one would wrap datasetAlleleResponses for different datasets, but for the biosamples or individuals then indicate their datasetId per item? Then we need this for the VariantInSample and any other object which can end up in response.results, too.

Or responses are always for a single dataset, with the possible exception of a generic response as in the old days.

Or in response.results are always lists of datasetResponse objects.

@mbaudis
Copy link
Member

mbaudis commented May 7, 2021

... also, to have a datasetId in a given biosample, individual, variantInSample response is ugly; it is NOT part of the native object schema and has to be overloaded for the response. So if a /biosamples response contains data from multiple datasets those should be wrapped in dataset specific objects.

@jrambla
Copy link
Collaborator

jrambla commented May 8, 2021

The rationale behind the model is: "we have two types of Beacons: evidence/knowledgeBase and Case/individuals".
The first one is represented by Dataset>Variant, the second one by Dataset>Individual (extended later with Cohort>Individual.
That is the reason that no other entity is having a DatasetId on it.
Michael's case is where the Beacon is made by samples from cell cultures (let's say) and it doesn't fit to one or the other.
As per our initial exploration that doesn't seem to be a "majority" case, and I have no feeling of how many other case we'll find.
Hence, we suggested Michael to extract the attributes from the individual from the samples and create these "virtual" individuals. Which I believe could make sense anyway, as thus you can relate samples from the same individual and such.
datasetAlleleResponse should be deprecated if it is not already.

@mbaudis
Copy link
Member

mbaudis commented May 9, 2021

@jrambla That's not what is meant here? This was about identification of a biosample <-> dataset relation.

In any case, it gets a bit confusing; but IMO this should be resolved through #68 (which I see as the most logical solution, until @jrambla tells me why this wouldn't work ...).

@sdelatorrep
Copy link
Contributor

Hi @Tom-Shorter. I think this is solved with the resultSet wrapper, right? If not, please, reopen this issue. Thanks!

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

No branches or pull requests

4 participants