Facet names and values in dropdown box are not translated properly acording to chosen TPAC locale
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Facet names and formats in dropdown box does not obey the chosen TPAC locale.
I have tested this in following catalogs:
- Jabok Library catalog (Evergreen 2.10.5).
Nor facets nor values in "format" dropdown box in on the Basic search page (see facet-formats-
- Jabok Library test catalog (Evergreen 2.12.2),
Nor facets nor values in "format" dropdown box in on the Basic search page (see facet-formats-
Note: Both installations mentioned above, contains data from the same Evergreen database. (As most of our patrons use Czech, and we need the Czech catalog at the first place, I decided to "solve" the problem by changing MARC codes value names to Czech expression. Similarly, I set the Czech names for facets. However, this is not ideal, because when English TPAC locale has been chosen, the values have still been displayed in Czech.)
- Terezín Initiative Institute test catalog,
Facet names are translated correctly, but this does not apply to "Format" dropdown box in on the Basic search page (see image facet-formats-
- Laurentian University catalog
Facet names are translated correctly, but this does not apply to "Format" dropdown box in on the Basic search page (see image facet-formats-
Summary:
1) The values in dropdown boxes are not displayed correctly in any of the catalogs I have tested. However, I was not able to find the pattern for translated/
2) The facet names are not displayed correctly only in both catalogs containing Jabok Library data (however, I know some other libraries came across the same problem too). Probably this might not be caused by a bug but (e.g.,by some setting inherited from some of the used previous Evergreen versions?
tags: | added: i18n |
Changed in evergreen: | |
status: | Incomplete → Invalid |
Hi Eva,
Basically, the problem you're seeing is that your entries in database table config.i18n_core do not match up the english database values for the fields you wish to see translated. This content is based on the fieldmapper design and how we define what the label is to be translated for the database value.
I identified several problems with the "filter by" fields and other db.seed i18n issues in bug 1160347 (https:/ /bugs.launchpad .net/evergreen/ +bug/1160347). There is a working branch on that with partial progress towards fixing the mismatches in the db.seed data.
In my own test server, I can see that as long as I load the correspondingly generated db.seed file for Czech and the expected values match, I can get translated values for the facets. Fixing the translated values for the filter by fields will come with the changes I proposed in my working branch, along with re-building the i18n PO file for db.seed's templates.
A related bug is this one reported by Dan Scott regarding db.seed PO file containing duplicate IDs which breaks the generated SQL files too by creating too many INSERT SQL statements with duplicate ID values (see bug 1681864 - https:/ /bugs.launchpad .net/evergreen/ +bug/1681864); I proposed a fix in that bug as well to remove the duplicate IDs and generate cleaner source files in the future.
I'll try to follow up on my original branches to clean up the source data files for db.seed and hopefully we can get it integrated into master for the upcoming 3.0 series.