Does anyone know how people who use CH API emuneration data are made aware of changes to these lookup files
we track the changes by retrieving the lookup files from github on a regular basis and comparing the content to the last time we retrieved it
We have a Diagnostics layer within our ingestion processes that validates against our expectations, for both schemas and enumerations, and reports any unmatched incoming items ahead of database load. This catches any change in a timely manner and ensures nothing unmatched disappears between stream and load. The build was tedious, and somewhat protracted, but has been well worth the original effort.
StatBooks®, the established Companies House data wranglers.