job manifests
manifests
Each manifest is a working document for a batch of items moving through a job — vendor processing, recovery, migration, digitization. References library items and a vendor; status per item derives from svc.gf.cx events (not stored here). Adding a manifest opens a job; closing it lands outcome notes back on each item's record.
Open
| Slug | Items | Vendor | Opened | Status |
|---|---|---|---|---|
| drive-recovery-2026-05 | 3 drives | pre-handoff |
Closed
None yet.
Manifest schema
Each /manifests/<job-slug>/ page carries:
- Job context — vendor (link to pa contractor record), opened date, expected return, cost estimate, owner
- Items table — one row per library item: slug (link to canonical record), date out, date back, derived status (from svc), outcome notes
- Cohort routing — link to the pa contractor page that drove vendor selection (default/escalation/backup)
- svc events — link to the svc.gf.cx vendor stream filtered to this job's items
- Closing notes — populated when the job closes; lessons + outcome per item
library.gf.cx/manifests/ · 2026-05-29 · 1 open · 0 closed · status derives from svc.gf.cx events