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

ILS Perceptions survey (Marshall Breeding)
by Marshall Breeding 21 Nov '11

21 Nov '11

To all libraries using Koha: As Joann mentioned, I am collecting data for the 2011 Annual Library Automation Perceptions survey. This survey aims to provide some general measurement of the levels of satisfaction that libraries have with their library automation systems and the organizations that support them. I am aware that many libraries using Koha do so independently without direct involvement of a support firm. Even in these cases, data regarding the perceived quality and functionality of the automation system would be very helpful. The survey also probes at the relative level of interest in open source automation systems. I do hope that all libraries using Koha will respond to the survey. The survey forms are linked to each library's entry in the lib-web-cats directory, so you will need to submit an entry if your library is not already represented. A large number of libraries using Koha are already represented, but I'm sure that there are many still missing. See: http://www.librarytechnology.org/libraries.pl?ILS=Koha http://www.librarytechnology.org/map.pl?ILS=Koha A strong response will help document the worldwide impact of Koha. To participate in the survey, you can start with the instructions given on the current posting on the top page of Library Technology Guides: http://www.librarytechnology.org/ Please let me know if you have an questions about the survey. Best regards, -marshall Marshall Breeding Editor, Library Technology Guides <http://www.librarytechnology.org> http://www.librarytechnology.org <mailto:marshall.breeding@librarytechnology.org> marshall.breeding(a)librarytechnology.org <http://twitter.com/mbreeding> http://twitter.com/mbreeding From: koha-devel-bounces(a)lists.koha-community.org [mailto:koha-devel-bounces@lists.koha-community.org] On Behalf Of Joann Ransom Sent: Tuesday, November 15, 2011 4:07 PM To: koha-devel(a)lists.koha-community.org Subject: [Koha-devel] ILS Perceptions survey (Marshall Breeding) Hi all, Marshall is collecting responses for the technology report about libraries perceptions of ILSs. http://www.librarytechnology.org/ Cheers Jo. -- Joann Ransom RLIANZA Head of Libraries, Horowhenua Library Trust.

9 11

Request for Koha data for development
by Chris Nighswonger 18 Nov '11

18 Nov '11

A common problem among those of us who do development work on Koha is the lack of complete datasets for the development and testing of features. This is probably more of a problem for those of us who do not support a large variety of organizations running Koha. I would like to see some good, sanitized datasets available for development and testing. Several of us have plead for this for years. Just now, the lack of a good dataset including a sizable number of serials is preventing me from doing some testing and development on DataTables integration work which has been started by Biblibre. So, this is a request to all of you libraries out there with small, medium, and large datasets who would be willing to contribute sanitized data for development purposes, to do so. It would be a great way to give back to the community that has provided such a wonderful product with all of its attendant benefits. Kind Regards, Chris Nighswonger Koha 3.4/3.6 Release Maintainer

1 0

Re: [Koha-devel] confirm b023495405f84d04f71f16ddde8366baa27cee70
by Dattatray Phadke 18 Nov '11

18 Nov '11

Please remove my Id from List On Fri, Nov 18, 2011 at 9:48 AM, < koha-devel-request(a)lists.koha-community.org> wrote: > Mailing list removal confirmation notice for mailing list Koha-devel > > We have received a request for the removal of your email address, > "dnphadke(a)gmail.com" from the koha-devel(a)lists.koha-community.org > mailing list. To confirm that you want to be removed from this > mailing list, simply reply to this message, keeping the Subject: > header intact. Or visit this web page: > > > http://lists.koha-community.org/cgi-bin/mailman/confirm/koha-devel/b0234954… > > > Or include the following line -- and only the following line -- in a > message to koha-devel-request(a)lists.koha-community.org: > > confirm b023495405f84d04f71f16ddde8366baa27cee70 > > Note that simply sending a `reply' to this message should work from > most mail readers, since that usually leaves the Subject: line in the > right form (additional "Re:" text in the Subject: is okay). > > If you do not wish to be removed from this list, please simply > disregard this message. If you think you are being maliciously > removed from the list, or have any other questions, send them to > koha-devel-owner(a)lists.koha-community.org. > -- Thanking you D.N.Phadke,Ph.D. Consultant Librarian,Pillai Group of Colleges C/O Dr.K.M. Vasudevan Pillai's Campus 10,Sector 16,New Panvel,New Mumbai,Mumbai 410206 Contact PhoneNo. Res.0251-2472983 Mob.+919869786186

1 0

Patch status workflow (for Bugzilla)
by Ian Walls 17 Nov '11

17 Nov '11

Community, As I'd mentioned in a previous thread, I think we should consider removing the custom attribute "patch status" from Bugzilla, and keeping track of this information in the regular Status attribute. This has several advantages: - Easier searching, since it's a default value, not a custom value - We can enable Workflows between Statuses - We no longer have the dependency on Priority to control the display of this critical value The Workflows allow us to specify how tickets are allowed to change status, from which to which. Here's an example workflow: - NEW (default for all incoming tickets) - ASSIGNED (to the developer working on it) - NEEDS_SIGNOFF (once a patch has been submitted) - SIGNED_OFF (after signoff) - PASSED_QA (once QA'ed successfully) - PATCH_PUSHED - RESOLVED For a patch that fails testing, it would look more like this: - NEW - ASSIGNED - NEEDS_SIGNOFF - FAILED QA (some obvious problem found by tester) - NEEDS_SIGNOFF (again, now that the problem is fixed - SIGNED OFF - FAILED QA (less obvious problem) - NEEDS_SIGNOFF - SIGNED OFF - PASSED QA - PATCH_PUSHED - RESOLVED Workflows could prevent jumping a status straight from ASSIGNED to PASSED QA, for example; that status could only be reached from SIGNED OFF. All the changes to these statuses are recorded in the bug reports history, so we have a record of the life cycle. I think this is what Status was initially designed to do, so we just need to leverage it. -Ian -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls(a)bywatersolutions.com Twitter: @sekjal

4 13

Call for News for the October Newsletter (especially KohaCon11)
by Daniel Grobani 17 Nov '11

17 Nov '11

Hi, I'm gathering news for the November newsletter. Please send me by the 25th anything you think the community might like to know about. "News" can be as short as a sentence or as long as a paper. I especially encourage you to send me a line or two about what you're currently working on for publication in the gossip/society column. And if you know of a go-live not announced on the list, please be sure to let me know about it. This month, I'd like to have a special section dedicated to KohaCon11. So if you were there, please send me reports, notes, impressions, incriminating evidence.... Many thanks, Daniel Grobani

1 0

bugzilla & email & bulkupdates
by Paul Poulain 17 Nov '11

17 Nov '11

Hello all (& Ian, more specifically) Digging into bugzilla administration, I see that there is an option to disable all mails: bugzilla > administration > Email > the 1st option is : mail_delivery_method Defines how email is sent, or if it is sent at all. 'Sendmail', 'SMTP' and 'Qmail' are all MTAs. You need to install a third-party sendmail replacement if you want to use sendmail on Windows. 'Test' is useful for debugging: all email is stored in 'data/mailer.testfile' instead of being sent. 'none' will completely disable email. Bugzilla continues to act as though it is sending mail, but nothing is sent or stored. So, for bulk updates, we could set the parameter to "none", do the change, and set it back to "Sendmail". For example : * I still want to clean version list (to have less than 20 very old versions...) * Ian, your idea of changing the workflow for patches could be achieved without overwhelming mails. I will do, during the week-end hopefully, a test on this feature, disabling mails, moving all 2.2.9 patches to rel_2_2 and re-enabling emails -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

1 0

Koha indian domain names.
by Joann Ransom 16 Nov '11

16 Nov '11

Hi everyone, HLT has recently taken ownership of the following domain names of behalf of the koha community: - koha-community.in - koha-community.org.in - koha.in - koha.org.in We would like to offer the use of these to domains to Indian Koha libraries. For example: - *granthalaya.koha-community.in* AND *granthalaya.koha.org.in* could both point to http://www.granthalaya.org - *delhipublic.koha.in* could redirect to http://www.dpl.gov.in - *magarpatta.koha.in* could redirect to http://library.mpatta.com etc. Does this idea have any appeal? Naturally there would be no cost for this - it is community property after all. If you are interested please contact Chris Cormack : chrisc(a)catalyst.co.nz Kind regards Jo. -- Joann Ransom RLIANZA Head of Libraries, Horowhenua Library Trust.

1 0

ILS Perceptions survey (Marshall Breeding)
by Breeding, Marshall 16 Nov '11

16 Nov '11

To all libraries using Koha: As Joann mentioned, I am collecting data for the 2011 Annual Library Automation Perceptions survey. This survey aims to provide some general measurement of the levels of satisfaction that libraries have with their library automation systems and the organizations that support them. I am aware that many libraries using Koha do so independently without direct involvement of a support firm. Even in these cases, data regarding the perceived quality and functionality of the automation system would be very helpful. The survey also probes at the relative level of interest in open source automation systems. I do hope that all libraries using Koha will respond to the survey. The survey forms are linked to each library's entry in the lib-web-cats directory, so you will need to submit an entry if your library is not already represented. A large number of libraries using Koha are already represented, but I'm sure that there are many still missing. See: http://www.librarytechnology.org/libraries.pl?ILS=Koha http://www.librarytechnology.org/map.pl?ILS=Koha A strong response will help document the worldwide impact of Koha. To participate in the survey, you can start with the instructions given on the current posting on the top page of Library Technology Guides: http://www.librarytechnology.org/ Please let me know if you have an questions about the survey. Best regards, -marshall Marshall Breeding Editor, Library Technology Guides http://www.librarytechnology.org marshall.breeding(a)librarytechnology.org<mailto:marshall.breeding@librarytechnology.org> http://twitter.com/mbreeding From: koha-devel-bounces(a)lists.koha-community.org<mailto:koha-devel-bounces@lists.koha-community.org> [mailto:koha-devel-bounces@lists.koha-community.org]<mailto:[mailto:koha-devel-bounces@lists.koha-community.org]> On Behalf Of Joann Ransom Sent: Tuesday, November 15, 2011 4:07 PM To: koha-devel(a)lists.koha-community.org<mailto:koha-devel@lists.koha-community.org> Subject: [Koha-devel] ILS Perceptions survey (Marshall Breeding) Hi all, Marshall is collecting responses for the technology report about libraries perceptions of ILSs. http://www.librarytechnology.org/ Cheers Jo. -- Joann Ransom RLIANZA Head of Libraries, Horowhenua Library Trust.

2 1

ILS Perceptions survey (Marshall Breeding)
by Joann Ransom 15 Nov '11

15 Nov '11

Hi all, Marshall is collecting responses for the technology report about libraries perceptions of ILSs. http://www.librarytechnology.org/ Cheers Jo. -- Joann Ransom RLIANZA Head of Libraries, Horowhenua Library Trust.

1 0

Proposal to Standardize Bug Number References in Commit Messages
by Chris Nighswonger 15 Nov '11

15 Nov '11

Hi all, While we are proposing changes to workflow, etc. I would like to propose that we standardize the manner in which we reference bug numbers in our commit messages. Lately I have been working on scripts to semi-automate the generation of release notes and having a standard reference to bug numbers would greatly simplify munging through git log and extracting them. So I propose that we use the form: [BZX...X] It will be pretty nigh impossible to obtain 100% compliance, so those doing sign-off, QA, or the RM could to 'git commit --amend' to add it in if it is missing or wrong. What say ye? Kind Regards, Chris

7 10