Charts reads both. ai1ec_events holds start, end, venue, cost, and recurrence columns, and wp_posts holds the published status. SleekView joins ai1ec_events to wp_posts on post_id and to the ai1ec category and tag taxonomies, so cards have every Timely column ready for groupBy or value duty.

Yes. The dataset joins term relationships on the ai1ec_event_categories taxonomy. A donut grouped by category resolves term IDs to readable names with their colors. Filtering by category narrows every card on the dashboard to that programming track across upcoming events.

Timely stores the recurrence rule on ai1ec_events and expands instances at query time. The dataset can either count rows in ai1ec_events directly for parent-level counts or expand instances through the same rrule expansion the public calendar uses for density cards across weeks.

Yes. Every card has a filter scope that can target a single venue string, a category, or a date range on the start column. The filter applies on top of the aggregation, so a weekly density card scoped to one venue shows only that venue's programming load.

ICS feed imports populate the ical_feed_url column on ai1ec_events with the source feed URL. A card grouped by ical_feed_url separates feed-imported events from manual entries, useful when partner calendars feed into the master calendar and the team wants to see contribution by source.

Yes. The free plugin writes the same ai1ec_events table and ai1ec_event_categories taxonomy. The Timely Pro tier adds premium features on top, but the underlying schema is shared, so a dataset built for Pro renders against the free plugin with the Pro-only fields blank where they do not apply.

Yes. Each card has an underlying dataset slice that exports to CSV with the columns the chart used to aggregate. Useful when a venue partner asks for the per-event list behind a venue total or when the editorial lead needs the recurrence parents behind a weekly density slice.

Reporting plugins typically build a parallel data layer fed by hooks on ai1ec_events writes, which means a second moving part to keep in sync with Timely. SleekView Charts reads ai1ec_events directly, so the dashboard reflects the same row the event editor saves without an extra sync step or stale cache.