Data & Analytics · By opensanctions

Scaffold a new PEP (Politically Exposed Persons) crawler — members of a parliament, legislature, senate, chamber of deputies, cabinet, judiciary, or an asset-declaration register — from a source URL…

opensanctions/opensanctions

Move hardcoded lookup/config constants (gender maps, header dicts, value translations, column-label maps, date formats) out of a crawler and into the dataset .yml — as datapatch lookups wherever…

opensanctions/opensanctions

Bring a dataset .yml's metadata in line with house conventions (title, summary, description, coverage, publisher, maintainer comments).

opensanctions/opensanctions

Refactor the title, description and coverage frequency of a legislature/parliament PEP dataset .yml into the house style.

opensanctions/opensanctions

Migrate ad-hoc name cleaning in a crawler to h.reviewnames (Step 1 of the name framework migration).

opensanctions/opensanctions

Rewrite messy or AI-generated crawler code into clean, production-ready style that follows the zavod best practices.

opensanctions/opensanctions

Release one or more datasets by adding them to a topical collection, bumping coverage.start, and verifying.

opensanctions/opensanctions

Fix mypy --strict type errors in crawler files. An agent skill from opensanctions/opensanctions.

opensanctions/opensanctions

Scaffold a new sanctions list crawler from a source URL or GitHub issue

opensanctions/opensanctions

Investigate a failing crawler and propose a fix, starting from a dataset name or an issues.json artifact URL.

opensanctions/opensanctions

Complete the name framework migration in a crawler (Step 3) by removing all custom name cleaning/splitting logic and the Step 1 review scaffolding, replacing it with a single…

opensanctions/opensanctions