Skip to content
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.

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

Incorrect bullet point ordering in docs #258

Closed
2 tasks done
surchs opened this issue Jan 7, 2025 · 0 comments · Fixed by #261
Closed
2 tasks done

Incorrect bullet point ordering in docs #258

surchs opened this issue Jan 7, 2025 · 0 comments · Fixed by #261
Assignees

Comments

@surchs
Copy link
Contributor

surchs commented Jan 7, 2025

This section: https://neurobagel.org/user_guide/maintaining/#updating-the-data-in-your-graph has an incorrect ordering:

Image

Most likely this is because the ordering is restarted by malformatted markdown:

1. Shut down the Neurobagel node, if it is already running
```bash
docker compose --profile full_stack down
```
(or, replace `full_stack` with the profile you are using)
2. Update the data files in the directory specified by the `LOCAL_GRAPH_DATA` variable in `.env`, or simply change the path to a directory containing your JSONLD files.
3. (Re)start the Neurobagel node
```bash
docker compose --profile full_stack up -d
```

We should:

  • Fix the markdown problem
  • Ensure the ordering makes sense
@alyssadai alyssadai self-assigned this Jan 13, 2025
@alyssadai alyssadai moved this to Implement - Active in Neurobagel Jan 13, 2025
@alyssadai alyssadai moved this from Implement - Active to Implement - Done in Neurobagel Jan 13, 2025
@surchs surchs moved this from Implement - Done to Review - Active in Neurobagel Jan 15, 2025
@github-project-automation github-project-automation bot moved this from Review - Active to Review - Done in Neurobagel Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Review - Done
Development

Successfully merging a pull request may close this issue.

2 participants