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

Installation of Koha 3.0
by Axel Bojer 28 Aug '07

28 Aug '07

Hi! I was trying to install koha 2.2.9, but found it overly complex and not very user friendly, but I found some links for it. I don't remember what went wrong, and I will certainly try again later. But it would have been nice if there could have benn for instance debian-packages of it to ease the pain. As I think of it not every small library has the technical know hos to install and build from the command line, and just the though of it scares some light hearted users away. Will Koha 3.0 be easier to install? I mean, the whole point with debian packages of course is that all the dependencies then are taken care of :-) Best regards Axel bojer

2 1

Bug reporting by amateurs
by Roger Horne 28 Aug '07

28 Aug '07

In file:///usr/local/koha/intranet/scripts/misc/release%20notes/release_notes_200RC2.txt it was said that known bugs included * autobarcode not calculated even if autobarcode system parameter is set and MARC=on. It seems that this has not been solved as yet, at any rate if MARC=off. It is, to put it mildly, annoying to find that if one enters a biblio manually using acqui-simple that one has to invent a barcode to be able to enter the new data and that if one fogets to do so one has to start all over again. The problem is, I think, that the no-marc pages require that a barcode be entered when starting even though koha should be producing one manually at a *later* stage. I found that commenting out the lines elsif ((! $barcode) && (! $website)) { print $input->redirect("additem-nomarc.pl?biblionumber=$biblionumber&error=nobarcode"); } at line 73 of /usr/local/koha/intranet/cgi-bin/acqui.simple/saveitem.pl enabled the program to save the data correctly so that it could be found on a subsequent search (with either opac or intranet). Presumably a safer option would involve a check that included whether autoBarcode was true but I did not feel up to that at the time. This alteration did not cause Koha to generate the missing barcode. So on looking at the output of a search the line containing the barcode was blank. A search for autoBarcode did however throw up an anomaly. Line 93 of aqui.simple/additem.pl reads: if (C4::Context->preference('autoBarcode')) { while line 102 of cgi-bin/aqui/aquire.pl reads: my $auto_barcode = C4::Context->boolean_preference("autoBarcode") || 0; Changing the former to if (C4::Context->boolean_preference('autoBarcode')) { seems to do something different since a search produces an error "Sorry that barcode is already in use" although I could not get it to tell me what the barcode was: I doubt that there was one.. (So could the appropriate change to saveitem.pl be the addition of &&(! C4::Context->boolean_preference('autoBarcode' )) (together with use C4::Context)? It seems to work.) Trying to take this further is beyond me but I suppose it might be of interest to someone else. The two different ways of (possibly) calculating the barcode in the two files defeat me at the moment. So how should someone who is not sure what he is doing report this sort of possible (partial) start of a solution to a known problem? Roger -- Roger Horne roger(a)hrothgar.co.uk http://hrothgar.co.uk/YAWS/

5 5

barcode printing status in HEAD.
by Paul POULAIN 27 Aug '07

27 Aug '07

Hello guys, I think that,in head, the barcode management is in a poor state : the tools menu points to tools/barcode.pl, and barcodes/ is unreachable from menus. iirc, katipo wrote that part of the code. Could you have a look & fix what has to be fixed ? (I won't do it, as I don't have any customer using that feature, so I would break more than fix ;-) ) -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19

3 3

Time estimate for the translation of koha
by Axel Bojer 20 Aug '07

20 Aug '07

Hello! I am new to this list. We, two norwegians, are trying to get sponsored a translation of koha to norwegian bokmål. We are already involved in other translation projects and have a translation list for the most used data terms, so we have something to start with :-) Our first step is to estimate the work and time included. I searched your web pages for something describing the amount of work needed for this, but found nothing. So then I downloaded the installation files for 2.2.9 to have a look at the translation files, but the result is a bit confusing. First I searched for the pot-files: # tree -fin koha-2.2.9|grep pot$ koha-2.2.9/scripts/misc/translator/po/css_opac.pot [472] koha-2.2.9/scripts/misc/translator/po/default_intranet.pot [2576] These two files together fills about 3000 strings (see the parentheses, the amount are taken from kbabels catalog manager), that means approximately 40 man hours (a full week) for both translation and proofreading if this is all that is needed for a full translation. But then I searched for po-files: # tree -fin koha-2.2.9|grep po$ koha-2.2.9/scripts/misc/translator/po/css_intranet_zh_TW.po [3998] koha-2.2.9/scripts/misc/translator/po/css_opac_en_EN.po [471] koha-2.2.9/scripts/misc/translator/po/css_opac_es_ES.po [509] koha-2.2.9/scripts/misc/translator/po/css_opac_eu.po [425] koha-2.2.9/scripts/misc/translator/po/css_opac_fr_FR.po [509] koha-2.2.9/scripts/misc/translator/po/css_opac_it_IT.po [509] koha-2.2.9/scripts/misc/translator/po/css_opac_pl_PL.po [509] koha-2.2.9/scripts/misc/translator/po/css_opac_ta_MY.po [509] koha-2.2.9/scripts/misc/translator/po/css_opac_uk_UA.po [509] koha-2.2.9/scripts/misc/translator/po/css_opac_zh_CN.po [509] koha-2.2.9/scripts/misc/translator/po/css_opac_zh_TW.po [509] koha-2.2.9/scripts/misc/translator/po/default_intranet_en_EN.po [2313] koha-2.2.9/scripts/misc/translator/po/default_intranet_es_AR.po [2613] koha-2.2.9/scripts/misc/translator/po/default_intranet_es_ES.po [2613] koha-2.2.9/scripts/misc/translator/po/default_intranet_eu.po [3561] koha-2.2.9/scripts/misc/translator/po/default_intranet_fr_FR.po [2613] koha-2.2.9/scripts/misc/translator/po/default_intranet_it_IT.po [2613] koha-2.2.9/scripts/misc/translator/po/default_intranet_pl_PL.po [2613] koha-2.2.9/scripts/misc/translator/po/default_intranet_ta_MY.po [2613] koha-2.2.9/scripts/misc/translator/po/default_intranet_uk_UA.po [2613] koha-2.2.9/scripts/misc/translator/po/default_intranet_zh_TW.po [2613] koha-2.2.9/scripts/misc/translator/po/default_opac_pl_PL.po [200] koha-2.2.9/scripts/misc/translator/po/default_opac_zh_TW.po [205] koha-2.2.9/scripts/misc/translator/po/npl_intranet_uk_UA.po [3175] koha-2.2.9/scripts/misc/translator/po/npl_intranet_zh_CN.po [3175] koha-2.2.9/scripts/misc/translator/po/npl_intranet_zh_TW.po [3175] koha-2.2.9/scripts/misc/translator/po/npl_opac_hu_HU.po [507] koha-2.2.9/scripts/misc/translator/po/npl_opac_jp_JP.po [507] koha-2.2.9/scripts/misc/translator/po/npl_opac_kr_KR.po [507] koha-2.2.9/scripts/misc/translator/po/npl_opac_uk_UA.po [507] koha-2.2.9/scripts/misc/translator/po/npl_opac_zh_CN.po [507] koha-2.2.9/scripts/misc/translator/po/npl_opac_zh_TW.po [507] New files that only exists as po and not pot includes: -- css_intranet* [3998] -- default_opac* [200--205] -- npl_intranet* [3175] -- npl_opac* [507] (I also see these same files on net: http://cvs.savannah.nongnu.org/viewvc/koha/misc/translator/po/?root=koha&pa… some with an age of 2--3 years, last change four months ago) If we have to translate these also, we will have about 8000 strings more, that makes a big difference! Do you have the pot-files for these files? (I also see that the likenamed files don't always have the same amount of strings, wich puzzles me -- see, again, the parantheses). Are alle these files needed, if not wich one are and what are the others for? I also see that you have a web interface: Best regards Axel Bojer

3 7

Got Git? We do!
by Joshua M. Ferraro 19 Aug '07

19 Aug '07

Hi folks, Well, it's official, we've moved the version control for Koha from CVS, hosted on Savannah, to a fully distributed system, running Git (http://git.or.cz/) Git is the same version control system used by the Linux Kernel and was originally developed by Linus himself. Koha 3.0 will be the first release of Koha to be managed using Git. There's never been a better time to get active in Koha development, submitting patches is now a cinch. Here's a basic overview of how the process works: http://wiki.koha.org/doku.php?id=en:development:git_usage If you'd like to track development changes, feel free to view our git-web: http://git.koha.org and take note of the available RSS feeds. Thanks to everyone who's helped us through this transition, most notably MJ Ray (who I believe was the first to recommend Git), and Chris Cormack for doing most of the heavy lifting. Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS

1 0

Version numbering & updating
by Paul POULAIN 17 Aug '07

17 Aug '07

Hello world, with Koha 3.0 we will have a new web installer, that can take care of database updating. hdl has added a Version systempref, that contains the database version. for instance there is a <kohaversion> number in the koha.xml file. When a user authentify itself, Koha checks that kohaversion and Version are the same, otherwise, the user is automatically redirected to the web installer for database update. I think we can improve a little the behaviour (mainly for libLime & us : it will be an improvement only on a multi-koha setup). I would suggest to move the <kohaversion> in the code itself. Thus, when you install a new version, all your database will automatically go to update the 1st time the user logs in, on each virtual host / library. How can we handle database updates during development stages ? If I add a systempref, of a column, how to have LibLime and other devs handle that ? I suggest that version could be a long number, like in Perl : N.SSTTVVV : N is 3 (until it becomes 4 ;-) ) SS is the version number (00 for instance) TT is the 3rd level version number (00 for instance too) VVV is the developper subrelease number. An example, based on koha 2.2.9 (but I propose this method for Koha 3.0 only, of course) We are currently in Koha 2.0209001 I add a column to the table items, it's called mycolumn, it's a date. I will add to updatedatabase : if ($DBversion < 2.0209002) { $dbh->do("BEGIN TRANSACTION"); $dbh->do("ALTER TABLE `items` ADD `mycolumn` DATE NOT NULL"); $DBversion = 2.0209002; $dbh->do("UPDATE systempref set value=$DBversion where parameter='Version'"); $dbh->do("COMMIT"); } Once it is in the public code, every developper will automatically be redirected to the updatedatabase page, without having to take care of what I have commited ;-) What do you think of this idea ? -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19

4 8

a new reserves system
by Joann Ransom 16 Aug '07

16 Aug '07

Hi Kyle, I wonder if it is worth considering which bits of the current reserves module are 'broken', as in not working as well as they could, and which 'bits'are new or enhancements. Are you looking at doing a whole rewrite / reengineering, or developing the existing reserves code? cheers Jo. *Joann Ransom* Deputy Head of Libraries. Horowhenua Library Trust.

3 3

systempreferences (partial) cleaning
by Paul POULAIN 16 Aug '07

16 Aug '07

Hello world, I have reviewed all the systemprefs, and the following ones seems now useless : - acquisitions - printcirculationslips - ReadingHistory - checkdigit : not used anymore. we can clean Input.pm sub checkdigit (unless chris & HLTers want to reintroduce it) - memberofinstitution : SANOP = this systempref seems unconsistent. Could you explain what it is done for ? - patronimages - opacheader -disable_dictionnary - the 2 ldap* ones I have changed nothing on git, just to let you know. I have updated the french version of the systempreferences (misc/sql-datas/fr/mandatory/), but not the english ones Reviewing them I see some systemprefs that are unknown to me : intranetuserjs, IntranetmainUserblock, item-level_itypes, kohaspsuggest, OpacMainUserBlock, opacuserjs, SpecifyDueDate (seems some of them are used, but would be nice to have all of the usefull ones in updatedatabase : LibLimers, the ball is your's ;-) ) -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19

2 2

Automation Survey
by Joshua M. Ferraro 15 Aug '07

15 Aug '07

Hi folks, Just thought I'd pass along this survey from Marshall Breeding, in case anyone in the Koha community would like to participate. See the forwarded message below. Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS ----- "Marshall Breeding" <marshall.breeding(a)vanderbilt.edu> wrote: > I am conducting a survey on library automation trends. The survey > aims to measure how well libraries are satisfied with their > automation systems and the companies or other organizations that > support them. It also attempts to get some indication of whether > libraries are looking favorably on open source software for their > automation system. > > The survey works through the lib-web-cats directory within the > Library Technology Guides web site. This approach eliminates the > need to retype any demographic information regarding your library. > You will just need to navigate to your library in lib-web-cats. > > Here are the instructions on how to complete the survey: > > http://www.librarytechnology.org/lwc-survey-2007.pl > > I am hoping to get a very large response to this survey. I will > publish the results of the study in an upcoming article, provided I > get enough responses to ensure its validity. > > Thanks in advance for taking the time to participate in the survey. > > Please contact me directly if you have any problems accessing or > completing the survey. > > -Marshall Breeding > > > ----------------------------------------------------------------- > Marshall Breeding > Director for Innovative Technologies and Research > Vanderbilt University Library > 615-343-6094 > > Editor, Library Technology Guides > http://www.librarytechnology.org > > _______________________________________________ > Web4lib mailing list > Web4lib(a)webjunction.org > http://lists.webjunction.org/web4lib/

1 0

New Feature planned : Automatically adding/linking authorities when creating biblios
by Henri-Damien LAURENT 14 Aug '07

14 Aug '07

Hi there, We are planning to add a new feature with a new System preference (BiblioAddsAuthorities). When set to One, in addbiblio.pl when saving a new biblio, or modifying one, For each used field linked to an authority, unless there is already a $3 or a $9, we search authorities for a similar one (same subfields). If found, we add a $9 to the first authority number (supposed to be stored in 001 field) (or maybe we should display all results to select the authority to link to ?) Else, we create a new authority of the type linked to current biblio field, so that heading contains all subfields of the current biblio field We add a $9 to that biblio field which points to authid. End End Comments and remarks welcome. -- Henri-Damien LAURENT

1 0