> For the complete documentation index, see [llms.txt](https://docs.correlaid.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.correlaid.org/education/educational-formats/daten-verstehen-und-nutzen.md).
# Daten verstehen und nutzen
Course Period 2024-2025
{% hint style="info" %}
:flag\_de: Language: German
:busts\_in\_silhouette: Target Group: Non-Profit Organizations
{% endhint %}
Membership lists, information on fundraising campaigns, participant lists and so on – Do you have data in your organisation and have no idea what to do with it? You need to write something about the impact of your project in your report and have never done anything to measure impact before? You want to tender a data project for your organisation but don't know what all the terms in the ‘world of data’ actually mean? Perhaps you've heard of data literacy but don't know exactly what it means? In our basic 12-week course on ‘Daten verstehen und nutzen" participants tackle these questions together with data professionals in weekly live-sessions.
### **How does the course work?**
* Period: 12 weeks
* Time required: 2-4 hours / week
* Format: Integrated learning format with interactive learning platform
* Weekly online live session with data science tutors, always on Fridays
* Studying in learning tandems
* Individual consultation hours
### **Ressources**
* Website:
* Learning Platform:
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.correlaid.org/education/educational-formats/daten-verstehen-und-nutzen.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.