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

Add ENA ACC map to Submission Registry #2

Open
ikostadi opened this issue Sep 3, 2015 · 3 comments
Open

Add ENA ACC map to Submission Registry #2

ikostadi opened this issue Sep 3, 2015 · 3 comments

Comments

@ikostadi
Copy link
Member

ikostadi commented Sep 3, 2015

All ENA objects receive a unique PID (accession), but are also connected to several others (e.g. an experiment is linked to a study and to a sample). As a user, I want to see all related ENA accessions.
Specific use cases:

  1. Given the accession of a sample, show me the accession of the study it belongs to.
  2. Given the accession of an experiment, show me the accessions of all associated samples.
  3. Given the accession of a study, show me the accessions of all associated objects (samples, experiments,runs).
@Marfroem
Copy link
Contributor

I have a solution for all three cases, but need it indded case 1 and 2?

and what ist, in the ENA widget the experiment?

@ikostadi
Copy link
Member Author

I have a solution for all three cases, but need it indded case 1 and 2?

That depends on how curators (and users) are going to browse through the research objects, but generally I would say yes. We can cover this in the telco tomorrow.

The more general definitions behind the concrete use cases above are as follows:

  • get-direct-parent
  • get-top-parent
  • get-direct-children
  • get-all-children

Is this what you have in mind (and code)?

and what ist, in the ENA widget the experiment?

The Experiment object contains the information about the sequencing procedure. You can look up the details here: http://www.ebi.ac.uk/ena/submit/metadata-model

@Marfroem
Copy link
Contributor

ok,
every sample, experiment, study is an own Research Object. We need a Parent Research Object for all Research Objects of a Submission. All RO's have a conection over this parent. And so I find the target objects and their accessions

1, 2, 3 are done and will upload with the next update to the dev server (today)

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

2 participants