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.
Choose how to start
Section titled “Choose how to start”You do not have to invent practice data if you prefer working with real field records from the start:
| Path | Time | Best for |
|---|---|---|
| Practice on this page | ~30–45 min | Learning the core concepts fast and testing your own taxon group in a temporary NAHPU Practice project |
| Basic tutorials | ~2 hours | Following a real 2014 Mt. Tujuh small-mammal paper catalog and field journal from project creation to a Darwin Core Archive |
Key concepts
Section titled “Key concepts”Select any record to see what it stores.
Three rules to remember
Section titled “Three rules to remember”- 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.
Location, locality, and coordinates
Section titled “Location, locality, and coordinates”| Term | What it records |
|---|---|
| Project location | Broad study area for the whole project |
| Site geography | Administrative hierarchy and specific locality description (reusable across sites) |
| Site ID | Short identifier for one place, such as a camp or trap line |
| Coordinate uncertainty | GPS accuracy for a specific point (a site can hold several points, such as one per trap or net) |
| Specimen coordinate extent | On the specimen form, how far the organism could have been from the selected point |
Field IDs and UUIDs
Section titled “Field IDs and UUIDs”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.
Roles and taxon identification
Section titled “Roles and taxon identification”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, andDeterminer. - 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.
Saving, attachments, and exports
Section titled “Saving, attachments, and exports”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.
| Export | What it includes | When to use it |
|---|---|---|
| Project identity | Project name, details, and UUID only | Setting up team devices so their records can merge later |
| Project transfer | Project records and media (.zip / .tar.gz), or records only (Light export, .json.gz) | Moving or merging one project between devices |
| User configs | Controlled vocabularies, field visibility, custom fields, templates, and presets | Reproducing the same setup on another device |
| Database backup | Full installation archive (all projects, media, and settings) | Creating a complete recovery point before imports, merges, or fieldwork checkpoints |
Practice using NAHPU
Section titled “Practice using NAHPU”Use a clearly named practice project (NAHPU Practice) and sample values so exercise records stay separate from research data.
Open NAHPU and explore setup
Open
Setup NAHPUfrom 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, projectDashboardmenu, orSetup NAHPU.Check: Locate the dashboard, navigation bar, and Info buttons. See Settings.
Create a practice project
Select
Create project>Create new projectand name itNAHPU 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.Add practice personnel and taxa
Add at least one person with the
Catalogerrole (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.
Create a practice site
Open
Sitesand select+. Enter a stableSite 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.
Add a practice event
Open
Eventsand 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.
Create a sample specimen record
Open
Specimensand select+using a practice label. Verify theField ID, assignCataloger,Preparator, andDeterminer, pick a taxon andID Confidence, link your collecting event, and enter measurements, specimen parts, symbionts (for vertebrate catalog formats), and sampleMediaorAssociated Data.Check: Reopen the specimen record to confirm every section saved. See Specimen Records.
Review records and write a narrative
Cross-check Field IDs, counts, linked events, coordinates, and attachments against your practice labels, then open
Narrativesto write a short daily entry and preview the rendered Markdown.Check: Try
Export recordsfor a review table andExport documentsfor printable labels or catalogs. See Narratives and Export.Practice project transfer and recovery
Export
NAHPU Practiceas a.zipor.tar.gzarchive (orLight export.json.gzwithout media) and inspect any warnings. On a second device, testImport projectfrom the home screen orMerge projectwhen 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.
Check your understanding
Section titled “Check your understanding”Before starting field or lab work, make sure you can:
- explain how
Site → Event → Specimenenters each context once; - identify whether your project uses
Personnel IDorProject 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.
Next steps
Section titled “Next steps”- Follow the Basic tutorials using a real 2014 paper field catalog from project setup to a Darwin Core Archive.
- Learn to configure custom fields.
- Browse the Cookbook for quick task recipes.