When importing records (CSV) using special_item_id, existing items do not update with new data. New items are created instead

Suporte Dúvidas
,
1

I have an existing collection containing items. I am trying to update the existing items with new data. I am using the Tainacan CSV import feature and including a special_item_id column. I obtained the ID’s by first exporting the items from my collection using the Tainacan CSV export tool.

However, when I try to import, instead of updating my existing items, it adds them as new items.

I see other users have had success with updating items via CSV import. Could you help me to troubleshoot my issue?

I have included a copy of the CSV file I am using to update the existing records.

Thank you for any help!

Nate Hilzinger
RIHN-Citations-from-in.csv (100.2 KB)

2

Hi Natehilzinger,

Your CSV file seems to be ok.
I have two questions:

  1. It may seem obvious, but are you really selecting the collection that exported the special_item_id of the items you want to update?
  2. On the CSV importer screen, in the Repeated Item section, is the option chosen really update? In case it is ignored, Tainacan’s standard procedure is to insert these items as new. And not as an update for the corresponding special_item_id.
3

Thanks so much for your reply! Yes, I am certain the correct collection is selected. (I only have the one).

Also yes, ‘update’ is chosen in the Repeated Item section.

I am stumped!

Nate

4

Hi @natehilzinger,
Can you share the contents of the “log file” generated of the import process?

5

Absolutely. Log file attached. (I had to zip to upload)

bg-import-32-2.log.zip (14.1 KB)

6

Hi @natehilzinger
This is very strange!!!
The importer process completely ignored the special_item_id field. I believe it be some special character in the field name (but I can’t identify it) .
when the importer find the special item id the options to select the metadata should not be displayed, instead this the message “Mapped to default field on collection.” it’s presented:

dd_no_mapper
dd_no_mapper1786×188 20 KB

–

dd_mapper
dd_mapper967×213 20.1 KB

I made a copy of your file and, incredibly, the special_item_id was identified (I’m surprised!).
@natehilzinger, could you test using this file?

citations.csv (99,5,KB)

1 Like
7

That worked! Interesting. Could it have anything to do with the data originating in Excel? Perhaps there was an issue with encoding.

I’m going to try and reproduce this by copying the file to a plain text editor.

Thank you so much!

8

I think so, I did a diff of the first lines between the two files and in fact they are different.

:v:t4:

9

Y’all are wonderful. Thank you for the support.

2 Likes