Sources

Story times, author talks, tech help, teen nights, ESL conversation circles — the largest single programme of free public events in the city, and the one most readers have never seen listed anywhere but a branch noticeboard.

FEED ONLY (2026-10-08). From bbd33fd9 to 2026-10-08 events.epl paged the events JSON (/v2/libraries/epl/events, ~52 pages of 100 a press) for its seriesId; the terms permit automated reading only by RSS/XML feeds, so the feed is read and recurring programmes are not grouped. The feed takes startDate/endDate and pages at 25. Mode is `api`, not `feed`, on purpose: this is RSS but it is a CALENDAR, read by pipeline/sources/events.py (epl), and must never reach the news feed collector, which would file every story time as a story. Takes startDate/endDate (YYYY-MM-DD) and page=N; pages at 25 and ignores `limit`. The JSON gateway (/v2/libraries/epl/events) holds the same events but ignores every date parameter and is not date-ordered, so a fortnight from it means reading all 5,000. Local start is <bc:start_date_local> — date-only for all-day, YYYY-MM-DDTHH:MM otherwise; <bc:is_cancelled> is honoured. Every row is filed as category 'library' regardless of title, so one chip hides the whole programme. MOVED FROM THE RSS TO THE JSON 2026-08-24, for seriesId — the only authoritative recurrence key any events source in this registry offers. EPL is 514 of the rail's rows and 442 of them are instances of a recurring programme. THE JSON IGNORES EVERY DATE PARAMETER: verified, startDate/endDate for one day and for a fortnight return identical pages spanning to 2027-05, so the window is applied client-side and a fortnight costs reading all ~5,100 events, about 52 pages against the RSS's 22. Bought deliberately. RESOLVE BOTH LOCATION COLLECTIONS: `locations` for branches and `places` for everything else — the epl2go pop-ups and community-league rooms live in `places`, and without it they lose their venue and become indistinguishable from one another.