Devtoberfest Planner: Confirm times between all assets?

[thecodester]

Is there a way to check if the youtube livestream is set to the same time as the Devtoberfest session in the planner, and the same as your zoom session and the same as the community event?

[jung-thomas]

Short answer: yes, a checker is feasible — with one important caveat about what each time actually is

The four times you want to reconcile live in four different systems, and only one of them is authoritative data we already hold. The rest have to be read back from where they were set. Here's the reality per source, grounded in the planner data contract we sync (external.devtoberfest.Session):

Time	Where it lives	Can we read it?	Reliability
Planner session	Session.SCHEDULEDSTART (+ SCHEDULEDTIMEZONE) in the planner DB	Yes, directly	✅ This is the source of truth we compare everything else against
YouTube livestream	On YouTube — liveStreamingDetails.scheduledStartTime	Yes, via the YouTube Data API (videos?part=liveStreamingDetails, videoId parsed from Session.YOUTUBEURL)	✅ Reliable. We already have a YOUTUBE_API_KEY in the credential store (the homepage video rail + freshness corpus use it)
Zoom session	In Zoom	Session.ZOOMURL is only a join link — it does not encode a time. The realistic offline path is parsing Session.CALENDARINVITE / Session.ZOOMINVITEDETAILS for a DTSTART	⚠️ Best-effort. We have no Zoom API credentials, so this only works if those fields are populated and contain a parseable start time
Community event	community.sap.com event page (Session.COMMUNITYEVENTURL)	Only by fetching + scraping the event page for its published date/time	⚠️ Fragile. No API — depends on page markup staying stable

So: planner + YouTube can be compared cleanly and deterministically. Zoom + community are best-effort and will produce "couldn't determine" results, not false mismatches, when the underlying data isn't there.

Nothing does this today — the planner Session rows (with the Zoom/YouTube/community URLs) are read-only via DevtoberfestService and aren't surfaced in any admin check screen.

Proposed approach

A per-edition "schedule consistency" report that treats SCHEDULEDSTART as truth and flags drift against each external asset:

• Endpoint: GET /api/devtoberfest/schedule-check?edition=<id> (admin-scoped), returning one row per session: { sessionCode, title, scheduledStart, youtube: {found, time, deltaMinutes, status}, zoom: {...}, community: {...} } where status ∈ ok | drift | missing | unknown.
• YouTube: parse videoId from YOUTUBEURL, batch-call videos?part=liveStreamingDetails (up to 50 ids/call), compare scheduledStartTime to SCHEDULEDSTART. Flag drift if delta exceeds a small tolerance (e.g. > 5 min).
• Zoom: parse CALENDARINVITE (.ics DTSTART) if present; else unknown. No Zoom API dependency.
• Community: fetch COMMUNITYEVENTURL, extract the event time from page metadata; unknown on any parse failure. Cache aggressively — this is the fragile leg.
• Surface: either a small admin page (a table with green/amber/red per asset) or, lighter-weight, a scheduled job that posts a drift summary (e.g. to a channel) a few times a day during the run-up. Everything fails soft — a source we can't read shows unknown, never a spurious mismatch.

Recommendation

Ship the YouTube + planner comparison first — it's the deterministic, high-value core (livestream time drifting from the announced time is the most visible failure). Add Zoom (CALENDARINVITE parse) and community scraping as best-effort columns behind the same report, clearly labelled "best-effort" so an unknown isn't read as "all good."

Before building, one thing worth a 5-minute probe against the live planner DB: how populated are CALENDARINVITE, ZOOMINVITEDETAILS, and COMMUNITYEVENTURL in practice? If Zoom times aren't actually stored anywhere we can read, that column is dead on arrival and we'd want to say so up front rather than ship an always-unknown field.

Happy to build the checker on the strength of this — just say the word and I'll open a PR to DEV.

[jung-thomas]

The schedule-consistency checker is built and merged to DEV (#2107).

Endpoint (admin-gated): GET /api/devtoberfest/schedule-check?edition=<id>&tolerance=<min> — reconciles each planner session's SCHEDULEDSTART against the actual scheduled times on its external assets and flags any that have drifted.

• YouTube — videos?part=liveStreamingDetails → scheduledStartTime
• community.sap.com — Khoros LiQL → occasion_data.start_time
• Zoom — not checkable; the planner carries no readable Zoom start time (bare join link, empty CALENDARINVITE, free-text ZOOMINVITEDETAILS), so it's excluded.

Each leg reports ok | drift | unknown | no-url | no-planner with a signed delta in minutes; a 5-minute tolerance by default. Fails soft — an unreadable asset shows unknown, never a false drift.

It already works and found a real problem. Verified live against Devtoberfest 2026 (87 sessions): the community leg resolved 40 event times — 39 exact-UTC matches, and 1 genuine drift on INT-43 ("Migrating from Joule Studio classic and the n8n Workflow Lifecycle"): planner says 2026-10-13 22:00Z, the community event says 2026-10-14 07:30Z — 9.5 hours apart. Worth correcting in the planner.

Not yet deployed — waiting on several other items to complete before the next DEV deploy. Two follow-ups are also out of scope for #2107: an Admin-UI surface for the report (API-only for now), and the YouTube leg needs YOUTUBE_API_KEY from the credstore, which resolves in the deployed srv but not in a local cds bind session.

[jung-thomas]

This is available in production now.

[thecodester]

How do I execute the checker or see the results?

[jung-thomas]

Resolved — the schedule-consistency check now has a UI in the Devtoberfest Planner (where the session data actually lives), rather than the UI-less admin REST endpoint that originally shipped here.

Delivered: developer-relations/devtoberfest-planner PR #57 (merged).

What it does: a dedicated "Schedule Check" List Report page in the Planner cockpit, reachable from a button on the Sessions list. One row per session, with a green/amber/red status per external asset:

• YouTube — reads the livestream's actual scheduledStartTime (Data API liveStreamingDetails).
• Community — reads the community.sap.com event start time (Khoros LiQL occasion_data.start_time).
• Zoom — not checkable (no readable scheduled start time exposed), so it's intentionally omitted.

Each leg is classified ok / drift (beyond a 5-min tolerance, with the delta in minutes) / unknown (URL present but unreadable) / no-planner / no-url. It's native to the Planner — it reconciles against the Planner's own Session.scheduledStart, no cross-approuter call back here. Fail-soft throughout: a missing YOUTUBE_API_KEY or an API hiccup reports unknown, never a spurious drift, and never errors the page.

Run it on-demand by opening the report; results are memoized briefly so paging/sorting doesn't re-hit the external APIs.

Closing here since the implementation lives in the Planner repo (separate GitHub host, so no automatic cross-link). The old admin-only GET /api/devtoberfest/schedule-check endpoint in this repo still exists — happy to remove it in a follow-up if we want to retire the dead surface.