Sources
Source registry, ingestion and entity resolution
SPEC §26.4 requires complete source provenance. Every record in the database points at a source document, and every supplied file is registered with its SHA-256 so the artefact the figures came from stays identifiable.
Supplied source files
| File | SHA-256 | Retrieved |
|---|---|---|
| primarywave-artist-news.csv | c02ad2f27503212d5b4096cc9aad380d… | 2026-10-22 |
| primarywave-artist-playlists.csv | 1b3b24543eea16896e517408c01ab653… | 2026-10-22 |
| primarywave-artist-tracks.csv | 09ba32d7c3a60403cc467dc84a381824… | 2026-10-22 |
| primarywave-artists-full.csv | b972eed8525a8df62226c7a14c89bc3b… | 2026-10-22 |
| primarywave-artists.csv | 00158aca6b254d8b3c5962ce234291d6… | 2026-10-22 |
| primarywave-news-posts.csv | d61df31c0459e97d1d6281e566212d83… | 2026-10-22 |
Supplied by the project owner on 2026-10-22, already extracted. Not re-scraped. See data/source/PROVENANCE.md.
Source documents by type
| Source type | Retrieval method | Documents |
|---|---|---|
| news post | supplied file | 804 |
| artist profile | supplied file | 178 |
| playlist embed | supplied file | 2 |
| artist directory | supplied file | 1 |
| company website | supplied file | 1 |
Ingestion jobs
The ingest is idempotent: every primary key is derived from the record’s natural key, so re-running on an unchanged dataset writes the same rows and changes no count (SPEC §26.13). Each stage can be re-run alone.
| Stage | Job | Kind | Status | Read | Written | Skipped | Notes |
|---|---|---|---|---|---|---|---|
| 2 | artists | extraction | succeeded | 178 | 178 | 0 | — |
| 2 | company | extraction | succeeded | 1 | 1 | 0 | — |
| 2 | news | extraction | succeeded | 1,692 | 1,692 | 0 | — |
| 2 | playlists | extraction | succeeded | 6,653 | 6,545 | 0 | — |
| 3 | recordings | normalization | succeeded | 6,545 | 6,545 | 0 | — |
| 4 | entity-resolution | entity resolution | succeeded | 7,694 | 3,919 | 3,775 | high 3742, medium(candidate) 177, unresolved 3775 of which ambiguous 0 |
| 7 | exceptions | quality assurance | succeeded | 0 | 16 | 0 | — |
Entity resolution (SPEC §12)
3,504 of 6,409 recordings have a primary artist matched to a known Primary Wave artist at high confidence. The remainder are credited to artists who are not in the directory — other artists on the same playlists — which is the expected outcome, not a failure.
Recording credits by resolution status
| Status | Confidence | Credits |
|---|---|---|
| resolved | high | 3,742 |
| candidate | medium | 177 |
| unresolved | low | 3,775 |
A candidate match is never counted as resolved. SPEC §12 forbids automatically merging low-confidence matches, so a candidate waits for review.
Artist aliases by status
| Status | Aliases |
|---|---|
| accepted | 178 |
| candidate | 6 |
An accepted alias may be used for lookup. A candidate alias may not, until a reviewer promotes it.