Charts reads the stec_event CPT plus the linked stec_venue and stec_organizer CPTs directly. Joins on the linked postmeta IDs resolve venue and organizer titles. The stec_cat taxonomy is also exposed for category grouping, so cards have every Stachethemes column ready for chart duty.

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

Stachethemes stores the recurrence rule in the repeat_data postmeta on stec_event. The dataset expands instances against that rule so a weekly density card shows the actual load per week, not just the parent post counts. Cards can switch between parent-level and instance-level scope as needed.

Yes. Every card has a filter scope that can target a single venue_id, organizer_id, category, or a date range on start_date. The filter applies on top of the aggregation, so a weekly density card scoped to one organizer shows only that organizer's programming load each week.

Yes. SleekView refreshes the dataset schema from the postmeta keys present on stec_event. A new Stachethemes add-on or theme integration that writes additional keys becomes available as columns on the next dataset refresh, no manual schema mapping required from the coordinators using the dashboard.

Yes. Custom integrations typically write to the same stec_event CPT or to stec_venue and stec_organizer via the documented post types. SleekView reads every postmeta and taxonomy on those records, so custom integration data coexists in the same dataset without conflict on the underlying CPT rows.

Yes. Each card has an underlying dataset slice that exports to CSV with the columns the chart used to aggregate. Useful when an organizer asks for the per-event list behind their organizer total or when finance needs the recurrence parents behind a weekly density slice on the season-ahead view.

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