Skip to content

Commit 37b79a2

Browse files
committed
fix: update outreach.md
1 parent 33c4d7f commit 37b79a2

File tree

1 file changed

+32
-25
lines changed

1 file changed

+32
-25
lines changed
Lines changed: 32 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -1,33 +1,40 @@
11
# Outreach Plan
22

3-
Broad engagement with the neuroscience community is necessary for the optimization,
4-
integration, and adoption of the Resource components.
5-
6-
We conduct five types of outreach activities that require different approaches:
3+
Broad engagement with the neuroscience community is essential for the optimization,
4+
integration, and adoption of the Resource components. To achieve this, we conduct five
5+
types of outreach activities, each requiring a tailored approach:
76

87
## 1. Precursor Projects
98

10-
Our [Selection Process](../selection) requires a "Precursor Project" for any new
11-
experiment modality to be included in DataJoint Elements. A precursor project is a
12-
project that develops a DataJoint pipeline for its own experiments either independently
13-
or in collaboration with our team. We reach out to teams who develop DataJoint
14-
pipelines for new experiment paradigms and modalities to identify essential design
15-
motifs, analysis tools, and related tools and interfaces. We interview the core team to
16-
learn about their collaborative culture, practices, and procedures. We jointly review
17-
their open-source code and their plans for dissemination. In many cases, our team
18-
already collaborates with such teams through our other projects and we have a good
19-
understanding of their process. As we develop a new Element to support the new
20-
modality, we remain in contact with the team to include their contribution, solicit
21-
feedback, and evaluate design tradeoffs. When the new Element is released, a full
22-
attribution is given to the Precursor Project.
23-
24-
**Rationale:** The Resource does not aim to develop fundamentally new solutions for
25-
neurophysiology data acquisition and analysis. Rather it aims to systematize and
26-
disseminate existing open-source tools proven in leading research projects.
9+
As part of our [Selection Process](../selection), a Precursor Project is required for
10+
any new experimental modality to be incorporated into DataJoint Elements.
11+
12+
A Precursor Project involves the development of a DataJoint pipeline for specific
13+
experiments, either independently or in collaboration with our team. Our outreach
14+
activities for Precursor Projects include:
15+
16+
- Engaging Development Teams: Reaching out to teams developing DataJoint pipelines for
17+
new experimental paradigms or modalities.
18+
- Identifying Key Components: Collaborating with these teams to identify essential
19+
design motifs, analysis tools, and related interfaces.
20+
- Team Interviews: Conducting interviews the core team to understand their collaborative
21+
culture, practices, and procedures.
22+
- Code and Dissemination Review: Reviewing their open-source code and dissemination
23+
plans to assess compatibility and adaptability.
24+
- Continuous Collaboration: Staying in contact with the team throughout the Element
25+
development process to incorporate their contributions, gather feedback, and evaluate
26+
design tradeoffs.
27+
28+
When the new Element is released, a full attribution is given to the Precursor Project,
29+
ensuring their contributions are recognized.
30+
31+
**Rationale:** The Resource does not aim to create fundamentally new solutions for
32+
neurophysiology data acquisition and analysis. Instead, it systematizes and disseminates
33+
existing open-source tools already proven in leading research projects.
2734

2835
## 2. Tool Developers
2936

30-
DataJoint pipelines rely on analysis tools, atlases, data standards, archives and
31-
catalogs, and other neuroinformatics resources developed and maintained by the broader
32-
scientific community. To ensure sustainability of the Resource, we reach out to the
33-
tool developer to establish joint sustainability roadmaps.
37+
DataJoint pipelines depend on a variety of analysis tools, atlases, data standards,
38+
archives, catalogs, and other neuroinformatics resources created and maintained by the
39+
broader scientific community. To ensure the long-term sustainability of the Resource, we
40+
reach out to the tool developers to establish shared sustainability roadmaps.

0 commit comments

Comments
 (0)