Open dvhassel opened 3 years ago
It's been some time since this issue had been reported; I don't know if it has been addressed in the mean time (I'm just reporting from a user perspective). Yet, testing with ArchivesSpace-4.3.1, I'm observing different (and I think better) behaviour. The CSV importer now seems to accept either:
AppConfig[:locale]
config I've tested with different standard ArchivesSpace languages, and behaviour seems consistent.
Important: it's the language configured in the config file that's being used for the controlled value label lookups, regardless of which language has been set in the application.
This definitely looks like an improvement to me: both keys and labels are accepted (if the values can be found in the locale set in the config file).
When using the bulk-import-template with eg a French locale, the import fails. The importer can't find the archival_record_levels:
Expected Behavior
The import template works regardless the locale used
Current Behavior
The import fails when not using the EN locale
Possible Solution
Modify the archival_record_levels in the XSL or CSV to the (in my case) French translations:
Better would be to modify the template and have the controlled value lists use the Values instead of the Translations (use 'item' instead of Item/Pièce, 'subseries' instead of Sub-Series/Sous-série, ...
Steps to Reproduce (for bugs)
Context
Your Environment