source-queue

What it does and when to use it

Triage the sources that feed DaTMech curation in curation/source_queue.tsv: add candidates, check licenses and access, rank, and decide what to adopt next. Use when asked what to curate from, whether a database or corpus is usable, or to plan bulk seeding.

How it works

1. Adding a candidate
2. Ranking
3. Adopting

---
name: source-queue
description: >-
  Triage the sources that feed DaTMech curation in
  curation/source_queue.tsv: add candidates, check licenses and access, rank,
  and decide what to adopt next. Use when asked what to curate from, whether
  a database or corpus is usable, or to plan bulk seeding.
---

# The source queue

`curation/source_queue.tsv` ranks the sources that feed curation. The
columns are explained in `curation/README.md`.

## Adding a candidate

For each source, find out and write down:

- **What it gives.** Which record sections it could fill, and for roughly
  how many records. Measure with a sample, not a guess.
- **License.** Read the actual terms. Write `UNKNOWN` if you could not find
  them. Never infer a license from a site's look.
- **Access.** API, bulk download, or pages only. Rate limits. Whether
  identifiers are stable.
- **Grounding.** Does it use CURIEs the schema accepts, or does it need
  mapping?

## Ranking

Rank by value per unit of effort, and say why in `notes`. A small, clean,
openly licensed source that fills a required section beats a large one that
needs mapping.

## Adopting

A source is `ADOPTED` when merged code or a written procedure uses it. The
pull request that adds the ingest code also changes the row. Ingest code
writes through `write_validated_record`, runs dry by default, and records a
history entry for each bulk change.

Bulk-seeded records start as `DRAFT`. Their evidence must still validate.
Seeding does not excuse a record from the evidence rules.

Versions

The database has no other skills named source-queue.

Identical content appears in 2 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 81003730df44 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

• 90extend-schema
  Change the DaTMech data model in src/datmech/schema/datmech.yaml: add, narrow, rename or remove a class, slot or enum, and migrate existing records. Use when a curation need has no place in the schema, or when deciding whether it warrants one. Not for filling existing slots.
• 90review-record
  Audit one DaTMech record, or a pull request that changes records, without editing anything. Use when asked to review, check, audit or assess a ZIP code area record or a curation pull request. Produces findings; changes nothing.
• 100curate-next
  Use when asked to curate the next N KG-Registry stub resources. Selects uncatalogued stub pages not already listed in reports/curation_problems.tsv and dispatches single-resource curation in parallel.
• 100add-source
  Add, fix or check a news source, YouTube channel or podcast in Hodi's sources.yml. Use when a contributor suggests a source or a feed stops working.