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

RFC - Admin Dashboard
by Barry Cannon 01 Sep '11

01 Sep '11

Hello, I have added an RFC and bug (6828) for the addition of a new feature in 3.6. The enhancement will provide an admin/staff user the ability to view a library Dashboard once logged in. The dashboard will display various library/branch specific information. Comment and suggestions much appreciated. Regards Barry(a)oslo.ie http://www.oslo.ie

2 1

2011-09-02 Global bug squashing day #4 - It's on! Join the fun!
by Magnus Enger 01 Sep '11

01 Sep '11

Dear Community! Just a gentle reminder that GBSD#4 started about half an hour ago, in Kiribati. If Friday September 2nd is inconvenient for you in your timezone you might want to consider diving in now, to get a head start! ;-) For those watching at home, a lot of the changes on Bugzilla will be tweeted here: http://twitter.com/#!/KohaGBSD Best regards, Magnus Enger ---------- Forwarded message ---------- From: Magnus Enger <magnus(a)enger.priv.no> Date: 30 August 2011 08:35 Subject: 2011-09-02 Global bug squashing day #4 To: Koha list <koha(a)lists.katipo.co.nz>, koha-devel(a)lists.koha-community.org Dear Community! Just a gentle reminder that GBSD#4 is approaching fast: http://wiki.koha-community.org/wiki/2011-09-02_Global_bug_squashing_day Please bear in mind that the Release Manager has declared the following dates: * Feature freeze – 22 September 23:59 UTC – From this point on, no new features will be considered for inclusion into 3.6.0 * String freeze – 8 October 23:59 UTC – no bugs that change templates accepted after this point. This allows the translators to translate without things changing on them http://koha-community.org/key-dates-3-6-0/ That means we have about 3 weeks for getting any new features in! And there are (at the moment) 83 (!) bugs/patches waiting to be signed off: http://bugs.koha-community.org/bugzilla3/buglist.cgi?bug_status=NEW&bug_sta… See one in there that you would like to make sure makes it into Koha 3.6? YOU can help it along by signing off on it! http://wiki.koha-community.org/wiki/Sign_off_on_patches Of course, we should take every opportunity to sign off patches in the coming weeks, but why not make a concerted effort on Friday September 2nd 2011 (in your timezone) and see how far we can get, as a team? Could we cut the queue in half? Happy hunting! Magnus Enger PS And you don't have to be a developer to help either!

1 0

Kohacon11 : paper abstracts to arrange into a program.
by Koustubha Kale 31 Aug '11

31 Aug '11

Hi All, Please find attached a CSV file with paper abstracts submitted for Kohacon11. Any apologies or last minute submissions before we finalize the program for the three days using these? Also please let me have your suggestions as to how to order these into a program. Regards, Koustubha Kale Anant Corporation Contact Details : Address : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka, Thane (w), Maharashtra, India, Pin : 400601. TeleFax : +91-22-21720108, +91-22-21720109 Mobile : +919820715876 Website : http://www.anantcorp.com Blog : http://www.anantcorp.com/blog/?author=2

1 1

2011-09-02 Global bug squashing day #4
by Magnus Enger 30 Aug '11

30 Aug '11

Dear Community! Just a gentle reminder that GBSD#4 is approaching fast: http://wiki.koha-community.org/wiki/2011-09-02_Global_bug_squashing_day Please bear in mind that the Release Manager has declared the following dates: * Feature freeze – 22 September 23:59 UTC – From this point on, no new features will be considered for inclusion into 3.6.0 * String freeze – 8 October 23:59 UTC – no bugs that change templates accepted after this point. This allows the translators to translate without things changing on them http://koha-community.org/key-dates-3-6-0/ That means we have about 3 weeks for getting any new features in! And there are (at the moment) 83 (!) bugs/patches waiting to be signed off: http://bugs.koha-community.org/bugzilla3/buglist.cgi?bug_status=NEW&bug_sta… See one in there that you would like to make sure makes it into Koha 3.6? YOU can help it along by signing off on it! http://wiki.koha-community.org/wiki/Sign_off_on_patches Of course, we should take every opportunity to sign off patches in the coming weeks, but why not make a concerted effort on Friday September 2nd 2011 (in your timezone) and see how far we can get, as a team? Could we cut the queue in half? Happy hunting! Magnus Enger PS And you don't have to be a developer to help either!

1 0

System design
by Paul 29 Aug '11

29 Aug '11

Our budget has finally allowed me a new "all singing, all dancing" server and it has physically arrived. Two questions if I may -- and if I'm off topic, plz say so: 1) The system (Ubuntu 11.04) is being installed on a SSD (solid state drive) which recommends keeping "writes" to a minimum for longevity. This obviously includes logs, etc, but not necessarily the sql database. A quick "find / -iname" on the sandbox (Koha 3.02.05.000) for '*koha*' is enormous. Does anyone have to hand a list of "system" versus "run-time" directories and files? I'm particularly curious about Zebra (which I do not fully understand) as it appears to be proliferous and ubiquitous. 2) I have stabilized a partially customized Koha 3.2.5 which is close to meeting our needs. Koha 3.4 would be my choice on the new server (and I'm not worried about cosmetics -- CSS, etc) but how bullet-proof is the data conversion (as of now about 80,000 records)? I truly want Koha to be our long term data solution for our holdings, but am still wet behind the ears with Koha, so all help would be appreciated. Many thanks in advance for all suggestions. Paul Tired old sys-admin

2 1

Maintenance on git.koha-community.org
by Ian Walls 27 Aug '11

27 Aug '11

Dear community, We have been experiencing downtime with community Git repo the last few days, mainly from insufficient system resources. ByWater Solutions, as the maintainer of this server, has decided we need to allocate more resources to the server in order to mitigate this issue and provide better uptime. git.koha-community.org will be down for the next hour or so as we resize the server. We apologize for any inconvenience this may cause; please check the wiki (http://wiki.koha-community.org/wiki/Public_Git_Repositories) for other public repositories, including mirrors, if you need to obtain updated patches in this downtime window. I will notify everyone on this thread when the server is once again available. Thank you all for you patience and understanding. Cheers, -Ian -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls(a)bywatersolutions.com Twitter: @sekjal

1 1

Re: [Koha-devel] Sending acquisition orders per email: confirmation
by Edgar Fuß 26 Aug '11

26 Aug '11

Regarding the feedback that the email has actually been sent, I can think of three ways to do that: 1. Add a field 'closeaction' to the basket hash complementing the 'closedate' field. Set that to empty, 'print' or 'email'. Display that information in acqui/booksellers.pl, acqui/basket.pl and acqui/bsketgroup.pl. 2. Use the message queue. 3. Don't send the email to the bookseller, but to yourself; forward it manually. I'll probably look into implementing variant 1.

2 1

Notifications RFC
by Elliott Davis 26 Aug '11

26 Aug '11

Hey Guys, I have noticed of late that notifications is in quite a state of disarray. At my library we have had to resort to running queries from a script and manually sending out mail because notifications just don't work in a usable way. I am proposing an overhaul of the notifications system. The only information I have to go on is what my library wants but since we are an academic library that may vary from what the vast majority of Koha wants. Before I made an official wiki for this RFC I wanted to get a general feel for how everyone felt about this. I also wanted to see if someone or a group was willing to pitch in and help me out with some coding. Essentially what I would like to do is model notifications to do the following: 1. Base notification rules on patron type, item type, and a new grouping I am hoping to write that I am calling the collection code 2. Define a frequency for notifications based on the previously stated groupings 3. Base the start time and end time for notifications on the due date rather than the checkout date I am very open to other suggestions and I hope to get some. I know that this idea is far from fully developed. Best, Elliott Davis

7 8

Official Koha Newsletter : Volume 2, Issue 8: August 2011
by Daniel Grobani 26 Aug '11

26 Aug '11

[Below is the text of the newsletter. For active links and a more readable format, please visit http://koha-community.org/koha-newsletter-volume-2issue-8-august-2011] Official Koha Newsletter (ISSN 2153-8328) Volume 2, Issue 8: August 2011 Edited by Daniel Grobani, Koha Community Newsletter Editor. Table of Contents Koha Developments Koha 3.4.4 Available Koha 3.6 Update Koha 3.2 End-of-Life Koha Community New Koha Libraries Community Gossip Past Koha Events New Zealand Koha Users Group Meeting Global Bug Squashing Day #3 August General IRC Meeting Upcoming Koha Events Global Bug Squashing Day #4 September General IRC Meeting KohaCon11 KohaCon12 Koha Developments Koha 3.4.4 Available by Chris Nighswonger It is with pleasure that I announce the release of Koha 3.4.4. The package can be retrieved from: http://download.koha-community.org/koha-3.04.04.tar.gz You can use the following checksum and signature files to verify the download: http://download.koha-community.org/koha-3.04.04.tar.gz.MD5 http://download.koha-community.org/koha-3.04.04.tar.gz.MD5.asc http://download.koha-community.org/koha-3.04.04.tar.gz.sig Release notes for 3.4.4 are below the fold. Come and get it! Continue reading “Koha 3.4.4 Available” Koha 3.6 Update by Chris Cormack We are rapidly closing in on the 3.6.0 release, so I thought it would be good remind everyone of the key dates. Feature freeze – 22 September 23:59 UTC – From this point on, no new features will be considered for inclusion into 3.6.0 String freeze – 8 October 23:59 UTC – no bugs that change templates accepted after this point. This allows the translators to translate without things changing on them Translations finished – 18 October 23:59 UTC – Translations submitted, so that they can be tested before release Release – 22 October Koha 3.2 End-of-Life It was decided at the August general IRC meeting that Koha 3.2 has reached the end of its life. Koha Community New Koha Libraries C.G. Jung Institute of New York (via ByWater Solutions) CAUSE (Comfort for America’s Uniformed Services) (via ByWater Solutions) Centenary College (via ByWater Solutions) Central Kansas Library System (via ByWater Solutions) All schools in the Canadian province of Prince Edward Island are now using Koha. Community Gossip Paul Poulain of BibLibre is assisting 3.6 Quality Assurance Manager Ian Walls in reducing the backlog of patches waiting for QA testing. Lori Bowen Ayre is working on a spreadsheet comparing Evergreen & Koha features. Brenda Chawner asked community members several years ago to complete a survey as part of her PhD research on factors affecting satisfaction with the experience of a free/libre open source software project. Brenda recently thanked the community and provided an abstract of her PhD thesis. For more info, see http://markmail.org/message/gdofvpmbgseao2vb. Joy Nelson joined ByWater Solutions as their Migration Support Specialist. Melia Meggs joined ByWater Solutions as their Operations Manager. Hal Bright reports that the Farmington Libraries has integrated its Koha database into a mobile app powered by the Boopsie company in cooperation with its vendor, ByWater Solutions. For more info and a demo, see http://flct.boopsie.com. Equinox Software is looking to hire a Library Data and Support Specialist. ByWater Solutions is looking to hire a Perl developer for their support desk. Past Koha Events New Zealand Koha Users Group Meeting by Chris Cormack Today I had the great fortune of attending the first New Zealand Koha users group meeting, in the birthplace of Koha, Horowhenua. There were 51 attendees and even road closures and snow didn’t stop people attending. There was a really good mix of Library types, I think 18 from Publics, 18 from specials, and the rest schools, corporate and academic. It was run as an unconference so the first task of the day was to decide what would be talked about the rest of the day. The programme that we came up with was: The community – How to get involved and make the most Installation/migration/training and why should we use Koha Features – what’s there, and what would we like added Serials, acquisitions, cataloguing Managing digital resources Consortia And one other I have forgotten The discussions went really well, with lots of participation. It definitely won’t be the last meeting, I think we are leaning towards 2 a year but that’s something that will be decided on the mailing lists. While we were busy plotting plans to take over the world, (or at least New Zealand) Koha 3.4.3 was released. Global Bug Squashing Day #3 by Magnus Enger Global bug squashing days are dedicated to getting bugs and patches moving toward resolution. The third GBSD coincided with holidays and other obligations for some people, but we still managed to move a fair number of bugs along. These numbers below show how many bugs were moved to a new status during the day: Needs Signoff: 13 Signed Off: 12 Passed QA: 6 Pushed: 11 Resolved: 30 For more info, see http://wiki.koha-community.org/wiki/2011-08-05_Global_bug_squashing_day. August General IRC Meeting The August general IRC meeting was held on 2 August 2011. Highlights from the meeting include: Koha 3.2 has reached its end of life. The bare minimum requirement for a vendor to be listed on the community website is a visible link to the community website on the main Koha page of the vendor’s website. Daniel Grobani is the new newsletter editor. Those interested in a role in 3.8 should express interest to the mailing list by 22 September for an October election. For more info, including links to the minutes, see http://wiki.koha-community.org/wiki/General_IRC_Meeting,_2_August_2011. Upcoming Koha Events Global Bug Squashing Day #4 The next GBSD will occur on Friday, 2 September 2011. For more info, see http://wiki.koha-community.org/wiki/2011-09-02_Global_bug_squashing_day. September General IRC Meeting The next general IRC meeting is 7 September 2011 1800 UTC. For more info, see http://wiki.koha-community.org/wiki/General_IRC_Meeting,_7_September_2011. KohaCon11 KohaCon11 will be held 31 October 2011 to 6 November 2011 in Thane, India. The organizers have extended the deadline for submitting papers from 15 August to 30 August 2011. For more info, see http://wiki.koha-community.org/wiki/Category:KohaCon11 or http://kohacon11.vpmthane.org/ocs/index.php/k/k11. KohaCon12 Proposals for KohaCon12 are being accepted until 1 September 2011. Voting will take place through 1 October 2011. Proposals have been made by software.coop in the UK and Washoe County Library System in Reno, Nevada, USA. For more info, see http://wiki.koha-community.org/wiki/Category:KohaCon12.

3 2

Regarding locale setting on Debian 6.0
by Somasekhar Rao K 25 Aug '11

25 Aug '11

Hi, I tried to set using 'dpkg-reconfigure locale'. But still I got same errors. Is there any alternative way of doing this? alos what should be the values of these locale settings. LANGUAGE = (unset), LC_ALL = (unset), LC_CTYPE = "UTF-8", LANG = (unset) Thanks & Regards, Somasekhar Rao K ------------------------------ ---------------------------------------- Message: 1 Date: Thu, 25 Aug 2011 08:02:18 +0530 From: Somasekhar Rao K <raosoma(a)gmail.com> Subject: Re: [Koha-devel] [Koha] Koha 3.4.4 is now available To: Mason James <mtj(a)kohaaloha.com> Cc: koha-devel(a)lists.koha-community.org Message-ID: <CAPzijStim=LBMg8eO4sKo=aOk4mimNM-cFBYrfKfbaF0bMtXpQ(a)mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" Hi, Operating system: Debian 6.0 (Squeeze) using rackspace.com cloud server After execution of command sudo apt-get dselect-upgrade the output is something like this... Get:284 http://http.us.debian.org/debian/ squeeze/main xfonts-utils amd64 1:7.5+2 [96.2 kB] Get:285 http://http.us.debian.org/debian/ squeeze/main x-ttcidfont-conf all 32 [23.9 kB] Get:286 http://http.us.debian.org/debian/ squeeze/main xml-core all 0.13 [23.4 kB] Get:287 http://http.us.debian.org/debian/ squeeze/main wfinnish all 0.7-17.3 [2008 kB] Fetched 183 MB in 34s (5244 kB/s) perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LC_CTYPE = "UTF-8", LANG = (unset) are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory Extracting templates from packages: 100% Preconfiguring packages ... /usr/bin/locale: Cannot set LC_CTYPE to default locale: No such file or directory /usr/bin/locale: Cannot set LC_ALL to default locale: No such file or directory perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LC_CTYPE = "UTF-8", LANG = (unset) are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). Use of uninitialized value $classprefix in concatenation (.) or string at /tmp/dictionaries-common.config.8987 line 155, <STDIN> line 31. Use of uninitialized value $classprefix in concatenation (.) or string at /tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31. Use of uninitialized value $classprefix in concatenation (.) or string at /tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31. Use of uninitialized value $classprefix in concatenation (.) or string at /tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31. Use of uninitialized value $classprefix in concatenation (.) or string at /tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31. Use of uninitialized value $classprefix in concatenation (.) or string at /tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31. Use of uninitialized value $classprefix in concatenation (.) or string at /tmp/dictionaries-common.config.8987 line 155, <STDIN> line 31. Use of uninitialized value $classprefix in concatenation (.) or string at /tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31. Use of uninitialized value $classprefix in concatenation (.) or string at /tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31. Use of uninitialized value $classprefix in concatenation (.) or string at /tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31. Use of uninitialized value $classprefix in concatenation (.) or string at /tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31. Use of uninitialized value $classprefix in concatenation (.) or string at /tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31. Use of uninitialized value $classprefix in concatenation (.) or string at /tmp/dictionaries-common.config.8987 line 155, <STDIN> line 31. Use of uninitialized value $classprefix in concatenation (.) or string at /tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31. Use of uninitialized value $classprefix in concatenation (.) or string at /tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31. Use of uninitialized value $classprefix in concatenation (.) or string at /tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31. Use of uninitialized value $classprefix in concatenation (.) or string at /tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31. Use of uninitialized value $classprefix in concatenation (.) or string at /tmp/dictionaries-common.config.8987 line 174, <STDIN> line 31. Regards, Sekhar On Wed, Aug 24, 2011 at 12:04 PM, Mason James <mtj(a)kohaaloha.com> wrote: > > On 2011-08-24, at 3:22 PM, Somasekhar Rao K wrote: > > > Hi, > > > > Looks like the installation procedure on debian has changed. > > I tried to install on Debian 6.0 (squeeze) machine. I used rackspace.comcloud server. It didn't work out. > > > > Many errors. > > and those many errors were...??? > >

2 1