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

Article request
by Vijaya Kumar 19 Mar '15

19 Mar '15

Respected Sir/Madam, kindly arrange to send articles as early as possible. the article details are given below for you consideration. Thanking you, Yours faithfully, *Requested article details:* Article Title The Use of Global Positioning Systems in Promoting Safer Walking for People with Dementia Journal Journal of Telemedicine and Telecare Authors Brian McKinstry; Aziz Sheikh Vol 19 Issue 5 Publication Date 01-07-2013 Page(s) 288-292 Date of Request 09-03-2015 Article availability Available in library as (ELECTRONIC) *From:* Dr.J.Vijaya Kumar Engineering College Library Andhra University Visakhapatnam- 530 003 Andhra Pradesh India. E-Mail Address: kumarjammala(a)gmail.com kumarjammala(a)rediffmail.com jammalamadakavijayakumar(a)yahoo.com

2 1

Calling for volunteers to join the sub-committee for the Koha Fund!
by Brendan Gallagher 19 Mar '15

19 Mar '15

Please excuse the cross-posting... (Please share this with others beyond these two lists - Thank you kindly) Calling for volunteers to join the sub-committee for the Koha Fund! What I propose is that those that volunteer for the sub-committee would volunteer for a 1 year term. *Immediate responsibilities* would include creating the "by-laws" that the sub-committee would act by. This would include taking the lead on creating a document (in an open forum) that would be presented to the Koha community for a vote of acceptance, at least one week before the next general meeting (7 days). Allowing for time for comments on the document and others to read the document, so that the document could be adjusted and corrected in time for a vote at the general meeting. **One note here is that if there is a bylaw that would potentially exclude one of the original volunteering sub-committee members (who knows right), that they would willingly step-down once the by-laws are completed (OR is that really a worry and we just really need to make sure we have enough volunteers to get a committee?)** Once the "by-laws" have been accepted by a majority vote in a general meeting, then the original volunteer members, would serve the rest of the year as part of the sub-committee for the Koha-fund. The main purpose of the sub-committee is to creatively raise money for Koha to be spent on Koha (most likely to begin money would be spent on sign-offs, QA-time, bugzilla maintenance cleaning, for example right now we have 26 critical bugs with no patch (so do those really need a patch or does bugzilla really need to be cleaned up?) ). So those that are interested in joining this to help make the bylaws so this is a successful venture and then being an active advocate for the Fund - please join up. You do not need to be a developer or anything close to that. I propose that we leave the volunteering open until 1 week before the next general meeting which is 8 April 2015 at 19:00 UTC. That should give people enough time to add their names here --> http://wiki.koha-community.org/wiki/Fundraising ... Look at the Fundraising Committee section for a place. Then at the general meeting April 8th we can vote on the names present and then move forward. So Dates... Starting now, until April 1st ---> people place their names on the wiki list for being a potential volunteer for the sub-committee (I would also be willing to keep this open until April 7th if others agree to that) April 1st to April 8th --> Community has a chance to review the names on their own time and be prepared for voting at the general meeting. April 8th - Sub-committee volunteers are confirmed... Please don't hesitate to ask any question at all, the more we have before we vote on April 8th the better and more prepared everyone will be! (no surprises) Cheers and Thank much, Brendan Gallagher (bag) -- --------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO

1 0

Roles for 3.22 - will be voted on at next General Meeting April 8th
by Brendan Gallagher 18 Mar '15

18 Mar '15

Hello All - Just a reminder - http://wiki.koha-community.org/wiki/General_IRC_meeting_8_April_2015 8 April 2015 at 19:00 UTC On the agenda we have Roles for 3.22... Please if you are volunteering for a position for the future release, please fill in the wiki-page ( http://wiki.koha-community.org/wiki/Roles_for_3.22 ). The sooner the better so that everyone has sometime to read any proposals or even just see who is volunteering for what. Those of you that are wishing to continue in the same role that you are in, please don't forget to fill out the wiki page. Thanks much, Brendan Gallagher -- --------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO

1 0

Call for development news: March 2015
by kohanews 17 Mar '15

17 Mar '15

Koha Development community ~ If you have any bugs or projects you'd like to highlight or promote in the March newsletter, please let me know. Maybe it'll attract some additional eyes, testers and sign-offs. k o h a news AT gmail dot com Thank you! -- Chad Roseburg Editor, Koha Newsletter

1 0

Call for news: March Newsletter
by kohanews 17 Mar '15

17 Mar '15

Fellow Koha users ~ I'm collecting news for the March newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- * News items can be of any length. * Anything and everything Koha. * Submit by the 28th. 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

1 0

Question about GPLv3 and AGPLv3
by Indranil Das Gupta 16 Mar '15

16 Mar '15

Hi all, I had earlier posted this on FB, and Chris has already responded to it. But I'm still not fully clear in my head so posting here. I'm integrating IA BookReader (under AGPLv3) with Koha. The JS and CSS files from IA BookReader will remain under AGPLv3. But I'm not sure of the following: What is the appropriate license for the bookreader.tt, bookreader.pl and the bookreader.pm that I've coded? Can these be under GPLv3 (and possibly pushed upstream as a patch for Koha in future)? Or do I need to maintain them as a separate "pack" under AGPLv3, that an user of Koha can choose to integrate. FWIW, both Omeka and Islandora (both GPLv3) offer IA BookReader integration thanks in advance. -- Indranil Das Gupta Phone : +91-98300-20971 Blog : http://indradg.randomink.org/blog IRC : indradg on irc://irc.freenode.net Twitter : indradg -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=- Please exchange editable Office documents only in ODF Format. No other format is acceptable. Support Open Standards. For a free editor supporting ODF, please visit LibreOffice - http://www.documentfoundation.org

2 1

Interlibrary Loans RFC
by Alex Sassmannshausen 16 Mar '15

16 Mar '15

Hello, I've now been able to draft a first version of an Interlibrary Loans Module for Koha RFC. You can find it at http://wiki.koha-community.org/wiki/ILL_Module. For the purposes of this work I have usurped bug number 7317. The RFC is based on work that I, as part of PTFS Europe am carrying out for our customers, and on discussions that we had at the hackfest. There are 2 primary concerns for this module from my perspective: 1) provide all the functionality our customers require 2) make the module generic enough so that we can implement different 'backends' that would service different ILL workflows/systems. Feedback (both on style and content), welcome. Best wishes, Alex

2 1

Upgrade path for packages
by Tomas Cohen Arazi 16 Mar '15

16 Mar '15

We still need to fix our packaging schema in which people are forced to jump into .0 releases because of our repository naming schema. I propose we step forward and create "3.18", "3.20" and so on, instead of just "stable", "oldstable", etc. This way no one will be forced to jump into another major release. "stable" "oldstable" and "testing" might still be usable as they are now, nothing prevents a .deb package from populating more than one slot. Or even of symbolic links... Some of you expressed your concerns about "people indefinitely using obsolete/insecure releases". I propose that once a release goes "unmaintained" [1] a "last" release/package adding a red-notorious warning message on the intranet footer is pushed stating that the release is no longer maintained and provinding a link for upgrade instructions. I hope we can fix this once and for all soon. [1] unmaintained = it has no release maintainer on some "Roles for XX" vote. -- Tomás Cohen Arazi Prosecretaría de Informática Universidad Nacional de Córdoba ✆ +54 351 5353750 ext 13168 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F

5 4

Hello, new BibLibre intern presentation
by Julian FIOL 13 Mar '15

13 Mar '15

Hi everyone, I'm Julian FIOL, the new intern of BibLibre for 6 months. I'm going to work on Koha. My mission is to implement new unit tests, and probably other things in a couple of weeks Thanks, My IRC : Jul / Jul- / Jul_

3 2

Overdrive authentication dialogue
by Bob Birchall 13 Mar '15

13 Mar '15

We've recently configured Overdrive integration for a client. It works very well and the client is getting positive feedback from members. There is a shortcoming in the authentication dialogue, where incorrect credentials are offered. 1. Where a correct cardnumber is entered with an incorrect password, Koha's SIP server responds with '(1) Greetings from Koha.' 2. Where an incorrect cardnumber is entered (with any password), the SIP server responds with a blank message: '(1) ' These are displayed on an Overdrive page which includes a link: 'Click here to return to the sign in form' but there is nothing to draw the user's attention to their error and the need to follow that link back to try again. Where correct credentials are offered, Overdrive redirects to the users' Overdrive account page and no messages from Koha are displayed. We propose to replace these messages with 'You have entered an incorrect cardnumber or password. Please try again.' This will appear just above the 'Click here to return ...' link and should make the process obvious for the user. Before I add this to bugzilla, has anyone seen this issue or have any thoughts on it? Have we missed anything? Thanks, Bob

3 2