Document the data pipeline and licence obligations #74

Closed
opened 2026-09-26 13:59:00 +00:00 by belvedere · 1 comment
Collaborator

Objective: Attribution and provenance are legal requirements for the upstream corpora, and
future-you will not remember where the rows came from.

Files:

  • Create: docs/data.md
  • Modify: README.md (link + attribution section)

Steps:

  1. For each upstream source: URL, licence, retrieved date, transformation applied, and where its
    provenance is recorded on the row.
  2. State the attribution shown in the app UI.
  3. Note the reproducible command sequence to rebuild the dataset from scratch.

Verify: a reader can rebuild the dataset by following docs/data.md alone.

Caution: verify each licence at the time of writing — the frequency corpus was MIT when
checked, but Wiktionary-derived data carries share-alike obligations. Do not assert licences
from memory; check the upstream repository.

**Objective:** Attribution and provenance are legal requirements for the upstream corpora, and future-you will not remember where the rows came from. **Files:** - Create: `docs/data.md` - Modify: `README.md` (link + attribution section) **Steps:** 1. For each upstream source: URL, licence, retrieved date, transformation applied, and where its provenance is recorded on the row. 2. State the attribution shown in the app UI. 3. Note the reproducible command sequence to rebuild the dataset from scratch. **Verify:** a reader can rebuild the dataset by following `docs/data.md` alone. **Caution:** verify each licence at the time of writing — the frequency corpus was MIT when checked, but Wiktionary-derived data carries share-alike obligations. Do not assert licences from memory; check the upstream repository.
Author
Collaborator

Duplicate of #22 — created by a re-run whose pagination helper only saw the first page of issues. Closing to keep the backlog clean. Repo owner can delete this outright.

Duplicate of #22 — created by a re-run whose pagination helper only saw the first page of issues. Closing to keep the backlog clean. Repo owner can delete this outright.
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
nickkeers/first-thousand-words#74
No description provided.