菜单
Verify ingest outcomes and send failure or status notifications to Slack or tech@dp.la. Use when the user asks to verify the ingest, check if it succeeded, notify about a failure, or post to tech-alerts.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
| name | dpla-verify-and-notify |
| description | Verify ingest outcomes and send failure or status notifications to Slack or tech@dp.la. Use when the user asks to verify the ingest, check if it succeeded, notify about a failure, or post to tech-alerts. |
After a run or when something fails, verify pipeline output and ensure the right people are notified (Slack #tech-alerts or email tech@dp.la).
Environment: For commands that run the orchestrator or scripts, ensure source .env has been run in the shell so JAVA_HOME, SLACK_WEBHOOK, etc. are set.
Each step writes _SUCCESS when complete:
ls $DPLA_DATA/<hub>/harvest/<timestamped-dir>/_SUCCESS
ls $DPLA_DATA/<hub>/mapping/<timestamped-dir>/_SUCCESS
ls $DPLA_DATA/<hub>/enrichment/<timestamped-dir>/_SUCCESS
ls $DPLA_DATA/<hub>/jsonl/<timestamped-dir>/_SUCCESS
cat $DPLA_DATA/<hub>/harvest/<timestamped-dir>/_MANIFEST
cat $DPLA_DATA/<hub>/mapping/<timestamped-dir>/_SUMMARY
When the orchestrator has failures, it writes:
data/escalations/failures-<run_id>.md — human-readabledata/escalations/failures-<run_id>.json — machine-readablels data/escalations/
cat data/escalations/failures-*.md | tail -1
| Stage | What to report |
|---|---|
| Harvest | Feed unreachable, timeout, or harvest step failed |
| Mapping/remap | Mapping or IngestRemap failed (non-zero exit, no output) |
| Sync | S3 sync failed or was blocked |
| Anomaly | Anomaly detection halted sync (critical threshold) |
Include: hub name, stage that failed, one-line error or path to logs/escalation report.
SLACK_WEBHOOK is set. Post a short message: hub, stage, error or link to report.When using the orchestrator, it posts failure alerts automatically; when running scripts manually, you (or the agent) must post or email.
To verify webhooks without running an ingest:
source .env
./venv/bin/python -m scheduler.orchestrator.main --dry-run-notify
Messages are sent with a [TEST] prefix.