A little hypothetical scenario:
An academic institution is setting up a bioinformatics support group. This group will service many investigators with many levels of expertise and interests, though the focus will be on genomics data analysis in human on both microarray and sequencing technologies. Since this resource will be quite limited, there is a need to gather highly relevant information about potential projects. Assuming that the original submission is going to be electronic, what are the most relevant pieces of information to gather. Examples might include:
- Biological questions to be answered
- Technologies employed
- Experimental design including sample descriptions and number of replicates
- Proposed bioinformatics plan (if one exists)
- Previous and current bioinformatics expertise involved
- Other related datasets (either public or local)
- References to similar studies and background
- Computational resources available (storage, commercial or open source software, workstations)
- Type of project--pilot, followup to previous study, full publishable dataset, other
Are there examples of such details available? I am aware of MIAME and similar standards, but what I am seeking is a more "operational" set of descriptors that will allow reasonably facile characterization of projects.
Thanks, Chris. You are preaching to the converted as far as the first two points. Part of the goal of providing a "support" component is a recognition that there are projects that lend themselves to being "serviced" and that streamlining these projects as much as possible leads to more opportunities to get at deeper questions. I, like you, though, would like to think of even these "service" projects as collaborations and not simply service delivery.
Thanks for the links. I think the ISA standards site is: http://isa-tools.org/ (with a "-").
You are right, edited now