Bug #5897

CSV import (archival descriptions) does not work in 2.x

Added by José Raddaoui Marín over 8 years ago. Updated over 8 years ago.

Status:VerifiedStart date:10/31/2013
Priority:CriticalDue date:
Assignee:José Raddaoui Marín% Done:

100%

Category:CSV import
Target version:Release 2.0.1
Google Code Legacy ID: Tested version:
Sponsored:No Requires documentation:

Description

To reproduce
Try to import a CSV file using the ISAD template

Resulting error
Import page reloads with no indication of success or failure; searching for the imported descriptions does not return any results.

Expected result
User is given an indication of success/failure and/or any warnings, as well as the option to view the imported description(s); CSV import results in a successful import.

csv-error.png (150 KB) Dan Gillean, 11/01/2013 03:43 PM

example_accessions.csv Magnifier (940 Bytes) Dan Gillean, 11/01/2013 05:10 PM

accessions-import-error.png (32.5 KB) Dan Gillean, 11/01/2013 05:10 PM

History

#1 Updated by José Raddaoui Marín over 8 years ago

  • Status changed from New to QA/Review
  • % Done changed from 0 to 100

#2 Updated by David Juhasz over 8 years ago

  • Priority changed from Medium to Critical

#3 Updated by Dan Gillean over 8 years ago

  • Status changed from QA/Review to Feedback

after a number of false starts, likely due to old CSV files that are not properly formatted anymore, I have tested this with the "example fonds" available on the Qubit toolkit website (https://www.qubit-toolkit.org/wiki/CSV_import - the ISAD example).

Imported into 1.x without problem (no errors or warnings were shown in the browser) and the browse archival descriptions button appeared, which took me to a browse screen where my newest import was listed at the top.

When imported into 2.x, I got the following long list of errors (see screenshot) and no link to browse, or any indication that the import succeeded regardless of the errors. If I navigate to browse and sort by most recent, however (or if I search for example fonds), then I can see that, despite the errors/warnings, the import did succeed.

so: it seems that the import is now working, but the resulting behaviour is not entirely as expected. Can we address that before I verify this issue? Haven't tested yet with other CSV import types, but I will.

#4 Updated by Dan Gillean over 8 years ago

Attaching screenshot.

#5 Updated by José Raddaoui Marín over 8 years ago

  • Status changed from Feedback to QA/Review

Sorry Dan, the search indexes needed to be rebuilt because I've merged #5781 after this fix. Sorry about it, should be fine now.

#6 Updated by Dan Gillean over 8 years ago

So far, authority records and archival descriptions have imported fine using the example CSV files. However, the accessions failed. Attaching the sample file used (from Qubit toolkit), and a screenshot of the error.

#7 Updated by José Raddaoui Marín over 8 years ago

  • Status changed from Feedback to QA/Review

Thanks Dan,

Now we're not sending the index option to the accessions and events CSV import tasks. Notice that this problem was happening in 1.x and 2.x, so I made this last fix in the 1.x branch and still need to be merged in 2.x.

#8 Updated by Dan Gillean over 8 years ago

  • Status changed from QA/Review to Verified

#9 Updated by Jesús García Crespo over 8 years ago

Radda, what's the commit checksum of the fix?

#10 Updated by José Raddaoui Marín over 8 years ago

AtoM|commit: 547a6e49c306b45d549641ac947f163493e27963

Also available in: Atom PDF