You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Given the accession of a sample, show me the accession of the study it belongs to.
Given the accession of an experiment, show me the accessions of all associated samples.
Given the accession of a study, show me the accessions of all associated objects (samples, experiments,runs).
The text was updated successfully, but these errors were encountered:
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:
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)
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:
The text was updated successfully, but these errors were encountered: