Douglas node with 2 datasets and connection to us

Context

The Douglas has had a deployed neurobagel node since https://github.com/neurobagel/project/issues/105. From this we got a lot of valuable technical feedback. But the node isn't very useful to the Douglas yet, and as a result we do not yet get any valuable user feedback. So the goal is to change this and then keep going.

Why

Part of neurobagel/planning#11 and neurobagel/planning#49
So the Douglas / Cobralab gets value out of neurobagel
So we get hands on feedback from target users on what they like / need from query
To have a concrete example to show Douglas stakeholders when discussing expansion

Outcomes

[x] minimum PEPP in the Douglas node
[ ] ~PNC in the Douglas node~
[ ] ~raw NIfTi BIDS versions of PEPP and PNC converted to MNC~
[x] Douglas node has read-only federation with the public neurobagel network (i.e. they see all that query.neurobagel.org sees)

What

[x] neurobagel/documentation#129
[ ] https://github.com/DouglasNeuroInformatics/project_issues/issues/70
[x] https://github.com/DouglasNeuroInformatics/project_issues/issues/69
[x] (re-) BIDSify PEPP and PNC on DNP storage (Matt or NB)
[x] (re-) annotate PEPP data (Matt or NB)
~[ ] annotate PNC data (Matt or NB)~
[x] process annotated datasets with CLI to create graph ready files (Matt or NB)
[x] ingest graph data into node (Gabe or Thomas)
~[ ] clarify process to keep Douglas node in sync with files on disk~
[x] #127
[x] #128
[ ] Confirm federation from DNP to MNI

TBD / maybe later

train Cobra lab members to annotate PEPP + PNC
run MNC conversion on the BIDSified data
clarify choice of NIfTi to MNC converter with Gabe

neurobagel / planning

Douglas node with 2 datasets and connection to us #58

Context

Why

Outcomes

What