Bug #6757

CSV import: GMD values that do not conform to current taxonomy cause import failure

Added by Sarah Romkey almost 8 years ago. Updated about 7 years ago.

Status:VerifiedStart date:05/27/2014
Priority:MediumDue date:
Assignee:Dan Gillean% Done:

0%

Category:CSV import
Target version:Release 2.2.0
Google Code Legacy ID: Tested version:2.1, 2.2
Sponsored:No Requires documentation:

Description

To reproduce:

1. Import a CSV file with a value in radGeneralMaterialDesignation which is not currently in Material types taxonomy. Import will fail.

2. Update the taxonomy to include this term.
2a. This time I waited a few minutes before attempted re-import.
2b. Second attempt to import same CSV was successful.

example_information_objects_rad_GMD.csv Magnifier (6 KB) Sarah Romkey, 05/27/2014 10:23 AM


Related issues

Copied from Access to Memory (AtoM) - Bug #6756: CSV import: levelOfDetail values that do not conform to c... Verified 05/27/2014
Copied to Access to Memory (AtoM) - Bug #6758: CSV import: descriptionStatus values that do not conform ... Verified 05/27/2014

History

#1 Updated by Sarah Romkey almost 8 years ago

I deleted my fake data from 2x for testing purposes.

#2 Updated by Dan Gillean almost 8 years ago

  • Category changed from Import/Export to CSV import

#3 Updated by Jesús García Crespo over 7 years ago

  • Target version changed from Release 2.1.0 to Release 2.2.0

#4 Updated by Mike Gale over 7 years ago

  • Status changed from New to Code Review
  • Assignee changed from Mike Gale to Mike Cantelon
  • Requires documentation set to No

#5 Updated by Mike Gale over 7 years ago

  • Status changed from Code Review to QA/Review
  • Assignee changed from Mike Cantelon to Dan Gillean

#6 Updated by Dan Gillean over 7 years ago

  • Requires documentation changed from No to Yes

There is a warning in the documentation that needs to be removed here: https://accesstomemory.org/en/docs/2.1/user-manual/import-export/csv-import/#other-data-entry-notes

#7 Updated by Dan Gillean about 7 years ago

  • Status changed from QA/Review to Verified
  • Tested version 2.1, 2.2 added

Works. Case sensitivity does not matter either, which is good - "Textual Record" will be matched to the existing term, Textual record, for example.

#8 Updated by Dan Gillean about 7 years ago

  • Requires documentation deleted (Yes)

Warning in docs removed.

Also available in: Atom PDF