Opened 16 years ago

Closed 15 years ago

Last modified 15 years ago

#369 closed feature (fixed)

Present metadata tiles in active language

Reported by: johnrose Owned by: anna
Priority: high Milestone: Release 2.82
Component: Greenstone2 Runtime Severity: major
Keywords: language interface, searching, classifiers Cc:


When you create an index in a GLI language interface, the index titles are proposed from the translation of the metadata set in that language if it exists. But a distrubing problem occurs if the user changes the language interface in Greenstone, as the metadata titles in the original language (not the interface language) are displayed for doing searches. I suggest that if the index title matches the name of a metadata element in the language version of the metadata set used in creating the collection (I assume that the language of creation is stocked somewhere?), then Greenstone should always display the translated metadata title name if the the interface is changed (assuming that the relevant metadata set element titles have been translated into the active language). But if the user has changed the name in the original language, he/she would have to add the intended translation to list of translated terms if the title is to be changed upon changing the interface. Same thing for the classifier titles. If we don't do this, perhaps the most important part of the user language interface will be in the wrong language.

Change History (5)

comment:1 by johnrose, 16 years ago

Resolution: duplicate
Status: newclosed

comment:2 by kjdon, 15 years ago

Cc: ihw removed
Resolution: duplicate
Status: closedreopened

John closed this ticket and added to another one. But it is a separate issue, so I have reopened this.

comment:3 by anna, 15 years ago

Owner: changed from lh92 to anna
Status: reopenednew

comment:4 by kjdon, 15 years ago

Resolution: fixed
Status: newclosed

Anna has fixed this so that by default a macro is used, eg _labeltitle_

If the user changes it to text, then they will need to do the translations themselves.

comment:5 by kjdon, 15 years ago

Just to clarify, this will only fix the problem in new or updated collections where macros are used for the names. No automatic translations will be done. Greenstone has no knowledge of metadata sets, they are only used in GLI.

Note: See TracTickets for help on using tickets.