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

koha-3.00.00 make fails
by Rick Welykochy 28 Dec '13

28 Dec '13

Hi all, I have downloaded http://download.koha.org/koha-3.00.00.tar.gz and began installing it on Debian/etch (in a Linux vserver environment). 0. FINE: cd koha-3.00.00 1. FINE: perl Makefile.PL 2. FAIL: make : : : Manifying blib/man3/C4::UploadedFile.3pm Manifying blib/man3/C4::BackgroundJob.3pm Manifying blib/man3/opac::opac-dictionary.3pm Manifying blib/man3/serials::member-search.3pm /usr/bin/perl "-Iblib/arch" "-Iblib/lib" fix-perl-path.PL blib /usr/bin/perl "-Iblib/arch" "-Iblib/lib" rewrite-config.PL blib/KOHA_CONF_DIR/koha-conf.xml Bad arg length for Socket::inet_ntoa, length is 0, should be 4 at rewrite-config.PL line 67. make: *** [blib/KOHA_CONF_DIR/koha-conf.xml] Error 255 Any ideas what went wrong and how to fix? Aside: there were a couple of other problems with this "out of the box" debian based install of Koha 3.0 which had to be fixed along the way, e.g. seven missing perl modules and libgd not found. I'll report on the entire process from unpacking to a running Koha/3.00.00 once I get to the end. cheers rickw -- ________________________________________________________________ Rick Welykochy || Praxis Services || Internet Driving Instructor The manual said Windows XP/SP2 or better so I installed Linux.

4 5

Proposal to change phone and email language on patron
by Nicole Engard 25 Sep '10

25 Sep '10

Hi all, I was talking with some librarians today and they were wondering if we could change the language on the patron record. Instead of saying Phone (home) could it read Phone (primary)? This suggestion came from the fact that many people now have only a cell phone and if you enter that number in the Phone (cell) box you don't see it on the transit slips or the patron record quick view on the left. This suggestion carries over to the email addresses as well. I recommend we use Primary, Secondary, and Tertiary instead of Home, Work, Cell so that the librarians and patrons can decide what's most important for the patron. What do you all think? Anyone have any strong feelings either way? I will gladly make the change if others think this makes sense, but I wanted to bring the question to you all first. Thanks Nicole C. Engard

7 15

system preference question (anonymous preferences)
by Nicole Engard 19 Jul '10

19 Jul '10

There are 2 system preferences in my most recent version of HEAD: - AnonSuggestions -- Set to anonymous borrowernumber to enable Anonymous suggestions - AnonymousPatron -- Set the identifier (borrowernumber) of the 'Mister anonymous' patron. Used for Suggestion and reading history privacy Does this mean that AnonSuggestions is not used? I personally think we need both and that Anon should be for suggestions and AnonymousPatron for reading history. Can someone please clarify these for me? Thanks Nicole

3 6

Proposal To Switch Koha's License to GPLv3 and AGPLv3 or AGPLv3
by Christopher Nighswonger 15 Jun '10

15 Jun '10

Greetings all, Some time ago the topic of changing the version/flavor of GPL license Koha is released under was discussed. In light of the momentum the community has built up in the area of change in recent months, now would be a good time to resume licensing discussions and bring them to a final resolve. Delaying them only means another round of disruptive changes at some point in the not too distant future. It would be nice to go ahead and have all the laundry cleaned and folded while we are about the task. As I see it, the advantage and rational for moving to GPLv3 are primarily that GPLv3 is compatible with AGPLv3. This allows us to accept work licensed under either of these two licenses. AGPLv3 carries the added advantage of the *additional* requirement that changes, etc. to the code be made available (at least) to those who access the changed code. This gives us quite a measure of protection more against Koha related code becoming locked up on a saas platform somewhere in the nebulous "cloud." Let's hash through this and come to a decision. Kind Regards, Chris

8 14

System pref for MARC field 008 authorities; additional logic for position 14
by Marcel de Rooy 31 May '10

31 May '10

Hi all, I would like to check if any of you feel the following adjustment on the marc21 field 008 plugin, is interesting for the community. >From bug report #4839: Currently, the default for this marc field is hardcoded in the plugin code of marc21_field_008_authorities.pl (two occurrences). I suggest to move this value to a new system preference. If this pref should not exist, the old hardcoded value could still be used. Furthermore, the default for position 14 (heading use: main or added entry) should be dependent on the authority type. For CHRON_TERM, GENRE/FORM and TOPIC_TERM, it should be b (not appropriate) instead of a (appropriate). Finally, a small bug should be resolved on the line: my $f32 = substr($result,32,2); this field is only one character, so should be: my $f32 = substr($result,32,1); Preview of patch: see below. Regards, Marcel --- .../value_builder/marc21_field_008_authorities.pl | 19 ++++++++++++++----- 1 files changed, 14 insertions(+), 5 deletions(-) diff --git a/cataloguing/value_builder/marc21_field_008_authorities.pl b/cataloguing/value_builder/marc21_field_008_authorities.pl index 1aae045..d05bea0 100755 --- a/cataloguing/value_builder/marc21_field_008_authorities.pl +++ b/cataloguing/value_builder/marc21_field_008_authorities.pl @@ -37,6 +37,8 @@ my ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime(time); $year +=1900; $mon +=1; my $dateentered = substr($year,2,2).sprintf ("%0.2d", $mon).sprintf ("%0.2d",$mday); +my $defaultval = C4::Context->preference('AuthorityField008Default') || '|| aca||aabn | a|a d'; + sub plugin_parameters { my ($dbh,$record,$tagslib,$i,$tabloop) = @_; return ""; @@ -51,7 +53,12 @@ sub plugin_javascript { function Focus$function_name(subfield_managed) { if (!document.getElementById(\"$field_number\").value) { - document.getElementById(\"$field_number\").value='$dateentered' + '|| aca||aabn | a|a d'; + var authtype=document.forms['f'].elements['authtypecode'].value; + var fieldval='$dateentered$defaultval'; + if(authtype && (authtype == 'TOPIC_TERM' || authtype == 'GENRE/FORM' || authtype == 'CHRON_TERM')) { + fieldval= fieldval.substr(0,14)+'b'+fieldval.substr(15); + } + document.getElementById(\"$field_number\").value=fieldval; } return 1; } @@ -61,8 +68,9 @@ function Blur$function_name(subfield_managed) { } function Clic$function_name(i) { + var authtype=document.forms['f'].elements['authtypecode'].value; defaultvalue=document.getElementById(\"$field_number\").value; - newin=window.open(\"../cataloguing/plugin_launcher.pl?plugin_name=marc21_field_008_authorities.pl&index=$field_number&result=\"+defaultvalue,\"unimarc field 100\",'width=1000,height=600,toolbar=false,scrollbars=yes'); + newin=window.open(\"../cataloguing/plugin_launcher.pl?plugin_name=marc21_field_008_authorities.pl&index=$field_number&result=\"+defaultvalue+\"&authtypecode=\"+authtype,\"unimarc field 100\",'width=1000,height=600,toolbar=false,scrollbars=yes'); } //]]> @@ -75,7 +83,8 @@ sub plugin { my ($input) = @_; my $index= $input->param('index'); my $result= $input->param('result'); - + my $authtype= $input->param('authtypecode')||''; + substr($defaultval,14-6,1)='b' if $authtype=~ /TOPIC_TERM|GENRE.FORM|CHRON_TERM/; my $dbh = C4::Context->dbh; @@ -87,7 +96,7 @@ sub plugin { flagsrequired => {editcatalogue => '*'}, debug => 1, }); - $result = "$dateentered".'|| aca||aabn | a|a d' unless $result; + $result = "$dateentered$defaultval" unless $result; my $f1 = substr($result,0,6); my $f6 = substr($result,6,1); my $f7 = substr($result,7,1); @@ -104,7 +113,7 @@ sub plugin { my $f28 = substr($result,28,1); my $f29 = substr($result,29,1); my $f31 = substr($result,31,1); - my $f32 = substr($result,32,2); + my $f32 = substr($result,32,1); my $f33 = substr($result,33,1); my $f38 = substr($result,38,1); my $f39 = substr($result,39,1); -- 1.6.0.6

1 0

Re: [Koha-devel] [Koha] changes in code doesnot appear
by Koustubha Kale 31 May '10

31 May '10

On Mon, May 31, 2010 at 1:55 PM, Nitesh Rijal <rijal.it(a)gmail.com> wrote: > > > On Mon, May 31, 2010 at 1:16 AM, Koustubha Kale <kmkale(a)anantcorp.com>wrote: > >> >> >> >> On Mon, May 31, 2010 at 1:25 PM, Nitesh Rijal <rijal.it(a)gmail.com> wrote: >> >>> Sorry, but I still did not understand what do you mean by "Dev Install". >>> I have installed KOHA 3.0.3 from source in Debian Lenny. >>> >> >> When you run perl Makefile.PL at the start of Koha installation the first >> question asked is Installation mode (dev, single, standard) >> > > Here I used default, its dev i guess > The default is standard which is what you seem to have.. > >> >>> >>> I have changed the files in >>> "/usr/share/koha/opac/htdocs/opac-tmpl/prog/en/modules/" and in intranet as >>> well. The same code is working in LIVE server, but I took days to be >>> working. I don't know why is it taking so long for the codes to be working. >>> >>> Please reply. >>> >>> >>> >> Off the top of the head.. >> 1) restart your apache server and also check for any errors shown in your >> Koha logs. >> 2) check if the code is mistakenly nested in the wrong <TMPL_IF> block. >> 3) If both the above fail, show us the code and your apache config >> >> I restarted the apache server, it showed no error. > I have checked the code, there is no <TMPL_IF> in my added code. > Which files should I send you? I have attached the detail.tmpl and > detail.pl. > > Please tell me what else should I send? > I may be in over my head already but here goes.. You seem to have a  but no corresponding fulltext added to $template->param( in detail.pl Is it added as a syspref perhaps or defined somewhere else? And this is more suited for koha-devel IMHO.. Regards, Koustubha Kale Anant Corporation Contact Details : Address : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka, Thane (w), Maharashtra, India, Pin : 400601. TeleFax : +91-22-21720108, +91-22-21720109 Mobile : +919820715876 Website : http://www.anantcorp.com Blog : http://www.anantcorp.com/blog/?author=2

1 0

Devanagari searching / sorting problem
by Koustubha Kale 28 May '10

28 May '10

Hi all, On a test server with latest git clone, I have Devanagari data. I am using zebra with icu. Here is my icu.xml <icu_chain locale="en_IN.UTF-8"> <transliterate rule="\'>\ "/> <transliterate rule="[:Number:] { '-' > '' "/> <transform rule="[:Control:] Any-Remove"/> <tokenize rule="l"/> <transform rule="[[:WhiteSpace:][:Punctuation:]] Remove"/> <transform rule="NFD"/> <transform rule="[:Nonspacing Mark:] Remove"/> <transform rule="NFC"/> <display/> <casemap rule="l"/> </icu_chain> Still when I search for any of the following words it seems to make no differentiation between any of the forms of the word.. They all return similar results with sorting order all mixed up. It makes no difference if I have turned off QueryAutoTruncate, QueryFuzzy & QueryStemming. कांळे काळे काळ काळो काळा काळं काळी काळां काळू काळु You can also see same behavior on www.granthalaya.org site which is running 3.00.00 with zebra + icu with above icu.xml file. I have two queries. 1) With all QueryAutoTruncate, QueryFuzzy, QueryStemming etc turned off shouldn't all the above forms of the word be treated as distinct words and NOT appear in other word searches? 2) The words are not sorted at all; even when I select Title A-z or Title Z-a. The ordering changes but its still a incorrect mixed bag. hdl_laptop had guided me on irc that I need to look into sort-string-utf.chr for the sorting. I read through a lot of stuff on icu and zebra but cant make out how to achieve this. Should I append the correct Devanagari sorting char sequence to the following lines in sort-string-utf.chr? lowercase {0-9}{a-y}üzæäøöå uppercase {0-9}{A-Y}ÜZÆÄØÖÅ Please help.. Regards, Koustubha Kale Anant Corporation Contact Details : Address : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka, Thane (w), Maharashtra, India, Pin : 400601. TeleFax : +91-22-21720108, +91-22-21720109 Mobile : +919820715876 Website : http://www.anantcorp.com Blog : http://www.anantcorp.com/blog/?author=2

1 1

Chrome extension for Koha libraries
by Cab Vinton 28 May '10

28 May '10

I've created a Firefox plugin for our library -- available here, http://userscripts.org/scripts/show/56847 (suggestions for improvement welcome!) -- and would like to create a similar plugin for Chrome. I found a Library Lookup extension here, https://chrome.google.com/extensions/detail/bghajdgipgikbgaendblaafckeekfamg but have been unsuccessful in trying to modify it to work with our Koha catalog -- I suspect because of the difference between the catalogs' respective result pages. (My "super-hack" was to simply replace all references to the original catalog w/ references to our own.) I'm pretty sure this project would be a trivial exercise for those on this list. If no one feels like creating a Koha-friendly extension & sharing it via Google Code, I'd be grateful for any pointers. Thank you all for your great work! Best, Cab Vinton, Director Sanbornton Public Library Sanbornton, NH

2 3

Help with documentation
by Nicole Engard 27 May '10

27 May '10

Hello all, There are two areas of the manual (maybe more later) that I don't know enough about to write and would love some help from anyone. They are: 1.4.6. Classification Sources 1.4.7. Record Matching Rules You can either write a summary up for me and email it or you can update the manual via git: http://git.koha-community.org/gitweb/?p=kohadocs.git;a=summary Thanks in advance, Nicole

1 0

Koha apt repository -- ALPHA level
by Lars Wirzenius 26 May '10

26 May '10

I have built some Debian packages for Koha, and configured an apt repository for them at debian.koha-community.org, kindly set up by Galen. Right now, only I can upload packages to the repository, but if that turns out to be a problem, we'll add an upload queue later. This way, we got something to work now. See http://debian.koha-community.org/koha/README for instructions. Note that the repository and the packages are ALPHA level. I have tested them a bit locally, but I do not know if they will work for anyone else. Also, I may have forgotten some important steps from the documentation. Please notify me of any problems, I will attempt to fix them promptly. DO NOT install this on a production server. It will break things. There are two packages: * koha, if you just want a Koha up an running * koha-common, if you want to host several Koha instances Either way, you'll need to do some post-installation configuration. I have not attempted to make the Debian packages configure everything automatically, or to use debconf to ask questions from the user and use the answers to configure things. At least at this stage, I think it is better to go for something simple that works. I have, however, put in some effort to make the packages flexible enough to suit several kinds of installation. Most importantly, I have made it possible to automate the installation by using koha-common and a custom package that provides configuration details for koha-common. I have such a custom package, but it is not currently fit to be shared. However, if there is interest, I would be happy to make a sample package that people can customize. Anyway, I hope that these packages will grow to be useful to the Koha community. PS. For the initial package upload, I had to deviate from the Koha git master branch, but I hope to not do that in the future. I've sent all patches I did to koha-patches.

3 2