uec / Issue.Tracker

Automatically exported from code.google.com/p/usc-epigenome-center
0 stars 0 forks source link

genelogics lims API #798

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
to list flowcells:

http://usc.claritylims.com:8080/api/v2/containers?type=Flowcell

from there, you can drill down as usual to find flowcell, lane, sample, project 
etc.

refer to the V2 rest api document

Original issue reported on code.google.com by zack...@gmail.com on 20 Aug 2014 at 9:44

GoogleCodeExporter commented 8 years ago
Question about parsing APIs

if I follow this path:

containers(list of flowcell_serials)->placement(list of lane 
numbers)->artifacts (list of samples) -> sample (sample info) -> project 
(project info)

then technician, instrument and date run info will be missing, because they are 
listed in processes. I can get to processes through parent-process in artifacts 
but this is a redundant, because this info is the same for every artifact.

Can you suggest a better way of parsing technician, instrument and date run 
info? 
Or we don't need to parse it at all?

Original comment by natalia....@gmail.com on 29 Aug 2014 at 7:41

GoogleCodeExporter commented 8 years ago
I also cant find where to parse the "organism" field

Original comment by natalia....@gmail.com on 29 Aug 2014 at 9:50

GoogleCodeExporter commented 8 years ago
Ok, I found the "organism" field in sample udf's. 

Where can I get a description of a genologics custom configuration with the 
list of fields that were configured or created?

Original comment by natalia....@gmail.com on 30 Aug 2014 at 12:37