Dev.to WebDev πŸ›  Dev πŸ‘ 0 πŸ“– 4 min read

A source-of-truth schema for event dates, venues, and subsidy rules

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

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. It points to one or more claims, and the currently published value is selected from those claims.

Add provenance to every field

A claim table can be small:

event_id
edition_id
field_name
value
source_url
source_type
observed_at
effective_from
effective_to
status

observed_at is not the same as effective_from. A subsidy page may be published in December for a policy that starts in January. A trade-fair website may announce dates two years ahead before the venue contract is final. Keeping both timestamps prevents a future-dated claim from silently overwriting today’s verified value.

Use status values such as proposed, verified, superseded and conflicted. Do not delete the losing record. A conflict is evidence that the source set needs review, not a database error to hide.

Make conflicts visible

When two official pages disagree, keep both claims and surface the conflict in the editorial queue. A simple rule set helps:

  1. Prefer the current organiser page over a third-party directory.
  2. Prefer a dated official notice over an undated marketing page.
  3. Prefer a specific exhibition edition over a generic industry page.
  4. Escalate when the sources are equally authoritative.

For a public exhibition database, the published page can show a compact evidence note: last checked date, source type and any unresolved conflict. This is more useful to readers than a confidence score with no explanation.

Treat subsidy rules as versioned records

Subsidy data needs its own structure because eligibility is not one number. At minimum, capture:

  • jurisdiction and responsible authority;
  • policy year and application window;
  • eligible exhibition catalogue or coverage rule;
  • eligible costs and caps;
  • required documents;
  • official notice URL and verification date.

A rule that was valid for one policy year must not be reused for the next without a new claim. Store the policy period explicitly and make the public page select the rule for the requested year. That prevents a stale amount from being presented as current guidance.

The overseas exhibition subsidy dataset is an example of publishing the source links and verification dates alongside the fields. The important design choice is not the file format; it is that every public value can be traced back to a dated official source.

Build a verification loop

A practical pipeline is:

  1. Ingest organiser pages, official notices and structured feeds.
  2. Normalise names, countries, dates and venue identifiers without discarding the raw text.
  3. Compare new claims with the current published values.
  4. Review only rows that changed, conflicted or expired.
  5. Publish the selected claim plus its evidence summary.
  6. Monitor source URLs for 404s, redirects and content changes.

The review queue should be the product of the comparison step, not a manual hunt through every record. This is where a source-linked trade fair directory becomes operationally useful: the team can see which editions need attention before a stale page reaches a visitor.

Keep the calendar disposable

A calendar view should be generated from the verified edition records, not edited by hand. The 2027 global exhibition calendar is a reader-facing projection; the underlying edition records remain the source of truth.

Generate the calendar with stable URLs, canonical dates and visible last-verified labels. When an edition changes, regenerate the view from the database instead of patching the page. That keeps every surface consistent and makes rollback simple.

The small discipline that matters

The hard part is not choosing a database. It is refusing to publish an unsourced field just because the layout expects a value. An empty state with a clear "not verified" label is better than a plausible-looking date that nobody can defend.

Model claims, keep provenance, expose conflicts and version the rules. Those four choices make an event directory easier to audit, cheaper to maintain and more trustworthy for the people using it.

πŸ“° Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.