Elysia Tools
Navigation
Workflow Playbook
Parse fixed-width records, messy delimited text, logs, Markdown tables, and HTML tables into CSV, JSON, XML, or Excel with reviewable cleanup steps.
Hubs
Semi-structured extraction fails when every input is treated as plain CSV. A fixed-width report, a mixed-delimiter support export, a Markdown table, and a logfmt trace each need a different first move. Use fixed-width-column-parser, messy-text-to-structured-data-workbench, or structured-log-analyzer to classify the source and preserve a few representative rows before changing anything.
The safest workflow separates cleanup from conversion. Use text-pipeline-builder to trim whitespace, remove repeated headers, standardize separators, and make the transformations repeatable. This prevents a one-off manual fix from hiding the exact rule that changed the data.
Once the text is stable, choose the export format deliberately. text-to-csv and text-to-excel are best for analysts, text-to-json is useful for APIs or fixtures, and text-to-xml fits schema-oriented exchange. For existing tables, use markdown-to-csv or html-table-to-csv so cell boundaries are preserved instead of re-parsed from raw text.
Logs and malformed rows need their own review pass. Use log-parser, logfmt-to-json-structured-log-bridge, and structured-log-analyzer to keep event fields consistent, then run csv-malformed-row-surgeon when row lengths or quoting issues would break an import. A complete handoff includes the parser assumptions, row counts, repaired records, and known exceptions.
Workflow playbook
Identify whether the evidence is fixed-width text, inconsistent delimited records, pasted tables, or log lines, then keep a small failing sample for validation.
Build a repeatable cleanup pipeline for trimming, splitting, replacing noise, and stabilizing separators before records are exported.
Export normalized text or extracted Markdown and HTML tables into the target interchange format while preserving headers and cell boundaries.
Handle application, web, and logfmt records separately, then repair malformed CSV rows and recheck the final table before delivery.
Use fixed-width parsing for aligned records, messy-text tooling for inconsistent delimiters, log tools for event lines, and Markdown or HTML extraction for embedded tables.
Normalize first when whitespace, quoting, mixed separators, repeated headers, or broken rows could shift columns during conversion.