ores.qt.dq

ores.qt.dq is the single Qt plugin for every entity owned by ores.dq: badge definitions/severities, code domains, coding schemes and their authority types, catalog, change reason and change reason category, data domains, subject areas, datasets, dataset bundles, methodologies, origin/nature/treatment dimensions, artefact types, plus the Data Librarian window. It absorbed the entities and controllers that had briefly lived in the now-deleted ores.qt.data_management stepping-stone plugin. Most entities are fully codegen-driven (domain/protocol/repository backend plus Controller/DetailDialog/MdiWindow/ClientModel Qt layer); the remainder are commissioned by hand pending their own codegen model. History browsing is served by the generic HistoryDialog, routed server-side through the shared history/diff registries rather than per-entity hand-written dialogs.

• NATS responses from the ores.dq service (get/save/delete/history requests for every owned entity).
• User interactions: create/edit/delete/view-history across all owned entities.
• shared_menus_context pointers for the Data Quality top-level menu and the shared Data Transfer menu (Data Librarian contribution).

• Rendered MDI windows, detail dialogs, and the generic history dialog for every owned entity.
• Data Quality top-level menu (Badges, Classifications, Audit Trail, Data Catalogue submenus), returned via create_menus.
• NATS request messages sent to the ores.dq service on user actions.

• include/ores.qt/DqPlugin.hpp — plugin class; menu and controller owner.
• include/ores.qt/CatalogController.hpp — representative entity controller (each owned entity has its own).
• include/ores.qt/DataLibrarianWindow.hpp — bulk ORE-data import window, contributed to the shared Data Transfer menu.

• ores.qt.api — IPlugin, base controller/window/dialog classes, ClientManager, generic HistoryDialog.
• ores.dq.api — domain types and NATS protocol schemas for every owned entity.

• Qt Plugin Architecture — two-phase plugin loading, IPlugin contract, and MDI patterns.
• Entity Controller Pattern — how domain controllers, windows, and dialogs are structured.
• ores.qt.api — shared Qt infrastructure and base classes.