Expose independent event keys in integrated coverage reports
Metadata integrity checks / metadata (push) Successful in 1m48s
Metadata integrity checks / metadata (push) Successful in 1m48s
This commit is contained in:
@@ -42,3 +42,8 @@ The production event-key migration and optional annotation activation have not o
|
||||
at preparation time. Existing migration/import/repair acceptance remains valid; do not
|
||||
rerun those jobs to install source code. Cross-feature tests use disposable fixtures
|
||||
and PostgreSQL schemas, never the production research tables.
|
||||
|
||||
Coverage output also returns event_key for each independent edition ID. Two same-year
|
||||
main events keep their own status/source counts; venue paper totals remain distinct
|
||||
work counts rather than sums across events. Legacy datasets without the event column
|
||||
return an empty event key and remain read-only compatible.
|
||||
|
||||
Reference in New Issue
Block a user