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

Re: [Koha-devel] Version numbering, starting a discussion
by MJ Ray 05 Dec '11

05 Dec '11

Mason James <mtj(a)kohaaloha.com> > we could also consider switching to the Debian style?, i have found it quite easy to understand. > would it work well for Koha? > > > the Debian project uses both an internal 'linux-kernal' style numbering system (like Koha does already) and people-friendly nick-names too... :) Debian's x.y.z number is not quite linux-style: there have been full (non-development) x.1 release versions. I'm not against the idea but a difficulty I have with Debian's nick-names is that (except for sid) there seems little meaning or relationship or progression to them, so remembering that lenny is 5.0 and squeeze is 6.0 is not straightforward for me. Hope that informs, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. http://koha-community.org supporter, web and LMS developer, statistician. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha

7 12

Passed QA
by Marcel de Rooy 05 Dec '11

05 Dec '11

Paul, While we are waiting on 7167, would it be possible to push patches with a db rev like 6190, 6880 and 7077? Since we already have revisions on borrowers/debarred in 001 and 002, we could just continue with pushing other db revs too until 7167 passed qa? That seems fair. The number at which the new dbrev scheme will start, is just a number ;) Does 7167 still need more community consensus or additional signoffs? Marcel

1 0

FW: Improving permissions on lists (virtual shelves)
by Marcel de Rooy 05 Dec '11

05 Dec '11

This would create the need for borrowernumber in virtualshelvescontent. And a new table for shared lists/invitations with shelfnumber, borrowernumber, invitationkey, date. Comments welcome. -----Oorspronkelijk bericht----- Van: Marcel de Rooy Verzonden: maandag 5 december 2011 11:43 Aan: koha Onderwerp: Improving permissions on lists (virtual shelves) Hi all, Still hoping to get some feedback on this subject, I would now propose the following. Please respond to the list, if you agree or disagree. 1 Do not allow to create a public list in the OPAC. (Only private lists.) Public lists are only created by staff users in the staff client. 2 Add three permission options to any list: a) Allow adding entries b) Allow deleting your own entries (that you added) and c) Allow deleting entries that someone else added. This makes the distinction between public list and open list no longer needed and adds some refinement in lists management. Only the owner of the list can change these permissions. 3 Add a new (opac) feature to private lists: Share a list (with another patron). Let the user share access to a list by Koha sending an email with a URL including some (temporary) invitation key. When the invited patron clicks that URL (when logged in) he gains access (in accordance with the described permission options for that specific list). The invited patron can always 'delete' the shared list, i.e. delete the share. The owner can 'unshare' the list and remove all shares for that list. 4 With respect to user privacy, a feature may be added in staff client to moderate shared list names. 5 Possibly, libraries do not want patrons sharing lists. So the option could be disabled with a preference. In that case points 2 and 3 still apply. Note that the shared private list concept makes report 7281 (Hiding some lists) obsolete. Bug 7310 will be used for this feature. Your comments are very welcome! Marcel

1 0

Adding .mailmap file to 3.6.x
by Chris Nighswonger 05 Dec '11

05 Dec '11

Hi all, I've added a .mailmap file to the 3.6.x branch. This file is used by git to help standardize authors' names/email addys. You can read more in the comments included in the file as well as as in 'man git-shortlog.' Please feel free to submit patches against this file to improve your own information. Paul, I would recommend adding this file to master as well. Kind Regards, Chris http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=.mailmap;h=b186da…

1 0

Koha 3.2.11 is now available [Security Release]
by Chris Nighswonger 04 Dec '11

04 Dec '11

It is with pleasure that I announce the release of Koha 3.2.11. The package can be retrieved from: http://download.koha-community.org/koha-3.02.11.tar.gz You can use the following checksum and signature files to verify the download: http://download.koha-community.org/koha-3.02.11.tar.gz.MD5 http://download.koha-community.org/koha-3.02.11.tar.gz.MD5.asc http://download.koha-community.org/koha-3.02.11.tar.gz.sig Release notes for 3.2.11 are below. Come and get it! RELEASE NOTES FOR KOHA 3.2.10 - 3 December 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.10 can be downloaded from: http://download.koha-community.org/koha-3.02.10.tar.gz Installation instructions can be found at: http://wiki.koha-community.org/wiki/Installation_Documentation IMPORTANT ANNOUNCEMENT CONCERNING 3.2.x EOL ======================================================================== 3.2.x has reached its EOL and is officialy unsupported at this point. Releases beyond 3.2.10 are for security issues only and are not gauranteed. Highlights of 3.2.10 ====================== NOTE: This release is a security release. It is strongly recommended that users apply this upgrade immediately to production systems. If you are installing a new system, please use this version rather than earlier versions. System Requirements ====================== 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.10: FrÃ©dÃ©rick Capovilla Chris Cormack Chris Nighswonger 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.6 Release Team and all who participated in QA for their diligent labors in testing and pushing well over 680 patches since the 3.2.0 relese. Their continued work very much makes possible the release of 3.2.10 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

Benchmarking Koha
by Paul Poulain 02 Dec '11

02 Dec '11

Hello, I've pushed a few minuts ago a new script, you'll find it at misc/load_testing/benchmark_staff.pl Run the script to get the parameters and information. It run up to 7 different benchmarks on a given setup. I'll use this script regularly, when pushing patches that are related to speed of Koha. I'll add the results on the page : http://wiki.koha-community.org/wiki/Benchmark_for_3.8 I already have added 2 benchmark, with the speed of today master, with and without memcache. My first surprise (and I did the tests 3 times to be sure I wasn't making a mistake !) is that you almost get no speed improvement with memcache ON. Some patches should be validated soon, I hope we will see a lot of improvements, as Koha really need it ! HTH -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

4 3

Re: [Koha-devel] [Koha] Koha Virtual Appliance 3.6 Now Available For Download
by Muhammad Abdullah 02 Dec '11

02 Dec '11

Thanks alot for this. Been using it for awhile now, very useful appliance. This upgrade should make it more robust, now that it is running on Debian 6. On Thu, Dec 1, 2011 at 10:48 PM, Kyle Hall <kyle.m.hall(a)gmail.com> wrote: > Hey All, > I just wanted to let everyone know that I've updated my virtual > appliances to 3.6. This is a complete rebuild using Debian 6.0 ( > Squeeze ) instead of Lenny. I also added a bit more to the Koha > Console program for automatically fixing the networking issue that > crops up on virtual machines from time to time. Enjoy! > > http://millruntech.com/koha/koha-virtual-appliances > > Kyle > > http://www.kylehall.info > Mill Run Technology Solutions ( http://millruntech.com ) > Crawford County Federated Library System ( http://www.ccfls.org ) > Meadville Public Library ( http://www.meadvillelibrary.org ) > _______________________________________________ > Koha mailing list http://koha-community.org > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha

2 1

[Bug 7310] Improving permissions on lists (virtual shelves)
by Marcel de Rooy 02 Dec '11

02 Dec '11

Hi, If you have a suggestion on report 7310 about lists management, please respond. Following up on report 7281 (hide lists from OPAC) I am sending the following question to the ml in order to improve lists management: 1 Who should be allowed to delete a public [closed] list (category 2 only!) or add/remove items from that list? (Note that removing all items from a list is more or less the same as removing the list at once.) My answer would be: the owner should only be allowed to do that in the OPAC. A user in the staff client may do it too. [Currently, any opac login can delete the list. This is a bug!] 2 Who should be allowed to delete an public open list (category 3 only!) or add/remove items from that list? My answer would be: any login from OPAC or staff. It should be made clear that creating such a list is really at your own risk ;) Currently, a user in the opac cannot create an open list. (Is that a bug?) 3 Proposed revisions to lists management: If we solve points 1 and 2, management of lists comes down to all or nothing. You can do everything with an open list, but if you are not owning a closed list, you can't do anything. Would it be useful to have something in between? Like deleting your own added items from a closed list (we could save borrowernumber in virtualshelfcontents)?? Or give the owner of an open list the choice between full access for other logins, adding items only or deleting own added items? What do you think? Marcel

1 0

Code4Lib Scholarships available
by Galen Charlton 01 Dec '11

01 Dec '11

Please excuse the cross-posting. Equinox Software is offering 2 scholarships to the code4lib conference in February. The scholarships will reimburse travel and accommodation expenses up to $750.00 USD for a full-time employee from public libraries using either Evergreen or Koha to attend the Code4Lib Conference in Seattle, Washington, USA, from February 6-9, 2012. The awardees will also receive free registration to Code4Lib. ELIGIBILITY The applicants must be presently working in a public library that is currently using or is actively committed to moving to either Evergreen or Koha as their ILS. The applicants must indicate any amount and source of additional funding which, combined with the Scholarship, will permit them to cover their expenses to attend the Conference. (This will not reduce the amount of the award.) Preference will be given to underfunded libraries or libraries in budget crisis. DEADLINE FOR APPLICATION December 31, 2011 The email application should include a current resume, including all contact information, education, and experience, along with an essay as described below. The applicants will write up to 750 words of narrative in English to address the following: • Description of the library’s mission and commitment to open source solutions • How attendance may benefit the applicant • How the applicant intends to share the benefit of the experience with colleagues • Description of funding constraints, budgetary limitations, or travel/hiring freezes pertinent to the applicant’s situation APPLICATION ADDRESS: Please send resumes and essays to Grace Dunbar before December 31, 2011 by email attachment to c4lgrant(a)esilibrary.com NOTIFICATION: The successful applicants will be notified by January 5, 2012. Feel free to re-post this announcement and/or our press release (http://esilibrary.com/esi/newsitem.php?id=2182) Regards, Galen -- Galen Charlton Director of Support and 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

1 1

Koha Virtual Appliance 3.6 Now Available For Download
by Kyle Hall 01 Dec '11

01 Dec '11

Hey All, I just wanted to let everyone know that I've updated my virtual appliances to 3.6. This is a complete rebuild using Debian 6.0 ( Squeeze ) instead of Lenny. I also added a bit more to the Koha Console program for automatically fixing the networking issue that crops up on virtual machines from time to time. Enjoy! http://millruntech.com/koha/koha-virtual-appliances Kyle http://www.kylehall.info Mill Run Technology Solutions ( http://millruntech.com ) Crawford County Federated Library System ( http://www.ccfls.org ) Meadville Public Library ( http://www.meadvillelibrary.org )

1 0