Add Customer 360 industry demo

[amising6]

This PR adds a Customer 360 industry demo using fully synthetic data.

The demo shows how DQX can validate common Customer 360 data quality rules, including customer identity, email format, non-negative revenue, ticket count validation, date validation, and active customer flag consistency.

The contribution is limited to a new demo file under demos/dqx_demo_industry and does not modify core package code.

No real customer, client, employer, or proprietary data is included.

[CLAassistant]

All committers have signed the CLA.

[github-actions]

All commits in PR should be signed ('git commit -S ...'). See https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits

[amising6]

Thank you. I have signed the CLA and updated the PR with a signed commit.

Please let me know if you would like me to adjust the demo structure, naming, or any DQX rule usage to better align with the existing industry demos.

[ghanse]

@amising6 dqx_customer_360_demo.py is empty. Do you need to push it?

[amising6]

Thanks for catching that. I had created the file but missed saving/pushing the actual notebook content. I have updated the branch with the Customer 360 demo content now.

[ghanse]

Thanks for adding this — a Customer 360 accelerator is a nice fit next to the other industry demos, and using fully synthetic data is the right call. A few things to sort out before it's ready:

Blockers (the demo won't run as-is):

• is_unique needs columns: as a list, not column: — this fails at validate_checks and stops the notebook.
• name: is nested under check: on all seven checks, so DQX ignores it. It belongs at the top level next to criticality.

Worth fixing:

• The duplicate CUST-001 row means your "valid active customer" gets quarantined by the uniqueness check — give the dupe its own id.
• Swap the magic is_in_range ceilings for is_not_less_than on the non-negative checks.
• A couple of rows commented "Invalid" are warn-level and stay in valid_df; a one-line note would save new users some confusion.

Small stuff:

• Add a trailing newline at the end of the file (trips some linters).
• Add this demo to docs/dqx/docs/demos.mdx alongside the other industry accelerators so people browsing the docs actually find it.
• The "Why this matters" and "Practical Takeaway" sections repeat the same point — trim one.

Good concept and structure — just needs the two YAML fixes to actually execute, plus the cleanups above.

---

This comment was generated with GitHub MCP.

[mwojtyczka]

Left some comments. In general, I would expect this demo to show example of some more comprehensive checks.

[amising6]

Thank you for the detailed review. I have pushed an expanded version of the Customer 360 demo and addressed the requested changes.

The demo now includes 12 checks covering identity completeness and uniqueness, customer name and email completeness, email validity, customer status completeness and allowed values, non-negative revenue and ticket counts, purchase and campaign date validation, and cross-field active-status consistency.

I also corrected the DQX check syntax, removed the artificial range ceilings, separated the duplicate test records, clarified warning-level behavior, removed redundant documentation, and verified that validate_checks completes without errors.

Please take another look when convenient.

[mwojtyczka]

Inline review comments from a correctness pass. The main issues (first two) are that the demo teaches the opposite of DQX's actual split semantics; the rest are smaller.

[mwojtyczka]

Thanks for the fixes. 1 old comment is still not fully addressed and I added few more.

[amising6]

Hi, I have pushed the requested updates and addressed the latest review comments.

The changes include correcting the warning and quarantine explanation, using runtime-relative dates, updating the active-status flag description, and pinning the demo documentation link to v0.16.0.

I have also re-requested the review. Thanks again for the detailed feedback.

[mwojtyczka]

LGTM - i added the demo to the e2e tests