Customs data workspace
Data quality command center
Live demo
SR
Ask DataGuard
What should we investigate?
Uses schema, ownership, tags & lineage
Find data problems affecting customs clearance
✦
Analyze data
Press Ctrl + Enter to analyze. No production data is changed.
!
5
Issues found
Needs review
◆
3
Datasets affected
of 5 scanned
↗
2
Downstream assets
Potential impact
◷
94%
Agent confidence
High confidence
Prioritized findings
Issues requiring attention
all
high
medium
low
Cleared declarations without confirmed payment
high
public.clearance_records
17 clearance records are marked CLEARED while the related payment is not PAID.
›
Critical dataset has no registered owner
high
public.clearance_records
DataHub does not identify an accountable owner for clearance_records.
›
Tax identifier is not classified as sensitive
medium
public.importers.tax_id
The tax_id field has no sensitive-data tag or glossary term.
›
Payment lineage is incomplete
medium
public.clearance_report
The clearance report is linked to clearance_records but the payments dependency is missing.
›
Operational status field has no definition
low
public.shipments
shipments.status is missing a business description and accepted-value documentation.
›
Impact path
Clearance lineage
Analyzed Aug 9, 03:30 PM
PostgreSQL table
importers
3 columns
!
→
PostgreSQL table
declarations
5 columns
→
PostgreSQL table
payments
4 columns
!
→
PostgreSQL table
clearance_records
3 columns
!
→
Analytics view
clearance_report
2 consumers
!