> For the complete documentation index, see [llms.txt](https://bridge-lab.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bridge-lab.gitbook.io/docs/archive/mri-data-organization-no-longer-used.md).
# MRI Data Organization \[No Longer Used]
## **NOTE: This is our old study organization method. This page is preserved for future reference but should no longer be used as a guide for data organization.**
Our MRI data is stored in a standard way across studies (for the most part). Doing this allows us to navigate through or share any study files or data easily.
Each study is structured like so:
Study Materials are any document that supports the study's function - SOPs, recruitment materials, etc. Billing documents are what they sound like, documents involving billing of any services used in the study. Patient Data is HIPAA protected data related to each study participant. Imaging includes all raw imaging data. Analysis include any kind of analysis done on any data, including imaging data. Depending on the study, there may also be other higher order folders.
Image analysis pipeline files also have a specific structure. It looks like this:
01\_Protocols includes any pipeline documentation, scripts, related papers, etc. 02\_Data contains all input data (this could be raw or preprocessed data). 03\_Analysis includes all of the intermediate output files of a pipeline. 04\_Summary includes all final outputs, CSV files, plots, etc.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://bridge-lab.gitbook.io/docs/archive/mri-data-organization-no-longer-used.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.