- Koha-devel - lists.koha-community.org

prove xt results
by Mark Tompsett 02 May '15

02 May '15

Greetings, mtompset@debian:~/kohaclone$ prove xt xt/permissions.t ............ ok xt/sample_notices.t ......... 1/? # Failed test 'No sample notice to add' # at xt/sample_notices.t line 82. # Sample notices to add in de-DE/mandatory/sample_notices.sql: DISCHARGE # Looks like you failed 1 test of 34. xt/sample_notices.t ......... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/34 subtests xt/single_quotes.t .......... ok xt/tt_valid.t ............... ok xt/verify-debian-docbook.t .. ok xt/yaml_valid.t ............. ok Test Summary Report ------------------- xt/sample_notices.t (Wstat: 256 Tests: 34 Failed: 1) Failed test: 9 Non-zero exit status: 1 Files=6, Tests=117, 3 wallclock secs ( 0.03 usr 0.01 sys + 2.73 cusr 0.00 csys = 2.77 CPU) Result: FAIL Given that I don’t know what to add (in terms of language), I thought I’d mention it here so that some loving developer familiar with de-DE might remedy the situation. GPML, Mark Tompsett

2 1

"News" area is gone
by Luciana Coca 01 May '15

01 May '15

Hello everyone! The "News" area have dissappeared. The configuration and preferences are correct. I have deleted and created new News, but nothing happend. Please, help me. Thank you all. Luciana.

2 1

Language overlays or: On the way to finally resolve important translation issues in Koha
by Marc Véron 30 Apr '15

30 Apr '15

Dear Koha community, Koha is translated in almost 50 languages - but it has no possibility to switch between languages for authorised values and item types (or more generally: database content). This is a long outstanding issue, see the discussion on Bug 7789 (2012-03-22). And it is a really painful one for multilingual countries, organisations, schools, museums, libraries... Especially the OPAC looks not very professional when untranslated text pops up. There are several more or less ugly workarounds: 1) Have all language versions in the same description, e.g. for OPAC_SUG something like "Damaged | Beschädigt | Abîmé" "Upcoming title by popular author | Neuer Titel eines populären Autors |Oeuvre... ... ... " 2) Have some sophisticated JavaScript tricks 3) Have custom Plug-ins 5) Locally tweak the code 6) Provide custom packages A couple of days ago I filed Bug 14063 - Implement language overlay for authorised values It is a small, minimal invasive patch (19 lines) that uses additional entries in the table authorised_values. To use it, one can simply create an additional entry with a trailing language code, e.g. BSELL-de-DE or BSELL-fr-FR It can be used "As is" without any changes to the database or to the user interface. A similar patch for Item types (Bug 14064) is in preparation. In comment #5 on Bug 14063, Joubu proposes to have a more generic solution with a table with columns "type" column (will contain "authorised_values", "item_types", "sysprefs", etc.) and "lang" ('fr-FR', 'de-DE', etc.). The complexity will be to implement an ergonomic view to edit the different translation. I totally agree with this. Typo3 CMS, for example, works with such language overlays e.g. for page content, and it works great. I'm best willing to help to implement such a generic solution. However, my concern is that it could take a very long time to get there. Now I have following questions: - In what (realistic) timeframe / for what Koha Version could such a generic solution be implemented? - Based on your experience, what development time would be necessary? - Who could contribute to this (time, maybe funding)? - What do you think about kind of "Taskforce language overlay" - What do you think to have Bug 14063 (Signed-off) and later Bug 14064 as a transitory solution to fix the issue for the most exposed places (e.g. Search interface in OPAC)? - I know and share concerns about temporary solutions, but we simply would need a small SQL script to move the language overlays from tables "authorised_values" and "itemtypes" to the new overlay table (once the generic solution is ready). Looking forward to your comments! Have a great day! Marc Véron (mveron)

5 4

License question
by Mark Tompsett 30 Apr '15

30 Apr '15

Greetings, While looking at bug 5685, I noticed the newer version is only licensed under MIT. Is that license compatible with the GPL3 that Koha is? GPML, Mark Tompsett

2 1

Re: [Koha-devel] [Koha] 3.18.06 Package Warning
by Robin Sheat 28 Apr '15

28 Apr '15

Barry Cannon schreef op ma 27-04-2015 om 13:54 [+0000]: > This installs 3.16.09 fine. Reverting to the "stable" source and > running an upgrade successfully gets Koha up to the latest version > (3.18.06.01). Damnit. The fix introduced in 3.18.06.1 was because fresh installs were possible but upgrades weren't. My fix ended up making it so that upgrades were possible, but fresh installs aren't. Now I've hopefully tested all the combinations and didn't encounter any issues, so have uploaded 3.18.06.2. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF

2 1

Hidden items associated item types turning up in facets - anyone done work on this?
by Liz Rea 28 Apr '15

28 Apr '15

Hi all, I'm just curious whether anyone has done work specifically on the hidden items and facets. I can see that there are bugs for hiding the associated item types from the Advanced Search, and quite a bit of work has been done to make the hiding more complete - but I wasn't able to find if anything had been done with the facets. Also quite curious if anyone has a thought on whether or not hiding associated item types will be easier or harder with 3.18+ (zebra facets). Please, share your thoughts! Cheers, Liz -- -- Liz Rea Catalyst.Net Limited Level 6, Catalyst House, 150 Willis Street, Wellington. P.O Box 11053, Manners Street, Wellington 6142 GPG: B149 A443 6B01 7386 C2C7 F481 B6c2 A49D 3726 38B7

4 5

Child-friendly interface
by Mark Tompsett 27 Apr '15

27 Apr '15

Greetings, I was wondering if anyone has a overly simplistic, child friendly interface already done for Koha. Or perhaps people just merely styled it with CSS? Thoughts? GPML, Mark Tompsett

2 1

Friendly warning about HTTP::OAI version 4.03
by David Cook 27 Apr '15

27 Apr '15

Hi all: Just a friendly warning to steer clear of HTTP::OAI version 4.03. It looks like there has been some substantial refactoring between versions 4.03 and 3.28, and they haven't been for the better. HTTP::OAI 4.03 will cause your Koha's OAI server to stop functioning all together! Fortunately, if you're using Debian, you probably won't need to worry about this problem, as Debian uses either version 3.23 or 3.27 (https://packages.debian.org/search?keywords=libhttp-oai-perl <https://packages.debian.org/search?keywords=libhttp-oai-perl&searchon=names &suite=all&section=all> &searchon=names&suite=all&section=all). This goes back to what Chris Cormack was saying recently in a blog post about avoiding CPAN if possible. If you're on a Debian-based system, either rely on the Koha packages or use libhttp-oai-perl. If you're not on a Debian-based system and you have to use CPAN, I'd recommend "cpanm HTTP::OAI@3.28" for installing this module. This is also useful if you find yourself using version 4.03 by accident (by doing "cpanm HTTP::OAI" for instance) and need to downgrade. Cheers, David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007

2 2

zebrasrv(17) [warn] ir_session (exception)
by Marcel de Rooy 24 Apr '15

24 Apr '15

Hi all, When closing a Zebra connection, I have a warning: 12:12:37-16/04 e0689fb5 [session] Connection closed by client 12:12:37-16/04 e0689fb5 [warn] ir_session (exception) The last line goes to zebra-output.log for each search in Koha, or closing yaz-client, etc. Zebra works apparently like it should (?) This happens under Debian 7 with the package install (oldstable). The yaz version is: YAZ version: 4.2.30 98864b44c654645bc16b2c54f822dc2e45a93031 Any thoughts? Thanks, Marcel

3 2

Bug 14057
by Mark Tompsett 24 Apr '15

24 Apr '15

Greetings, I’d appreciate feedback, not on how it fails to meet standards (which the current draft does – avert your eyes at its ugliness and complete disregard for standards), but if anyone can find an example where it fails to match the current version. Am I correct in assuming the kohafield and framework will uniquely identify the category whose value is stored in that particular items table field? Constructive and/or meaningful feedback appreciated. GPML, Mark Tompsett

1 0