How alan-przybylski/python_dq_application works
DQ Studio is a local Tkinter data-quality workspace. Its principal workflow imports CSV or Databricks data into SQLite, prepares datasets, defines SQL rules, runs checks, and presents traceable results for investigation and export. Additional branches cover user and ticket management, SQL preview, rule-file exchange, and independently scheduled Databricks checks. Edges use README workflow statements and SOURCE INDEX references; unsampled subsystem details and relationships are not inferred beyond those references.
Main entry points: data_quality.py Workspace windows · connection.py Local SQLite · import_window.py Import interface · check_dq_panel.py Quality report
Components 23
Desktop workspace
- App entry
main.py - Sign-in
ui/login_window.py - Workspace windows
ui/data_quality.py - Account management
logic/accounts.py - SQL workspace
ui/sql_workspace.py
Dataset management
- Import interface
ui/import_window.py - Dataset import/export
logic/datasets.py - Table editor
logic/table_editor.py - Databricks interface
ui/databricks_window.py - Snapshot downloads
logic/databricks_import.py
Quality workflow
- Rule details
ui/rule_details.py - Rule management
logic/rules.py - Rule file exchange
logic/rule_files.py - Check runner
logic/dq_engine.py - Quality report
ui/check_dq_panel.py - Run reports
logic/dq_report.py - DQ tickets
logic/tickets.py - Ticket interface
ui/tickets_window.py
Persistence and integrations
- Remote checks and sync
logic/databricks_sync.py - Databricks contract
integrations/databricks_contract.py - Scheduled job
databricks_dq_job.py - Local SQLite
database/connection.py
Other components
- Desktop user
Connections 27
- Desktop user → App entry: launches
README.md - App entry → Sign-in: opens
main.py - Desktop user → Workspace windows: uses
README.md - Workspace windows → Import interface: opens import
- Import interface → Dataset import/export: imports CSV
ui/import_window.py - Dataset import/export → Local SQLite: writes data
logic/datasets.py - Import interface → Table editor: opens editor
ui/import_window.py - Import interface → Databricks interface: opens download
ui/import_window.py - Databricks interface → Snapshot downloads: downloads snapshot
ui/databricks_window.py - Snapshot downloads → Local SQLite: saves snapshot
logic/databricks_import.py - Workspace windows → Rule details: opens rules
ui/data_quality.py - Rule details → Rule management: edits rules
ui/rule_details.py - Rule details → Rule file exchange: exchanges files
ui/data_quality.py - Workspace windows → Quality report: opens checks
ui/data_quality.py - Quality report → Check runner: runs checks
ui/check_dq_panel.py - Check runner → Local SQLite: reads and records
logic/dq_engine.py - Check runner → DQ tickets: syncs tickets
logic/dq_engine.py - Quality report → Run reports: loads reports
ui/check_dq_panel.py - Workspace windows → Ticket interface: opens tickets
README.md - Ticket interface → DQ tickets: manages tickets
README.md - Sign-in → Account management: authenticates
- Account management → Local SQLite: reads and writes
logic/accounts.py - Workspace windows → SQL workspace: opens editor
README.md - Quality report → Remote checks and sync: starts remote checks
ui/check_dq_panel.py - Remote checks and sync → Databricks contract: builds payload
logic/databricks_sync.py - Remote checks and sync → Local SQLite: stores mappings
logic/databricks_sync.py - Scheduled job → Remote checks and sync: uses runner
databricks_dq_job.py