docs/ai-context/archive/cursor-skills/dpla-ingest-status/SKILL.md
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.
npx skillsauth add dpla/ingestion3 dpla-ingest-statusInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
data-ai
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.
development
Run Community Webs ingest. Use when the user says harvest community-webs, run community-webs ingest, export community webs, or process community webs DB.
testing
Verify ingest outcomes and send failure or status notifications to Slack or [email protected]. Use when the user asks to verify the ingest, check if it succeeded, notify about a failure, or post to tech-alerts.
business
Report which hubs have new JSONL staged in S3 for a given month, and optionally post the report to Slack. Use when user asks what hubs are staged/ready for indexing, /ingest staged, or what changed this month in S3.