Bug #13287

Repository CSV import fails when new terms added to Description Statuses in import file

Added by Dan Gillean over 1 year ago.

Status:NewStart date:04/13/2020
Priority:MediumDue date:
Assignee:-% Done:

0%

Category:CSV import
Target version:-
Google Code Legacy ID: Tested version:2.5, 2.6
Sponsored:No Requires documentation:

Description

Reported via the User forum (2.5) here - reproduced in vagrant qa/2.6.x, 2020-04-13.

In issue #10472 we added support for a repository CSV import. However, currently attempts to add new terms to some of the taxonomy-linked fields causes the import to fail, rather than adding the term and informing the user in the console.

To reproduce

Use the attached test file - it contains the word "Coffee" in the first row's descriptionStatus column, and the second example row has been changed to fr in the culture column.

Import it with:

php symfony csv:repository-import /path/to/culture-test-example-repositories.csv

Resulting error

  • Import fails
  • Error in console: "Could not find "Coffee" in description status terms array."

See the attached screenshot, repo-descriptionStatus-import.png

Expected result

  • The term "Coffee" should be created in the Description Statuses taxonomy on import and the user notified in the console log
  • The import should not fail due to a new term being added

Note: we should also review other related fields for similar behavior.

culture-test-example-repositories.csv Magnifier (7.68 KB) Dan Gillean, 04/13/2020 11:39 AM

repo-descriptionStatus-import.png (23.7 KB) Dan Gillean, 04/13/2020 11:39 AM


Related issues

Related to Access to Memory (AtoM) - Feature #10472: Add repository CSV import via UI and job scheduler Verified 10/25/2016

History

#1 Updated by Dan Gillean over 1 year ago

  • Related to Feature #10472: Add repository CSV import via UI and job scheduler added

Also available in: Atom PDF