A parks department wants event dates pulled out during enrichment so the search index can filter programs by calendar. What should they add to the ingestion pipeline?

A parks department that wants event dates filterable in search must add custom enrichment skills that extract those dates during ingestion before indexing. Enrichment promotes calendar values from prose or flyer text into structured fields the index can filter and facet, so residents and staff can narrow programs by date range instead of reading every hit. Entity linking skills that resolve venue names before indexing link disambiguated venue names to a knowledge base, but they do not extract and normalize calendar dates into filterable fields. Key phrase extraction skills that tag program topics before indexing may add useful topical tags, but they do not populate normalized start and end date fields parks needs for filtering. PII detection skills that redact attendee details before indexing detect and mask sensitive personal data, but they cannot reliably power structured calendar filters. Exam caveat: municipal event filtering by calendar requires enrichment that extracts dates into indexable metadata—not entity linking that resolves venue names, key phrase extraction that tags program topics, or PII detection that redacts attendee details. Operational check: run custom date-extraction enrichment on sample parks flyers and program PDFs; store normalized start and end date fields; exercise search filters for upcoming weekends and multi-day ranges; fix extraction errors on ambiguous formats before the public events index ships.