Export a batch of sample person records — generated server-side — as CSV (comma-separated values): one header row of field names, then one data row per person. CSV is the interchange format spreadsheets, Excel, Google Sheets, and many ETL jobs expect when you need flat tabular sample data.
How it works
Synthetic person objects (name, gender, birth date, contact fields, and related attributes) are serialized with peopleToCsv: column headers come from the object keys, each cell is stringified, and rows are joined with commas and newlines. Nested objects are JSON-stringified into a single cell so the grid stays rectangular. No server round-trip is required beyond generating the people themselves.
When to use it
- Seed CRM or mailing-list demos in spreadsheet tools
- Feed CSV-only upload forms during QA
- Share sample records with analysts who live in Excel
Limitations
CSV quoting is minimal—values containing commas or quotes may need manual cleanup in strict parsers. Nested municipality/country structures become opaque JSON strings in one column. Encoding is plain text; open files as UTF-8 in your spreadsheet. Batch size is capped server-side by the same limits as the generator subtool.
Example
Two people might export as:
firstName,lastName,gender,birthDate,email
Ada,Lovelace,F,1815-12-10,ada@example.com
Alan,Turing,M,1912-06-23,alan@example.com
Opening that file in a spreadsheet yields two rows under those column headers.