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

How to view Zebra indexes..?
by Сергій Дубик 24 Apr '12

24 Apr '12

Hi all! Koha Wiki has an page Understanding Zebra indexing (http://wiki.koha-community.org/wiki/Understanding_Zebra_indexing) about adding fileds/subfields to seach indexes. In particular are indices for the some case: Name-and-title = {"Goddard College"} Name = {"Faculty publications"} Subject = {"Faculty publications"} Subject:p = {"Faculty publications"} Corporate-name = {"Faculty publications"} General question: how to see the generated indexes for a specific record? ... For my case, I try to build the correct indexes for call numbers, UDC, Dewey, BBK codes etc. For ex. we have callnum = 222.12/4 I need a searches like next: 22* - 223.14/1, 224.1/2 ... 222* - all indexes start from 222 - 222.11/1, 222.12/2 ... 222.12* - in result I need only 222.12/1, 222.12/2, 222.12/3 ... During formation of index - point, space, parentheses or other mark should not break the index into pieces.

6 9

Koha 3.8 released... Koha 3.10 (or 4.0) started
by Paul Poulain 24 Apr '12

24 Apr '12

Hello Koha developers, Koha 3.8 has been released. It means we can start working on the next version that will be released in October. For this version, my goal, as RM, is to focus on: * cleaning the code. We have decided a while ago to move from C4 to Koha, separate business logic from data access (see http://wiki.koha-community.org/wiki/Namespace_QA_Rules) but only a few things have been made since then. I hope to be able to submit a proposal for going that way in the next weeks. That will be a long-term thing, but it's needed for a better stability, maintainability, readability. * Persistence layer (Plack) for Koha is stable for the OPAC, and experimental for the staff interface. I hope we will quickly have feedbacks that it works too. My goal is to be able to provide Plack configuration activated by default when you install Koha. * adding new features, of course. On this matter, there are 108 bugs that are waiting for your signoff, something like 75 being ENHancements ;-) PS: I leave for a week of holiday, I hope I'll have a lot of things to push when I come back, next Monday ;-) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

1 0

Releasing Koha 3.8.0, last minute problem
by Paul Poulain 23 Apr '12

23 Apr '12

Hello koha-devel, i'm ready to release Koha 3.8.0, except i've a blocking problems in the release process (and 2 annoying ones): The annoying ones: * i've tagged v3.08.00 on my local git repo, how can I push it on git.koha-community.org ? * I think I can't create the branch 3.8.x (untested, but iirc, I can only create new/... branches) The main problem is for creating the tarball. What I do: * perl Makefile.PL * make * make manifest tardist => /usr/bin/perl "-MExtUtils::Manifest=mkmanifest" -e mkmanifest Unmatched [ in regex; marked by <-- HERE in m/(?:Makefile$)|(?:release_notes_2)|(?:release_notes_1)|(?:\bCVS/)|(?:~$)|(?:\.patch$)|(?:\.orig$)|(?:\.old$)|(?:\.bak$)|(?:[ <-- HERE )|(?:\.git/)|(?:MANIFEST.bak)/ at /usr/share/perl/5.12/ExtUtils/Manifest.pm line 433. make: *** [manifest] Erreur 255 I'm totally unable to fix this kind of problem, so, if someone can help, i'll stay around... -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

8 10

Babeltheque CSS in the OPAC
by Owen Leonard 23 Apr '12

23 Apr '12

There's a big commented-out section of opac.css, added by Bug 7470: Babeltheque integration (http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7470) /* ## BABELTHEQUE ## */ /* Uncomment if babeltheque configuration no contains these lines */ /* ... If there is CSS which is only used when Babeltheque is enabled it can be put into its own CSS file. I can't see libraries editing opac.css themselves under normal circumstances. Can this be removed? Thanks, Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

2 1

Re: [Koha-devel] A few things you could do before I release of Koha 3.8
by Paul 20 Apr '12

20 Apr '12

At 02:54 PM 4/19/2012 -0400, Owen Leonard wrote: > > ... very respectfully, it's bloatware. Firebug pagespeed finds a 23% > > increase in transfer size: > >There's no way to "respectfully" use the term "bloatware." If I've offended you, please accept my humble apologies. We use the term rather loosely to describe an increase in code size (in this case 23% - see my previous post) combined with a (perceived) decrease in user friendliness. If there's a better term, I'll be most happy to use it. > > The "old" fitted nicely onto one screen without scrolling; for the > "new" you > > have to scroll for all functions except search. > >What are the dimensions of your browser window? It should be possible >to make it more flexible. We us a standard setting of 1024 x 768 on all monitors in our organization (from end-user kiosks to my desk-top.) For a graphical comparison, please see: <http://navalmarinearchive.com/admin/koha_home_page_comparison.html>. > > Adding a new Marc record now requires 2 clicks instead of one. > >True, if you do all your cataloging using the default framework. Or any other framework, surely? It's only when you get to the koha-admin/cgi-bin/koha/cataloguing/addbiblio.pl page that the choice of frameworks is available. > > We'd have to experiment to see how our "news and links" can be functionally > > fitted to the left hand side of the screen. > >The display of news is essentially unchanged in this version. Not from what we can see - again please see the "comparison page" link above. > > Question: can the css, templates etc from 3.6 be retained? Or do the mods > > permeate further? > >The changes are primarily CSS-based with the exception of the removal >two links, "Add MARC record" and "System preferences." Fine - thanks. The css is no problem, but where is the removal of the two links? In a perl script or in a template? Best - Paul

4 5

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