# In-house data and code

## Where is the data?

Our data is stored in many places. Here is a partial list:

* BLab share - our main central storage. VPN-protected, anything with private identifying information must be stored there.
* GitHub - see [BLAB\_DATA](/data-and-code/blab_data.md)
* Individual github repos - see project pages to find them.
* Google drive.
* Google docs/sheets.
* OSF - a set of projects. No central repository.

## Where is the code?

All new code should go into one of the following:

* Reusable R code goes into `blabr`.
* Reusable Python code goes into `blabpy`.
* Project-specific code goes into individual GitHub repos.
* Smaller lab-wide projects that don't correspond to a full research project and are typically done by the lab technician, go into the [one\_time\_scripts ](https://github.com/BergelsonLab/one_time_scripts)repo.

Lab-wide code (reusable or not) used to be spread out across multiple github repos before we started putting everything into `blabr`/`blabpy`/`one_time_scripts`. [Git repos cloned on BLab share](/data-and-code/git-repos-in-lab-and-links-to-their-github.md)has a partial list of those repos. They are often a useful source for code that can be adapted for new tasks.

## GitHub organizations

Our GitHub repos belong to two GitHub organizations: [BergelsonLab](https://github.com/bergelsonLab/) and [SeedlingsBabylab](https://github.com/seedlingsBabylab). All new repo should go into `BergelsonLab`. Dr. B. and staff members are admins of these organizations and give access to the individual lab members' GitHub accounts.


---

# Agent Instructions: 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:

```
GET https://gitbook.bergelsonlab.com/data-and-code.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.