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

Issues table and foreign keys in general
by Srdjan 19 Apr '11

19 Apr '11

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have noticed some things: 1. issues table has nullable borrowernumber and itemnumber; foreign key constraints are consequently declared as "ON DELETE SET NULL ON UPDATE SET NULL" 2. That is not an isolated issue, there are many cases where foreign key field/constraints are declared like that Can anyone shed more light, that looksvery wrong to me. Thanks, Srdjan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk2k/pcACgkQX6p/D9UE7dy2fQCfZP/QeVQSb7VNNMJvA5yYWdBj AvAAn0fRuZ1KinfIiIIWCR+EgXhmYBu8 =2WSQ -----END PGP SIGNATURE-----

4 4

Re: [Koha-devel] Subfields 952 $i, $k
by Paul 18 Apr '11

18 Apr '11

At 04:18 PM 4/18/2011 +0200, Fischer, Katrin wrote: >Hi Paul, >in 3.4 a mapping and a new search index was introduced for 952$i and >items.stocknumber (Bug 5839). Many thanks for the answers. So if we upgrade to 3.4, I'll have to modify kohadb to take out the (varchar 32) constraint? So far, we have endeavoured to remain "faithful" to the Master version, but cataloguing our serials is an uphill challenge. >You can easily add new subfields in your bibliographic frameworks. If you >leave the mapping field empty the data will be stored in the >more_subfields_xml column. As the name indicates it's stored in a XML format. Perhaps easier to add specific items.xyx - I don't think the XML will be problematic, but wonder if these are all concatenated for OPAC display? (e.g. at the moment 520 $a and $b ARE concatenated. I'm looking for a way to undo this.) >There are not many lowercase letters left for 952. According to the MARC21 >Standard it's also possible to use uppercase letters, but I am not >completely sure if Koha works correctly if you do. This would need some >more testing, although we have done so in the past without running into >problems. This sounds like a possible solution - instead of "local" specialized uses (German remapping of 995$j to 952$i in this case) getting into the Master, surely it is more logical to leave more flexibility? I don't think everyone has the time to follow all bugs (I certainly missed this one), maybe the development team could assure us that 952 $[A-Z] are fully working and available for local use, while 952 $[a-z] are for Koha use? Best - Paul >For search you would need to add new indexes to your Zebra configuration. >This is independent from the way you store the data in your database. > >Hope this makes sense and is helpful for you, > >Katrin > > > > -----Original Message----- > > From: koha-devel-bounces(a)lists.koha-community.org [mailto:koha-devel- > > bounces(a)lists.koha-community.org] On Behalf Of Paul > > Sent: Monday, April 18, 2011 4:04 PM > > To: koha; koha-devel(a)lists.koha-community.org > > Subject: [Koha-devel] Subfields 952 $i, $k > > > > [Apologies for cross-posting, users and devel] > > > > Marc 952 $i, $k are not used in "standard" Koha. They can be added to the > > default framework (allowed by Koha), but this appears to require a > > modification to the Mysql structure. Has anyone tried to do this? > > > > Background: for Serials, we want to add at *item* level "Extended > > Keywords" (952$z is limited to 255 characters) and "Abstracts" (at *biblio* > > level, we use 520 $a and $b.) > > > > This will require new "Koha Fields" - e.g, in the same way that 952$z uses > > "items.itemnotes" we will need to introduce "items.itemkeywords" and > > "items.itemabstracts". > > > > I am looking for suggestions as to how to best add these fields so that > > they can be usefully searched by the OPAC - and of course for any pitfalls > > or showstoppers. > > > > Thanks > > > > Paul > > Tired old sys-admin > > > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel(a)lists.koha-community.org > > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : http://www.koha-community.org/ > > git : http://git.koha-community.org/ > > bugs : http://bugs.koha-community.org/ > >

2 1

Subfields 952 $i, $k
by Paul 18 Apr '11

18 Apr '11

[Apologies for cross-posting, users and devel] Marc 952 $i, $k are not used in "standard" Koha. They can be added to the default framework (allowed by Koha), but this appears to require a modification to the Mysql structure. Has anyone tried to do this? Background: for Serials, we want to add at *item* level "Extended Keywords" (952$z is limited to 255 characters) and "Abstracts" (at *biblio* level, we use 520 $a and $b.) This will require new "Koha Fields" - e.g, in the same way that 952$z uses "items.itemnotes" we will need to introduce "items.itemkeywords" and "items.itemabstracts". I am looking for suggestions as to how to best add these fields so that they can be usefully searched by the OPAC - and of course for any pitfalls or showstoppers. Thanks Paul Tired old sys-admin

3 2

How to convert a HTML::Template::Pro template to Template::Toolkit
by Chris Cormack 17 Apr '11

17 Apr '11

Hi All There may be a need for people to convert a template to template::toolkit so they can send a patch that will apply cleanly. To do so checkout a branch based on commit d4cd05126da3accef83144d8322fcd455d7eba9b eg git checkout -b convert_templates d4cd05126da3accef83144d8322fcd455d7eba9b Now you have a branch with both sets of templates, you can then cherry-pick your template change over. And run ./installer/html-template-to-template-toolkit.pl --koharoot /path/to/the/root This will convert all the templates, if you want to just convert 1 use -f eg ./installer/html-template-to-template-toolkit.pl --koharoot /path/to/the/root -f koha-tmpl/opac-tmpl/prog/en/modules/ilsdi.tmpl So for me ./installer/html-template-to-template-toolkit.pl -c --koharoot /home/chrisc/git/koha/ -f koha-tmpl/opac-tmpl/prog/en/modules/ilsdi.tmpl Then that file will be in the koha-tt dir and you will now have a converted file. Hope this helps Chris -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand

4 4

Important notice regarding patches intended for backporting into 3.2.x
by Chris Nighswonger 16 Apr '11

16 Apr '11

At present the 3.2.x branch is current with master at all applicable commits. Due to many possible pitfalls with the switch to T::T, it is imperative that those submitting patches indicate exactly which patches should be backported to 3.2.x. It is possible that a change to an underlying perl script to correct a bug with a T::T template may apply cleanly to the 3.2.x branch and break H::T::P functionality. So, moving forward, I will backport only those patches with notes indicating that the commits should be backported to 3.2.x. Please take note of this and be sure to make the indication in your commit message. Kind Regards, Chris Koha 3.2.x/3.4.x Release Maintainer

1 0

DB number incrementing revisited
by Chris Nighswonger 16 Apr '11

16 Apr '11

Not to beat a dead horse here, but... What works very well for me as Release Maintainer regarding DB version numbers is when the patch to updatedatabase.pl simply uses the format: 3.03.XXX (which some folks are doing) and no modification is made to kohaversion.pl In 99% of cases, this applies cleanly and allows me to follow up with a single patch to adjust the version number in both places. So I'd love to see everyone adapt this style. Kind Regards, Chris

1 0

3.2.x Roadmap Update
by Chris Nighswonger 16 Apr '11

16 Apr '11

Hi all, With the release of 3.2.7 and the eminent release of 3.4.0, I want to let the community know what my plans are moving forward. Due to the excellent work during the recent hack-fest sponsored by Biblibre, there were a multitude of bugfixes which did not make it into 3.2.7. My plans are to begin work on getting these backported into the 3.2.x branch over the next week or so. Because there are such a large number, I will be releasing 3.2.8 on May 15, 2011. I had originally intended to go to a bi-monthly release schedule for 3.2.x after the release of 3.2.0. This will still be the case, but will be delayed until the release of 3.2.8. Subsequent 3.2.x releases will take place on the 15th of the month with 3.4.x releases taking place on the 22nd of the month. ***Translators please take especial note of the above dates.*** As long as there are commits to backport to 3.2.x, I will release on a bi-monthly schedule. If there are no commits during a two month period, no release will be made. If you have template related bugfixes you want included in 3.2.x, it will be your responsibility to ensure that they apply correctly to the current 3.2.x branch. With the switch to TT in master, backporting template commits will be nigh impossible. Of course any related underlying logic changes should be applicable to the current 3.2.x branch as well. After the 3.2.10 release, I will add an agenda item for the next monthly IRC to discuss EOL of the 3.2.x branch. The results of that discussion will determine the direction of 3.2.x from that point forward. I plan to handle 3.4.x maintenance in the same fashion as I have handled 3.2.x. If anyone has any suggestions for improvement, please speak up! I'm very open to suggestions, critiques, etc. Thanks to everyone for the hard work being put into Koha lately. Things have moved along at a fantastic rate! Keep up the good work. Kind Regards, Chris Nighswonger Koha 3.2.x/3.4.x Release Maintainer

1 0

Koha 3.2.7 is now available
by Chris Nighswonger 16 Apr '11

16 Apr '11

It is with pleasure that I announce the release of Koha 3.2.7. The package can be retrieved from: http://download.koha-community.org/koha-3.02.07.tar.gz You can use the following checksum and signature files to verify the download: http://download.koha-community.org/koha-3.02.07.tar.gz.MD5 http://download.koha-community.org/koha-3.02.07.tar.gz.MD5.asc http://download.koha-community.org/koha-3.02.07.tar.gz.sig Release notes for 3.2.7 are below the fold. Come and get it! RELEASE NOTES FOR KOHA 3.2.7 - 15 April 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.7 can be downloaded from: http://download.koha-community.org/koha-3.02.07.tar.gz Installation instructions can be found at: http://wiki.koha-community.org/wiki/Installation_Documentation Koha 3.2.7 is a bugfix/maintenance release. Highlights of 3.2.7 ====================== Some of the higher profile bugs addressed in this release are: 5646 translated message names on sql level break messaging 5860 Adding duplicate stocknumber will fail silently 6044 Authority is deleted when mergeto and mergefrom are the same 6045 Accepted by is empty when accepting from list 6058 Uncertain price can not be undone Bugs fixed in 3.2.7 ====================== 3270 Cancelling a hold request after transfer initiated orphans item 5390 library choice not remaining when searching opac 5555 ISBN search returns bad results 5651 can't use ? character in searches 5817 Malformed author search link breaks sorting on results page 5865 Labels wrap incorrectly when paper width is greater than height 6043 No suggestions showing when independant branches set to OFF 3098 XSLT stylesheet does not obey OPACURLOpenInNewWindow syspref 3203 Some Letters template variables are not available to certain notice types 3326 xml entity refs display incorrectly in results page if exported and indexed as xml 3595 Items seen at checkin should always go to 1st priority hold 3629 search limit by group is not OK 3727 If item type is mandatory in marc editor, itemtype is autofilled 4196 Defintion of popularity index into Unimarc setup 4218 Staff client detail page does not show item hold status 4265 Sorting by call number in OPAC is slightly off 4330 Copyright statements out of date 4366 COinS support for MARC21 4870 Damaged status does not prevent items from being selected for reserves 5305 Resorting results of CCL queries fails in Staff Client 5410 "Right truncation not supported" error when running link_bibs_to_authorities.pl 5625 late orders report missing titles 5833 opacstylesheet not loading on all pages 5834 Holds link missing when 942$c is not for loan 5862 Incompatibility in ajax.js with "localName" for Internet Explorer 5879 Biblio.pm : fix isbd syspref and default location 5883 UTF-8 characters in items (952) get encoded wrong when the record is modified. 5889 Allow message names to be translatable 5902 Locations should default to current library in add item screen 5909 Authorities : SetUTF8Flag on any incoming data 5924 Authorities search : Heading Main is defined in unimarc record.abs 5940 Update Help Files for 3.4 5960 Itemtype icons not showing in search results 5962 Budgets are showing when they shouldn't on acqui-home.pl 5989 Funds filter does not remember library choice 6040 opac-export.pl can throw an untrapped error when trying to export an invalid record 6046 Managed by list in suggestions was not created correctly 6047 Authority not added if subfield 3 in biblio 3735 Wrong search results for a few fields in ccl.properties 4943 Search history cookie size limit 5253 runreport.pl does not work with new options (-to, -from, -email, -format) 5816 table of contents looking for subfield a 5864 Is C4::Serials::GetSubscriptions searching too generally? 5890 Mismatched operator in C4::Auth 5892 opac-user: minor spelling/html changes 5907 Using default authtypecode for authority display 5965 Make sure opac-detail.pl outputs marc in utf-8 5996 Patron import defaults not being set right 6004 checking in an item that needs to be transferred home, and is on-hold for a patron, causes dual transfer message box 6026 Remove useless condition for export.pl 4878 Command line tool for getting and setting sysprefs Translations new/updated in 3.2.7 ====================== de-DE es-ES el-GR fr-FR it-IT nb-NO nl-BE pl-PL pt-PT ru-RU sv-SE tet-i uk-UA ====================== 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.7: Alex Arnaud D Ruth Bavousett Jared Camins-Esakov Colin Campbell FrÃ©dÃ©rick Capovilla Chris Cormack Christophe Croullebois fdurand FrÃ©dÃ©ric Demians Marcel de Rooy Nicole C. Engard Magnus Enger Katrin Fischer Janusz Kaczmarek Henri-Damien LAURENT Owen Leonard Julian Maurice Matthias Meusburger Sophie Meynieux Chris Nighswonger Paul Poulain Salvador Zaragoza Rubio Ian Walls Jesse Weaver 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 570 patches since the 3.2.0 relese. Their continued work very much makes possible the release of 3.2.7 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

Hacker's corner, wk14 / Hackfest Europe
by Paul Poulain 16 Apr '11

16 Apr '11

Hello koha-devel, This week was a very busy week in Marseille: 25 fellow developers came from Europe to work on koha. The work done was huge ! Just a few numbers: * 112 bugs have been set to sign-off * 128 patches have been signed off * 92 patches have been pushed by chris * 90 bugs have been marked "fixed" The changes on bugzilla have resulted in an astonishing number of 1140 mails in a week ! (note that's not only hackfest activity, but it's something like 4 times a standard weekly activity) ==== Hackfest news ==== This hackfest has seen some new developers joining us: * Mark Gavillet, from PTFS-Europe, made his first patches and has signed/marked fix a lot. He also learned many things, and said before leaving that it has been an invaluable boost for him. * Fridolyn Somer, from Progilone, helped a lot, and we spoke of the patches available at git.progilone.com Some of them should make their way to git.koha-community.org soon, as they are really interesting (some will remain local, as they look too specific to Lyon 2 university, the sponsoring customer) * Juan and Miguel, from Xercode in spain were here for 2 days. * Frédéric Durand, from Lyon 2, has made a lot of work testing and checking * Not really developers, but Pascale Nalon (Mines Paris tech school), Guillaume Hatt (Ecole des Chartes school) and Stéphane Delaye (BibLibre librarian/project manager) made a lot of work on french translation, as well as many testings. All other attendees were already known developers. All of us agree that it was really cool to work together in small groups of 3 or 4 Just a special thanks to Magnus, that came from Norway, and to Katrin, that came from Germany. We should send some picture we've taken very soon ! === Hacker's corner === Needs signoff: 112 bugs are awaiting for you sign-off. The number includes many many patches/fixes that BibLibre did on git.biblibre.com and that still had to be submitted. Signed-off: 35 bugs are signed off and should be commited soon by chris Patch pushed, please test : 102 bugs have been pushed recently and are awaigint to be marked "fixed" to definetly solve the bug described ! Discussion: i've sent a mail on koha-devel about some bugs that have a patch that does not apply. Some of them are very old. Unless the author of the patch (or any other volunteer) rebase and submit a working patch, i'll mark the bugzilla "fixed, wontfix" in something like 2 weeks. It's the best solution not to have bugs that stay open and remain here forever. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

8 11

Koha Load Testing
by Ian Walls 15 Apr '11

15 Apr '11

Fellow Kohackers, Do any of you have a favour script or suite of scripts (or even a method) for doing load testing against a Koha installation? I know there are some scripts available in misc/load_testing, but my understanding is they aren't terribly useful or current. Is that correct? Something that can throw a user-configured amount of punishment at a Koha server, then report on the results, would be ideal. The output should include both the user perspective (response times) and what's happening on the machine (memory/CPU usage, query times, etc) in the context of the machine's specifications. If all this data can be compiled for various configurations, I think we'd have the makings of a fine, evidence-based Koha Tuning Guide. Thanks, all! -Ian -- Ian Walls Lead Development Specialist ByWater Solutions ALA Booth 732 Phone # (888) 900-8944 http://bywatersolutions.com ian.walls(a)bywatersolutions.com Twitter: @sekjal

5 5