fix(exporter,importer): resolve legacy-vs-viewer gaps found in islamicart audit (#1423)

Commit: 2ddd157eafe21d4208d848e9330c1033cfd62aa4
Date: 2026-07-05 20:02:53 +0000
Author: PascalHavelange

Commit Message

fix(exporter,importer): resolve legacy-vs-viewer gaps found in islamicart audit (#1423)

- partner-exporter: require collection_partner.level IS NOT NULL so generic
  item-owner institutions (e.g. Ministry of Culture) no longer leak into the
  curated Partners list (was 12 institutions, legacy shows 2)
- partner/institution-hierarchy-importer: give each tier-1 partner_museums/
  partner_institutions row its own per-context group Collection and attach
  associated/further-associated partners to it, reusing the existing
  Collection/collection_partner model (collection_type='collection') instead
  of a new schema field; partner-exporter now derives parent_id from it
- dynasty-exporter: export all project dynasties directly instead of only
  ones linked to a cataloged item (legacy shows 60 for ISL, was 43)
- glossary-exporter: scope glossary.json to terms actually referenced by this
  project's items/collections/timeline-events instead of shipping every
  project's glossary; item-exporter now includes glossary_ids per item
- import-tool: add local-glossary-sync compose service to run glossary:resync
  + drain its queue inline against local-mysql, so link rows are already
  part of the dump before ship — ship no longer relies on OVH's
  inventory-queue.service to resync after the fact
EOF

Co-authored-by: Pascal HAVELANGE <havelangep@hotmail.com>

Files Changed


This documentation was automatically generated from Git commit data.