Ernex

ernex

Discuss an engagement

Discuss an engagement

Errata and corrections.

Errata and corrections.

Errata and corrections.

01 No silent edits. Once an edition is published, its content is never changed in place.

01 No silent edits. Once an edition is published, its content is never changed in place.

02 A correction that changes a published number, a chart, a named entity, a definition or a conclusion is published as a new version number and recorded in the log.

02 A correction that changes a published number, a chart, a named entity, a definition or a conclusion is published as a new version number and recorded in the log.

03 Earlier versions stay available at their original download link for at least five years.

04 Typographical corrections that do not change meaning are recorded in the log but do not create a new version.

04 Typographical corrections that do not change meaning are recorded in the log but do not create a new version.

05 Buyers of an affected edition are notified of any version change at the address they purchased with.

05 Buyers of an affected edition are notified of any version change at the address they purchased with.

06 Corrections can be requested by anyone at office@erne-x.com. A request concerning a named company is answered, and the underlying source rows are re-checked, before any change is made or declined.

06 Corrections can be requested by anyone at office@erne-x.com. A request concerning a named company is answered, and the underlying source rows are re-checked, before any change is made or declined.

07 Where the source corrects its own data after our frozen extraction, the published edition is not retro-fitted. The change is recorded here and reflected in the next edition’s comparability table.

07 Where the source corrects its own data after our frozen extraction, the published edition is not retro-fitted. The change is recorded here and reflected in the next edition’s comparability table.

Policy owner and named editor: Ant Gokcek, Ernex, UAB, office@erne-x.com.

Policy owner and named editor: Ant Gokcek, Ernex, UAB, office@erne-x.com.

How an erratum comes to light

How an erratum comes to light

The policy above states how a correction is made. This section states how we find what needs correcting, because a correction policy means nothing without a method that triggers it.

The policy above states how a correction is made. This section states how we find what needs correcting, because a correction policy means nothing without a method that triggers it.

We do not wait for a reader to tell us. The errata address is printed in every edition and on this page, and every challenge is answered by re-reading the underlying source rows. If that channel is the first to tell us something, the system has failed.

We do not wait for a reader to tell us. The errata address is printed in every edition and on this page, and every challenge is answered by re-reading the underlying source rows. If that channel is the first to tell us something, the system has failed.

Every new edition audits the one before it. An edition that shares a data set reads that data through its own independent pipeline and is required to reconcile with the figures already published. Running the same code against the same data returns the same answer and finds no error of logic; what finds an error is arriving at the same number by a different route. Every defect caught so far has come from this channel.

Every new edition audits the one before it. An edition that shares a data set reads that data through its own independent pipeline and is required to reconcile with the figures already published. Running the same code against the same data returns the same answer and finds no error of logic; what finds an error is arriving at the same number by a different route. Every defect caught so far has come from this channel.

Every published file is rebuilt monthly. The file on sale is rebuilt from its tagged version in a clean environment and compared against the checksum recorded on the day of publication. Every link in the source register is checked for life in the same run.

Every published file is rebuilt monthly. The file on sale is rebuilt from its tagged version in a clean environment and compared against the checksum recorded on the day of publication. Every link in the source register is checked for life in the same run.

The source and the law are watched quarterly. Whether the publishing authority has corrected its own records, whether the legislation an edition cites has changed, and whether the licence terms have changed.

The source and the law are watched quarterly. Whether the publishing authority has corrected its own records, whether the legislation an edition cites has changed, and whether the licence terms have changed.

Not every finding is an erratum, and the line is stated here. If a published figure, chart, named entity, definition or conclusion changes, or if the content of a file in the licensed data pack changes, that is an erratum: it takes a new version number, it is recorded in the log above, and buyers are notified. If the source corrects its own data after our frozen extraction, that is not an erratum; the published edition is not retro-fitted, the change is recorded here and carried into the next edition's comparability table. If legislation cited in an edition later changes, that is not an erratum either; the text was correct on the date of publication and is bound to that date.

No errata. Edition 1 is not yet published.

No errata. Edition 1 is not yet published.