> 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/lrs-user-journey-visualizer.md). # LRS User Journey Visualizer The LRS **User Journey Visualizer** project aimed to develop a tool for displaying user journeys in a simple and effective manner based on interactions with learning content. By visualizing user flows, the tool intended to provide content providers and platform administrators with valuable **insights into user behavior** and learning patterns. The project explored multiple visualization approaches derived from xAPI statements to represent these journeys. Although various visualization techniques were tested in the prototype phase, none were deemed sufficiently effective to achieve the project's objectives. Additionally, plans to extend LRS functionalities were deprioritized due to time constraints and their relatively low impact on the core goals. Despite these challenges, the project provided valuable lessons and highlighted the complexities involved in representing user journeys, offering a foundation for future work in this area. --- # 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/lrs-user-journey-visualizer.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.