[Koha-bugs] [Bug 10986] Limit the list of languages in advanced search through system preferences

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Wed Oct 2 23:47:50 CEST 2013


http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10986

mathieu saby <mathieu.saby at univ-rennes2.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mathieu.saby at univ-rennes2.f
                   |                            |r

--- Comment #2 from mathieu saby <mathieu.saby at univ-rennes2.fr> ---
Hi
I did not look yet, and I will, as it could be usefull, but I have considering
a more important more work for management of document languages in Koha for
years. The current way of dealing with it is just horrible! 3 SQL tables, no
way to update them easily, no way to translate them automaticaly...

It's out of the scope of your bug, but if you are interested in language
management, you will probably have an opinion. Could you tell me what you think
of that?

A enh could be : 
- store somewhere (a table? a yaml file?) the complete list of iso 639-2 codes,
used in UNIMARC, with the "native name" of this language
- store somewhere the complete list of MARC21 codes used in MARC21 (mostly the
same as iso 639-2, but not always), with the "native name" of this language
- include in the 2 lists "obsolete" codes for the 2 lists, because when a code
is marked as obsolete by the agency responsible for a list (ISO or LoC), it
does not mean automaticaly that the records using it are updated in every
library...
Maybe store the 2 lists (iso 639 and marc codes) in the same table or the same
yaml file, using for a key the iso 639-2(or iso 639-3 if needed) code (we must
check if there are some languages existing in one list and not in the other...)
These 2 lists won't be editable by users

- map each of these code with the english name of the list, and store the
resulting file (xml?) somewhere in koha templates where it could be translated
- make some PO files for translating this list

The PO files could be make automaticaly (need some work...) from data freely
available on Lexvo.org website (GLP licence).

effects for users on OPAC : 
- in language search dropdown list, show for "name depending on OPAC locale
language - native name". Sort the list alphabeticaly according to the name on
OPAC locale language. Ex : if OPAC is in french : "allemand - deutsch" ; in
english : "german - deutshc"
- when OPAC is switch in some language, the name of the language used in the
record would be translated. Ex : for a UNIMARC record with 101$a = "ger",
display "german" if OPAC is in english, "allemand" if it in french...
- we could also build facets on document language.

administration on staff interface:
- show the complete list of avalaible language on a page
- let the staff check a box before the name of the languages they want to be in
the dropdown list on avanced search page.

M. Saby

-- 
You are receiving this mail because:
You are watching all bug changes.


More information about the Koha-bugs mailing list