Deploy a MNI-only and protected node

[surchs]

Context

We just built the IDP functionality #167, and the MNI has IDPs we can track. Now we want to see if users find this new feature useful and will use it. Here is a list of people and datasets we're looking to include in this demonstration node.

The rollout will go in phases:

• Phase 1: Demo node to JB. If all good, JB will invite other PIs for review
• Phase 2: Other PIs review the node. If all good, we can invite their trainees to test the node. All good here means: explicit yes from all PIs.
• Phase 3: Invite the trainees for a test

Why

• to get real user feedback
• to validate our assumptions on what features will make the query more useful

Outcomes

• There is a query interface for QPN and PPMI that is only accessible to a select group of people
• We can see if users are running queries against this endpoint / how many queries
• Users can search for tabular, imaging, and derivative criteria
• Users get in response the paths to the files they just found or at least the participant IDs
• We have a way of following up with the users about their experience / what works well for them and what doesn't

[surchs]

@neurobagel/dev I added the sub-issues I can think of that have to be done before this PD node runs. Please add ones I have missed directly.

[alyssadai]

Other tasks

• after the query tool updates, redeploy the BIC internal node w/ the new query tool
• add copy of symlink script to /data/pd
• update our public QPN node
• message Nikhil / JB with tips on how to use the new query tool and symlink script

[alyssadai]

Note: To redeploy the BIC node following neurobagel/query-tool#379 and related PRs, the following steps were necessary:

• add https://query-bic.neurobagel.org to the authorized URIs for our Auth0 application
• pull the latest versions of our Docker images
• update the value of NB_QUERY_CLIENT_ID for the local federation stack, as well as for the 2 local node stacks for the closed and open datasets