القائمة
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.
التثبيت باستخدام 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-ingest-status |
| description | 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. |
Show ingest status for all hubs (or specific hubs) in one command. Reads logs/status/*.status files — no per-hub log tailing.
Run one command:
source .env
./scripts/status/ingest-status.sh
For live updates:
source .env
./scripts/status/ingest-status.sh --watch
logs/status/*.status and logs/orchestrator_state.json. Ensure ingests use harvest.sh, ingest.sh, or the orchestrator (all write status). For debugging failures, use the dpla-ingest-debug skill instead.| Option | Purpose |
|---|---|
| (none) | Table view, all hubs |
--watch | Auto-refresh every 30s |
--watch 10 | Auto-refresh every 10s |
-v | Include stage history |
--json | Raw JSON output |
--all | Include stale entries (e.g. stuck >72h) |
hub1 hub2 | Show only specified hubs |
Status comes from:
logs/orchestrator_state.json (latest run's hubs)logs/status/*.status (written by orchestrator, harvest.sh, ingest.sh, remap.sh)Stale entries (e.g. a hub stuck in S3 Sync for >72h from a previous run) are excluded by default; use --all to include them. Manual runs (run_id=manual) are always shown.