Manage multiple events and years

Give each event its own identity

Use separate event connections for different years or programs. A connection owns its source binding, imported records and configuration. Do not repurpose last year's identifiers to import next year's program.

Start the next event

Select the previous connection in Imports and use Start the next event. Supply a new connection name, a different event identifier, the feed identifier and the new Cadmium Education Harvester API key.

You can copy field selections, labels, transformations and mappings as an independent configuration. Review copied rules for year-specific dates and replacements.

The new event starts with manual imports and private public-field permissions. It does not inherit the old API key, imported records, source binding, import history or public approvals. Creating it does not verify the new key; prepare a preview.

Reuse designs carefully

Use Layout Studio's reuse tools or export/restore a draft. Review the destination event's field names and approvals. Copying a design does not authorize its fields for public use.

Archive without unpublishing

Archiving an event stops its normal import activity while retaining its records. It is not an unpublish action. Existing public displays and an enabled public API can remain available.

To hide an event, turn off its public publishing and verify cache removal. To keep a past program online, retain its approved published layout and link to its WordPress page.

Build an archive page

Create a normal WordPress page with links to each year's program page. The beta does not provide an automatic event-archive directory shortcode.

Related: Connect an event, Public fields, and Place a layout.