- Koha - lists.katipo.co.nz

Re: [Koha] Summary of Open session at KohaCon13 - with a focus on Funding the Future of Koha.
by Joel Sasse 07 Nov '13

07 Nov '13

Brendan, Excellent post and analysis of the current situation and the path forward for Koha, both for users and developers. I was just considering putting forth the idea of a Midwestern US Koha users and developers conference, perhaps just more of an informal get together, and gauging the level of interest. Regardless of the title, everyone would certainly be welcome. Although technology can facilitate distance collaborations, I don't believe it can ever substitute for face to face human interaction. After attending KohaCon 13, I can attest that great ideas came not just from the planned events of each day but also from the informal social gatherings in the evenings. I also learned a lot more in those seven days interacting with all of the excellent attendees than I ever would have from simply surfing Koha info on the Web. An Ohio hack fest is an awesome idea. What can we do to help? Plum Creek is willing to aid in the effort to get us together again as often as possible. I don't think a formal non-profit organization is needed in the short term to just get us together under one roof. I truly believe open source and Koha are the future of library automation worldwide and I am always willing to share my knowledge and enthusiasm for Koha with anyone willing to listen. Thanks, Joel Sasse Network Systems Administrator Plum Creek Library System 507-376-5803 -----Original Message----- From: koha-bounces(a)lists.katipo.co.nz [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Brendan Gallagher Sent: Wednesday, November 06, 2013 9:39 PM To: Koha Devel; koha(a)lists.katipo.co.nz Subject: [Koha] Summary of Open session at KohaCon13 - with a focus on Funding the Future of Koha. Hello All - I'd like to give a summary of a open discussion that occurred at KohaCon14 in Reno. A spot opened up from a presenter not being able to attend - so I volunteered to lead a discussion on Funding the future of Koha. First we invited all current and past RM's of Koha up to the front of the room, to educate the audience on some of the "plumbing" needs in the code. When I use the term "plumbing" - I really mean portions of the code that need to be "rewritten", "updated for current coding practices", and a "plan for placing newer technologies and practices into the code". Mainly plumbing = what do we need to get completed in the near future and how are we going to get that done. Many of these "needs" are larger projects that not a single organization or library can fund, as we would really need to dedicate an expert programmer some uninterrupted time to accomplish these goals. Not one support vendor can brunt the front of the plumbing needs that need to happen. We need to work together to fund this and we need to have a place and plan going forward "now". Let's do this for Koha! Points that were raised. Many attendees felt that a clear plan on what path Koha should be developing towards would be a useful project. Although setting a ridged path is a difficult thing with a community like ours, maybe a place for everyone to get or stash ideas for future paths would be a good thing to organize. An important comment here from the attendees was that when someone is funding a development - they should not just fund the code, but also plan for time and funding for the Sign-Off process and the QA process. Funding and how would we organize this? Since many in the audience were from the USA - there was discussion of getting a users group going again OR creating some sort of "non-profit like org" where libraries could pool funding towards projects. An organization like this would be able to apply for grants etc. Something where we could crowd-source funding and then fund a developer for a number of hours towards a project. My thoughts on some things that we can do in the USA. Have a hackfest in Athen's Ohio next summer. Next year will be 10 years since Koha migrated to the US and I think it's about time we have a hackfest here. I have briefly talked with Owen Leonard about putting this together for next summer and would love for help and encourage those from overseas to join us. (Also a commitment here that we will be sending a few employees to the France Hackfest in March and will continue to do this every year that we can - that also being right around a feature freeze for releases it's important to have a solid week dedicated to hacking koha only) Gauge the interest of a North American Koha users group so at least we are having more of the community meeting together and sharing practices and ideas. Comments from Galen "As far as a US or North American user group goes: I think a relaunch should start off with just the goal of hosting a US/NA conference, as it would /not/ be necessary to set up a nonprofit first to run conferences. We'd just need willing hosts and, if necessary, a firm willing and able to act as a fiscal agent. That's not to say that such a group couldn't pursue nonprofit status later, but we can get a lot of education and user-connecting done without ever having to have a formal organization." Thanks all - this is to promote discussion and hopefully we can all do this together! Brendan -- ---------------------------------------------------------------------------- ----------------------------------- 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 brendan(a)bywatersolutions.com <info(a)bywatersolutions.com> _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

1 0

Patches to test for 3.16
by Jonathan Druart 07 Nov '13

07 Nov '13

Hello Koha community, As some of you know, I work for BibLibre. So I am a Koha developper and a member of the QA team (freshly re-elected for 3.16 cycle \o/). The 3.14 version is closed to be release and we have 6 months for working together for the 3.16 version. A lot of BibLibre's patches are in the patches queue (needs signoff, needs QA) and I think some could interest you. We never communicate enough. That's why I would like to list and explain some of features you can already tested: * Search history I refactored some code on search history. This has been permit to simply add a search history to the intranet interface. Moreover, I added a search history for authority searches too. See: - Bug 10807 - OPAC: There is no authority search history - Bug 10862 - Add an search history for the staff interface and linked reports. These ones are closed to be pushed * Acquisition module Small fixes: - Bug 11171 - The basket group is not displayed on the supplier list page - Bug 11170 - The pending order list should only display orders to receive Improvements: - Bug 8991 - Add a script to delete old orders A simple script for deleting old oeders. - Bug 11141 - Filters are not kept on receiving You are irritated when you receive an order to fill filters for each reception? This patch will fix that. - Bug 11018 - Add order from a reverted file Currently, a reverted staged file cannot be add to an order. It is caused by a bug. A simple patch will allow to do it. The only big feature in the queue for the moment is: - Bug 7180 - Order from staged file improvements (in failed QA). * Serials module - Bug 8438 - Users should only claim for serials related to their branch. - Bug 5342 - Serial claiming improvements This one is lost in the bug list depth. On the same way of orders, a claim counter will be added to the serials claims. * Reports module - Bug 9216 - Add a file for table headings translation and copy of this file during the translation process. This patch allows to translate headers. Currently, in the report module, headers are always in English. - Bug 7683 - statistic wizard: cataloging - Bug 7679 - Statistics wizard: circulation (new filters) * Circulation module - Bug 11120 - The date option for the overdue_notices cronjob is broken The overdue_notices cronjob has a --date parameter but it has never worked. With this patch, you will be able to generate overdue notices for a given date. It is really useful when you want to recover a failure, for example. - Bug 10860 - In-House Use The current Koha in-house use implementation is not complete. This feature will allow you to easily distinguish a normal checkout to an in-house use. - Multi transport types Several patches focus on notices and a way to add more than one transport type for a notice. For example, it will be possible to notify a patron with an email *and* a sms for the first overdue level. Moreover a template per transport type can be created for 1 letter. So it is possible to create a short notice for sms and a longer one for email. See the following: Bug 9016 - Multi transport types for notices Bug 10833 - Multi transport types for advanced notices Bug 10845 - Multi transport types for holds Bug 10832 - Multi transport types for overdue notices * Cataloguing - Bug 8064 - Merge several biblio records To merge 2 records is possible since several versions but this patch allows to merge as many records as you want. * Search - Bug 10857 - Add facets cancellation At the OPAC and staff interfaces, a link will permit to cancel a facet. In the current code, you have to re launch your search and re add wanted facets, with this patch, a simple link will save your time :) - Bug 10858 - Browse selected biblios Select a set of biblios and browse them, it is now possible. - Bug 9811 - Patrons search improvements A new sexy patron search! Using AJAX, it will be easy to find any patrons with any information. * Tools - Bug 11023 - Toggle new status for items Automatically change the status for items: a cronjob script will update status given some conditions. It can be useful for displaying an icon near new items, create a syndication feeds with new items only, etc. - Bug 10212 - Columns configuration for tables I think this one is really fun. Everyone may configure tables like he wants. If you want to display only 5 columns in the parcel page, it will be possible. This patch is a start, but has to move forward for continuing. And a lot of others patches! If something is not clear, don't hesitate to let a question on a note on the appropriate report. The goal of this email is to motivate all of you to signing off them (and all others!), or QA them, and takes your attention on what is existing in the queue. During the last year, it was really difficult to rebase again and again patches for 2 reasons: 1/ Patches are not tested and 2/ Others features don't take into account patches already submitted. So please developers, check if an existing patch does not exist before to start to write a new feature. All of these features could be in the next release, all depends on you :) Don't forget: a list of BibLibre's development exists on the following doc https://docs.google.com/a/biblibre.com/spreadsheet/ccc?key=0AuZF5Y_c4pIxdHE… We try to keep it up-to-date. And Sandboxes exist! [1] So you don't have any excuse not to test patches. Thanks and welcome to PTFS Europe on the sandbox area. Hope to share with you on these report :) Regards, Jonathan [1] http://wiki.koha-community.org/wiki/Sandboxes

3 2

z39.50 for K12
by Jeremy Wellner 07 Nov '13

07 Nov '13

Hello! Just wondering if anybody has some good z39.50 servers we can use for getting Scholastic book fair ISBN hits as well as textbook hits. Thanks! -- Jeremy Wellner Technology Group Stanwood-Camano School District jwellner(a)stanwood.wednet.edu Internal: x4357 External: 360-629-1205 Cell: 360-420-5486 “We’re here to put a dent in the universe. Otherwise why else even be here?” -Steve Jobs

3 2

printing of certain barcodes/accession numbers
by schnydszch 07 Nov '13

07 Nov '13

This has actually bug us since Koha 3.2, and now we have Koha 3.12. Using default template Avery 5160 | 1 x 2-5/8 and layout DEFAULT, printing the following barcodes 033073hp, 07776d, 028595hp we get a blank pdf after it's exported. I've tried different combinations then but to no avail. There could be something wrong with the barcode/s? that koha barcode tool does not accept it? While the following barcodes: 228, 229, 230, 231, koha was able to print. I've actually tried it too with bywaters demo. Because of this, we instead used other ways of printing barcodes, but it would be better if we could do it outright in Koha. Thanks in advance and more power! -- View this message in context: http://koha.1045719.n5.nabble.com/printing-of-certain-barcodes-accession-nu… Sent from the Koha-general mailing list archive at Nabble.com.

2 2

Minutes from the 6 November 2013 general meeting
by Galen Charlton 06 Nov '13

06 Nov '13

Hi, Minutes from the IRC meeting concluded just now can be found at the following links: Minutes: http://meetings.koha-community.org/2013/general_irc_meeting__6_november_201… Minutes (text): http://meetings.koha-community.org/2013/general_irc_meeting__6_november_201… Log: http://meetings.koha-community.org/2013/general_irc_meeting__6_november_201… The next meeting is scheduled for 18:00 UTC on 4 December 2013. Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc(a)esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org

2 1

Fwd: Notices Documentation Question
by Nicole Engard 06 Nov '13

06 Nov '13

Sorry I didn't hit reply to all ---------- Forwarded message ---------- From: Nicole Engard <nengard(a)gmail.com> Date: Wed, Nov 6, 2013 at 9:14 AM Subject: Re: [Koha] Notices Documentation Question To: MJ Ray <mjr(a)phonecoop.coop> On Mon, Oct 28, 2013 at 8:19 AM, MJ Ray <mjr(a)phonecoop.coop> wrote: > > advance_notices.pl notices (and any others I think) are like that. > > overdue_notices.pl notices use the <item>...</item> tags. > > Hope that helps, > > It does help - but which notices are generated by advance_notices.pl ? I don't think hold notices are controlled by that .. so what code do we use on those? As far as I know overdue_notices.pl controls overdues advance_notices.pl controls advance notice (predue) and item due notices (due) That leaves holds, checkin and check out notices ... Nicole

1 0

Re: [Koha] Add fileds in Z39.50 results mask
by Stefano Bargioni 06 Nov '13

06 Nov '13

Hi, Andrea: in my opinion, fields shown are hardcoded in .../intranet/htdocs/intranet-tmpl/prog/en/modules/cataloguing/z3950_search.tt. Year of publication is shown as Date. Ciao. Stefano > Hi to all. > This is my first question to the list. > I use Z39.50 searching: I'd like to know if there is a way to add new > fileds in the results windows after a Z39.50 searching: I'd need > "Publisher" and "Year of publication". > > Thanks in advance > > Andrea Furin

1 0

The barcode was not found
by Shivendra 06 Nov '13

06 Nov '13

during the checking out. the message displayed ""The barcode was not found" how can i resolve this issue? -- Shivendra India 9815526163

3 2

Unable to print barcode
by John Leger 06 Nov '13

06 Nov '13

Hi community. I am a new koha user here and I am having trouble printing out the barcodes in the patron card creator. The problem is that the barcodes just do not show up. In my layout I have the box checked that says "Print card number as barcode" coordinates are x=115 y=5 Using Barcode type Code 39 Thanks in advance for any help provided. John

2 4

My favourite new feature coming in Pi - borrower lists!
by Liz Rea 06 Nov '13

06 Nov '13

I was just so excited I had to share - a new feature coming in version Pi is the addition of Borrower Lists. It works like this: Do a borrower search, tick off some borrowers. Just like adding books to a list, you pick Add to -> new list Give it a name Then, what you can do with it - is BATCH MODIFY based on that list - Tools -> Batch Modify Patrons -> From a List omg. Guys, that's so cool! What's your favourite new feature? Liz (sorry if this comes as a duplicate - didn't see my first message come through so sending again, because yes, I'm "just that excited (tm).")

2 1