Bug #12155

CSV export issues in cultures not in English

Added by Dan Gillean about 3 years ago. Updated about 2 years ago.

Status:NewStart date:04/19/2018
Priority:MediumDue date:
Assignee:-% Done:

0%

Category:CSV exportEstimated time:16.00 hours
Target version:-
Google Code Legacy ID: Tested version:2.4, 2.5
Sponsored:No Requires documentation:

Description

If you manage to (see related issue #12107) export a French description from an English site, all controlled values (such as levels of description, event terms, publication status etc) come out in English. This can cause issues in roundtripping - for example, importing this to a FR-install site will create a new french event term "Creation" rather than linking to the original one (which is "Production" in French). This causes issues in the display of events in the user interface.

Additionally, even in a FR-installed site, the English terms for events are appearing in export - Creating an FR description in a FR-install site still used "Creation" as they eventType on export.

Finally, there is seemingly no way to export non-default culture records via the user interface, whether they are original records or translations.

Issue 1: Secondary culture descriptions use default culture terms on CSV export even when translations are available

To reproduce

  • Log into an EN default install site
  • Flip the user interface to FR and create a new description
  • Be sure to include controlled values from dropdown options, such as a creation event, description status, level of detail, etc. Save.
  • Use the command-line to export all descriptions, and then find the target description in the resulting export.

Resulting error

  • Terms such as eventType, descriptionStatus, and levelOfDetail export in EN, even though FR terms are shown in the FR interface
  • This can cause issues when being imported into another FR site - for example, "Creation" as an event type, when imported to an FR install, will create a new FR event term, rather than linking to the existing "Creation" term - because AtoM is expecting the French "Production"
  • This happens both when the original record was created in french, or when french translations are added to original english records
  • See attached CSV for an example

Expected result

  • When exporting content in a different culture, use the terms matching that culture whenever available.

Issue 2: English default terms are used on export even when exporting FR descriptions from an FR-installed site

To reproduce

  • Log into an FR default install site and create a new description
  • Be sure to include controlled values from dropdown options, such as a creation event, description status, level of detail, etc. Save.
  • Add the resource to the clipboard and export

Resulting error

  • Terms such as eventType, descriptionStatus, and levelOfDetail export in EN, even though FR terms are shown in the FR interface, and the default installation culture is FR
  • As above, this can cause issues when being imported into another FR site - for example, "Creation" as an event type, when imported to an FR install, will create a new FR event term, rather than linking to the existing "Creation" term - because AtoM is expecting the French "Production"

Issue 3: No way to export records that are not created in the same culture as the default install culture from the user interface

To reproduce

  • follow the same steps outlined in issue 3 but try to export via the user interface, using the clipboard or the Search results export

Resulting error

  • For a description created in the FR interface, the only user-added values populated on export are the identifier, and any controlled values that exist in English. All other metadata is excluded from the export, regardless of the language of the interface at the time of export

Expected result

  • Users have the ability to export all relevant data from AtoM
  • See Wishlist issue #12107

CSV example notes

I've attached 2 CSV examples for reference.

The first one (fr-cli-test.csv) was exported from the CLI from a default EN-culture installation. In it I created 3 records - 1 just in the French interface, 1 in the FR interface, with EN translations added after, and 1 in the EN interface with FR translations added after. This results in 5 records being exported from the command-line - note that levelOfDescription, descriptionStatus, levelOfDetail, and eventType use the EN term value in all export rows regardless of culture.

For the second one (fr-clipboard-test.csv), I exported the same records from the default EN-culture installation via the Clipboard, while the UI was set to French. Note that almost no metadata was exported for the French record, and where there are controlled terms, again only the EN values were exported, even though FR translations are available in AtoM.

fr-cli-test.csv Magnifier - Export 1, from the CLI (2.29 KB) Dan Gillean, 04/19/2018 05:31 PM

fr-clipboard-test.csv Magnifier - Export 2, from the Clipboard via the UI (1.68 KB) Dan Gillean, 04/19/2018 05:31 PM


Related issues

Related to AtoM Wishlist - Feature #12107: Add i18n language options to CSV and XML exports from the... In progress 04/05/2018
Related to Access to Memory (AtoM) - Bug #8570: Publication statuses in other languages don't import prop... New 06/17/2015
Related to Access to Memory (AtoM) - Bug #6689: CSV import for archival descriptions creates terms with w... New 05/12/2014
Related to Access to Memory (AtoM) - Bug #9663: CSV export only exports English, leaves non-English field... New 04/04/2016

History

#1 Updated by Dan Gillean about 3 years ago

  • Related to Feature #12107: Add i18n language options to CSV and XML exports from the clipboard added

#2 Updated by Dan Gillean about 3 years ago

  • Assignee set to Nick Wilkinson

#3 Updated by Nick Wilkinson about 3 years ago

  • Assignee changed from Nick Wilkinson to Steve Breker

Hi Steve, can you please provide an estimate for this?

#4 Updated by Steve Breker about 3 years ago

  • Assignee changed from Steve Breker to Nick Wilkinson

#6 Updated by Dan Gillean about 3 years ago

  • Estimated time set to 16.00

#7 Updated by Dan Gillean about 3 years ago

  • Assignee deleted (Nick Wilkinson)

#9 Updated by Dan Gillean almost 3 years ago

  • Related to Bug #8570: Publication statuses in other languages don't import properly added

#10 Updated by Nick Wilkinson over 2 years ago

  • Assignee set to Steve Breker
  • Target version set to Release 2.5.0

Hi Steve, can you please look into resolving this?

#11 Updated by Steve Breker over 2 years ago

  • Assignee deleted (Steve Breker)

#12 Updated by Dan Gillean over 2 years ago

  • Related to Bug #6689: CSV import for archival descriptions creates terms with wrong culture added

#13 Updated by Dan Gillean about 2 years ago

  • Related to Bug #9663: CSV export only exports English, leaves non-English fields blank added

#14 Updated by Dan Gillean about 2 years ago

  • Target version deleted (Release 2.5.0)

Also available in: Atom PDF