Skip to content
Esc
↑↓navigate↵open⌘Jpreview
On this page

Organize content

Structure Content Database entries with tags on individual Content Block DB blocks (with color, icon, grouping, and bulk actions), sections inside Learning Journey DB entries, and course sync links.

Organisation in the Content Database helps administrators find shared material quickly and keep linked courses consistent. Tags label individual blocks in the Content Block DB so you can filter, group, and manage them in bulk; sections structure blocks inside a Learning Journey DB entry; and sync links define which courses receive content.

Why it matters

Without structure, a central library becomes a graveyard of similarly named quizzes and journeys. Universities run content across faculties, accreditation cycles, and language variants — organisation is what lets the right team find the right master, link the right cohort of courses, and push updates without touching unrelated offerings. Good tagging and deliberate sync linking are as important as authoring the blocks themselves.

Ways to organise

Mechanism Applies to Purpose
Tags Individual blocks in the Content Block DB Label, filter, group, and bulk-manage blocks
Sections Inside a Learning Journey DB entry Group related blocks; copied to linked courses on sync
Sync links Learning Journey DB entries and library blocks Define which courses receive content
Search and filters Content Block DB Find individual blocks in the table

Key concepts

Term Meaning
Content block tag A named, colored label with an optional icon, attached to one or more blocks in the Content Block DB
Tag group view A table view that clusters blocks by their tags, with an Untagged group for blocks without one
Section A named group of blocks inside a journey, matching the section model in Create a learning journey
Standalone Blocks Blocks outside any section — useful for one-off steps that do not belong to a group
Sync link A connection between a database entry and a target course for import or ongoing sync

Tag content blocks in the library

Each block in the Content Block DB can carry one or more tags:

Open Campus Management → Course Management and go to the Content Block DB tab.

In the Tags column for a block, open the tag picker to add existing tags or select multiple rows and use the bulk tag action in the toolbar.

To create a new tag on the fly, choose Create tag, give it a name, and optionally set a color and an icon. New tags can be applied immediately to the current selection.

Remove a tag from a block the same way — from the block's tag cell, or with the bulk remove tag action for multiple selected blocks.

Group and filter by tag

The Content Block DB table can be viewed as a flat list or grouped by tag:

In the Content Block DB tab, switch the grouping control to Tags.

Blocks are clustered under each tag; blocks with no tag appear under Untagged.

Use the tag filter in the toolbar to narrow the table to specific tags without changing the grouping.

Sections inside a Learning Journey DB

Learning Journey DB entries use the same section model as course learning journeys:

Open a Learning Journey DB entry and switch to Table View.

Add sections to group related blocks.

Place blocks inside sections or as Standalone Blocks when they sit outside a group.

Sections are copied to linked courses when you import or sync the full journey. This is how a database preserves not just individual activities but the pedagogical sequence — week-by-week structure, thematic units, or prerequisite groupings — when rolled out to multiple offerings.

Organise rollout by linking the right courses to each Learning Journey DB entry:

Open the database Settings page (or use the Syncs column on the Learning Journey DB table).

Click Link to courses and select target courses.

Run Sync now or Sync all to push content. The Last synced column shows when each link was updated.

Plan links before the teaching term: courses must be empty for a full journey import or sync. If teachers have already built content locally, you need a deliberate migration strategy — for example saving blocks to the database from the pilot course first, or starting fresh in a new course shell created through Course management.

Content Block DB layout

The Content Block DB tab lists all library blocks in one searchable, filterable table. Combine naming, search, and tags to keep large libraries manageable; use bulk tag actions to relabel many blocks at once instead of editing them one by one.

Library organisation Journey database organisation
Flat table, optionally grouped by tag Hierarchical sections and standalone blocks
Naming, search, and tags Sections (no tags on the journey structure itself — tags also apply on the Learning Journey DB list)
Per-block sync links Full-journey sync to linked courses
Mix blocks into any course journey Delivers an entire structured path

When a block logically belongs to a larger unit, consider whether it should live inside a Learning Journey DB entry (with sections) instead of — or in addition to — the standalone library.

Best practices

  • Link courses in batches aligned to rollout — for example all sections of one module — and sync together so Last synced stays consistent.
  • Use descriptive block titles and a controlled tag vocabulary (with distinct colors) so Browse the database stays scannable for non-authors.
  • Keep the Content Block DB for atomic reusables; use Learning Journey DB entries when section order and grouping matter.
  • Use bulk tag actions when reorganising many blocks after a naming or taxonomy change, rather than editing each block individually.

Common pitfalls

  • Trying to add sections to individual library blocks — sections exist only inside Learning Journey DB entries or directly in courses; the Content Block DB itself stays flat.
  • Linking courses that already have content for a full journey sync — the import state will be locked; start from an empty course or use individual block import instead.
  • Tag sprawl — too many unique tags defeats filtering and grouping; treat tags as a controlled vocabulary and reuse existing ones instead of creating near-duplicates.
  • Deleting a shared tag without checking usage — the delete confirmation shows the number of affected blocks; review it before confirming on a widely used tag.

FAQ

Can I tag individual library blocks?

Yes. Tags apply directly to blocks in the Content Block DB — add them from a block's tag cell or with bulk actions across a selection. Give each tag a name, and optionally a color and icon, to make them easy to scan in the table.

Can I tag many blocks at once?

Yes. Select multiple rows in the Content Block DB table and use the bulk tag action to add or remove a tag across the whole selection, or create a new tag and apply it to the selection in one step.

What happens if I delete a tag that's in use?

The delete confirmation shows how many blocks currently carry the tag. Confirming removes the tag from all of them; the blocks themselves are not deleted.

Do sections sync independently?

Sections are part of the full Learning Journey DB entry. They are copied to linked courses when you import or sync the entire journey — not as separate library entries. Tags on blocks organise the Content Block DB table; they are not part of section sync.

Where do I see which courses are linked?

The Syncs column on the Learning Journey DB table and the database Settings page show linked courses and Last synced times.

Last updated on

Was this page helpful?