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

Editing the Comments feature on Koha
by Cole Hudson 22 Feb '11

22 Feb '11

*Note: my apologies to all who have already seen this post on the koha general list-serv* Hi all, I'm running Koha 3.02 on Ubuntu 10.10. I'm trying to edit the comments feature that displays with each record in the opac. I'd like to edit it where the name of the patron is not pulled from each patron record-so as to make comments anonymous. Could someone point me in the right direction here on what code to edit/remove? Thanks. Cole Hudson Library Assistant MSU College of Osteopathic Medicine Macomb University Center

2 2

bugzilla workflow, question when "pushed, pls test" rejected
by Paul Poulain 22 Feb '11

22 Feb '11

Hello, On http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3495, chris has pushed a patch, it's now "patch pushed" "please test". I tested and have found a problem (see comment 3) Should I modify the patch status ? which value to set to have the RM seing there's something more to do ? What i know for sure is that it can't stay "patch pushed", as there's a problem ;-) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

2 4

koha cataloging
by Cybermon 22 Feb '11

22 Feb '11

Dear All, I would like to ask about few questions for koha configuration. I was successfully installed the koha used following address. http://wiki.koha-community.org/wiki/Koha_3.2_on_Debian_Squeeze. But my opac address not working only show the apache the default web page /it works/, which configuration is missing for me. I would like to add *084/other classification/* field for Koha cataloging, what should i do ? Best regards, Gana

2 1

KohaCon2011
by Koustubha Kale 22 Feb '11

22 Feb '11

Hi All, To get the ball rolling, I have put up a page in Koha wiki at http://wiki.koha-community.org/wiki/KohaCon2011 I have also put up a supporting site at http://kohacon11.vpmthane.org/ Its just a stub yet but I will be working on it. Looking for ideas, volunteers, suggestions, comments..... 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

2 2

Koha 3.2.4 is now available
by Christopher Nighswonger 22 Feb '11

22 Feb '11

It is with pleasure that I announce the release of Koha 3.2.4. The package can be retrieved from: http://download.koha-community.org/koha-3.02.04.tar.gz You can use the following checksum and signature files to verify the download: http://download.koha-community.org/koha-3.02.04.tar.gz.MD5 http://download.koha-community.org/koha-3.02.04.tar.gz.MD5.asc http://download.koha-community.org/koha-3.02.04.tar.gz.sig Release notes for 3.2.3 are below the fold. Come and get it! RELEASE NOTES FOR KOHA 3.2.4 - 22 February 2011 ======================================================================== Koha is the first free and open source software library automation package (ILS). Development is sponsored by libraries of varying types and sizes, volunteers, and support companies from around the world. The website for the Koha project is http://koha-community.org/ Koha 3.2.4 can be downloaded from: http://download.koha-community.org/koha-3.02.04.tar.gz Installation instructions can be found at: http://wiki.koha-community.org/wiki/Installation_Documentation Koha 3.2.4 is a bugfix/maintenance release. Highlights of 3.2.4 ====================== Some of the higher profile bugs addressed in this release are: 2341 items marked 'On Order' (notforloan == -1) don't interact correctly with opac-reserve.tmpl 4263 repeatable subfields in items 5376 Batch Edit and Delete need Superlibrarian Permissions 5683 link_bibs_to_authorities.pl can corrupt records 5477 Test cases requiring database access fail 5681 Autobarcode using C4::Barcode has issues with leading zeros and large values 5731 If an item doesn't have a collection code set, moredetail.pl will error This release also contains a variety of minor enhancements improving Koha's interface and underlying scripts as well as updates to several translations. Bugs fixed in 3.2.4 ====================== 2742 Wrong language name in the preferences 3009 Change items.content field so it prints due date by default 3212 MARC21 leader plugins should force Leader/09 to 'a' 3319 Need a nicer error message when attempting to add a patron with no libraries defined 4160 Currency Conversion dosn't handle rates other than 100 5115 Tags JavaScript includes many untranslatable strings 5140 In Chrome, drop-down menus disappear after using pop-up calendar 5230 MARC export by call number range results in a zero byte file 5661 Authority search return an "Error 500" when "Sort by" is set to "No order" 5673 Incorrect Test of guarantorid 5689 System preference notifications are not translatable 5690 items.timestamp was not being updated when an item was edited 5691 If someone deletes all items, with independent branches on, it deletes all 5699 Don't ignore subfield 3 when building a new record (UNIMARC specfic) 5700 Statuses not being set properly 5718 Moveitem has the wrong permissions 5735 Expanding/collapsing cloned fields in editor takes original field 5736 Fixing some zebra configuration errors in marc21/biblios/record.abs 5741 Extra comma causes JavaScript error in Internet Explorer 5745 overdues with fines not showing titles 5777 System preferences Tab content title and Save button partially translatable 4306 Label manage batch listing should show item-level itemtype 5452 Overdue date color in borrower's today issues 5616 UTF-8 problem in Card View 5629 Adding anchor to holdings link in opac-detail.pl tabs 5665 Routing slip prints too wide for narrow printers 5702 Opac - Results : Highlight link need IF condition 5726 Fix a bug in the selection of biblios to merge 5727 Use of uninitialized value in concatenation (.) or string 5734 Fix column order in issue history 5751 Removing refetences to unused members quicksearch code/template 5759 When printing a borrowers information the secondary email address is not printed 5769 notice tab disappearing on edit patron 5776 menu on funds wraps when only 1 fund 5649 Change wording on review.tmpl from white/blacklists to approved/rejected 5654 misc/installer_devel_notes not needed 5716 Whitespace correction for browse shelf link 4931 Stocktaking must be based on holdingbranch instead of homebranch 5506 Translation Process Simplification 5532 "Saved" message for sysprefs editor should show names of saved prefs 5733 Empty cart in intranet when session is closed 5760 Add the jquery table sorter to borrowers reading record System requirements ====================== Changes since 3.0: * The minimum version of Perl required is now 5.8.8. * There are a number of new Perl module dependencies. Run ./koha_perl_deps.pl -u -m to get a list of any new modules to install during upgrade. Upgrades ====================== The structure of the acquisitions tables have changed significantly from 3.0.x. In particular, the budget hierarchy is quite different. During an upgrade, a new database table is created called fundmapping that contains a record of how budgets were mapped. It is strongly recommended that users of Koha 3.0.x acquisitions carefully review the results of the upgrade before resuming ordering in Koha 3.2.x. Documentation ====================== As of Koha 3.2, the Koha manual is now maintained in DocBook. The home page for Koha documentation is http://koha-community.org/documentation/ As of the date of these release notes, several translations of the Koha manual are available: English: http://koha-community.org/documentation/3-2-manual/ Spanish: http://koha-community.org/documentation/3-2-manual-es/ French: http://koha-community.org/documentation/3-2-manual-fr/ The Git repository for the Koha manual can be found at http://git.koha-community.org/gitweb/?p=kohadocs.git;a=summary Translations ====================== Complete or near-complete translations of the OPAC and staff interface are available in this release for the following languages: * Chinese * Danish * English (New Zealand) * English (USA) * French (France) * French (Canada) * German * Greek * Hindi * Italian * Norwegian * Portuguese * Spanish * Turkish Partial translations are available for various other languages. The Koha team welcomes additional translations; please see http://www.kohadocs.org/usersguide/apb.html for information about translating Koha, and join the koha-translate list to volunteer: http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-translate The most up-to-date translations can be found at: http://translate.koha-community.org/ Release Team ====================== The release team for Koha 3.2 is Release Manager: Galen Charlton <gmcharlt(a)gmail.com> Documentation Manager: Nicole Engard <nengard(a)gmail.com> Translation Manager: Chris Cormack <chris(a)bigallofwax.co.nz> Release Maintainer (3.0.x): Henri-Damien Laurent <henridamien.laurent(a)biblibre.com> Release Maintainer (3.2.x): Chris Nighswonger <cnighswonger(a)foundations.edu> Credits ====================== We thank the following individuals who contributed patches to Koha 3.2.4: D Ruth Bavousett Jared Camins-Esakov Colin Campbell Frédérick Capovilla Jerome Charaoui Galen Charlton Chris Cormack Frédéric Demians Magnus Enger Katrin Fischer Henri-Damien LAURENT Owen Leonard Chris Nighswonger Liz Rea Marcel de Rooy Paul Poulain Brice Sanchez David Schuster Robin Sheat Reed Wade Ian Walls We regret any omissions. If a contributor has been inadvertantly missed, please send patch against these release notes to koha-patches(a)lists.koha-community.org. The 3.2.x Release Maintainer especially thanks the 3.4 Release Team and all who participated in QA for their diligent labors in testing and pushing well over 330 patches since the 3.2.0 relese. Their continued work very much makes possible the release of 3.2.4 on its announced schedule. Revision control notes ====================== The Koha project uses Git for version control. The current development version of Koha can be retrieved by checking out the master branch of git://git.koha-community.org/koha.git The branch for Koha 3.2.x (i.e., this version of Koha and future bugfix releases) is 3.2.x. The next major feature release of Koha will be Koha 3.4.0. Bugs and feature requests ====================== Bug reports and feature requests can be filed at the Koha bug tracker at http://bugs.koha-community.org/ Naku te rourou, nau te rourou, ka ora ai te iwi.

1 0

Call for Articles: February Newsletter
by Nicole Engard 21 Feb '11

21 Feb '11

Hi all, It's that time again - please get me your newsletter articles by the 23rd (your time zone) of February so that I can include them in the newsletter. Thanks a bunch, Nicole C. Engard

1 1

Re: [Koha-devel] Solr and Z3950 server some news.
by Thomas Dukleth 21 Feb '11

21 Feb '11

When briefly testing the BibLibre test configuration of SimpleServer Z39.50 server I have found same problem as BibLibre are reporting when using yaz-client. I have also noted some other issues. 1. BAD MARC ERROR. When setting format to UNIMARC in yaz-client, the following error message is returned along with the record when displaying a record with the show command. "[]Record type: Unimarc bad MARC. Dumping as it is:" When setting format to XML in yaz-client, no error message is returned when displaying a record with the show command. "[]Record type: XML" The issue seems to be consistent for all records in the result set. YAZ is converting between ISO 2709 and MARCXML on the client side. yaz-client does not report a "bad MARC" error when displaying UNIMARC MARCXML records returned from Zebra in ISO 2709 form. Whatever the MARC error may be, it prevents YAZ from parsing the records properly in ISO 2709. Consequently, unlike yaz-client, my very well tested PHP YAZ based Z39.50 client obtains the result set but cannot even attempt to display the records because it relies upon YAZ for parsing them. 2. INVARIANT RESULT SET. In the configuration which I tested, any query would return exactly the same 1011 record result set whether or not there would be any legitimate matches. 3. MISSING EXPLAIN RECORD. Lack of an Explain record should not be fatal but might be helpful for obtaining more debugging information from YAZ. 4. DEBUGGING. I do not have time to try intensive tests myself. First, fix the issue where the result set is an invariant 1011 records. I suggest having yaz-client save the ISO 2709 records, then attempt to validate them with MARC::Lint keeping in mind that most errors would be from the MARC 21 checks in MARC::Lint. I have not verified that MARCXML is working with SimpleServer using Solr/Lucene but I would be happy to test that if some SimpleServer target would be configured to return only MARCXML. If all else fails, Index Data can help solve the problems for a very significant fee. Thomas Dukleth Agogme 109 E 9th Street, 3D New York, NY 10003 USA http://www.agogme.com +1 212-674-3783

2 3

Who are the various Koha vendors in the USA?
by Joann Ransom 21 Feb '11

21 Feb '11

ByWater have an excellent reputation in the States - check out Marshall Breeding's Perception guide: http://www.librarytechnology.org/perceptions2010.pl I wouldn't go near PTFS if you are looking for open source Koha. Cheers Jo. 2011/2/21 Buster <storypage(a)gmail.com> > And which one do you use, if any? > > > I know about LibLime and Bay Water. Anybody else? > > --JimMaroon > > -- > > ================================================== > "The man, who, by his own and his family's labour, can provide a > sufficiency of food and raiment and a comfortable dwelling place, is not a > poor man." --William Cobbett, *Cottage Economy*, 1826. > > > > _______________________________________________ > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha > > -- Joann Ransom RLIANZA Head of Libraries, Horowhenua Library Trust. *Q: Why is this email three sentences or less? A: http://three.sentenc.es* -- Joann Ransom RLIANZA Head of Libraries, Horowhenua Library Trust. *Q: Why is this email three sentences or less? A: http://three.sentenc.es*

1 0

Re: [Koha-devel] [Koha] KohaCon 2011 : The Votes Are In
by Koustubha Kale 19 Feb '11

19 Feb '11

Hi All, I am just back from a Koha training trip in Konkan. And this is great news to come back to. :) Thanks to all who voted for VPM, Thane, India. And also special thanks to Nicole for conducting the vote. I will start preparations and discussions immediately as soon as I reach office. Looking forward to participation, help and advise from all the Koha community in making KohaCon11 a success.. 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 On Fri, Feb 18, 2011 at 5:26 PM, Nicole Engard <nengard(a)gmail.com> wrote: > On Fri, Feb 18, 2011 at 6:27 AM, MJ Ray <mjr(a)phonecoop.coop> wrote: >> So... how can we win next time? In particular, should we bid with >> Weston-super-Mare or Edinburgh and are there any other pointers or >> tips that people would like to pass on, on-list or privately? > > MJ, I think it was pure numbers! With India off the table next year > (based on talks on #koha) I think we're gonna see a European location > next year :) I liked your location choice - all I wanted was for it to > be in the spring instead of the fall (but that's just me). > > Nicole > _______________________________________________ > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha >

1 0

Add authorities add/del/mod logging
by Tomas Cohen Arazi 18 Feb '11

18 Feb '11

Hi, I'm planning to add logging to the authorities management. In the 'action_logs' table we have, for biblios: module : CATALOGUING action : ADD/DELETE/MODIFY for biblios, and other actions for issuing, object : a biblionumber or itemnumber info : string: 'biblio' or 'item' or previous 'marc' field (when MODIFYing) My first thought was that we could use 'CATALOGUING' too, and that instead of 'biblio' in the info field we could use 'authority'. Something like module : CATALOGUING action : ADD/DELETE/MODIFY object : a authid info : string: 'authority' or previous 'marc' field (when MODIFYing) But I realized that it is impossible to differentiate, from tools/viewlog.pl point of view, if we're talking about a biblionumber or an itemnumber (and now an authid) when the operation is MODIFY. Check this from Items.pm: logaction("CATALOGUING", "MODIFY", $itemnumber, $new_item_marc->as_formatted) if C4::Context->preference("CataloguingLog"); In the results in fact, they are all shown as biblios (bug?)! So, adding 'authid' to the mix will make it worse. Should I add AUTHCAT module? Should we split CATALOGUING module into BIBLIOCAT and ITEMCAT? Also: should we avoid logging when calling ModItem from Issues::AddIssue? It looks too much overhead as there is a call to $new_item_marc->as_formatted. Have a nice weekend! To+

1 0