Skip to content
Interface language: English
Design / Signal

Data export: a file must preserve meaning, not just row count

A table export is an agreement with the next program. Design the choice of columns, codes, units and missing values, then test the finished file.

Article language: English

In a garden at night, a woman examines an illuminated white petal beside a sleeping cat.
In this article

The screen says "For review", while the downloaded file contains the number 2. A length is shown as 120 cm in the table, but only 120 remains after export. Both representations may be technically correct, yet the recipient needs to know what they mean. Export moves data somewhere else. The readable screen does not automatically travel with it.

We will work with a hypothetical inventory of workshop equipment. The required records have already been selected. Now their form must be prepared for the next person or application: columns, representations of values and the way the file will be read. The finished file should serve the task even when its recipient has never seen our table.

Name the use before choosing an extension

One recipient wants to review equipment and add a note. Another needs the same set for import into an inventory system. The first expects recognisable labels; the second needs stable identifiers and agreed value types. One file can serve both tasks, but it does not do so by definition. Its contents need a deliberate decision.

A menu saying only "CSV, XLSX, PDF" asks users to make a technical choice without explaining its effect. It is better to connect formats to uses the application actually supports. "Data for import" and "Report for reading" help people choose if the application really prepares those variants. They should not be new names for an identical file whose properties nobody has checked.

In our example, the readable report shows equipment name, status and length with its unit. An importer version may also need a status code and a separate unit field. The option description should make that difference clear. A user need not know the technical schema, but should know whether the chosen form is fit for the next action.

Do not assume every visible screen element belongs in the export. A thumbnail, an open button and a colour indicating status perform interface roles. The file needs appropriate data that preserves meaning without those decorations. Cell colour alone should not be the only information about whether equipment can be issued.

In a saved table view (in Polish), someone may have hidden certain columns. The export should explain whether it respects that layout or offers a separate set of fields. Either choice can be justified. Trouble begins when a user passes on a file assuming hidden information was not included.

The settings should therefore show the chosen columns and their roles. With many fields, a useful default set helps more than an empty wall of dozens of checkboxes. A variant for a particular task can be simpler than complete freedom. Changing column order should update the preview so the recipient can assess the result before downloading.

A label helps people read; a code helps identify

A status such as "For review" may have a stable code in the application. In an analysis file it can be useful to retain both: a code for joining to another set and a label for reading. There is no need to choose between a human description and an identifier if both columns are needed and clearly named. Accidentally repeating the same words does not add value, however.

Table Schema in the Data Package Standard distinguishes a field name, a human-readable title, type and format. Such a description communicates more than CSV headers alone. It does not mean every program will automatically read an accompanying schema; the recipient's compatibility must be confirmed separately.

In our inventory, "Equipment code" identifies the item, while "Equipment name" is for reading. Two devices can have the same commercial name. When data is joined again, they should not become one record merely because their labels look alike. The identifier needs a meaning agreed with the recipient, rather than being the number of the next row in the export.

Changing a label should not silently change its code either. If a company renames a status from "Waiting" to "For inspection", a file intended for integration needs an established way to handle that change. A human-facing name can be edited or translated. Stable references and a comprehensible description do different jobs.

Column headers involve a similar decision. An automated recipient may expect a stable field name, while a person needs an understandable title in their language. Changing the site's language should not silently make an importer look for a different column. The design may offer a separate technical-header variant or another structural description if the recipient supports it. Show that choice as part of the format rather than making it an undisclosed consequence of the menu language.

For a relationship to another object, show what was exported. A project name may not identify it uniquely. A project code alone may mean little to someone unfamiliar with that register. If the recipient must combine material from several catalogues, consider both fields together with a description of the source. Do not copy every detail about the project when the task only requires identifying it.

These decisions are best drawn from the company's catalogue data model. The guide to catalogue data models (in Polish) discusses how to build one. The exporter should not invent a separate meaning for "variant" or "set". If the screen shows a product family while the file contains its individual variants, column names and the export description must reveal that difference. Otherwise the correct row count can tell a story about a different kind of object.

A number should not travel without its unit

A length of 120 cm can be written as a value of 120 with a unit column, as a clearly named "Length [cm]" field, or in another agreed form. The choice depends on the recipient. What cannot be assumed is that the next person will remember the unit from our screen. The file may be separated from the application as soon as it is sent to a colleague.

For data used in calculations, separate the value from decorative display. The text "about 120 cm" is not the same information as an exact number in a specified unit. If the source genuinely contains an approximation, preserve it in a suitable form. Do not remove that condition merely because a numeric column is easier to import.

Conversely, rounding in a view should not become a loss of export precision without a decision. The screen may conveniently show one decimal place while a fuller value is needed for the next calculation. Agree what the recipient receives and how they can check it. A note about rounding is useful when it can change their result, not as permanent decoration on every download.

Aeneia conceptual photography

A code made of digits needs different treatment. For the fictional identifier 00417, the leading zeros belong to its contents. If the next program converts it to a number, it may obtain a different identifier. The export format should account for how the file is read, not just for bytes correctly written by our application.

Microsoft describes automatic data conversion settings in Excel, including conversion of numeric text and removal of leading zeros. It also describes notification of conversions when loading CSV. The actual reading therefore depends on the recipient program's configuration as well as the filename.

A check of a spreadsheet in an AI process (in Polish) shows the wider effect of such changes on later work. For the export we need a narrower test: download the specified version and read the code in the agreed destination. A screenshot of the correct code in our table does not prove the zeros survived that passage.

An empty field deserves an equally deliberate decision. No measurement, zero and "not applicable" can lead to different calculations or actions. If all are exported as an empty cell, the recipient cannot recover the distinction from the file alone. An additional value-status column may be a solution if the task needs it.

The W3C CSVW metadata vocabulary describes textual representations of missing values through the null property. Whether a cell value is required is specified separately. Such a contract helps establish how a cell is interpreted, but the business meaning of "no measurement" and zero still needs to be defined for the particular set.

A dash on screen can be a convenient mark for absence, but in data it may conflict with another meaning. Do not transfer it without describing the rule. The recipient should know whether the dash is actual text, a missing-value marker or merely presentation. An export preview can show one example of each situation being distinguished.

Dates and text must survive a change of environment

In the fictional inventory, the inspection date is 3 April 2026. The file should convey it in a form agreed for the recipient, for example 2026-04-03. "03/04/2026" without a rule is an unnecessary puzzle. Not every recipient will use the export author's settings.

A day and an exact instant are separate concepts. An inspection deadline may be a day without a time. The time of the last change may need a time zone or another unambiguous way to convey the instant. Do not add midnight merely to make both fields look alike. The recipient needs the correct information, not symmetrical columns.

Text containing a comma, quotation mark or new line should also remain one proper field. The export must preserve meaning and cell boundaries according to the agreed format. The user should not have to paste a description back together after it has been spread across neighbouring columns. A preview before download and a test in the destination program check different parts of that journey.

If the file opens in a spreadsheet, text interpreted as a formula (in Polish) is a separate question. Correctly quoting a field does not explain every behaviour of the next program. Prepare the representation for the particular recipient. Do not destroy valid content in the process by arbitrarily cutting out characters.

The delimiter and number notation should be agreed together too. A variant intended for a particular program can have a chosen configuration described in the download option. Do not silently change it with the interface language if the recipient uses a fixed importer. The person requesting an export should be able to distinguish a display layout from a data contract, meaning the agreement about its format and meaning.

This is part of export interface design with Aeneia Design: choosing options, a preview and names that explain the actual result. The design also needs a description of the next program and the recipient's task. An instruction as short as "add CSV download" leaves too many decisions to the person who happens to connect the button.

Accept the file at the next person's end

An export test should begin with a small set and agreed expectations. In our example, that means a code with a leading zero, a number with a fractional part, a missing measurement and a date. Add a description containing the delimiter and two items with similar names. This is a fictional control set, not proof that an export has been performed.

Then download the file through the application's ordinary route and pass it to the agreed place of reading. Do not replace it with a manually corrected copy for the demonstration. The comparison should show whether the code still identifies the right object, the unit has not disappeared and the missing value remains distinguishable. Opening without an error message alone resolves none of these questions.

For CSV import (in Polish), also check whether headers and types allow fields to be matched without guessing. If the next application needs a status code, an export of labels alone may not suffice. If a person must read the report without a dictionary, codes alone may be too little. Record the expectation on both sides of the handoff.

The filename and a short description should help identify the contents once the file is detached from the screen. Indicate the kind of data, important scope or structure version if needed in subsequent work. The entire report need not fit in the name. Avoid leaving a recipient with a series of similarly named "export-1.csv" and "export-2.csv" files and choosing the right one by its position in a folder.

After a format change, keep a sample for comparison. Adding a column or changing a label may require a response from the importer. The specification should establish what remains stable, which changes are permitted and how the recipient recognises a new contract version. Do not promise indefinite compatibility that nobody maintains; identify the person responsible for the agreement.

The export can be accepted when a test confirms that the chosen program reads the specified file in a way that serves the task. Outside the application, the recipient still knows what 120 means and why 2 is not the name of a status. Row count remains useful for checking scope. The meaning of the data must also arrive, together with a well-prepared representation.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear