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

Change orientation of label printing
by akafortes 24 Sep '15

24 Sep '15

Hello everyone, I'd like to ask if there is a way to change the orientation of the text when you print labels. I want the spine labels to be printed with vertical text -- View this message in context: http://koha.1045719.n5.nabble.com/Change-orientation-of-label-printing-tp58… Sent from the Koha-devel mailing list archive at Nabble.com.

3 4

Call for News: September Newsletter
by kohanews 24 Sep '15

24 Sep '15

Fellow Koha users ~ ** Please Note ** The cut-off date for news submissions is now the 26th of the month. I'm collecting news for the September newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- ** For events **: - Please include dates for past events. If I can't find dates I may not add it. - Announcements for future events with dates T.B.A. are fine ...Eg., Kohacon - For past events -- **** one month back is the cut-off ***. * News items can be of any length. * Images are fine * Anything and everything Koha. * Submit by the 26th of the month. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. -- Chad Roseburg Editor, Koha Newsletter

2 2

Get the values from other fields
by akafortes 24 Sep '15

24 Sep '15

Hello, is there a way to get the values of other fields? I want to create a plugin for a custom field I've added. When you click on that field, during cataloguing, I want to be able to get the values from two other fields. Something similar to the "callnumber.pl" plugin -- View this message in context: http://koha.1045719.n5.nabble.com/Get-the-values-from-other-fields-tp585449… Sent from the Koha-devel mailing list archive at Nabble.com.

1 0

git commit messages
by Colin Campbell 24 Sep '15

24 Sep '15

Hi, can I humbly suggest that we should take a couple of secs to make the commit messages for submitted patches a bit more useful. When looking at the history of the code its useful if the summary gives a brief indication of what has been changed or added by the commit. Good summaries can save a lot of frustrated time wasting when trying to track down where a change has been introduced. Although we flag up the bugzilla bug in the summary, just echoing the bug summary is nearly always counter-productive. The commit should indicate the change introduced not the bug that prompted it. Once the patch is applied the original bug is "background reading" not the main event. It is also misleading if the commit summary says "X is broken" then when that is extracted into the release notes or the gitlog it looks like the commit introduces the breakage of x not vice-versa. It is surely better to have the commit say something along the lines of "Fix broken behaviour in X", which makes it sound a bit more like the desirable feature it no doubt is. A long standing succinct post on commit messages is http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html Colin (Author of some of the world's worst commit messages) -- Colin Campbell Chief Software Engineer, PTFS Europe Limited Content Management and Library Solutions +44 (0) 800 756 6803 (phone) +44 (0) 7759 633626 (mobile) colin.campbell(a)ptfs-europe.com skype: colin_campbell2 http://www.ptfs-europe.com

6 7

RESTful Apis
by Brendan Gallagher 24 Sep '15

24 Sep '15

Hi All - For those of you in the know, can we get a public update of where we are with this? I believe we had some new action items out of the last IRC dev meeting, and I'm curious as to what we've met so far. Also there was some discussion/difficulty with perhaps having to run something (mojolicous iirc) as a daemon vs not having to. (I think maybe Tomas was going to help with the technical difficulty on that. I'm just looking for updates on this whole thing. We've got some excited thoughts, ideas, and plans to use these APIs asap. Oh yeah BTW Elastic is completely developed and ready. We need tons of testing etc. and reports to Robin for "tweaking" the code for the results we are looking for. Please if you have time - test ES and send your feedback. We've got sometime left for this to be an option for the next release (and the RESTapis too). Thanks much, Brendan Gallagher -- --------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting and Complete Support Packages Headquarters: Santa Barbara, CA - Office: Redding, CT Phone # (888) 900-8944 http://bywatersolutions.com info(a)bywatersolutions.com

3 3

Re: [Koha-devel] Cataloguer's info in MARC field
by Hector Castro 22 Sep '15

22 Sep '15

> I've seen the 040 Modifying Agency, and have often though 'wouldn't it be > nice if there was a MARC plugin in the framework to automate filling that > field with the librarians name'. Maybe someone should add a feature > request to bugzilla for that. > Yep! A better solution would be file a new bug and store that kind of data in a new SQL table or if you prefer store it in a local file like holding fileds in 9xx. There are a reference of holdings data fields in koha wiki: <http://wiki.koha-community.org/wiki/Holdings_data_fields_%289xx%29> Regards -- Atte, Hector Castro Universidad de El Salvador

2 1

Debian 8 Jessie, Ubuntu 15.04 Vivid, and Zebra 2.0.59
by David Cook 21 Sep '15

21 Sep '15

Hey all, Just a reminder that Zebra 2.0.59, which is packaged with Debian 8 Jessie and Ubuntu 15.04 Vivid, is buggy when using ICU. Robin Sheat opened a bug in Debian back on 9 Feb 2015, but it doesn't look like anyone has acted upon it: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777515. I reported the issue to IndexData and they fixed it back on 7 Feb 2015: http://git.indexdata.com/?p=idzebra.git;a=commit;h=704fd190292cb771df94553b0 ed6f9f4b71660a6. The fix made it into Zebra 2.0.60. We use OpenSuse for our Koha servers, and they've included Zebra 2.0.60 since version 13.2. I'm not sure if Robin has looked into this more lately and I think he's on holidays so I can't ask him. but I just remembered that the 2.0.59 version was buggy and thought I'd remind you all too. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007

1 0

Cleaning up...
by Mark Tompsett 18 Sep '15

18 Sep '15

Greetings, mysql> SELECT table_name, table_rows, round(((data_length + index_length) / 1024 / 1024),2) "Size in MB" FROM information_schema.TABLES where table_schema = "koha_library" and ((data_length+index_length)/1024/1024)>10 order by (data_length+index_length); +-------------------------+------------+------------+ | table_name | table_rows | Size in MB | +-------------------------+------------+------------+ | marc_subfield_structure | 48064 | 11.73 | | statistics | 26298 | 11.98 | | biblio | 96620 | 14.03 | | deleteditems | 27767 | 14.48 | | import_biblios | 136336 | 36.33 | | deletedbiblioitems | 19509 | 61.45 | | items | 122738 | 67.25 | | nozebra | 264699 | 76.66 | | import_items | 147630 | 130.19 | | biblioitems | 103188 | 343.14 | | import_records | 113028 | 659.55 | | biblioimages | 1176 | 919.47 | +-------------------------+------------+------------+ 12 rows in set (0.33 sec) So, I was looking to clean up the database a bit, so I figured I’d see what was taking up the most space. The import_{something} series of tables looked like promising clean up candidates. After all, who doesn’t want to free up 750MB or more when running in a 40GB VM? This led me to this pretty schema page: http://schema.koha-community.org/tables/import_records.html QUESTION: Would there be any problems if I deleted records associated with import_batch_id’s prior to a given date in these related import_{something} tables? Grace, Peace, Mercy, and Love, Mark Tompsett

7 11

About the dependency Test::CGI::Multipart
by Tajoli Zeno 17 Sep '15

17 Sep '15

Hi to all, I write to advice about the module Test::CGI::Multipart It is an optional module, connect with test. Attention that it is availabe only in whezzy as .deb, it is not presente in jessied (or in sid or in testing). It was added with bug 6874, this commit: http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=209faec1830… Probalby we need to create the package in koha repo. Bye Zeno Tajoli -- Zeno Tajoli /Dipartimento Sviluppi Innovativi/ - Automazione Biblioteche Email: z.tajoli(a)cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI)

5 5

Kohacon 2016 location
by Mirko Tietgen 16 Sep '15

16 Sep '15

Hello everyone, the voting period is over and the preliminary results are in. Kohacon 2016 will be hosted by Aristotle University of Thessaloniki, Greece. Congratulations! The survey has been completed 1074 times. In some cases, people were overly enthusiastic and had to vote more than once, which lead to disqualification. The results are 80,35% Thessaloniki, Greece 08,10% Manila, Philippines [11,55% invalid] I'd like to thank the people behind both proposals for offering to host Kohacon 2016! See you all in Thessaloniki next May or June, Mirko -- Mirko Tietgen mirko(a)abunchofthings.net http://koha.abunchofthings.net http://meinkoha.de

1 0