11# Project Selection Process
22
33The project milestones are set annually by the team under the stewardship of the NIH
4- programmatic staff and with the guidance of the project's
4+ programmatic staff and with the guidance of the project's
55[ Scientific Steering Group] ( ../governance )
66
77We have adopted the following general criteria for selecting and accepting new projects
88to be included in the Resource.
99
10101 . ** Open Precursor Projects**
1111
12- At least one open-source DataJoint-based precursor project must exist for any new
13- experiment modality to be accepted for support as part of the Resource. The
14- precursor project team must be open to interviews to describe in detail their
15- process for the experiment workflow, tools, and interfaces.
12+ At least one open-source DataJoint-based Precursor Project must exist for any new
13+ experiment modality to be accepted for support as part of the Resource. The Precursor
14+ Project team must be open to interviews to describe in detail their process for the
15+ experiment workflow, tools, and interfaces.
1616
17- The precursor projects must provide sample data for testing during development and
18- for tutorials. The precursor projects will be acknowledged in the development of the
17+ The Precursor Projects must provide sample data for testing during development and
18+ for tutorials. The Precursor Projects will be acknowledged in the development of the
1919 component.
2020
2121 ** Rationale:** This Resource does not aim to develop fundamentally new solutions for
22- neurophysiology data acquisition and analysis. Rather it seeks to systematize and
23- disseminate existing open-source tools proven in leading research projects.
22+ neurophysiology data acquisition and analysis. Rather it seeks to systematize and
23+ disseminate existing open-source tools proven in leading research projects.
2424
25251 . ** Impact**
2626
@@ -30,7 +30,7 @@ to be included in the Resource.
30301 . ** Sustainability**
3131
3232 For all third-party tools or resources included in the proposed component, their
33- long-term maintenance roadmap must be established. When possible, we will contact
34- the developer team and work with them to establish a sustainability roadmap. If no
35- such roadmap can be established, alternative tools and resources must be identified
36- as replacement.
33+ long-term maintenance roadmap must be established. When possible, we will contact the
34+ developer team and work with them to establish a sustainability roadmap. If no such
35+ roadmap can be established, alternative tools and resources must be identified as
36+ replacement.
0 commit comments