Combine records from another copy of the same project through guided conflict review.
- Back up the receiving database.
- Open the receiving project and select
Merge project. - Choose a project JSON.GZ, ZIP, TAR.GZ, or compatible NAHPU Data Package.
- Review project information, personnel, taxonomy, sites, events, specimens, and narratives in order.
- For each conflict, choose
Keep current,Use imported,Import as new, orSkip. - Clear every card marked
Needs attentionbefore continuing. - Review the final summary, run the merge, and verify counts and media afterward.
How records are matched
Section titled “How records are matched”Events match on the parts NAHPU shows as the event ID: the site, the start date, and the suffix. The same field event still matches when its start time was recorded differently.
Duplicate identifiers
Section titled “Duplicate identifiers”Field IDs, project IDs, tissue IDs, and barcode IDs end up on physical labels and in published exports, so NAHPU never renumbers them for you. A duplicate identifier, a specimen or parasite UUID already in the database, and a site or event ID that matches more than one existing record all become cards marked Needs attention. The wizard will not continue until each one has an action.
Check the imported records, change the ID and import again, or skip that record.
Use this workflow only inside an existing project. To receive a project that is not yet on the installation, start with Import project on the home screen.