> 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/curios-video-mashups.md).

# CURIOS video mashups

We have been using a neat tool in OLab3 to insert segments of videos into OLab Nodes, WordPress pages, Moodle pages and many other types of online content. We are pleased to say that CURIOS works just as well in OLab4.&#x20;

For more general information on how to use the CURIOS mashup tool, take a look at <https://openlabyrinth.ca/wp-content/uploads/2016/04/UsingtheVideomash-UpToolinOpenLabyrinth.pdf> — this explains how to use the CURIOS mashup editor and why you might want to try this tool.&#x20;

You can still access the CURIOS service at <https://curios.openlabyrinth.ca>&#x20;

When CURIOS has generated the small piece of HTML code (or slugline), the help document above does explain what to do with it. In OLab4, we use the same process but it is very slightly different.&#x20;

Firstly, you cannot just paste that HTML code in as plain text. The Node Editor has to understand that this is a piece of raw HTML code. For those of you who are used to working with raw HTML, this may be obvious.&#x20;

In OLab4, you need to use the Advanced Node Editor (instead of the smaller Basic Node Editor that you use most of the time). In the Designer, go to the Node where you want to insert your video mashup. Click on the Node content to open the Basic Node Editor.&#x20;

In the Basic Node Editor window, you will see a button at the top marked \[ADVANCED] — click on this to open the Advanced Node Editor in a second tab. Here you will see a more complex editor window, quite similar in appearance to the old OLab3 editors.&#x20;

In OLab3, you were told to choose the 'Source Code' menu item. The equivalent in the OLab4 Advanced Node Editor is a small button just above the node's text marked as <>

<figure><img src="/files/VyhmZLsMYFQHEyso4xNc" alt=""><figcaption></figcaption></figure>

When you click on this, you will now see the node's content rendered in raw HTML, with all the angle brackets etc. We refer you to other online materials if you are not at all familiar with HTML editing.&#x20;

<figure><img src="/files/FzielNejjEWSVDSOfAmK" alt=""><figcaption></figcaption></figure>

For inserting the CURIOS slugline, you simply need to paste the generated raw HTML code into the page, usually between two paragraph markers, \<p> and \</p>. You will often find these at the bottom of the page if you pressed Enter one time too many when editing your Node.&#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/curios-video-mashups.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.
