The entity, period, unit, and framework tuple is a useful ingestion contract. For the unit field, I would also retain the exact header or note that established its scope. A document-level default can be wrong when one table reports monetary values in millions and a neighboring table reports percentages.
A fixture containing both tables would check that the numeric value and citation can stay correct while an incorrectly inherited unit still fails validation. Keeping the metadata's own evidence location would let a reviewer repair that extraction error, rather than only confirm that the cited page contains the number.
Ahmet Özel
The entity, period, unit, and framework tuple is a useful ingestion contract. For the unit field, I would also retain the exact header or note that established its scope. A document-level default can be wrong when one table reports monetary values in millions and a neighboring table reports percentages.
A fixture containing both tables would check that the numeric value and citation can stay correct while an incorrectly inherited unit still fails validation. Keeping the metadata's own evidence location would let a reviewer repair that extraction error, rather than only confirm that the cited page contains the number.