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

Meeting reminder - general meeting, tomorrow, 2 June 2010, 10:00 UTC+0
by Galen Charlton 02 Jun '10

02 Jun '10

Hi, The next general meeting of the Koha project is scheduled for tomorrow, 2 June 2010, at 10:00 UTC+0. The page for the meeting, including current agenda and links to time converters, can be found at: http://wiki.koha-community.org/wiki/General_Meeting,_June_2_2010 At present, the agenda is: 1. Update on Roadmap to 3.2. 2. Update on Roadmap to 3.0. 3. Follow-up on actions from General Meeting, May 5 2010. 4. Discuss switching licensing for all new code submissions to Affero General Public License (AGPL) 1. AGPL does not prevent unfriendly vendor lock-in (still achievable through access control, particularly to the databases) while introducing onerous burdens on friendly hosters. http://lists.katipo.co.nz/pipermail/koha/2010-May/023816.html 5. (If time permits) Revisit vendor listing requirements on koha-community.org. 1. Anti-privatisation requirement (private domains or trademarks, legal proceedings) http://lists.katipo.co.nz/pipermail/koha/2010-May/023785.html 2. Linkback requirement - also http://lists.katipo.co.nz/pipermail/koha/2010-May/023785.html 6. info(a)koha.org address: various places reference an info(a)koha.org address whose destination is unknown. Should we have an info(a)koha-community.org? If so, where should it go? 1. forward to the main Koha mailing list? 2. replace references to info(a)koha.org with themain Koha mailing list address? 3. establish a new koha-info mailing list that info(a)koha-community.org forwards to? 4. have it be an auto-responder that directs the inquiry to the project website? 7. Agree times of next meetings. Regards, Galen -- Galen Charlton gmcharlt(a)gmail.com

1 0

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

Bugzilla - call for additional administrators
by Galen Charlton 26 May '10

26 May '10

Hi, At present, Chris Cormack and I are the only people who have administrator-level accounts in the Bugzilla. I am calling for additional volunteers to become administrators, who would be responsible for helping to: * add, subtract, reassign, and modify components as needed * help handle requests for batch changes to bugs * perform other configuration and administrative tasks as needed In particular, I am looking for additional coverage outside of the US and NZ working hours. If you are interested, please respond publicly to this mailing list. Regards, Galen -- Galen Charlton gmcharlt(a)gmail.com

1 0

Bug assignees - call for volunteers
by Galen Charlton 26 May '10

26 May '10

Hi, The current list of default assignees for bug categories is here: http://wiki.koha.org/doku.php?id=en:development:bug_default_assignees I am issuing a call for module experts to volunteer to be default assignees, and for existing assignees to confirm their willingness and availability to investigate, fix, and delegate bugs. By the time of the next general meeting (3 March 2010 at 19:00 UTC+0), please reply to this thread and signal if: * you want to be or remain as assignee for a component * you no longer want to be an assignee * you want to be added to the default CC list for a component In particular, one of the things we should figure out by the time of the meeting is which components do not have anybody actively interested in being assignee. I'm the default assignee for a lot of these, and would dearly like this to change. The components I'm specifically interested in remaining assignee for are: Architecture, internals, and plumbing Cataloging MARC Authority data support MARC Bibliographic data support MARC Bibliographic record staging/import Searching Z39.50 / SRU / OpenSearch Servers As a reminder, anybody who wants to work on a bug should feel free to do so, particularly if the bug's status hasn't been changed to 'assigned' - in other words, I don't think it should be the role of the bug assignees to have to explicitly fix or delegate every single bug in their components, just to watch over the component as a whole and ensure that important bugs do get addressed. Regards, Galen -- Galen Charlton gmcharlt(a)gmail.com

8 8

Re: [Koha-devel] Patrons with no Checkouts report
by Joe Atzberger 25 May '10

25 May '10

That seems pretty reasonable. Beneficial patches are accepted from anybody! > --joe > On Wed, May 19, 2010 at 9:31 AM, Toni <arosa(a)tginet.com> wrote: > Hello, > >> > After looking into the code of the predefined report "Patrons with No > >> Checkouts" (borrowers_out.pl), I wonder whether the way it is generated > >> (at least in Koha version 3.0.5) is a Bug: > >> It only takes into consideration "old_issues" table, which means that > >> Patrons having items for the first time will appear in the list of > >> "Patrons with no Checkouts". > >> > Taking this case (first time users) into account should be as easy as > >> filtering out by the "issues" table in addition to the “old_issues” table. > >> > > Is it a BUG? Should I therefore report it? > >> If I report it, I could attach the necessary modification to make it work > >> taking in consideratin first time borrowers, Do you accept "casual" > >> patches from external people? > >> Thanks, > >> > Toni >

1 0