Bug #4738

Subjects not imported properly using CSV

Added by Jesús García Crespo about 9 years ago. Updated about 9 years ago.

Status:VerifiedStart date:02/27/2013
Priority:MediumDue date:
Assignee:José Raddaoui Marín% Done:


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


The issue has been described in the user list:


#1 Updated by José Raddaoui Marín about 9 years ago

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

Applied in changeset atom|commit:d41034239b4d4e742048c3f9284e7c90680391a0.

#2 Updated by José Raddaoui Marín about 9 years ago

Applied in changeset atom|commit:885465a9f8695dd348e698c949b659721449bfa2.

#3 Updated by Dan Gillean about 9 years ago

  • Status changed from QA/Review to Verified

Tested by doing the following:

1) Take the ISAD.csv located at: https://www.qubit-toolkit.org/wiki/CSV_import#Column_mapping
2) Add another row of my own silly example data (item) - including 4 different subject access points.
3) changing culture at the end of the rows so they are all different - en, fr, es
4) trying import. examining subject access points at all levels.
5) switch cultures to fr and examine subject access points at all levels. no problems so far. switch cultures to es and try again.
6) navigate to browse subjects and repeat check for imported subject terms across 3 different cultures. no problems

7) Delete import data - archival description, subjects, repository. change CSV so culture of each is es.
8) repeat steps 4-6

No problems encountered.

Also available in: Atom PDF