Data Quality
SouqData publishes every correction, purge, and methodology change in a public changelog and carries source attribution on every extracted record. This page summarises current coverage, lineage completeness, and the most recent data events.
Recent events
No events logged.
Lineage coverage
Share of rows in each table that carry a populated source_type.
| Table | Rows | With source | Coverage |
|---|---|---|---|
| directors | 9,796 | 3,101 | 32% |
| director_appointments | 10,020 | 2,688 | 27% |
| management_team | 4,403 | 0 | 0% |
| announcements | 22,920 | 0 | 0% |
| related_party_transactions | 7,318 | 0 | 0% |
| executive_compensation | 537 | 0 | 0% |
| auditor_fees | 140 | 0 | 0% |
Coverage by exchange
| Exchange | Issuers | Director appts | Income stmts | Announcements |
|---|---|---|---|---|
| ADX | 98 | 667 | 64 | 1,726 |
| ASE | 205 | 1,657 | 167 | 0 |
| BHB | 17 | 124 | 20 | 0 |
| BIST | 568 | 0 | 0 | 1,839 |
| BK | 136 | 821 | 199 | 0 |
| DFM | 70 | 674 | 146 | 1,063 |
| EGX | 252 | 1 | 21 | 0 |
| ISX | 102 | 0 | 0 | 0 |
| MSX | 85 | 502 | 30 | 0 |
| QSE | 55 | 1,628 | 1,338 | 16,609 |
| TDWL | 385 | 3,946 | 1,350 | 1,683 |
How we handle corrections
When we discover an extraction error or purge records, the event is recorded inthe changelogwith severity, affected tables, root cause, and remediation. API clients can pin to a snapshot using the X-Data-Version response header and subscribe to /api/v1/data-quality/changelog?severity=criticalto be alerted to breaking corrections.