> For the complete documentation index, see [llms.txt](https://upskilling.stacs.scot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://upskilling.stacs.scot/conference26/session-c-workshops/teaching-learners-about-our-data-rich-world.md). # Teaching learners about our Data-rich World Computational Problem-Solving in the Age of AI How can you teach about ‘a data rich world’ that is in the draft CIC Technologies? Data Literacy is the ability to ask questions, collect, analyse, interpret, and communicate stories about data. These are skills that all learners need to navigate our increasingly data-rich world. In this session, you will get a taster of how to use data as a lens to engage all learners in curiosity-led, interdisciplinary activities, and empower them to solve real-world problems with data. You will get a chance to try out hands-on activities, and discover a wealth of free resources that can be used right away with learners across Primary and Secondary, including our new Robot Cards resource developed with the National Robotarium. {% hint style="info" icon="school" %} **Kate Farrell and Dr Jasmeen Kanwal** Data Education in Schools team University of Edinburgh {% endhint %} --- # 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://upskilling.stacs.scot/conference26/session-c-workshops/teaching-learners-about-our-data-rich-world.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.