Repository navigation
Data accuracy: corrections, duplicates and dates (workstream) #296
Description
Purpose
Tracker for data accuracy: correcting existing values, merging duplicates, fixing dates and links. It is one of the workstreams split out of the #1 roadmap on 2026-09-27.
PRs that fix data (fix(data…), or label data + bug) link here with Closes #<this>. The tracker stays open.
Scope
- Cross-checks against Wikipedia and manufacturer spec pages (CPU, GPU, SoC, watch)
- Plausibility outliers (storage recorded as RAM, unit slips, impossible values)
- Duplicate or near-duplicate records (merging while keeping the better record)
- Placeholder dates (
YYYY-01-01) and placeholder SoC links - Removing values that turn out to be estimates (e.g. DX12 benchmarks on pre-DX12 GPUs)
Rules
- Only change a value when a source unambiguously gives the right one for that exact SKU or variant. If sources conflict, document the conflict instead of picking a side.
- Add the evidence URL to
source_urls; keepverifiedas it is. - Each fix PR lists its changed fields and the unresolved items in the body.
Status (2026-09-27)
| Area | Done | Open |
|---|---|---|
| Storage recorded as RAM | #257, #279, #281, #293 (~100 records) | 5 devices with no source stating RAM |
| SoC release dates | #287, #289 (182 records) | Kirin tables have no dates; coarse same-year dates |
| GPU cross-check | #260, #290 | 49 conflicts reviewed; no supportable fix |
| Intel CPU cross-check | #263, #266 (150 records) | 45 ambiguous slugs |
| Duplicates | #280, #282 (17 GPU pairs) | Near-duplicates in other categories not yet scanned |
| Placeholder SoC links | #271 (53 tablet "0" values) |
7,077 phone references to 51 generic SoC slugs; needs an external per-device source |
Reporting
One comment per batch: what was fixed, with counts and examples, and what stays unresolved.
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity