Holdings list not viewable in other cultures even when content is multi-lingual
|Assignee:||Jesús García Crespo||% Done:|
|Target version:||Release 2.0.0|
|Google Code Legacy ID:||Tested version:|
1) Navigate to an archival description that is listed as being in both english and french (ex: for local devs in test site - http://OUR-TEST-SITE/denis-landry-2
2) Switch culture to french - note that a translation is available, and the the fonds languages are listed as both english and french.
3) Click on the repository logo to navigate to the related archival institution (for the above example, City of Sudbury Archives)
4) Note that no holdings are listed whatsoever (including denis landry)
5) switch culture back to English
Holdings are not visible in another culture, even when they are translated
This is harder. At minimum, users should see content that is available in French when they are viewing the institution in French. But from a broader sense, we need to discuss, throughout the application, how to let users know that there is other content available in different cultures - many will not expect these descriptions to be hidden, and some may want to change the culture of the interface even if they must view the content in English (etc). Without culture fallback as in 1.x, we need to improve this design so that the application can be truly multilingual, as well as usable.
#3 Updated by Jesús García Crespo over 8 years ago
- Assignee changed from José Raddaoui Marín to Jesús García Crespo
The problem was that we were trying to sort by the title in the language where the UI is. As many documents had not been translated, ES was throwing an error. I've updated the query so ES ignores these errors.