Closed teleaslamellatus closed 2 months ago
The current way to prevent the import from creating multiple CEs is to use eventID
. With it you tell the importer that several records refer to the same CE when they share the same ID.
Thank you, Hernan!
István
On Mon, Jul 8, 2024 at 12:32 PM Hernán Lucas Pereira < @.***> wrote:
The current way to prevent the import from creating multiple CEs is to use eventID. With it you tell the importer that several records refer to the same CE when they share the same ID.
— Reply to this email directly, view it on GitHub https://github.com/SpeciesFileGroup/taxonworks/issues/3985#issuecomment-2214629952, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACGX6JL7DYIFO4YBMTQBELLZLK5JTAVCNFSM6AAAAABKRFIAWWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJUGYZDSOJVGI . You are receiving this because you authored the thread.Message ID: @.***>
-- István Mikó PhD Collection Manager Department of Biological Sciences 117 Spaulding Life Sciences Building 38 Academic Way, Durham, NH 03824
Is it a huge problem to have multiple copies of the same collecting event in Taxonworks?
Also, we would like to batch-upload many images to already existing collection objects. As I understood, it should be done with your assistance.
Steps to reproduce the bug
Screenshot
No response
Expected behavior
I expect the collecting events are parsed and only one event is created, but perhaps it is not a big deal as later they will be merged by the database, so we should not worry about that. It is the production already, I was just wondering if we should be concerned about this or not.
Thanks!
István
Additional Screenshots
No response
Environment
Production
Sandbox Used
https://sfg.taxonworks.org/tasks/dwca_import/index
Version
No response
Browser Used
No response