- Koha - lists.katipo.co.nz

Re: [Koha] Proposal to form Koha Technical Committee (and Time Based Releases)
by Lori Bowen Ayre 22 Nov '10

22 Nov '10

I want to pull out these paragraphs from David Lang's email because I think it is an important point about the benefits of sticking to time-based releases. I think if we had stuck to this principle, we wouldn't be having the troubles we are having (as a community) with some of our biggest contributors needing to support versions of Koha that are different from the latest official version. *Several years of time based releases after many years of 'let the dates > slip, the release will be better' seems to show pretty decisivly that > frequent releases with what's ready at that time work better in practice > than delaying a release until the features that were tagged for it are all > ready.* * > * *if you delay a release until the feature is ready, there is a lot of **preasure > to declare it ready when it really isn't, because people really **want all > the other features that are in a new release.* * > * *because the releases aren't predictable, developers really want thir stuff > **to go into _this_ release because they don't know how long they will > have **to wait for the next one. If you have frequent releases, the > knowledge of **when the next release will happen (and therefor when the > code will be **upstream)* Well said, David. And here here! And ++ Lori Ayre

4 5

RFCs - could we make better use of MediaWiki?
by Magnus Enger 21 Nov '10

21 Nov '10

Hi! I agree with everything that has been said about making RFCs more visible and accessible, and have some ideas for how MediaWiki might help us achieve this. I don't think the layout of the RFCs is clear enough as it is, all of these pages seem (at first glance) to be doing some of the same things: http://wiki.koha-community.org/wiki/Category:RFCs http://wiki.koha-community.org/wiki/Category:RFCs:for_3.2 http://wiki.koha-community.org/wiki/Category:3.2 And how do you find out which RFCs have sponsors, which are under active development etc? *** Editing and "cataloguing" RFCs For another project I have used the "Semantic Mediawiki" (http://semantic-mediawiki.org/) family of extensions to MediaWiki, and I think it/they might help with making our RFCs easier to interact with. It would go something like this: 1. Create a template that collects relevant information about RFCs, building on Template:RFC 2. Create a form (http://www.mediawiki.org/wiki/Extension:Semantic_Forms) that makes filling in the template easy, including lists of allowed values for things like e.g. sponsorship status or development status. 3. Create a number of pages with inline queries (http://semantic-mediawiki.org/wiki/Help:Inline_queries) that list RFCs based on given criteria, e.g. - all sponosored RFCs - all RFCs that do not have sponsors - all RFCs that are in active development - etc It is possible to confugure what is shown in these query results, so there could be columns for targeted Koha version etc (Basically all the info that is collected by the template). These pages could also link to the same results as RSS (http://semantic-mediawiki.org/wiki/Help:Inline_queries#Exporting_query_resu….) making it relatively easy to monitor e.g. all new, unsponsored RFCs. We could also create categories for different areas of Koha, e.g. cataloguing, aquisitions etc. *** Enhance RFC pages The page for an RFC could perhaps also be enhanced in interesting ways: * Pull in info from the relevant bug on Bugzilla (http://www.mediawiki.org/wiki/Extension:Bugzilla_Reports - I havn't used this, but it looks promising) * Pull in info (commits) from public git repos when a branch has been published for the RFC (http://www.mediawiki.org/wiki/Extension:RSS) * Provide a "standard" comment form as an alternative to the "Talk" page (http://www.mediawiki.org/wiki/Extension:ArticleComments) If this sounds like something people would be interested in trying out, I'd be happy to spend some time on setting it up. Regards, Magnus libriotech.no

8 10

Implementing RDA?
by Sharon Reidt 21 Nov '10

21 Nov '10

Dear fellow members of the Koha community, Now that the (possible) implementation of RDA is growing closer, I would be curious to learn what (if any) changes will be made to the Cataloging module in Koha. Are there any plans at this time to implement RDA in Koha? Thank you! Sharon Reidt Technical Services Specialist Rice-Aron Library Marlboro College

7 6

Koha 3.2.1 Released
by Chris Nighswonger 21 Nov '10

21 Nov '10

Greetings: It is with pleasure that I announce the release of Koha 3.2.1 two days ahead of the scheduled release date. The package can be retrieved from: http://download.koha-community.org/koha-3.02.01.tar.gz You can use the following checksum and signature files to verify the download: http://download.koha-community.org/koha-3.02.01.tar.gz.MD5 http://download.koha-community.org/koha-3.02.01.tar.gz.MD5.asc http://download.koha-community.org/koha-3.02.01.tar.gz.sig Come and get it! RELEASE NOTES FOR KOHA 3.2.1 - 20 November 2010 ======================================================================== 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.1 can be downloaded from: http://download.koha-community.org/koha-3.02.01.tar.gz Installation instructions can be found at: http://wiki.koha-community.org/wiki/Installation_Documentation Koha 3.2.1 is a bugfix/maintenance release. Highlights of 3.2.1 ====================== Some of the higher profile bugs addressed in this release are: * Further fixes smoothing the upgrade process from 3.0.x to 3.2.x. (Bug 4141) * Subject links in search results are now properly formed. (Bug 4074) * Advanced notice preferences set during new patron creation are now saved correctly. (Bug 4254) * Img tags in XSLT templates are now handled correctly during automatic translation. (Bug 4472) * The "Show More" link listed with facets has been made to work. (Bug 4520) * Amanzon book covers will now work with ISBN13. (Bug 4305) * The staff client XSLT templates are now unique. (Bug 4423) * The Unimarc XSLT templates are now translated in English. (Bug 5204) Other notable fixes in this release include: * A number of spelling corrections * Various fixes to formerly non-translatable phrases * Some tweaks to fix display problems in Internet Explorer This release also contains a variety of minor enhancements improving Koha's interface. Maintenance activities performed in this release include: * A number of new and improved test cases * Removal of unused dependencies Bugs fixed in 3.2.1 ====================== 2122 Grayed out Fields not always visible 2567 008 editor falsely populating Illustrations and Nature of Contents positions 3013 Value builder for 006 and 008 need choices for all format types 3211 cataloging value plugin forms should be valid XHTML 3271 Missing message when adding to a list with no items selected 3811 biblios record.abs indexes 008 language as numeric (marc21) 4074 The 'Subject(s)' link(s) are malformed resulting in no search results 4141 reconcile 3.0.x and HEAD database updates for 3.2.0 4254 adding new patron advanced notice doesn't save 4261 keyword mapping should show which framework the map is for 4305 Amazon book covers do not work with ISBN13 4359 noItemTypeImages not active in OPAC 4423 Staff Client XSLT is just a copy of the OPAC one 4472 img tags in xslt broken after automatic translation 4498 Acq always shows '1 suggestions waiting' 4515 Few very small errors in opac-search.pl 4520 facets "show more" doesn't work 4866 Optionally enable Change event for item plugins 4912 After editing private list, user should be redirect to private lists 4913 Budget planning pages should show currency name instead of symbol 4924 Public/Internal notes missing in staff normal view 4933 Link to subfield's edit tab from MARC subfield structure admin summary 4963 sys prefs need date hints and/or picker 4979 Acq: input fields for new record are too short 4980 Acq: pull down 'Restrict access to:' for funds not translatable 4986 move serials prefs from cataloging tab 4991 Overhaul Calendar interface 5003 Can not search for organisation by name 5004 Do not block deletion of cities when instances exist in borrowers table 5008 "Remove" link missing when viewing Cart in expanded "More details" view 5019 funds link doesn't go to list 5037 If patron category is empty it shouldn't show 5050 Staff client's language preference should be grouped with I18N/L10N preferences 5056 Untranslatable strings in members.js 5059 Inconsistent use of ordering price and list price in vendor form 5066 Incorrect use of localtime function when calling _session_log 5075 Terms not highlighted w/ xslt on 5082 Not translatable name of default framework 'Default' in MARCdetail.tmpl 5110 NewItemsDefaultLocation should be under cataloging 5112 Organisation does not show links to professional patrons 5114 Can't edit basket in Internet Explorer 5117 Misspelled word: Orgnisztion 5118 Misspelled word: Currencey 5119 Misspelled word: correspounding 5121 Misspelled words: stripts biographyl Begininning 5122 Misspelled word: Transfered/transfered 5123 Misspelled words: Depdending Commited flutucations 5124 Duplicate and Misspelled words: periodicy outputing 5128 Define default 9xx fields for Unimarc setup in all languages 5130 Misspelled words: biblographic delimeter extention 5132 Misspelled words: Acquistion Succesfully professionnal 5133 Misspelled words: reservior notifiying deleete 5134 Misspelled words: exisiting anomolies genereated 5135 Authorized value input maxlength should match table column 5136 Replace embedded SQL query with call to GetAuthorisedValues 5137 Remove obsolete code for counting issues by item type in circulation 5142 Untranslatable strings in tag review template 5146 Patron Import Requires Header Row 5149 Link to noItemTypeImages pref on item types is wrong 5151 Saved Report Breadcrumb in bold 5152 confirm buttons different styles on lists 5162 patron attributes 'new' link should create blank value 5163 holds to pull is titled pending holds 5168 add holdings' should read 'add/edit items' 5171 edit items should be edit item when under 1 item 5175 The opac XSLTDetails view field Publisher: doesn't provide a hyperlink as the non XSLT view does. 5177 Descending sort search result defined by syspref doesn't work 5190 MARC and UNIMARC bibliographic fields documentation accesible when cataloging 5204 Unimarc xslt default templates are in french 5210 Function of back button on batch modification result page unclear 5214 undefined itype images cause broken image icon in request.pl 5219 Perltidy code 5221 Preselect tab containing itemtype/authorized value image in use 5223 related subjects' should read 'subjects' 5224 Replace Shopping Basket with basket 5235 checkout receipt should include patron name 5236 "hide my tags" link does nothing 5237 Special characters in patron barcodes cause renewals to fail. 5243 C4::Search::SimpleSearch call in AuthoritiesMarc.pm 5254 no need to scroll left to right on acq z search 5258 Order should read 'order line' in receive table 5301 In C4/XSLT.pm, itemcallnumber can contain special XML characters 5308 subscriptionroutinglist table is too lax 5309 Progress bar inaccurate 5311 Language dropdown in advanced search broken? 5315 Authority search Templates refer to unused variable 5318 rank weight error in ccl.properties 5322 pwgen not a dependency for the packages 5326 when ExtendedPatronAttributes off error links to old sys prefs 5327 Unit tests required for all C4 modules 5363 Remove dependency on Cache::Memcached::Fast 5368 Browse Shelf link appears even if there isn't an itemcallnumber 5370 Fix all the references to koha.org 5372 Editing a bilbio record, existing value can be replace by default value 5380 an end to copy-and-paste-itis 5381 Fines in notices prints always 0.00 5385 Correct POD errors as highlighted by podchecker 5389 Business::ISBN should be marked as required dependency 5392 reserve/renewscript logging lots of warnings 5393 test case for verifying XML/XSLT files are well-formed 5396 UseTablesortForCirc syspref to toggle table sorter on circ/ circulation.pl 5400 add test case to detect merge conflict markers in the code 5412 Double quotes in publisher name, no date cause search results links to break Commits in 3.2.1 without a referenced bug report: * Adding a simple test for Service.pm * create unit test files * Create Unit Test for ImportBatch * unit test stub for Z3950.pm * Test modules compile * Updated links in Main Page Help * remove extraneous semicolon * History updates * history updates - recent releases * Adding 3.2 Release Maintainer to Release Team List * Adding possibility to cleanup_database.pl to purge only older sessions * Display available error information during bulkmarcimport * add missing help file for merging records * (MT 2985) simplify CanBookBeReserved * fix use of outdated boilerplate * remove unused template include * Misspells: deleteing -> deleting * Misspell: Quanity -> Quantity 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 Translation related commits new to 3.2.1: * Staff interface .po file updates * Russian and Ukranian opac language updates * Ukranian and Russian syspref language updates * German and italian language updates 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.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.1. Nahuel Angelinetti TomÃ¡s Cohen Arazi Jared Camins-Esakov Colin Campbell Galen Charlton Chris Cormack Nate Curulla FrÃ©dÃ©ric Demians Andrew Elwell Brian Engard Nicole Engard Magnus Enger Katrin Fischer Daniel Grobani Kyle M Hall Srdjan Jankovic Bernardo Gonzalez Kriegel Henri-Damien Laurent Owen Leonard Chris Nighswonger Paul Poulain MJ Ray Liz Rea Marcel de Rooy Robin Sheat ByWater Solutions Zeno Tajoli 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 100 patches since the 3.2.0 relese. Their work very much makes possible the release of 3.2.1 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.

2 1

Re: [Koha] Borrowers' password encryption method in database
by Paul 20 Nov '10

20 Nov '10

At 07:01 AM 11/20/2010 -0500, Chris Nighswonger wrote: >2010/11/20 Altaf Mahmud ><<mailto:altaf.mahmud@gmail.com>altaf.mahmud(a)gmail.com> >Hi, >I want to know how Koha saves its borrowers' password in database? Is it >one-way conversion? For example, if a password is saved as >'4QrcOUm6Wau+VuBX8g+IPg', can I decode it back to its original text which >was '123456'? >They are stored as MD5 hashes and you cannot "decode" them as such. IIRCC, >what you must do is make an MD5 hash of the password and then compare the >two hashes. They should be the same. The above is not a "pure" MD5 hash [32 character hexadecimal value]; for 123456, it would be e10adc3949ba59abbe56e057f20f883e However, the decrypt function at <http://www.cmd5.org/> does return 123456 for 4QrcOUm6Wau+VuBX8g+IPg Best - Paul

2 1

Borrowers' password encryption method in database
by Altaf Mahmud 20 Nov '10

20 Nov '10

Hi, I want to know how Koha saves its borrowers' password in database? Is it one-way conversion? For example, if a password is saved as '4QrcOUm6Wau+VuBX8g+IPg', can I decode it back to its original text which was '123456'? Thanks. -- Altaf Mahmud System Programmer Ayesha Abed Library BRAC University Bangladesh.

3 3

how to ldap configration on koha
by tibabu beza 20 Nov '10

20 Nov '10

how to ldap configration on koha. i try to configra ldap on koha like below but it give me the following fantal error. how I can correct it <useldapserver>1</useldapserver>  <ldapserver id="idm"> <hostname>192.168.5.55</hostname> <base>dc=idmdomain,dc=edu</base> <user>cn=kohaadmin,ou=koha,dc=idmdomain,dc=edu</user>  <pass>adama</pass>  <replicate>1</replicate>  <update>1</update>  <auth_by_bind>1</auth_by_bind>  <principal_name>%s(a)my_domain.com</principal_name>  <mapping>  <firstname is="givenname" ></firstname> <surname is="sn" ></surname> <address is="postaladdress" ></address> <city is="l" >Athens, OH</city> <zipcode is="postalcode" ></zipcode> <branchcode is="branch" >MAIN</branchcode> <userid is="uid" ></userid> <password is="userpassword" ></password> <email is="mail" ></email> <categorycode is="employeetype" >PT</categorycode> <phone is="telephonenumber"></phone> </mapping> </ldapserver> Koha error The following fatal error has occurred: No "ldapserver" in server hash from KOHA_CONF: /etc/koha/koha-conf.xml at /usr/share/koha/lib/C4/Auth_with_ldap.pm line 53. Compilation failed in require at /usr/share/koha/lib/C4/Auth.pm line 44, <DATA> line 275. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Auth.pm line 47, <DATA> line 275. Compilation failed in require at /usr/share/koha/intranet/cgi-bin/mainpage.pl line 23, <DATA> line 275. BEGIN failed--compilation aborted at /usr/share/koha/intranet/cgi-bin/mainpage.pl line 23, <DATA> line 275. Apache Server version: Apache/2.2.14 (Ubuntu) Server built: Apr 13 2010 19:28:27 Koha 3.00.06.010 Koha DB 3.0006010 MySQL mysql Ver 14.14 Distrib 5.1.41, for debian-linux-gnu (i486) using readline 6.1 OS Linux tibabu-desktop 2.6.32-22-generic-pae #33-Ubuntu SMP Wed Apr 28 14:57:29 UTC 2010 i686 Perl 5.010001

1 0

Re: [Koha] Proposal to form Koha Technical Committee
by Chris Cormack 20 Nov '10

20 Nov '10

I feel I have made it fairly clear that I am not opposed to solr. But, and this is a big but, I will not be accepting for 3.4 a rewrite of C4::Search that only works with Solr. If people want Solr in 3.4, then the search needs to work with both zebra and Solr. I don't think this is unreasonable at all and provides a smooth transition for any libraries who want to use solr without forcing those who don't to have to upgrade. I would hope that any meeting on the subject would have this as its aim. My aim is to release a stable release in what is now 5 months time. The same rule is applied for the template work, the new templating system should be functionally equivalent to the current system there should be utterly no regression. The same with dbix::class::schema and any rfcs. So let's move forward on this, time is short if we want solr in 3.4 we need to start work on making sure it still works with zebra Chris Ps my son turned 4 today and I have birthday party tomorrow so won't be around the net until Monday nz time. On 20 Nov 2010 17:49, "LAURENT Henri-Damien" < henridamien.laurent(a)biblibre.com> wrote: Le 19/11/2010 22:41, Thomas Dukleth a écrit : > Reply inline: > [snip]> > Much of the capabilities which Zebra support provides are not being used > in Koha and we are comp... As far as I know, solr is succesfully everyday used in many opensource OPACS, and other projects too (thunderbird, alfresco, Drupal, .... ). I donot claim that they are better than we do. But why should we doubt that this solution, widely used, which is a real kind of standard in indexing engine would be a good one ? a) Getting and providing Suppport fot that tool would be easier. Solr community exists. b) Since it has been used in Vufind, and Blacklight, i think we could share experiences more easily, Eventually direct bridges between Koha and those solutions. > > There is more than just the problem of losing very good Z39.50/SRU server > support which wou... It was done in koha2.2 and as far as I know, without zebra, this feature still exists in our testing box. It is just using direct ZOOM search rather than C4::Search::SimpleSearch. So this valuable feature is still there. And we care not to break existing features. Same for the Z3950 server which we wrote a wrapper using Net::Z3950::SimpleServer. This would allow ppl to expose their collection as a Z3950 server. > > As I have stated previously, C4::Search ought to be rewritten in future > using prefix query f... Well, Rewriting the whole Search With PQF would not be handy in many aspects. I have thought about that many times. And using PQF still appears to me not to be the solution. a) It is really a pain to maintain and analyse. b) Whenever you need some more feature in your search, you have to add some more qualifiers, and therefore provide a robust parser. > Continuing to support Common Command Language (CCL) is trivial because Yaz > translates CCL to PQF... Again, we used Data::SearchEngine as a base for coding, and use the results from qurying Data::SearchEngine If anyone is willing to write a Data::SearchEngine::Zebra, Data::SearchEngine::Nutch, Data::SearchEngine::Pazpar2, feel free to do so. We will contribute not just to our little community. But to the wider PERL community. > When > the opportunity to rewrite the Zebra code would arise, rewriting would be > much easier w... This is why we are willing to gather use cases. To build Tests !!! No tests have ever really been built for C4::Search. So at the moment, I can't assign your fear of loss of features. Provide tests and will do our best to make it pass. If it is proven that we can't then we will talk precisely. By the way, did you know that the "valuable" feature you told about searching "The" was not really a zebra feature as you stated. But provided by the Search itself. It duplicated the old need for null words in Koha. But then again, there was no tests for that. > > I have raised all of these issues on the koha-devel list without much > specific response. On... Well I wanted a meeting to be held and we were working on testing and trying to assing all the raised problems in order to provide you with more technical details. Expect another message from us soon. -- Henri-Damien LAURENT BibLibre _______________________________________________ Koha mailing list http://koha-community.org Koha@li...

1 0

FW: Zebra Issue
by Scott Kushner 19 Nov '10

19 Nov '10

________________________________ From: Scott Kushner Sent: Fri 11/19/2010 9:57 AM To: koha-bounces(a)lists.katipo.co.nz Subject: Zebra Issue Hello all, I've run out of disk space on one physical HD and can't finish indexing. Has anyone set up Zebra to do the index on another physical volume? How would you go about configuring that? thanks, sincerely, Scott Kushner Middletown Library 55 New Monmouth Rd Middletown, NJ 07748

4 3

Questions about printing paper notices
by Heidi J. Oliversen 19 Nov '10

19 Nov '10

Hello all: If you have time, please respond to this email if you are currently printing notices in order to snail mail them to your patrons. 1. When printing paper notices what kind of paper do you print the notices on? * Regular 8x11 sheets * Pre-perforated 8x11 sheets * Continuous pin-feed, tri-fold forms 2. What type of printer do you print your notices on? * Desk top or system laser printer * System copier/printer with folding capabilities * High speed pin-feed printer Any information you can share will be very helpful. Thank you, Heidi Oliversen -- "Helping member libraries provide the best possible service to the public." Heidi Oliversen Circulation Technology Specialist South Central Library System hjo(a)scls.lib.wi.us 608-242-4711

2 1