Skip to content

First Day Using NAHPU

This guide introduces NAHPU's data model and gives you a safe place to practice before real fieldwork or lab work. NAHPU runs on any screen, though a laptop or tablet gives you more room while you learn the layout.

You do not have to invent practice data if you prefer working with real field records from the start:

PathTimeBest for
Practice on this page~30–45 minLearning the core concepts fast and testing your own taxon group in a temporary NAHPU Practice project
Basic tutorials~2 hoursFollowing a real 2014 Mt. Tujuh small-mammal paper catalog and field journal from project creation to a Darwin Core Archive

Select any record to see what it stores.

ProjectGroups an expedition, a monitoring program, or laboratory preparation work. Most day-to-day screens and exports operate on the active project.
  • Enter context once (Site → Event → Specimen): reuse one site for repeat visits, create a new event for each sampling session, and link specimens from that session to the event. Keep collection dates separate from laboratory preparation dates.
  • Keep daily context in Narratives: use journal entries for weather, logistics, permit notes, and observations that did not produce specimens.
  • Treat Personnel and Taxa as shared: editing a person or taxon updates every project that uses it. To fix one misidentified specimen, change the specimen's identification rather than editing the shared taxon entry.
TermWhat it records
Project locationBroad study area for the whole project
Site geographyAdministrative hierarchy and specific locality description (reusable across sites)
Site IDShort identifier for one place, such as a camp or trap line
Coordinate uncertaintyGPS accuracy for a specific point (a site can hold several points, such as one per trap or net)
Specimen coordinate extentOn the specimen form, how far the organism could have been from the selected point

A Field ID is the working identifier written on a physical specimen tag:

  • Personnel ID (default): combines a Cataloger's initials and personal running number. Best when multiple people catalog specimens in parallel.
  • Project ID: combines a project prefix, sequential catalog number, and suffix. Best for assembly-line preparation where one person catalogs for the whole project.

NAHPU follows FAIR principles and automatically assigns internal UUIDs to specimen and symbiont records (and optionally to specimen parts), independent of Field IDs.

NAHPU separates specimen care roles from event personnel roles:

  • Specimen care roles are set on each person and control specimen forms: Cataloger (eligible for all specimen personnel fields), Preparator, and Determiner.
  • Event personnel roles describe participation in a specific collecting event (such as leader, student helper, local guide, or driver) and can vary per event.

The taxon registry defaults to species imports but accepts higher ranks such as genus or family, so you can record an identification at the rank you can support alongside its identification confidence.

Settings, controlled vocabularies, and custom fields

Section titled “Settings, controlled vocabularies, and custom fields”
  • Controlled vocabularies populate dropdowns such as collection methods and preparation types; share user configs so every field device uses the same terms.
  • Catalog format selects the active specimen form and measurement fields on this device. One project can still hold specimens from multiple taxon groups.
  • Custom fields capture project-scoped or global observations that do not fit built-in fields.
  • Project time zone documents the local reference time for recorded observations without changing the device clock or converting existing timestamps.

Most form fields save automatically as you edit; dialogs, imports, and exports ask for confirmation. Use Narratives for the daily field journal, Associated Data for links and non-media files (links do not store offline copies), and Media for images, audio, or video.

ExportWhat it includesWhen to use it
Project identityProject name, details, and UUID onlySetting up team devices so their records can merge later
Project transferProject records and media (.zip / .tar.gz), or records only (Light export, .json.gz)Moving or merging one project between devices
User configsControlled vocabularies, field visibility, custom fields, templates, and presetsReproducing the same setup on another device
Database backupFull installation archive (all projects, media, and settings)Creating a complete recovery point before imports, merges, or fieldwork checkpoints

Use a clearly named practice project (NAHPU Practice) and sample values so exercise records stay separate from research data.

  1. Open NAHPU and explore setup

    Open Setup NAHPU from the home screen menu to review catalog formats, Field ID modes, controlled vocabularies, and export presets—or import team user configs from the home screen menu, project Dashboard menu, or Setup NAHPU.

    Check: Locate the dashboard, navigation bar, and Info buttons. See Settings.

  2. Create a practice project

    Select Create project > Create new project and name it NAHPU Practice. Enter project details and the reference time zone, choose a catalog format and Field ID mode, and finish the review. (For an existing team project, import its project identity to share its UUID.)

    Check: Confirm the new project opens on the Dashboard. See Projects.

  3. Add practice personnel and taxa

    Add at least one person with the Cataloger role (initials and starting number), then register sample taxa manually by rank or import a CSV, TSV, or Excel file.

    Check: Verify proposed taxonomic ranks before confirming file or QR imports. See Personnel and Taxon Registry.

  4. Create a practice site

    Open Sites and select +. Enter a stable Site ID, administrative geography, and habitat description, then add one or more coordinates manually, from device GPS, from a file, or via QR.

    Check: Verify the map pin, datum, units, and coordinate uncertainty. Reuse this site for repeat visits. See Sites.

  5. Add a practice event

    Open Events and select +. Choose your practice site, set start and end dates and times (adding an Event ID suffix if multiple sessions share a site and date), and record activity, collection methods, event personnel, and weather.

    Check: Try duplicating the event to see that setup copies over while environmental measurements stay blank. See Collecting Events.

  6. Create a sample specimen record

    Open Specimens and select + using a practice label. Verify the Field ID, assign Cataloger, Preparator, and Determiner, pick a taxon and ID Confidence, link your collecting event, and enter measurements, specimen parts, symbionts (for vertebrate catalog formats), and sample Media or Associated Data.

    Check: Reopen the specimen record to confirm every section saved. See Specimen Records.

  7. Review records and write a narrative

    Cross-check Field IDs, counts, linked events, coordinates, and attachments against your practice labels, then open Narratives to write a short daily entry and preview the rendered Markdown.

    Check: Try Export records for a review table and Export documents for printable labels or catalogs. See Narratives and Export.

  8. Practice project transfer and recovery

    Export NAHPU Practice as a .zip or .tar.gz archive (or Light export .json.gz without media) and inspect any warnings. On a second device, test Import project from the home screen or Merge project when the project UUID already exists there.

    Check: Always create a database backup before importing or merging, and never overwrite a live research database for practice. See Project transfer and recovery.

Before starting field or lab work, make sure you can:

  • explain how Site → Event → Specimen enters each context once;
  • identify whether your project uses Personnel ID or Project ID;
  • fix a single specimen's identification without editing the shared taxon;
  • choose between sharing project identity, transferring a project, exporting user configs, and creating a full database backup.