Bug 11029 - Marc Language Code in a list
Summary: Marc Language Code in a list
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: Main
Hardware: All All
: P3 enhancement (vote)
Assignee: Galen Charlton
QA Contact: Testopia
URL:
Keywords:
: 35340 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-10-09 18:55 UTC by Francisco Peixoto
Modified: 2023-11-17 18:34 UTC (History)
5 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Francisco Peixoto 2013-10-09 18:55:27 UTC
When inputing a language code KOHA could have a pre-defined list of language codes from the Library of Congress Marc Language Code List. It would save time and would reduce errors in cataloguing.
Comment 1 Nicole C. Engard 2013-12-06 15:57:16 UTC
This is good for beginners, but I'd hate for it to be there all the time. I know the language codes I have to use and don't want to have to scroll through a pull down to pick it - I want to be able to type it.

So this should have some way to keep it the way it is while adding a new option.

Nicole
Comment 2 Josef Moravec 2015-03-30 14:50:22 UTC
Maybe it could by something like autocomplete? 

We use autocomplete for RDA field 336/337/338 and for indicators. It is implemented in javascript inserted in intranetuserjs syspref. Although not ideal, it works fine for us... But some more sophisticated solution in Koha may be better. 

What about an option to have authorised values behave like autocomplete instead to be a dropdown list?
Comment 3 Francisco Peixoto 2015-11-09 02:12:59 UTC
DO we have any changes on this on Koha 3.20?

Thanks!

Kind regards
Comment 4 Katrin Fischer 2015-11-17 13:34:21 UTC
Hi Francisco, no patch has been submitted for this yet.
Comment 5 Phil Ringnalda 2023-11-17 18:34:02 UTC
*** Bug 35340 has been marked as a duplicate of this bug. ***