Large screen
Small screen
Projects keep NAHPU data organized. Each project holds its own sites, collecting events, specimen records, narratives, associated data, and linked media, while sharing personnel and taxonomy records from the NAHPU database.
Creating a project
Section titled “Creating a project”From the home screen, select Create project to create a new project identity or reuse project information from another device.
- On
Welcome, selectCreate new projectE. To reuse an existing project identity instead, chooseImport project-info JSONF or, on a device with camera scanning (Android, iOS, macOS, or web),Scan project QRG. - Under
Project information, enter a uniqueProject name(3–25 characters). Optionally add aDescription(up to 160 characters),Principal investigator,Accession,Location, IANATime zone,Start date, andEnd date. - Under
Main taxon, choose the catalog format for new specimen forms on this device. A single project can still hold specimens from multiple taxon groups. You canSkipthis step and change it later inSettings>Catalogs>Format. - Under
Field ID, choosePersonnelorProject(orSkipand configure it later inSettings>Catalogs>Specimens):Personneluses an eligible cataloger's initials and running field number. Select an existing cataloger or create a new one on the nextCatalogerstep.ProjectjoinsPrefix,Current catalog number, andSuffixdirectly with no inserted separators. Turn onAuto-increment catalog numberto advance the number automatically.
- On
Review, check the project details, device setup, and taxonomy readiness, then selectCreate projectto open the dashboard.
NAHPU assigns a UUID to every new project. On wide screens, wizard steps appear in a left rail; on narrower screens, they appear as horizontal chips with the same validation.
Importing project-info JSON or scanning a project QR code preserves the source UUID and jumps straight to Review. It copies project metadata only—not records, personnel, taxa, media, or device settings. Use a full project transfer when records and media must also move between devices.
Project time zone
Section titled “Project time zone”Time zone records where the fieldwork takes place using an IANA name such as Asia/Jakarta or America/New_York. Choose the fieldwork location's time zone, not the time zone of the data-entry device.
NAHPU never converts times. Dates and times are stored exactly as entered in the field's local clock. Opening the project in another time zone does not shift stored times—it may only change how dates or 12/24-hour clocks display. For example, with Asia/Jakarta, an event entered as 12 May, 08:30 always shows 08:30 on every device, and the project time zone documents which clock that 08:30 refers to.
- The time zone appears in
Project overview, travels with project-info and project transfers, and is exposed asproject::timeZonein templates and exports so downstream databases can convert local times to UTC. - Changing
Time zonenever alters the device clock or rewrites existing records. Keep the same value on every device sharing a project. - If a team spans multiple time zones or enters historical records from elsewhere, note exceptions in the project description or a narrative—or use a separate project per time zone.
Managing projects from the home screen
Section titled “Managing projects from the home screen”When projects exist, the home screen provides a search bar, quick actions (Create project, Gallery, Import project, and Statistics), and a list/grid view toggle. Each project's three-dot menu includes:
| Action | What it does |
|---|---|
Edit info | Opens the project form to update metadata. |
Show QR | Displays a QR code of the project metadata for another device to scan. |
Export info | Saves project metadata as JSON (without records or media). |
Details | Views project information without editing it. |
Project dashboard
Section titled “Project dashboard”The Project dashboard has four panels and a bottom Tools dock:
Project overviewA: shows the project QR code and metadata grouped underIdentity,Description,Project details,Schedule, andRecord metadata. UseEditB to update details orExport infoC to export metadata as JSON.PersonnelD: lists people assigned to the project, withAdd personnel,Manage, edit icons, and selection controls.Taxon registry: shows counts of registered orders, families, species (and total taxa when higher-rank or subspecies entries exist), withManageandAdd taxon.Record statistics: summarizes project records and opens detailed statistics.Toolsdock: provides quick launchers along the bottom of the dashboard (configured inSettings>Toolsor viaEditat the end of the dock).
The project menu (a side rail on desktop, or a drawer on smaller screens) provides Merge project, Export project, Batch import, Bundle records, Export records, Export documents, Backup database, Settings, Export user configs, Import user configs, and Delete project.
Updating project information
Section titled “Updating project information”Select Edit B in Project overview on the dashboard, or choose Edit info from a project's home-screen menu. Fields are grouped under Project details, Place and time, and Project dates. Change the active catalog format or Field ID settings in Settings.
Sharing project information
Section titled “Sharing project information”Copy a project's identity and metadata to another device without transferring records:
- On the source device, choose
Export infoorShow QRfrom the project's home-screen menu (or tap the QR code /Export infoinProject overview). - On the receiving device, select
Create project, then chooseImport project-info JSONF orScan project QRG on a device with camera scanning.
This preserves the source UUID and creates a matching project shell. To move records, media, and linked data, use Project transfer instead.
Transferring project data
Section titled “Transferring project data”To move records and media, run Export project from the project menu, then on the receiving device:
| On the receiving device | Use | Result |
|---|---|---|
| Project does not exist yet | Import project on the home screen | Creates a new local project |
| Project already exists | Merge project in that project's menu | Merges imported records into the existing project |
ZIP and TAR.GZ exports include media; Light export (JSON.GZ) includes records only. A NAHPU data package can also be imported or merged. Darwin Core packages and tabular exports cannot restore a project. Keep the source archive until you have verified the records and media on the receiving device. See Project transfer for full steps.
Deleting a project
Section titled “Deleting a project”Open the project menu and select Delete project. NAHPU asks you to type the first five characters of the project's UUID because deletion cannot be undone.
Deleting a project removes its specimen records and measurements, collecting events (with collection methods, event personnel, and environmental data), narratives, sites and coordinates, associated data, project-personnel links, project media, stored project files, and the project record itself. Media still referenced by a taxonomy record is detached rather than deleted. If file cleanup fails, NAHPU shows a warning after removing the database records.
Export a project transfer or database backup first if you may need the data later.
Terminology
Section titled “Terminology”Principal Investigator
Section titled “Principal Investigator”The person responsible for the project.



