search

uec / Issue.Tracker

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

separate actual seqeunce runs from test anzalyses and merges to keep interface clean #680

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Is this even possible?  Would definitely help me out

Original issue reported on code.google.com by cmnico...@gmail.com on 27 Feb 2014 at 7:44

GoogleCodeExporter commented 8 years ago 
I guess clean is a relative term. removing stuff by default for one user isn't 
necessarily good for another and vice versa. lets discuss the happy medium.

But yes, I think this would be a good discussion, and may become clear as we 
move forward these next few months.

What is the long-term role of ECDP?
Who's needs should it meet: Sequencing Core? Collaborators? a resource for the 
entire Cancer Center? All of the above?  
Where to spend developer time (= $$), who's covering that expense (this will 
probably determine whose needs are a priority)
displaying 3rd party data is a growing need, it may even outgrow in-house data, 
how to handle this case?
Not everyone can be pleased, how can we find the optimal solution that is best 
for most.

Original comment by zack...@gmail.com on 27 Feb 2014 at 8:59

GoogleCodeExporter commented 8 years ago 
as we discuss/plan etc lets move it off the public issue tracker to something 
more private

Original comment by zack...@gmail.com on 27 Feb 2014 at 9:07