> For the complete documentation index, see [llms.txt](https://olab4.gitbook.io/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://olab4.gitbook.io/help/advanced-topics/cigars.md).

# CIGARS

{% hint style="warning" %}
This whole concept, while powerful and promising, will likely be deprecated from future versions of OLab beyond 4.5 -- very few groups were interested in tracking activity metrics across a set of connected apps. 

Perhaps this will return if we become more sophisticated in our assessment of learner activities. 
{% endhint %}

When sending activity statements to a **Learning Records Store** (LRS), it is sometimes important to be able to collate statements that relate to a group of learning activities that are all part of a single learning design. We are trying to move away from the monolithic perspective that there is one ~~ring~~ ~~app~~ ecosystem to bind them all. (Yes, we are looking at you, Adobe). 

Within the definition of an xAPI Activity Statement, there is a section about 'context'. The definition is broad and flexible, which is both a good and a bad thing. 

{% hint style="warning" %}
insert link to xapi context and identifier. Should be <https://cigars.olab.ca&#x20>;
{% endhint %}

Very few groups have taken a meaningful look at how to use context and a context identifier. Indeed, it is not in the interests of large vendors to do so. They want to keep you within their ecosystem of linked applications. We all know that one size does not fit all. When all you have is a hammer, etc etc,

We have established a basic context identifier service which provides both the generation of new unique context IDs, and a simple lookup service so you can establish if a colleague has already set one up for you.&#x20;

{% hint style="warning" %}
insert links to CIGARS, the context metadata
{% endhint %}

CIGARS is intended to be more of a straw man or **prototype** so that interested groups can explore the various aspects of trying to blend xAPI statements from across a variety of learning tools. It is **not** intended to be the ultimate solution that is generalizable to all contexts(!) - we got tired of waiting for that. Better to have something we can poke at and test.&#x20;


---

# 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://olab4.gitbook.io/help/advanced-topics/cigars.md?ask=<question>&goal=<endgoal>
```

`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.