Skip to content

EU Journal Sanctions: Operational Guide

EU sanctions take legal effect the moment they are published in the EU Official Journal (EUR-Lex), but the consolidated XML feed consumed by the eu_fsf and eu_sanctions_maps crawlers has historically lagged by days or even weeks. OpenSanctions bridges this gap via a manual workflow: an operator extracts entity tables from EUR-Lex amendment pages and pastes them into a Google Sheet, which the eu_journal_sanctions crawler reads every two hours. See the blog post for the public-facing explanation.

The Google Sheet is at: https://docs.google.com/spreadsheets/d/1rauQMdCYTjTwmSzqfUvur1SfkCGYwfRn6_e5_oX39EY/edit?gid=0

Monitoring for amendments

A cron job watches for new amendments to the legislation listed at https://www.sanctionsmap.eu/#/main and posts a Slack message when one is found, e.g.:

New document on EUR-Lex regarding 'Restrictive measures in view of Russia's actions…': Commission Implementing Regulation (EU) 2026/124 of 14 January 2026 amending Council Regulation (EU) No 833/2014… https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32026R0124

Previously seen amendments are stored at https://github.com/opensanctions/eu_journal.

Claiming work

Add the 👀 emoji to the Slack message to signal that you are handling it. This prevents duplicate effort when multiple operators are watching the channel.

Evaluating an amendment

Most amendment packages consist of a Council Decision and an Implementing Regulation published on the same day. Process the pair only once — prefer the Regulation over the Decision.

For each Slack message, decide:

Situation Action
Amendment adds or modifies entities Extract tables and add to the Google Sheet (see below)
Amendment removes entities Delete matching rows (same entities, same sanctions program) from both the Unconsolidated and Context sheets
Amendment is procedural, a correction, or otherwise has no entity changes Add 🚫 to the Slack thread
Already handled as the paired document Add 🚫 to the Slack thread

When all items in an amendment are fully handled, copy the new rows to the Context worksheet, and add ✅ to the Slack thread.

Extracting tables from EUR-Lex HTML

EUR-Lex uses Cloudfront WAF that blocks direct HTTP fetches. Save the amendment page manually:

  1. Open the EUR-Lex URL from the Slack message in a browser.
  2. Save as HTML Only (not "Web Page, Complete").
  3. Run the extraction script from the project root:
python datasets/eu/journal_sanctions/extract_tables.py --path /path/to/saved.htm

The script outputs one CSV per entity table: {doc_reference}_table_{i}.csv. It prints a summary of tables extracted and skipped (layout-only tables are skipped automatically).

  1. Open each CSV in a spreadsheet editor and inspect the columns before copying.

Note: The script also supports --url for direct fetching, but this fails when Cloudfront blocks the request.

Adding data to the Google Sheet

Target worksheet: Unconsolidated (the first tab, gid=0).

Copy the rows from the CSV into the sheet, matching the column layout. Key rules:

  • Multiple values in a single cell are semicolon-separated (e.g. John Smith; Ivan Petrov).
  • Leave the schema column until last. The crawler cannot emit an entity without a schema, so the crawler fails with an error preventing exporting partially-edited data.
  • Be careful with fill-down on source URLs. Google Sheets auto-increments the last number in a URL when you drag-fill a cell. Hold Ctrl (Windows/Linux) or Option (Mac) while filling down to copy the value literally without incrementing.
  • Check every row. Pasting a value into the wrong column emits incorrect entity data. Double-check the column headers before and after pasting.

Verification

The eu_journal_sanctions crawler runs on a 0 */2 * * * schedule (every two hours). After the next run, check data/datasets/eu_journal_sanctions/issues.log for any parsing errors or unexpected warnings related to your new rows.