Case Summary

What this is

Case Summary turns a GMIAU case-summary export into the canonical gmiau-case-summary/1 JSON that other tools: Letter, Court Doc, Bundle Builder, and Evidence Exhibitor, use to auto-fill client and matter details. Paste the markdown text, drop a Case Summary PDF, or type the details out by hand, and it produces a ready-to-save JSON file.

Typical workflow

1. Open the CMS and export (or copy) the case summary for the client.
2. Go to the Convert tab and choose your source: Paste text for markdown, Drop PDF / JSON / HTML for an export, or Type it out to enter the details by hand.
3. Paste the markdown into the text area, or drop one or more Case Summary PDFs onto the drop zone.
4. Click Convert JSON (text) or wait for the automatic parse (PDF). The Detected fields panel shows what was extracted.
5. Check the detected fields: look for any that read undefined or look wrong, and note them for manual correction if needed.
6. Every convert automatically saves all three files: the .json, the one-page .pdf, and a new editable .html sheet: named to your Config pattern (default stem {ref} Case Summary {date}). The buttons in Detected fields re-save any one on demand.
7. Drop the files into ~/Work/00 Open Cases/Case Summaries/ (or wherever your tools look) so they are available to Letter, Court Doc, and other tools' Import Case Summary pickers. All three re-import here: drop the .html, .json or .pdf back in.
8. To correct a summary later, open the .html sheet, edit the fields, and press Save sheet: it saves over itself (or re-downloads) and stays re-importable everywhere.

The tabs

Convert

The main workspace. Choose Paste text to paste a markdown case summary, Drop PDF / JSON / HTML to drag one or more existing summaries (a CMS PDF, a gmiau-case-summary/1 JSON, or a saved editable HTML sheet), or Type it out to fill in a form by hand when there's no export to work from. Each convert auto-saves the JSON, PDF and editable HTML together; the right panel's buttons re-save any one, or copy the JSON. In batch mode you can process several files at once and Download all (JSON + PDF + HTML) saves every result's three files in one click. To add key dates, drop an AdvicePro Case Key Dates CSV alongside (or after) a summary: its rows are matched to the summary by client name and render as a dedicated Key Dates page in the PDF, editable in the HTML sheet. One CSV can hold several clients and still feed a batch.

Config

Set the output filename pattern. The default is {ref} Case Summary {date}.json; you can change it here and it will persist across sessions. The pattern supports {ref} (case reference) and {date} (today's date).

Settings

App appearance (light / dark / system, theme family) and the app font. These settings sync across every GMIAU Shell tool.

Tips & gotchas

• Markdown format matters. The parser expects the CMS's ### Client / ### Case / ### References section headings. Plain Label: value exports also work.
• PDFs are parsed via pdf.js: the text layer must be present (scanned images without OCR will not extract any fields).
• Batch PDF mode processes each file independently. Download all saves the JSON + PDF + HTML for every result in one click.
• The three files are interchangeable. JSON, PDF and the editable HTML sheet all carry the same gmiau-case-summary/1 data and all re-import here (and into Letter, Court Doc, etc.). The HTML sheet is the one you edit: it saves over itself.
• Save the files to the right folder. The canonical location is ~/Work/00 Open Cases/Case Summaries/: that is where Letter and other tools look by default.
• If a field reads blank or wrong, edit it in the consuming tool (Letter, Court Doc) after importing, the converter reflects exactly what the CMS exported.

Questions

Q. The reference field is blank.
A. The CMS export may use a different label spelling. Check the raw JSON (Show raw JSON button) and confirm the field name the parser is looking for matches your CMS version.

Q. Can I drop multiple PDFs at once?
A. Yes: switch to Drop PDF mode, drop several files, and use Download all JSON to get them in one go.

Q. Where should I put the output JSON?
A. Drop it into ~/Work/00 Open Cases/Case Summaries/ (symlinked as 02 Summaries/). Tools that import a case summary scan that folder automatically.

More: the GMIAU Caseworker User Guide in your Obsidian vault covers the full case-summary workflow and which tools consume the JSON., Confidentiality: this tool runs entirely in your browser; nothing is uploaded. The case reference, client name and all field values are confidential, keep the produced JSON on this machine and handle it through your normal channels.