> For the complete documentation index, see [llms.txt](https://docs.eduplex.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eduplex.eu/text-analysis/report/data-sources.md).
# Data sources
During this work, we explored diverse data sources, both open and closed. For example, we made extensive use of advertised job data to better understand skills and their relationship with course offerings. We used standards like ESCO, as shown in Figure 1, to create our database for skills descriptors.
Figure 1, ESCO data preparation
Regarding course data, we explore several open collections available on the Internet to understand the data ecosystem. However, for our experiments and demonstrators, we used two primary course data sources. WBS provided the first, and it consisted of courses with three main data fields, namely course title, course description and course learning goals.
Hochschule Schmalkalden provided the second-course data set. It consisted of more complex content because it included additional information such as credit number, course semester, instructor, etc. An example is shown in Figure 2.
Figure 2, Hochschule Schmalkalden MS course data
---
# 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://docs.eduplex.eu/text-analysis/report/data-sources.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.