This site republishes machine-readable ORFE Upcoming Events for ingest into campus services — among them the School of Engineering events newsletter and the department pages on the Engineering site. Production and development assets are available here for external consumers, integrations, and manual inspection.
Pick a publication date and a submission deadline to see exactly which events the editorial system would ingest for that edition, and which of them still needs a proper title.
Runs entirely in your browser against events.json,
the full feed; nothing is sent anywhere and nothing is changed.
Loading the feed…
| Starts | Title the editors would see | Series | Speaker | Location |
|---|
| Starts | Title | Series | Why it is out |
|---|
The production JSON feed is generated from the upstream ICS source on a recurring GitHub Actions schedule. Development assets are published on demand from whichever branch you dispatch the development workflow from.
Every upcoming department event, refreshed from the upstream ICS source every 30 minutes.
This is the canonical feed. Each record carries the event’s time, location, series,
speaker and abstract, plus titleSource and titleIsPlaceholder
describing where its title came from.
The same records, narrowed to one newsletter edition: publication day 00:00 through that week’s Sunday 23:59:59, Eastern.
Built for editors assembling an issue, so the list is short enough to review and the
events in it are the ones most likely to have a real title. Each record adds
newsletterEdition, the edition it was built for. Use the
simulator to see any edition’s contents.
The same two files, attached to the latest release for consumers that
prefer GitHub downloads over the Pages domain.
The release notes also record the ICS checksum and the newsletter edition each build was made for, which is how the pipeline detects that nothing has changed.
Links to the latest development feed assets published from a manually dispatched branch run.
Purpose: validation and pre-merge testing without disturbing the production release.
A static realistic dummy payload for remote ingest and downstream integration testing.
Purpose: a stable non-empty staging endpoint when live data is empty or unsuitable.
Both feeds are a JSON array of event objects in start-time order. Times are local Eastern
wall clock written without a timezone suffix (2026-09-21T16:15:00), matching
how the events are advertised.
| Field | What it holds |
|---|---|
guid | Stable identifier carried over from the upstream calendar. |
startTime, endTime | Local Eastern wall clock, YYYY-MM-DDTHH:MM:SS, no suffix. |
title | The talk title. Never empty — see titleSource for whether a person wrote it. |
titleSource | enriched or ics for a real title; fallback-speaker, fallback-template or fallback-series when this pipeline had to synthesise one. |
titleIsPlaceholder | true for the three fallback- sources. These are the listings an editor will want to chase before publication. |
speaker | Speaker and affiliation, as advertised. |
series | Seminar or colloquium series, comma-joined when an event belongs to more than one. |
location | Object with name (building), detail (room) and a reserved id. |
content | Abstract or description text. |
urlRef | Link to the event detail page. |
rawEventDetails | Optional raw HTML of the detail panel, with rawExtractAbstract and rawExtractBio pulled out of it. |
newsletterEdition | Newsletter variant only: the edition the record was selected for, identified by that week’s Monday. |
cancelled, bannerImage, itemType | Reserved fields the editorial system expects. |
The ICS to JSON workflow runs on main every 30 minutes, publishes the
latest release asset, and deploys /events.json to Pages.
The ICS to JSON (Development) workflow is manual. Dispatch it from a branch to overwrite
the shared dev release and the Pages content under /dev/.
The implementation, workflow definitions, and Pages templates all live in pu-orfe/upcoming.