Refresh conj2026 sessions from Sessionize - #2
Conversation
Re-ran bin/sessionize import against the live API to pick up schedule changes made since the original one-time import: a new Late Registration session, a ~20min-earlier Friday morning schedule, an extended Friday coffee break, the Silk talk retitle/speaker name fix, and the Closing Party's official name/description (Charlotte Beer Garden). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Maps each already-existing Google Calendar event on "Clojure Conj 2026" to its Sessionize external-id, so a future sync script can update titles/descriptions/times without ever creating or deleting events. Deliberately excludes the Closing Party event, which was hand-edited after creation (custom location, label, reminder). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
also adds some data that helps me to populate an opt in google calendar im spiking out https://calendar.google.com/calendar/u/0?cid=Y185YmU5NWExYWMzNjgzZjY3OTY4NzgzNzE2NGQxNjY2ZGU1MjViN2I2NjFiZWY0OWUzMzUzYjBkMDNiMGJjNjgyQGdyb3VwLmNhbGVuZGFyLmdvb2dsZS5jb20 |
| @@ -0,0 +1,42 @@ | |||
| ;; Maps conj2026 sessions to their pre-existing Google Calendar event ids on the | |||
| ;; "Clojure Conj 2026" calendar. `bin/sync-gcal` only ever updates events listed | |||
There was a problem hiding this comment.
bin/sync-gcal is an experimental bb script meant to update google cal when sessions.edn is updated. not yet committed (and honestly eh, not sure its worth the trouble.. its pretty easy to populate changes to google calendar using the google cal mcp server on my work laptop).)
regardless of implementation details, having the associated google cal id's is useful though so committing as part of this PR
|
Thanks! Note that these are migration files, they won't be re-imported if you change them in place. I added a |
Summary
data/conj2026/03_sessions.ednwas populated bybin/sessionize importrun on 2026-08-06 so it was stale and missing new updates. Re-ran it against the live Sessionize API and diffed the result.01_locations.ednand02_session_types.ednwere re-fetched too but had no changes.Test plan
03_sessions.ednsession-by-session (external-id/title/time keyed) to confirm only real schedule/content changes are included, no accidental data loss