dpla

Workflow for generating and sending DPLA monthly pre-ingest emails to hub partners via AWS SES. Use this skill whenever someone asks to: send the monthly ingest email, prepare the DPLA pre-ingest notice, generate the hub email for a given month, preview the pre-ingest email, or do anything involving the pre-ingest email pipeline. Trigger even if the user just says something like "time to send the ingest email" or "it's email day" — context from the project makes the intent clear.

Run Community Webs ingest. Use when the user says harvest community-webs, run community-webs ingest, export community webs, or process community webs DB.

Remove DPLA items from the live site and search index in response to takedown requests. Use when the user says take down, delete, remove item(s) from dp.la, or action a takedown request. Accepts DPLA IDs directly or criteria (hub, institution, collection) to generate an ID list. Includes mandatory pre-flight verification, search-before-delete on Elasticsearch, and post-deletion confirmation with count delta verification.

Show key i3.conf config for a hub (provider, harvest.type, harvest.endpoint, schedule, email, setlist). Use when user asks for hub config, harvest type/endpoint, who gets emails, schedule months, or OAI setlist details.

Debug and fix DPLA hub ingestion failures (harvest/mapping/enrichment/jsonl/s3-sync/anomaly). Use when user asks why a hub failed, to debug an ingest failure, check an escalation report, or retry a failed hub/stage.

Show all active and completed ingests in one consolidated view. Use when user asks status of the ingests, ingest status, which hubs are running, show active ingests, or ingest progress.

Monitor a running IngestRemap (remap.sh / ingest.sh step 2) or orchestrator remap stages. Use when user asks whether mapping/enrichment/jsonl is done yet, to monitor remap progress, or to check which stage is currently running.

Generate/preview/draft/send the monthly pre-scheduling summary email to hub contacts scheduled for a month (from i3.conf schedule.months). Use when user asks to send the scheduling email, monthly scheduling email, notify hubs for a month, or pre-scheduling email.

Deploys the Black Women's Suffrage site (blackwomenssuffrage.dp.la) to production. Use this skill whenever the user wants to deploy, push, release, or ship changes to blackwomenssuffrage.dp.la or the "BWS site" — phrases like "deploy BWS", "deploy black women's suffrage", "push BWS to prod", "update the suffrage site", or "run the BWS pipeline".

Deploys a pull request to the live analytics-dashboard.dp.la site (dpla/dashboard-analytics repo). ALWAYS use this skill — never run deploy steps manually — whenever the user mentions deploying, shipping, pushing, merging+deploying, or releasing changes for the analytics dashboard. Trigger phrases include: "deploy PR 201", "ship this to analytics dashboard", "push PR X to production", "deploy to analytics-dashboard.dp.la", "kick off a deployment", "merge the PR and deploy", "deploy the analytics dashboard", or simply "deploy" in the context of the dashboard-analytics repo, even without a PR number. IMPORTANT: The ECR image must be built before the PR is merged — never merge first. This skill enforces the correct order.