You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should also explicitly distinguish "public" from "local" nodes (i.e., the former could also be nodes deployed locally at an institute or lab, but they are data that can be openly queried). This could potentially live on its own page ("About Neurobagel graph databases" or "About Neurobagel nodes"?)
alyssadai
changed the title
mentioning that one node is expected to correspond to one graph database
Mention that each node is expected to correspond to one graph database
Nov 28, 2023
We want to keep our issues up to date and active. This issue hasn't seen any activity in the last 75 days.
We have applied the _flag:stale label to indicate that this issue should be reviewed again.
When you review, please reread the spec and then apply one of these three options:
prioritize: apply the flag:schedule label to suggest moving this issue into the backlog now
close: if the issue is no longer relevant, explain why (give others a chance to reply) and then close.
archive: sometimes an issue has important information or ideas but we won't work on it soon. In this case
apply the someday label to show that this won't be prioritized. The stalebot will ignore issues with this
label in the future. Use sparingly!
We should also explicitly distinguish "public" from "local" nodes (i.e., the former could also be nodes deployed locally at an institute or lab, but they are data that can be openly queried). This could potentially live on its own page ("About Neurobagel graph databases" or "About Neurobagel nodes"?)
Originally posted by @surchs in #133 (comment)
The text was updated successfully, but these errors were encountered: