← Back to docs
Setup Docs

Authoring the Library: Study Notes & Glossary

The Library gives players something to revise from: study notes and a glossary for every module, slide deck, case study and video in the Adventure, written by the A.I. from that material alone, never from its questions or answers. You read and correct every set before players see it. Players find the published notes on their Resources page, and Cooper teaches and quizzes from them.

What It Builds From

Every step that carries material is a source: a SCORM Package, a Slides (PDF) deck, a Case Study (HTML) and a Video. Each source gets its own set of notes, with its own short glossary of the terms it uses. An Adventure with none of those steps yet has nothing to build; add one as a step and it shows up in the Library.

The Library Tab

Open Manage Content and its Library tab. Counters at the top say how many sources there are and how many sets are published, drafts or have no notes yet. Below, it lists every source with its kind and where its notes stand: No notes yet, Writing…, Could not build, Draft or Published, and a warning when the step's material changed after the notes were written. From there:

The Library tab listing four sources, a video, a slide deck, a SCORM module and a case study, two published and two drafts, with Publish and Make draft on the rows.
Manage Content → Library. One row per source. Drafts offer Publish; published sets offer Make draft. The counters above move as you go.

The step editor of each source carries the same thing in small: a Study notes in the Library panel saying where its notes stand, with Build notes and a link to read and publish them. When you upload or replace a SCORM package, its notes are written for you as a draft.

The Study notes in the Library panel inside a step's editor, reading Published: players and Cooper read these notes, with a Build again button.
In the step editor. The panel follows the notes: here they're published, and Build notes has become Build again.

The Edit Window

One window holds everything about a set of notes, saved with one Save:

The notes edit window with a title, three short sections of study notes, and key points under Your own notes for the A.I., status Draft.
The edit window. These notes were written by hand, the way you'd write or correct a built set. Save answers "Notes saved as a draft." or "Notes saved and published."
The Glossary part of the edit window with terms and their meanings, and Add a term.
A set's own glossary. The material's terms, acronyms and roles, each with its meaning.

Your Own Notes for the A.I.

Some material can't be read: a video's soundtrack, a live session, a module that's all pictures. Each set has a box, Your own notes for the A.I., for a transcript or the key points. It's used the next time those notes are built, on top of the material, and players never see it, only the notes written from it. Pasting a video's transcript there is the way to give a video step real study notes.

Which Key Pays

Building calls the A.I., so it needs a key: the Adventure's own Claude key on the Connections pane of Adventure Settings (a cohort uses its template's), else the Adventure owner's account key (My Account → A.I. (Cooper)), or, when the Adventure has Cooper switched on, the platform's Cooper key. Without either, the Library says so in red and offers Edit only: notes can still be written by hand, just not built. The step editor's Build notes answers with the same warning.

The Library tab on an adventure with no A.I. key: a red line explaining that notes can't be built, and Edit on every row.
No key that pays. The red line says what to do (add a key under Adventure Settings → Connections, or switch Cooper on); until then, Edit lets you write the notes yourself.

The Glossary

Every set of notes has its own glossary, so a term two modules both teach shows up twice, and "MFA" sits apart from "Multi-factor authentication". The Glossary panel under the table counts the terms across all the notes and says whether they've been compiled. Compile the glossary hands every term to the A.I., which joins the ones that are the same entry into one, with one short meaning made from their own words and nothing added. Terms with no twin stay as they are. It's offered only when a key can pay, and needs at least two terms. Read the joined entries, fix any wording, or Keep apart two terms that should stay separate, then publish. Players then read one A-to-Z list, and every set of notes shows the joined meaning.

The Glossary panel under the Library table, reading 11 terms across the notes, not compiled yet.
The Glossary panel. How many terms the notes hold, and whether they've been compiled. A compile lands as a draft to review and publish, like notes.

What Players See

Once there are published notes, the Resources page becomes the player's Library, with three tabs: Study notes, one card for every module, deck and case study they've reached, with a search box over all of them; Glossary, the A-to-Z list with a box to find a term; and Resources, the files and articles described in Posts & Resources. A set of notes opens to a player once its milestone is open to them; until then it simply isn't there, so the Library never hints at what's ahead. A joined glossary entry shows only once the player can read every set of notes it joins.

A player's Resources page on the Study notes tab: a card for each published set of notes with its kind, milestone and a preview.
What players read. A card for every published set of notes on a milestone open to them; drafts and notes for locked milestones aren't shown or named.

Players read the notes on the Resources page, so the Lore / Resources section has to be switched on (Adventure Settings → Sections). With it off, the Library tab warns you; Cooper still uses the published notes.

Templates and Cohorts

The Library belongs to the template, like the steps it's built from: build and publish once, and every cohort's players read the same notes.

Related