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

git repo size (restarting a discussion)
by Paul Poulain 20 Apr '12

20 Apr '12

Hello koha-devel, Some months ago, Frederic started an interesting thread about translations and their consequences on the git repository size. The wiki page speaking of this is on http://wiki.koha-community.org/wiki/Git_Splitting_and_Shrinking We have decided nothing and only a few of us have expressed their opinion. Now, there is a big patch from Ukraine, that add another 2MB to Koha repo size (http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6434) Frederic proposes 3 scenarios: 1- Keep history -- Create two (or more) Koha sub-projects, one for Koha code koha-core, and one for Koha .po files koha-i18n, and keep the whole history in both of the repositories. 2- Keep history as history -- We froze the current Git repository in which Koha history will live for eternity as a koha-legacy repo, and initialize two new clean and fresh repositories. 3- Keep-loose history -- Keep the history in koha-core, start fresh for koha-l8n. The gain is impressive (see: http://wiki.koha-community.org/wiki/Git_Splitting_and_Shrinking#Evaluation) When Frederic wrote the page, the repository was 177MB large. Now, it is 355 ! I think we can't continue that way, and should decide something before 3.8 is released (in 3 weeks) Everyone is welcomed to read the wiki page, express his opinion, I propose to have a vote on the next IRC meeting. Frederic = isn't there another option ? = a huge "git rebase -i" where we would discard all commits that are related to .po files (the list being found with git log --oneline misc/translator/po (i haven't checked it work, just rising the idea) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

5 9

Feasibility question
by Cab Vinton 20 Apr '12

20 Apr '12

We're a small library with roughly 20,000 items. Our statewide digital consortium, however, provides access to a further 10,000 items (ebooks and downloadable audiobooks). We'd like to integrate records for these latter items into our catalog to facilitate access, but don't want search results to be overwhelmed with the downloadable, digital content. So ideally we'd like to be able to have searches default to our physical collection, with an option to include digital materials or to search the latter exclusively. Feasible? Cab Vinton, Director Sanbornton Public Library Sanbornton, NH

3 4

Staff client home page redesign (was Re: A few things you could do before I release of Koha 3.8)
by Owen Leonard 20 Apr '12

20 Apr '12

> Attached is how it look for (all of ?) us. The menus are on the RIGHT of > the news, not BELOW ! They are if your browser is wide enough. If the browser is too small it looks like that screenshot. My follow-up patch to the bug changes the grid to make it more flexible in an attempt to solve this problem. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

1 0

A few things you could do before I release of Koha 3.8
by Paul Poulain 20 Apr '12

20 Apr '12

Hello, Would you please take care of the following request before the release of Koha 3.8: * I've added a draft of the release notes to 3.8 to the wiki. I'll continue working on them, but if you have something to say, they are here = http://wiki.koha-community.org/wiki/3.8_Release_Notes * one of the last patches I've pushed is bug 7849. I'm quite uncomfortable because it touches something in the core of circulation. I couldn't find anything wrong, but please, double or triple check !!! * The INSTALL.* files are a little bit outdated. Zeno made some changes on bug 7759, that is waiting for your signoff, but I think/feel more updates would be welcomed. For example, the INSTALL file don't speak of checking XML sax parser, while the INSTALL.debian does. If someone can take care... * The QA team has no patches that is signed-off and that must be QAed before the release, good job people ! * There are some bugfixes that are still waiting for a sign-off. The most important ones are: 7641 Add ability to suspend reserves. 7848 Issues data missing from circulation notices 7441 search results showing wrong branch? 6976 User hold limit can be avoided by users in OPAC * The bug 7979 introduces a new stylesheet and homepage for the staff interface. I've setup the sandbox with this bug. If you want to have a look, head here = http://pro.test1.biblibre.com/ login/password= test/test . Many people already had a look at this new design. We made some tweaks. Please *don't* say that you would prefer another color or something like that: it's something we would debate for years. Gaetan, that made the design, will add a wiki page in the next days, to explain how to tweak this design using intranetusercss. But, if you find something *technically wrong*, please report it. I plan to push this patch just before releasing (i've checked it doesn't change any string : the french homepage is fully translated). Tomorrow will be my last day pushing patches. (This week-end, my wife is 40, don't expect me to push anything !!! On monday -european- morning, Koha 3.8 will be released !) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

6 6

Zebra with ICU and startswithnt, first-in-subfield, etc.
by Pongtawat Chippimolchai 19 Apr '12

19 Apr '12

Hello all, Could anyone please kindly advice me how to search OPAC / Staff Client for title with "starts with" or "exact" matching? I'm using Zebra with ICU. In OPAC, I try something the following: "ti,startswithnt: Financial" (no result), "ti,first-in-subfield: Financial" (result with first record title start with Financial, but the rest are mixed) , "ti,ext: Financial" (same as first-in-subfield), "ti,first-in-field: Financial" (doesn't work). The result (when it work), seems to be similar to the default Title search (ti,wrdl). It favors records with title starting with the search term, but not every records that start with the search terms are on top. Is there anything I have to set up? Or maybe I'm searching with a wrong syntax? Thank you, Pongtawat

2 3

A longer barcode
by Zeno Tajoli 18 Apr '12

18 Apr '12

Hi to all, a library of us ask me to use barcode more long of 20 char. I think I need to change from 'barcode' varchar(20) NOT NULL, to 'barcode' varchar(60) NOT NULL, Clerly there are problems on OPAC and Intranet display (template are organized with a max barcode lenght of 20 chars). But in .pl and C4 perl code ? Is the limit of 20 char only in DB definitions or also in any points of the code? Do you have experience on the topic ? Cheers Zeno Tajoli -- Dott. Zeno Tajoli tajoliAT_SPAM_no_prendiATcilea.it fax +39 02 2135520 CILEA - Consorzio Interuniversitario http://www.cilea.it/disclaimer

2 1

Re: [Koha-devel] Koha performance enhancement overview
by Jared Camins-Esakov 18 Apr '12

18 Apr '12

[Adding koha-devel back in] On Mon, Apr 9, 2012 at 9:37 PM, Ian Walls <koha.sekjal(a)gmail.com> wrote: > I'd be curious if TurboMARC might be a worthwhile compromise: the > extensibility of XML, but easier to process than MARCXML. > It might be worth looking into, but it seems like the amount of work necessary just to test it in a small way would be much to high to justify for idle curiosity (though if anyone feels like doing it, I wouldn't want to discourage them!). Regards, Jared -- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins(a)cpbibliography.com (web) http://www.cpbibliography.com/

9 17

Call for News for the April Newsletter
by Daniel Grobani 16 Apr '12

16 Apr '12

Dear Koha Kommunitarians, I'm harvesting news for the April newsletter. Please send me by the 25th anything you think your fellow community members might like to know about. "News" can be as short as a sentence or as long as a paper. I especially encourage you to send me a line or two for the gossip/society column about what you're currently working on. And if you know of a go-live not announced on the list, please be sure to let me know about it. Thanks, Daniel Grobani

1 0

Koha performance enhancement overview
by Ian Walls 16 Apr '12

16 Apr '12

Everyone, I was doing some thinking this weekend about the overall goal of making Koha perform faster. We're approaching this from several different angles, so I thought it might be a good idea to come up with a summary of all the various methods we could use to speed Koha up. Tuning & Hardware (http://wiki.koha-community.org/wiki/Koha_Tuning_Guide) - Hardware selection guide (how much CPU, RAM and disk to run Koha on) - Tuning the operating system - Tuning Apache - Tuning MySQL Performance tools - Alternate, Persistent Perl interpreters, like Plack/PSGI or mod_perl/FastCGI (http://wiki.koha-community.org/wiki/Plack) - Alternate webservers like Nginx or Starman - caching tools like memcached or T:T cache Code cleanup - Denesting dependencies - Optimizing SQL queries - Dual database handles (readonly, read/write) - Simplifying code - Minimizing XML parsing Network latency - AJAX calls for key functions like circ (cheaper to send/receive than full page loads) - Minifying JS and CSS ( http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1918) - CSS sprites (css-tricks.com/css-sprites/) - caching some data client-side (like user preferences) in cookies or localStorage Ergonomics - Fewer clicks to do common actions - Display important info more prominently - Preferences to customize to individuals' workflows Now, here's the question: which of these techniques will net us the biggest boosts for the least effort? We've got lots of great work on Plack so far, but would figuring out the perfect MySQL tuning settings be easier and give us a similar performance enhancement (I don't know, just using as an example)? Some of these are of course inter-related; doing code cleanup and denesting would make it easier to do AJAX calls or use mod_perl. I should probably dump this into a wiki page, but I wanted to raise the issue on-list first. Does anyone have any data that we could use to determine what above is low-hanging fruit, or what will get the biggest gains? We're lucky in this community in that we have many, many kinds of expertise, so we're not limited to pursuing any one course at a time, but having a coordinated effort would help us reap more tangible benefits sooner. Cheers, -Ian

7 8

Only 7 days until the deadline for submitting your talk for Kohacon12
by Chris Cormack 13 Apr '12

13 Apr '12

If you are thinking about presenting at Kohacon12 at either conference or hackfest, you only have 1 week left to get your abstract in. So please head on over to http://koha-community.org/kohacon12/call-papers/ and submit your talk now. You know you want to :) Chris

1 0