Skip to content

Export Records

Use Export records to save the active project's records as a CSV, TSV, Excel, or JSON file. A saved record-export preset defines which records become rows, which columns are included, and how headers are named.

  1. Open the project Dashboard menu and select Export records.
  2. Choose an Export preset A. To create or edit presets, select Manage presets B.
  3. Review the preset summary (record type, header format, and columns) and select Preview Table D to inspect real rows. On a phone, open the Preview tab F.
  4. Choose a file format C and enter a file name. Turn on Append date G to add today's date to the name. JSON cannot use Darwin Core headers.
  5. Choose a destination folder on desktop and select Export records E.
  6. Inspect the exported file for rows, headers, units, and repeated values. Use Share, open the folder, save a copy, or select Export another.

A record-export preset is a reusable recipe for one table. It defines three things:

  • Rows: the Record type, and for specimens the Specimen taxon group (All taxa, Mammals—which includes bats, Birds, Herpetofauna, Invertebrates, or Fishes).
  • Columns: the fields configured under Edit Fields.
  • Headers: set by Generated header format or overridden per column.

Edit presets under Settings > Tabular Data, not on the export screen. Field and format edits save automatically; the preset's name and optional Description (up to 80 characters, shown under the name in the list) save when you select Update. Use Duplicate to build a new preset from an existing one.

Record typeOne row per
SpecimenSpecimen. Parts and other repeated details can be joined into one cell or spread across numbered columns.
Specimen partsSpecimen part (such as a skin or tissue tube), with its specimen details repeated on each row. Ideal for tissue inventories.
SiteSite.
Collecting eventCollecting event.
NarrativeNarrative entry.
SymbiontsSymbiont record.

Each column in Selected Mappings uses one of four Mapping type options:

Mapping typeUse it forExample output
Single fieldOne NAHPU field, stored as-is or reformatted.Rattus
List fieldMultiple fields joined together, skipping empty values.Indonesia, West Java, Cibodas
Custom fieldFields mixed with fixed text, or fixed text alone.HH-156
Nested recordsRepeated child records, such as specimen parts or collectors.Skin; Skull; Tissue

Check a field under Insert Source Field (Available Fields on phones) to add it as a Single field. Use Add custom field and Add nested for the other types. Select a column's edit icon to configure it, and drag its handle to reorder. See Export expressions for custom fields and conditional output.

A Single field column can transform its value using Value format:

Value formatWhat it does
Normal textWrites the value as stored.
Encoded textWrites the human-readable label for a stored code, such as Male for 0.
CoordinatesFormats coordinates using the style under Advanced.
DateFormats dates using Advanced > Raw format option, such as dd/mm/yyyy.
Conditional brackets, Conditional field, Conditional valueBrackets or replaces the value when conditions match; see Conditional output.

Every column type also supports Replace text to rewrite formatted values—for example, renaming a part type to match a museum database.

When a specimen has multiple parts, collectors, or collecting methods, List field and Nested records columns control how those values appear:

OutputResult
One columnAll values in one cell, joined by your chosen separator.
Indexed columnsOne column (or group of columns) per value, such as prep_1_type, prep_2_type, … The count matches the record with the most values.
Repeated rowsNested records only: one row per value, repeating the parent record. At most one column per preset can use this.

With Indexed columns or Repeated rows, each child field of a nested column can take its own Column name (optional). Place {n} where the index belongs: PrepType{n}Count writes PrepType1Count, PrepType2Count, and so on. A name without {n} uses the Indexed column names numbering style.

Preview a record with multiple values to confirm the layout suits the receiving tool.

Generated header format names any column without an explicit Column name:

FormatHeader for specimen::uuid
table::fieldNamespecimen::uuid
fieldNameuuid
Darwin Core (dwc:/dcterms:)dwc:occurrenceID
NAHPU namespace (nahpu:table.field)nahpu:specimen.uuid

An explicit Column name always overrides the generated header.

With Darwin Core headers, fields without a Darwin Core term keep a NAHPU header rather than forcing an approximate term. Darwin Core output also:

  • credits the identification to the specimen's determiner;
  • preserves verbatim coordinates;
  • adds a positive specimen coordinate extent to a positive coordinate uncertainty—verify this combined value against your project's georeferencing method.

Measurement units are not converted; verify them in the exported table.

If a receiving spreadsheet expects a column NAHPU does not record (such as continent), add a custom field with that Column name and leave its expression empty. NAHPU writes an empty column so your columns line up.

Custom fields defined in Settings (such as environmental observations) export like built-in fields, using keys like customEnvironment::<definition UUID>. Event and specimen exports include stored values even if those fields are currently hidden on forms; hiding a field never filters it out of exports.

FormatBest for
CSV or TSVExchange with databases, R, Python, and other scripts.
ExcelReviewing tables in a spreadsheet app.
JSONSoftware consuming JSON directly (Darwin Core headers are unavailable).

Always inspect the exported file in the destination tool—spreadsheets can strip leading zeros from IDs or reformat dates automatically.

The LSUMZ Mammalogy tutorial walks through building a complete museum database preset using most of these options.

A record export is one-way: NAHPU cannot import it back as a project. To move or restore data in NAHPU, use:

To share a single preset with your team, see Create a tabular export preset.