DUMPS.md — universal form-dump exports (the dump station)
Owner rule (round 24, binding): every form in the system can be dumped to Excel/CSV with filters drawn from that form's own fields. Dumps are NOT reports (see REPORTS.md §1): a report is the finished product placed at a workflow step; a dump is raw records for the long tail of analysis that does not have a prebuilt report yet, and for the team's own discovery. Dump exports are a must — they ship with every form.
1. The dump station (UI)
- One Dump section (utility, like the old software's Utility menu) listing every form. Opening a form shows its dump dialog: filters (auto-derived from the form's fields — see §3) → export (CSV / Excel .xlsx / PDF-print on request) with an as-of timestamp in the filename.
- Dumps are also reachable as an "Export" action on each form's own list screen (per the no-silo rule, the action lives where the form is; the Dump section is the index).
- Dump = all stored columns, raw (nothing computed-for-display hidden, nothing summarized), newest-first, filters applied. Deliberately labelled: the export header reads "DUMP — raw records, not a report".
- Role-gated (office/owner; floor roles get their own form dumps only).
2. The dump loop (discovery → build → retire)
- The team exports a dump from any form with date/party/quality filters;
- if the same dump keeps recurring, that is the signal for a missing in-system analysis — we build it as a tile/report placed at the workflow step (REPORTS.md §3);
- the recurring export retires (the tile replaces it); the raw dump itself stays available — it is the underlying layer, never removed.
So dumps are both the stopgap for unbuilt reports AND the sensor that tells us what the team needs built.
3. Per-form dump map (v1 — grows with each field deep-dive)
Filters marked always: from–to date. Others are per-form. Columns = the form's record set (final column list follows the FIELDMAP deep-dives).
| Form / screen | Plus-filters (beyond date range) | Notes |
|---|---|---|
| orders (SO / JW contract / production order) | type (trading/JW/prod), party, quality/design, status, broker | one row per order line (beam/mtr qty) |
| procurement need (A2) | yarn, setup, period | computed need per yarn (demand − free − in-transit) |
| samples / strike-offs | party, design, status (sent/approved/waived), follow-up date | |
| yarn-purchase-order (booking, B1) | supplier/mill (ticket), yantype/count, status open/partial/closed | |
| yarn-receipt (inward, B2) | supplier, mill, count, lot no, set no, GP no, contract | |
| allocate-stock | order, yarn, date | allocation history (soft) |
| yarn-movements (B5: issue/return/transfer/take) | type, from/to party · set · contract, yarn, lot | the exception ledger |
| gatepass (G0–G2) | source/target (trader/our godown/sizer/weaver/transporter), status (entered→…→reconciled), transport, vehicle | |
| warp-to-sizing / tippan (C1) | set no, sizer, weaver, status | |
| sizing-receipt (C2/C3) | set no, sizer, beam no range, status | two-step: beams-in + full recon |
| winding (C4) | winder, yarn, date | |
| beam-card (C5) | beam no, flange no, set, contract, loom, status | |
| beam-movements | beam no, from/to, date | |
| production-plan (D1) | loom no, loom type, contract, status (on-loom/floor/cut) | planning board rows |
| weft-issue (D2) | loom, shift, beam/design, type-of-issue, set no | the actual-consumption source |
| weaver-yarn-out / weaver-fabric-in (D3) | weaver, contract, mode | |
| loom-telemetry (D4) | loom, shift, event type | IoT events, read-only |
| rolling (D5) | beam, mode (one-to-many / many-to-one), date | |
| checking-rolls (E1) | beam, party, design, grade, status | grading rows |
| lumps-bales (E2) | grade F, bale no, date | |
| folding/mending (E3) | beam, date, pieces | |
| delivery-plan (F1) | SO, vehicle, date | |
| dispatch (F2) | party, SO, grade, vehicle, LR no, mode (roll/lump) | incl. balance qty |
| delivery-tracking (F3) | SO, status, date | |
| job-work hishob (A6) | contract, party, status (pending/sent/accepted) | statement + per-set summary rows |
| yarn hishob (party accounts) | party, yarn, FY | kgs + value layer |
| stock take (B7) | yarn, set, date | scan vs count + unmarked list |
4. Formats & integrity
- CSV (Excel-open) and .xlsx are the default pair; PDF/print only when a form's records are handed to an external party (still a dump — same raw columns).
- Exports carry an as-of timestamp and the filter values used, so any two exports are reconcilable.
- Numbering/report-period rules (FIELDMAP §10 q.17, transfer-year FY) apply to dump date filters — one decision, reused everywhere.
- The dump action is a first-class part of every form's build checklist: a form without its dump is not done.
5. Statement PDF exports (round 44)
- Hishob statements (job-work, sizing, winding) export as PDF archive from the dump station with filters: party · contract · status-history (pending/sent/accepted/objected-resolved) · period. Current statements are also one-click PDF/Print from the Hishob dashboard (Print unlocks only after the owner's final approval — BOARDS-A §6). The statement itself is a REPORT generated from events; dumps of the underlying records remain CSV/XLSX as anywhere else.