paper-atlas/docs/joint-editions.md

Repairing joint conference membership

EURAI's official history identifies ECAI 2018 and 2022 as joint IJCAI/ECAI conferences. The pinned DBLP volumes conf/ijcai/2018 and conf/ijcai/2022 use IJCAI as their booktitle and title. Existing records can therefore already be present under IJCAI while an ECAI query shows a missing year. Adding ECAI as a global alias to the ordinary IJCAI venue would incorrectly include all other IJCAI years.

The existing canonical ECAI+IJCAI venue has both member aliases. This maintenance command changes only the venue reference of the two existing main edition rows. Edition IDs, submission IDs, decisions, source text, authors, identifiers, tags, source links and coverage records stay intact. It does not merge or create papers or submissions, resolve per-paper tracks, or turn reviews into negative decisions. The DBLP collector applies the joint mapping only to these two exact main volume keys; original booktitle/title remain in source metadata with the membership evidence. The shared ingestion entry point also resolves these exact pinned source volumes before creating an edition, so refreshing an older normalized file cannot recreate a separate IJCAI edition. Other sources, years, workshop volumes and additional tracks retain their existing rules.

Review a read-only plan

Use a runtime containing this repair command. The configured PostgreSQL writer lock is used only for the apply operation; do not replace a newer ingestion runtime with an older main-based feature branch.

PGSERVICEFILE=/etc/paper-atlas/pg_service.conf paper-atlas maintain joint-editions \
  --pg-service foundry-research --pg-schema research --out joint-plan.json

The preflight requires the existing joint venue and exactly its two member aliases, one nonempty unambiguous edition per year, and matching pinned DBLP volume evidence for every existing submission. A colliding target edition, missing provenance or unexpected source scope fails closed. The plan binds current database/schema, IDs, counts and full fingerprints of affected papers, identifiers, source records, tags, submissions, decisions and their provenance, and coverage rows. Observation time is recorded separately from conference year. These are scoped checks, not a final global identity or conference completeness audit.

Apply the exact reviewed plan

Compute the file's SHA256 after review and pass it explicitly:

PGSERVICEFILE=/etc/paper-atlas/pg_service.conf paper-atlas maintain joint-editions \
  --pg-service foundry-research --pg-schema research --plan joint-plan.json \
  --plan-sha256 "$PLAN_SHA256" --out joint-applied.json

The plan hash is checked before opening a writer. Current evidence is checked again under the dataset writer lock; both edition updates and an audit marker commit in one transaction. Protected row hashes are checked again before commit. Changed evidence requires a fresh reviewed plan. Existing output reports are preserved; choose a new path for another run. SQLite samples use --db sample.sqlite; the frozen production backup remains protected.

If a response is lost after commit, rerun with the same plan and a new output path. When protected evidence is unchanged and both editions already point to the joint venue, the result is already_joint with zero updates. It does not replay imports or regenerate source records. Keep the plan, apply report and independent postcheck alongside collection evidence. The audit marker is joint_ijcai_ecai_2018_2022_v1.

Publication counts can differ between the DBLP volume and the current publisher page. This membership repair preserves all existing rows rather than deleting entries to force an aggregate match; section-level main/invited/other classification and publication completeness require separate per-paper evidence.