Preserve commas, quotes and line breaks through CSV exports — what should the operator record?
A public excerpt can contain commas, quotation marks and several lines. A manual split can turn one evidence object into several broken rows while still producing a file that looks tabular. Use a format-aware round trip and compare logical values before handing the export to another operator.
Test logical field round trips instead of splitting research text on delimiters manually.
Record delimiter, quoting convention, encoding and line-ending representation for the local export, using actual writer settings rather than assumptions. If a recipient requires a different delimiter, create a new checked representation rather than asking them to replace characters globally in an evidence file.
Include the checked import contract and unresolved application limitations so a recipient does not reopen the file with incompatible defaults. The delivery note should identify the logical schema and dialect, allowing the next operator to reproduce the import without guessing from their spreadsheet's local defaults.Declare the dialect
Record delimiter, quoting convention, encoding and line-ending representation for the local export, using actual writer settings rather than assumptions. If a recipient requires a different delimiter, create a new checked representation rather than asking them to replace characters globally in an evidence file.
Preserve structured fields
Map each source field to one logical cell and avoid replacing commas or newlines in the original text merely to simplify parsing. A field containing a quoted phrase should round-trip with its exact logical characters even though the serialized bytes contain additional escaping required by the CSV format.
Test difficult strings
Use labeled fixture text containing a comma, an embedded quote and a line break, then parse the written file back into values. Include an empty string and an explicit unavailable state in the fixture so the export does not collapse distinct evidence meanings while fixing punctuation handling.
Reconcile row integrity
Compare recovered qualified keys and field values with the permitted input, distinguishing representation quoting from changed source content. A physical-line count is not a record count for quoted multiline fields; derive actual parsed rows from the format-aware reader used in the check.
Deliver dialect instructions
Include the checked import contract and unresolved application limitations so a recipient does not reopen the file with incompatible defaults. The delivery note should identify the logical schema and dialect, allowing the next operator to reproduce the import without guessing from their spreadsheet's local defaults.
Keep the boundaries clear.
- Test logical field round trips instead of splitting research text on delimiters manually.
- Operational record: Declare the dialect. Context badges do not certify access.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.