Large screen
Small screen
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.
Quick way to export records
Section titled “Quick way to export records”- Open the project
Dashboardmenu and selectExport records. - Choose an
Export presetA. To create or edit presets, selectManage presetsB. - Review the preset summary (record type, header format, and columns) and select
Preview TableD to inspect real rows. On a phone, open thePreviewtab F. - Choose a file format C and enter a file name. Turn on
Append dateG to add today's date to the name. JSON cannot use Darwin Core headers. - Choose a destination folder on desktop and select
Export recordsE. - Inspect the exported file for rows, headers, units, and repeated values. Use
Share, open the folder, save a copy, or selectExport another.
Deep dive
Section titled “Deep dive ”A record-export preset is a reusable recipe for one table. It defines three things:
- Rows: the
Record type, and for specimens theSpecimen taxon group(All taxa,Mammals—which includes bats,Birds,Herpetofauna,Invertebrates, orFishes). - Columns: the fields configured under
Edit Fields. - Headers: set by
Generated header formator 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.
What one row is
Section titled “What one row is”| Record type | One row per |
|---|---|
Specimen | Specimen. Parts and other repeated details can be joined into one cell or spread across numbered columns. |
Specimen parts | Specimen part (such as a skin or tissue tube), with its specimen details repeated on each row. Ideal for tissue inventories. |
Site | Site. |
Collecting event | Collecting event. |
Narrative | Narrative entry. |
Symbionts | Symbiont record. |
Kinds of columns
Section titled “Kinds of columns”Each column in Selected Mappings uses one of four Mapping type options:
| Mapping type | Use it for | Example output |
|---|---|---|
Single field | One NAHPU field, stored as-is or reformatted. | Rattus |
List field | Multiple fields joined together, skipping empty values. | Indonesia, West Java, Cibodas |
Custom field | Fields mixed with fixed text, or fixed text alone. | HH-156 |
Nested records | Repeated 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.
Format a single field
Section titled “Format a single field”A Single field column can transform its value using Value format:
| Value format | What it does |
|---|---|
Normal text | Writes the value as stored. |
Encoded text | Writes the human-readable label for a stored code, such as Male for 0. |
Coordinates | Formats coordinates using the style under Advanced. |
Date | Formats dates using Advanced > Raw format option, such as dd/mm/yyyy. |
Conditional brackets, Conditional field, Conditional value | Brackets 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.
Repeated values
Section titled “Repeated values”When a specimen has multiple parts, collectors, or collecting methods, List field and Nested records columns control how those values appear:
| Output | Result |
|---|---|
One column | All values in one cell, joined by your chosen separator. |
Indexed columns | One 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 rows | Nested 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.
Column headers
Section titled “Column headers”Generated header format names any column without an explicit Column name:
| Format | Header for specimen::uuid |
|---|---|
table::fieldName | specimen::uuid |
fieldName | uuid |
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.
Blank columns
Section titled “Blank columns”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.
Additional observation fields
Section titled “Additional observation fields”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.
File formats
Section titled “File formats”| Format | Best for |
|---|---|
CSV or TSV | Exchange with databases, R, Python, and other scripts. |
Excel | Reviewing tables in a spreadsheet app. |
JSON | Software 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.
Transfers and recovery
Section titled “Transfers and recovery”A record export is one-way: NAHPU cannot import it back as a project. To move or restore data in NAHPU, use:
- a project transfer or NAHPU Data Package with
Import projecton the home screen orMerge projectinside an open project; - a database backup to restore the entire installation.
To share a single preset with your team, see Create a tabular export preset.


