Skip to content

[ENH] add new FAQs #37

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jdkent merged 1 commit into from
May 1, 2026
Merged

[ENH] add new FAQs #37

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 27 additions & 1 deletion docs/introduction/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,4 +37,30 @@ You may also make a Version private if you don't want to share your edits with o
<details>
<summary>How does this project relate to the original Neurosynth?</summary>
Neurosynth 1.0 was an online platform for browsing automatically generated large-scale neuroimaging meta-analyses. However, because all analyses were pre-generated, users were unable to define custom meta-analyses using the Neurosynth database. Instead, Neurosynth 1.0 used text mining techniques to automatically group studies based on the frequency of the terms mentioned in the text. Neurosynth Compose is focused on allowing users to overcome the limitations of automated large-scale meta-analysis, by enabling users to annotate studies, and curate sets of studies amenable for meta-analysis. This way, users can systematically define meta-analyses using their own expertise, while still leveraging the Neurosynth database, and an easy-to-use web-based analysis builder to accelerate the meta-analysis process.<br/>
</details>
</details>

<details>
<summary>How do I collaborate with another person on the same meta-analysis project?</summary>
The answer depends on what you want your collaborator(s) to be able to do.
If you just want them to view the project, you can make the project public and share the Project URL with them.
If you want them to be able to edit the project, the best approach is to create a shared account
using a shared email address and create the project under that account.
It is on our roadmap to provide more robust collaboration features in the future.
</details>

<details>
<summary>How do I run a legacy Neurosynth-like meta-analysis?</summary>
Use the <a href="../tutorial/automated">Automated Meta-Analysis tutorial</a> as the closest workflow. In brief: create a Project, use the Simple curation workflow, import studies from NeuroStore using your search term, promote the relevant studies to Included, move to Extraction, and then create a Meta-Analysis Specification. Using the search term is similar to the tf-idf approach used in the original Neurosynth platform since the threshold for inclusion was so low, if the word was mentioned in the abstract, it would be included.
<br/><br/>
For the algorithm, select `MKDAChi2`. This is the large-scale association-test workflow used by the original Neurosynth platform. When prompted for a reference dataset, choose `Neurosynth` if you want the legacy Neurosynth reference sample, or `Neurostore` if you want the newer continuously updated database.
</details>


<details>
<summary>What's an annotation?</summary>
An annotation is a column of structured information attached to the Analyses in a StudySet. You can think of annotations like a spreadsheet: rows are Analyses, and columns are values such as `included`, task type, contrast direction, participant group, or any other variable you need for curation and analysis.
<br/><br/>
Annotations are most often used to decide which Analyses should be included in a meta-analysis. For example, a Boolean annotation can mark each Analysis as included or excluded, and the Meta-Analysis Specification step can use that annotation column to select the final inputs.
<br/><br/>
See the <a href="../guide/glossary#annotation">Glossary entry on Annotations</a> and the <a href="../guide/Project/Extraction#annotations">Extraction guide</a> for more detail.
</details>
19 changes: 16 additions & 3 deletions docs/introduction/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,8 +24,8 @@ import Typography from '@mui/material/Typography';
## Get started! 🚀


<div style={{ display: 'flex' }}>
<Card style={{ width: '100%', display: 'flex', marginRight: '50px' }}>
<div style={{ display: 'flex', gap: '24px', flexWrap: 'wrap' }}>
<Card style={{ flex: '1 1 240px', display: 'flex' }}>
<CardContent>
<Typography variant="h5" component="h2" gutterBottom>
Tutorials
Expand All @@ -38,7 +38,7 @@ import Typography from '@mui/material/Typography';
</Button>
</CardContent>
</Card>
<Card style={{ width: '100%', display: 'flex' }}>
<Card style={{ flex: '1 1 240px', display: 'flex' }}>
<CardContent>
<Typography variant="h5" component="h2" gutterBottom>
User Guide
Expand All @@ -51,6 +51,19 @@ import Typography from '@mui/material/Typography';
</Button>
</CardContent>
</Card>
<Card style={{ flex: '1 1 240px', display: 'flex' }}>
<CardContent>
<Typography variant="h5" component="h2" gutterBottom>
FAQ
</Typography>
<Typography variant="body1" gutterBottom>
Find answers to common questions about collaboration, automated analyses, algorithms, and annotations.
</Typography>
<Button variant="contained" color="primary" href="introduction/faq">
Go to FAQ
</Button>
</CardContent>
</Card>
</div>

<Card style={{ marginTop: '24px' }}>
Expand Down
Loading