Skip to content

Projects

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.

From the home screen, select Create project to create a new project identity or reuse project information from another device.

  1. On Welcome, select Create new project E. To reuse an existing project identity instead, choose Import project-info JSON F or, on a device with camera scanning (Android, iOS, macOS, or web), Scan project QR G.
  2. Under Project information, enter a unique Project name (3–25 characters). Optionally add a Description (up to 160 characters), Principal investigator, Accession, Location, IANA Time zone, Start date, and End date.
  3. 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 can Skip this step and change it later in Settings > Catalogs > Format.
  4. Under Field ID, choose Personnel or Project (or Skip and configure it later in Settings > Catalogs > Specimens):
    • Personnel uses an eligible cataloger's initials and running field number. Select an existing cataloger or create a new one on the next Cataloger step.
    • Project joins Prefix, Current catalog number, and Suffix directly with no inserted separators. Turn on Auto-increment catalog number to advance the number automatically.
  5. On Review, check the project details, device setup, and taxonomy readiness, then select Create project to 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.

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 as project::timeZone in templates and exports so downstream databases can convert local times to UTC.
  • Changing Time zone never 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.

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:

ActionWhat it does
Edit infoOpens the project form to update metadata.
Show QRDisplays a QR code of the project metadata for another device to scan.
Export infoSaves project metadata as JSON (without records or media).
DetailsViews project information without editing it.

The Project dashboard has four panels and a bottom Tools dock:

  • Project overview A: shows the project QR code and metadata grouped under Identity, Description, Project details, Schedule, and Record metadata. Use Edit B to update details or Export info C to export metadata as JSON.
  • Personnel D: lists people assigned to the project, with Add 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), with Manage and Add taxon.
  • Record statistics: summarizes project records and opens detailed statistics.
  • Tools dock: provides quick launchers along the bottom of the dashboard (configured in Settings > Tools or via Edit at 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.

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.

Copy a project's identity and metadata to another device without transferring records:

  1. On the source device, choose Export info or Show QR from the project's home-screen menu (or tap the QR code / Export info in Project overview).
  2. On the receiving device, select Create project, then choose Import project-info JSON F or Scan project QR G 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.

To move records and media, run Export project from the project menu, then on the receiving device:

On the receiving deviceUseResult
Project does not exist yetImport project on the home screenCreates a new local project
Project already existsMerge project in that project's menuMerges 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.

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.

The person responsible for the project.