You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 13, 2024. It is now read-only.
bulk import is very powerful, and we want to enable users to add new individuals as well as existing individuals during the bulk import process.
Technical notes
upload should use flatfile verification to determine if the individual already exists in the catalog. This check should run against individual [name, adoption name, and codex ID] and [species]
If a match is found, the data creates a new sighting which gets associated with the existing individual
If NO match is found, the data creates a new sighting that gets associated with a new individual
Dependent stories
Bulk import: not about new individual functionality
The text was updated successfully, but these errors were encountered:
@naknomum we may need to accelerate the transition from flatfile with their new push to flatfile platform. Given the scope of the 2.2 release, I'm not sure now is the time, but we should check in before adding additional verification in this older technology
Context
bulk import is very powerful, and we want to enable users to add new individuals as well as existing individuals during the bulk import process.
Technical notes
upload should use flatfile verification to determine if the individual already exists in the catalog. This check should run against individual [name, adoption name, and codex ID] and [species]
If a match is found, the data creates a new sighting which gets associated with the existing individual
If NO match is found, the data creates a new sighting that gets associated with a new individual
Dependent stories
The text was updated successfully, but these errors were encountered: