An event directory looks simple until a date changes, a venue is renamed, or a subsidy rule is replaced for the next policy year. If the database stores only the latest value, the team loses the ability to explain where that value came from and when it was checked.
A safer approach is to model the claim rather than only the event. The event can stay stable while each date, venue, organiser or subsidy condition becomes a time-stamped assertion backed by a source document.
Separate the entities
A useful minimum schema is:
event : the recurring series, such as a named trade fair.
edition : one dated occurrence, with its own venue, dates and organiser.
venue : a stable place record with city and country.
source_document : the official page, PDF notice or organiser announcement.
claim : one field-level statement linked to a source.
verification : who checked the claim, when, and what changed.
The key rule is that an edition never stores an unexplained date or venue.…