<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Koha Library Software Community &#187; Koha News</title>
	<atom:link href="http://koha-community.org/category/koha-news/feed/" rel="self" type="application/rss+xml" />
	<link>http://koha-community.org</link>
	<description></description>
	<lastBuildDate>Tue, 15 May 2012 16:37:15 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>1st Australian Koha User Group Meeting :  Melbourne (Vic), Thursday 26 April at 6pm at The Melbourne Athenaeum Library</title>
		<link>http://koha-community.org/1st-australian-koha-user-group-meeting-melbourne-vic-thursday-26-april-6pm-melbourne-athenaeum-library/</link>
		<comments>http://koha-community.org/1st-australian-koha-user-group-meeting-melbourne-vic-thursday-26-april-6pm-melbourne-athenaeum-library/#comments</comments>
		<pubDate>Mon, 23 Apr 2012 12:35:21 +0000</pubDate>
		<dc:creator>calyx</dc:creator>
				<category><![CDATA[Events]]></category>
		<category><![CDATA[Koha News]]></category>

		<guid isPermaLink="false">http://koha-community.org/?p=3399</guid>
		<description><![CDATA[[ April 26, 2012; 6:00 pm to 8:00 pm. ] Location and map: The Melbourne Atheneaum Library 
Moyra McAllister emailed the Koha e-list with the following invitation: "I am a Koha user based in Melbourne, and I know of a few others. At the recent VALA conference held here it was suggested that we form a user group to meet a few times a year to [...]]]></description>
			<content:encoded><![CDATA[<table class="ec3_schedule"><tr><td colspan="3">April 26, 2012</td></tr><tr><td class="ec3_start">6:00 pm</td><td class="ec3_to">to</td><td class="ec3_end">8:00 pm</td></tr></table><pre><span style="font-family: FreeSans, sans-serif"><span style="font-size: x-small">Location and map: <a title="The Melbourne Athenaeum Library" href="http://www.melbourneathenaeum.org.au/content/view/50/60/" target="_blank">The Melbourne Atheneaum Library </a></span></span></pre>
<pre><span style="font-family: FreeSans, sans-serif"><span style="font-size: x-small">Moyra McAllister emailed the Koha e-list with the following invitation: "I am a Koha user based in Melbourne, and I know of a few others. At the recent VALA conference held here it was suggested that we form a user group to meet a few times a year to exchange tips and ideas and provide support for newbies. If there is anyone on the list who is interested in this idea could you contact me (off list please). Moyra E-mail: <a title="moyrab@internode.on.net" href="moyrab@internode.on.net" target="_blank">moyrab@internode.on.net</a>"</span></span></pre>
<pre><span style="font-family: FreeSans, sans-serif"><span style="font-size: x-small">Moyra is a senior librarian who has many years experience installing and using Koha in several library contexts. We congratulate Moyra on her initiative.  At CALYX, we have wanted to see Koha user groups established in major Australian cities, but preferred to see this done by librarians, not by a support company.  So we are thrilled that that is now occurring with Melbourne the first city to host the 1st Koha user group meeting in Australia. We hope that librarians in other cities will create their own Koha user group too. Moyra also said “As a number of you work in other states, it has been suggested that we could perhaps use Skype for teleconferencing. “ We don't know if this will be possible at this first meeting.</span></span></pre>
<pre><span style="font-family: FreeSans, sans-serif"><span style="font-size: x-small">Have you ever noticed in the Koha Release Notes, Maori proverbs like this one? "Ehara taku toa i te toa takitahi, engari he toa takitini" It means, 'Success is not the work of one, but the work of many.' The Koha project gains its strength from the community of librarians and support companies.  The Maori word 'Koha' means 'gift': in Maori culture, it is a gift given with some expectation of reciprocity.  Participating in a user group and sharing your experience with others is a great way to give back to the community.</span></span></pre>
<p><span style="font-family: FreeSans, sans-serif"><span style="font-size: x-small">Best wishes, Irma </span></span></p>
<p><span style="font-size: x-small;font-family: FreeSans, sans-serif"> </span></p>
]]></content:encoded>
			<wfw:commentRss>http://koha-community.org/1st-australian-koha-user-group-meeting-melbourne-vic-thursday-26-april-6pm-melbourne-athenaeum-library/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>KohaCon12 &#8211; Fishing Trip</title>
		<link>http://koha-community.org/kohacon12-fishing-trip/</link>
		<comments>http://koha-community.org/kohacon12-fishing-trip/#comments</comments>
		<pubDate>Sat, 14 Apr 2012 08:09:23 +0000</pubDate>
		<dc:creator>kfischer</dc:creator>
				<category><![CDATA[Koha News]]></category>

		<guid isPermaLink="false">http://koha-community.org/?p=3378</guid>
		<description><![CDATA[There was a request for fishing to be one of the options for the excursion day. So we could put together a package to go sea fishing. The trip could be about 4 hours, will probably be with Dougie out of North Berwick. No experience is required, rods and bait provided. It is likely to [...]]]></description>
			<content:encoded><![CDATA[<p>There was a request for fishing to be one of the options for the excursion day. So we could put together a package to go sea fishing. The trip could be about 4 hours, will probably be with Dougie out of North Berwick. No experience is required, rods and bait provided. It is likely to cost up to £40 and we need 10 people to sign up, includes travel and lunch, but is weather dependant.</p>
<p><span id="more-3378"></span></p>
<p>Further to my enquiry the skipper said this: &#8220;You can fish for mackerel, then for cod and pollok, probably best if there are only 8 or 9 fishing at one time for mackerel as we can get a bit tied up when we hit a shoal! You can bring your own food and drink and we can also take you round the Bass Rock as well to see the amazing gannets and perhaps some seals.&#8221;</p>
<p><a href="http://www.charterboats-uk.co.uk/braveheart-northberwick/" target="_blank">http://www.charterboats-uk.co.uk/braveheart-northberwick/</a></p>
<p>Payment and further details will be sorted out when enough people registered.</p>
<p><strong>UPDATE: Please register before 30th April at the latest so arrangements can be made.<br />
</strong></p>

		<div id="usermessage6a" class="cf_info "></div>
		<form enctype="multipart/form-data" action="/category/koha-news/feed/#usermessage6a" method="post" class="cform kohacon-fishing-trip " id="cforms6form">
		<fieldset class="cf-fs1">
		<legend>Fishing Trip Registration</legend>
		<ol class="cf-ol">
			<li id="li-6-2" class=""><label for="cf6_field_2"><span>Your Name</span></label><input type="text" name="cf6_field_2" id="cf6_field_2" class="single fldrequired" value="Your Name" onfocus="clearField(this)" onblur="setField(this)"/><span class="reqtxt">(required)</span></li>
			<li id="li-6-3" class=""><label for="cf6_field_3"><span>Email</span></label><input type="text" name="cf6_field_3" id="cf6_field_3" class="single fldemail fldrequired" value=""/><span class="emailreqtxt">(valid email required)</span></li>
			<li id="li-6-4" class=""><label for="cf6_field_4"><span>Number of Persons</span></label><input type="text" name="cf6_field_4" id="cf6_field_4" class="single" value=""/></li>
			<li id="li-6-5" class=""><label for="cf6_field_5"><span>Message</span></label><textarea cols="30" rows="8" name="cf6_field_5" id="cf6_field_5" class="area"></textarea></li>
		</ol>
		</fieldset>
		<fieldset class="cf_hidden">
			<legend>&nbsp;</legend>
			<input type="hidden" name="cf_working6" id="cf_working6" value="One%20moment%20please..."/>
			<input type="hidden" name="cf_failure6" id="cf_failure6" value="Please%20fill%20in%20all%20the%20required%20fields."/>
			<input type="hidden" name="cf_codeerr6" id="cf_codeerr6" value="Please%20double-check%20your%20verification%20code."/>
			<input type="hidden" name="cf_customerr6" id="cf_customerr6" value="yyy"/>
			<input type="hidden" name="cf_popup6" id="cf_popup6" value="nn"/>
		</fieldset>
		<p class="cf-sb"><input type="submit" name="sendbutton6" id="sendbutton6" class="sendbutton" value="Submit" onclick="return cforms_validate('6', false)"/></p></form><p class="linklove" id="ll6"><a href="http://www.deliciousdays.com/cforms-plugin"><em>cforms</em> contact form by delicious:days</a></p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://koha-community.org/kohacon12-fishing-trip/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Roles for Koha 3.10.0</title>
		<link>http://koha-community.org/roles-koha-3-10-0/</link>
		<comments>http://koha-community.org/roles-koha-3-10-0/#comments</comments>
		<pubDate>Wed, 04 Apr 2012 21:27:19 +0000</pubDate>
		<dc:creator>Chris Cormack</dc:creator>
				<category><![CDATA[Koha]]></category>
		<category><![CDATA[Koha News]]></category>

		<guid isPermaLink="false">http://koha-community.org/?p=3301</guid>
		<description><![CDATA[In a Koha community meeting last night, positions for the Koha 3.10.0 release cycle (due October 2012) were confirmed. It is our biggest release team yet and a really good sign of the health of the community that we had so many volunteers. The roles are

Release Manager : Paul Poulain, France
Translation Manager: Shared between Samuel [...]]]></description>
			<content:encoded><![CDATA[<p>In a Koha community meeting last night, positions for the Koha 3.10.0 release cycle (due October 2012) were confirmed. It is our biggest release team yet and a really good sign of the health of the community that we had so many volunteers. The roles are</p>
<ul>
<li><strong>Release Manager</strong> : Paul Poulain, France</li>
<li><strong>Translation Manager</strong>: Shared between Samuel Desseaux and Frédéric Demians both from France</li>
<li><strong>Translation Assistants</strong>: Katrin Fischer, Germany; Marijana Glavica, Croatia</li>
<li><strong>Documentation Manager: </strong>Nicole Engard, USA</li>
<li><strong>DB Documentation</strong> <strong>Manager</strong>: Nicole Engard, USA</li>
<li><strong>Quality Assurance (QA) Manager</strong>: Ian Walls, USA</li>
<li><strong>Quality Assurance (QA) Assistants</strong>: Marcel de Rooy, Netherlands; Jonathan Druart, France; Mason James, New Zealand</li>
<li><strong>Release Maintainer 3.8.x</strong>: Chris Cormack, New Zealand</li>
<li><strong>Release Maintainer 3.6.x</strong>: Jared Camins-Esakov, USA</li>
<li><strong>Packaging Manager</strong>: Robin Sheat, New Zealand</li>
<li><strong>Packaging Assistant</strong>: Mason James, New Zealand</li>
<li><strong><strong>Bug Wrangler: </strong></strong>Magnus Enger, Norway; Katrin Fischer, Germany; Dobrica Pavlinušić, Croatia; Koustubha Kale, India</li>
<li><strong>Meeting Chair</strong>: BWS Johnson, USA</li>
</ul>
<p>So that&#8217;s 17 people in total who have volunteered and been accepted to positions for the next 6 months (starting after the release of 3.8.0 on April 23). I think it is also great we have a nice geographic spread especially the bug wrangler team.</p>
]]></content:encoded>
			<wfw:commentRss>http://koha-community.org/roles-koha-3-10-0/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Marseille Hackfest 2012, feedback</title>
		<link>http://koha-community.org/marseille-hackfest-2012-feedback/</link>
		<comments>http://koha-community.org/marseille-hackfest-2012-feedback/#comments</comments>
		<pubDate>Fri, 23 Mar 2012 16:13:10 +0000</pubDate>
		<dc:creator>Paul Poulain</dc:creator>
				<category><![CDATA[3.8]]></category>
		<category><![CDATA[Koha]]></category>
		<category><![CDATA[Koha News]]></category>

		<guid isPermaLink="false">http://koha-community.org/?p=3230</guid>
		<description><![CDATA[The Hackfest BibLibre organized in Marseille is almost over ! time passes too quickly.
A lot of great great great work has been made, I&#8217;ll try to report things we made:
As we planned, we splitted in 5 groups, 4 of them focusing on specific hackers topics, the 5th one being librarians testing &#038; translating.
Plack group
(Alex, Matthias, [...]]]></description>
			<content:encoded><![CDATA[<p>The Hackfest BibLibre organized in Marseille is almost over ! time passes too quickly.</p>
<p>A lot of great great great work has been made, I&#8217;ll try to report things we made:<br />
As we planned, we splitted in 5 groups, 4 of them focusing on specific hackers topics, the 5th one being librarians testing &#038; translating.</p>
<h3>Plack group</h3>
<p>(Alex, Matthias, Dobrika and Henri-Damien at the beginning)<br />
this group focused on introducing plack on Koha. A big performance boost was expected from their work.</p>
<ul>
<li>Alex, Matthias and Dobrika worked on &#8220;plackifying&#8221; Koha. The OPAC is already working fine under plack (it&#8217;s lived in Lyon3 university, running 3.6, since 3 months)<br />
A wiki page has been written to show how to integrate plack into Koha setup: http://wiki.koha-community.org/wiki/Plack</li>
<li>The main problem that has been encountered with the staff interface is described in section 3 of this page: http://wiki.koha-community.org/wiki/Plack#Running_Intranet<br />
Dobrika worked a lot on writing patches to solve those problems (see bug 7172). He plans to run Koha on plack in production on staff interface next week, so that will be easier to identify any remaining problem !</li>
<li>The major goal is to be Plack available as an option for Koha 3.8.</li>
</ul>
<p><b>Just a comparison</b> (patron search taken as example): generating a page in CGI mode takes 1.12s, and in Plack mode, it takes 0.334s (<b>3 times faster. Yes you&#8217;re reading well. Koha is 3 times faster with Plack !</b>)</p>
<p>A second comparison : zebra search: 1.6s for plack and 3s for CGI</p>
<p>A better use of Plack can even be made, and everybody plan to continue the work for 3.10<br />
Just beware that you&#8217;re trading speed for memory: plack consumes more memory than CGI: each child running consumes around 60MB of memory, so if you&#8217;ve 12 childs (suggested/recommended value), it mean you need aroung 1GB for Plack.</p>
<p>Alex also tried to see how Koha could be fully PSGI compliant, but the tries were not successfull for now.</p>
<h3>Ergonomy</h3>
<p>(Owen, Katrin, Adrien, Gaetan, Marijana and Julian)</p>
<ul>
<li>The group made big lists of things that are inconsistent, ergonomy guidelines,&#8230; Some wiki pages have been written.</li>
<li>the group suggested to use &#8220;Add&#8221; when we add something to an existing object, and the term &#8220;New&#8221; when it&#8217;s something not related to anything else</li>
<li>Adrien added header search bar, that is everywhere else on Koha has been introduced in the mainpage (patch submitted)</li>
<li>Gaetan started to work on a design for the home page, and the staff interface. The goal is to have it for 3.8</li>
<li>Katrin added id to all pages, as well as a specific css class. It mean we will be able to write a css with different colors for each module (the patch has been pushed, see bug 7760, comment 32 for an example how to use it). The bug 7812 is also related to this improvement, and is about adding a global &#8220;header&#8221; that include the menu, the header search bar and the breadcrumb, but no code has been submitted yet.</li>
<li>Owen presented a framework (bootstrap) that could be a replacement for YUI. The interesting point with bootstrap is that it contains all what we need for smartphones. Julian hacked a little bit, and replaced the opac-search.pl. </li>
</ul>
<h3>Database</h3>
<p>(Marc, Stéphane and Christophe)</p>
<ul>
<li>the group focused on removing mysql-ism</li>
<li>a first list of mysql-ism has been identified and put on the wiki: http://wiki.koha-community.org/wiki/PostgreSQL.</li>
<li>the &#8220;show column&#8221; mysqlism has been removed in a patch submitted on bug </li>
<li>a generic OO approach has been taken for things that don&#8217;t have a generic equivalent. </li>
</ul>
<h3>Solr</h3>
<p>(Zeno, Juan, Claire, Jonathan (a little) and Henri-Damien)<br />
The Solr work is a long term work.<br />
All the work the group made is explained in the wiki page : http://wiki.koha-community.org/wiki/Switch_to_Solr_RFC#.23kohahack12</p>
<h3>Librarians</h3>
<p>The group of french librarians did a great work !</p>
<p>Bugzilla show the following numbers : no patches need to be pushed, 16 patches are waiting for QA, 71 patches are waiting for signoff.</p>
<p>The number of patches needing signoff hasn&#8217;t been lowered at first glance. But it&#8217;s a wrong feeling ! If you look closer, you&#8217;ll discover that :</p>
<ul>
<li>3 patches only had no activity since january</li>
<li>6 patches only had no activity since february</li>
<li>13 patches haven&#8217;t been updated this week but earlier in march.</li>
</ul>
<p><b>all other patches still to sign-off had an activity this week.</b><br />
Around 30 patches have been signed-off.</p>
<p>Those librarians where french, so the french translation of Koha 3.8 have been done, and a large part of the manual has been translated as well.</p>
<h3>Conclusion</h3>
<p>Last year, everybody was happy of our hackfest. This year, everybody is happy with this hackfest. So next year we will organize another one, you can already ask your boss (for end of march)</p>
]]></content:encoded>
			<wfw:commentRss>http://koha-community.org/marseille-hackfest-2012-feedback/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Koha 3.6.4 is now available</title>
		<link>http://koha-community.org/koha-3-6-4/</link>
		<comments>http://koha-community.org/koha-3-6-4/#comments</comments>
		<pubDate>Sun, 04 Mar 2012 21:47:50 +0000</pubDate>
		<dc:creator>Chris Nighswonger</dc:creator>
				<category><![CDATA[3.6]]></category>
		<category><![CDATA[Announcements]]></category>
		<category><![CDATA[Koha]]></category>
		<category><![CDATA[Koha News]]></category>
		<category><![CDATA[release]]></category>

		<guid isPermaLink="false">http://koha-community.org/?p=3203</guid>
		<description><![CDATA[It is with pleasure that I announce the release of Koha 3.6.4.
The package can be retrieved from:
http://download.koha-community.org/koha-3.06.04.tar.gz
You can use the following checksum and signature files to verify the download:
http://download.koha-community.org/koha-3.06.04.tar.gz.MD5
http://download.koha-community.org/koha-3.06.04.tar.gz.MD5.asc
http://download.koha-community.org/koha-3.06.04.tar.gz.sig
Release notes for 3.6.4 are below the fold.
Come and get it!
RELEASE NOTES FOR KOHA 3.6.4
22 Feb 2012
========================================================================

Koha is the first free and open source software library automation [...]]]></description>
			<content:encoded><![CDATA[<h5>It is with pleasure that I announce the release of Koha 3.6.4.</h5>
<p>The package can be retrieved from:</p>
<p><a href="http://download.koha-community.org/koha-3.06.04.tar.gz">http://download.koha-community.org/koha-3.06.04.tar.gz</a></p>
<p>You can use the following checksum and signature files to verify the download:</p>
<p><a href="http://download.koha-community.org/koha-3.06.04.tar.gz.MD5">http://download.koha-community.org/koha-3.06.04.tar.gz.MD5</a><br />
<a href="http://download.koha-community.org/koha-3.06.04.tar.gz.MD5.asc">http://download.koha-community.org/koha-3.06.04.tar.gz.MD5.asc</a><br />
<a href="http://download.koha-community.org/koha-3.06.04.tar.gz.sig">http://download.koha-community.org/koha-3.06.04.tar.gz.sig</a></p>
<p>Release notes for 3.6.4 are below the fold.</p>
<p>Come and get it!<img title="More..." src="http://koha-community.org/wp-includes/js/tinymce/plugins/wordpress/img/trans.gif" alt="" /><span id="more-3203"></span></p>
<pre>RELEASE NOTES FOR KOHA 3.6.4
22 Feb 2012
========================================================================

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.6.4 can be downloaded from:

http://download.koha-community.org/koha-3.06.04.tar.gz

Installation instructions can be found at:

http://wiki.koha-community.org/wiki/Installation_Documentation

    OR in the INSTALL files that come in the tarball

Koha 3.6.4 is a bugfix/maintenance release.

Highlights of 3.6.4
======================

6488	critical	opachiddenitems not working in master
6634	critical	manager_id not populated when paying fines
6984	critical	Holds Statistics Doesn't Work
7018	critical	need all acq permissions to search
7339	critical	Help System in IE8-9 Does Not Load With 500 Error
7359	critical	Begin migration to a new "Koha" namespace from the old "C4" namespace
7432	critical	Changing frameworks should refresh cache
7450	critical	Missing placeholders in admin/authorised_values.pl
7551	critical	Any logged-in OPAC user can renew items for others using a properly constructed URL
2012	major		Add bilio crashes under no zebra
3264	major		Uncloning a dropdown list in MARC authorities/biblio editor may clear all subfields (see comment 17)
5327	major		Unit tests required for all C4 modules
6115	major		Acquisition reports : date filter &amp; sorting don't work
6490	major		Lost and paid not updated when book is checked out without check-in
6631	major		Unrestricted creation of lists by anonymous users
6718	major		No manager_id saved for writeoff of fines
6842	major		Branch transfer limits broken
7005	major		no confirmation for write off all
7431	major		OPAC item hold list doesn't show 'checked out'
7459	major		Can only add to one public list in OPAC search results

Bugs fixed in 3.6.4
======================

5473	normal		952 fields should be filled in by Acquisitions
6598	normal		OPACFineNoRenewals syspreference does not stop user renewing in opac
6694	normal		Anonymous sessions not kept when casAuthentication is on
7114	normal		Hiding filters on funds page messes with layout
7127	normal		Templates must be valid XHTML
7190	normal		written off fines being refunded
7350	normal		In New order the "+" button duplicates input text but not the "selected" in ddl
7402	normal		invoice not showing received titles
7406	normal		saved reports not showing right number
7409	normal		Missing dependencies for Debian package
7457	normal		basket.pl makes a lot of noise in the logs
7466	normal		Cart notification popup should appear onscreen even when button is offscreen
7472	normal		Edit button ineffective when paying borrower fee
7476	normal		Files executable that probably should not be
7489	normal		Implement DisplayOPACiconsXSLT for NORMARC XSLT
7501	normal		OPAC authority browser should mark alternate rows as highlighted
7521	normal		Cannot receive serials without full serials permissions
4376	enhancement	A minor change in the â€œGetMarcAuthorsâ€  function of C4/Biblio.pm would allow differentiate the type of authors in the templates
5346	enhancement	Linking suggestions &amp; orders
6210	enhancement	Choose framework on Merge
6299	enhancement	Provide a list of authorized values for relator terms
6314	enhancement	UNIMARC OPAC XSL improvements
6323	enhancement	Attach/move items - adding option "try again" after success or wrong barcode
6752	enhancement	Be stricter with utf-8 output
6790	enhancement	C4::Serials::getroutinglist returns unnecessary variable
6838	enhancement	Filtering and pagination in subscriptions table
6865	enhancement	Replace image-based gradient backgrounds with CSS3 gradients
6913	enhancement	Improving koha-list and koha-create
6985	enhancement	Hide "kw,wrdl:" from Search Results
7080	enhancement	Clean up interface on fine payment screens
7083	enhancement	Show creator name on list of public lists
7090	enhancement	Add "AllowItemsOnHandCheckout" syspref to allow issue to the patron regardless of hold status
7148	enhancement	Add some error handling to Acquisitions' Z39.50 search to match Cataloging's
7157	enhancement	Improve the j2a.pl cronjob
7201	enhancement	Hold to pull report needs extra fields
7246	enhancement	rebuild_zebra.pl --limit option to allow partial re-indexing
7289	enhancement	edition statement field
7343	enhancement	search tag usability in MARC framework
7345	enhancement	Should be possible to export MARC records without private fields
7355	enhancement	Note subfields are not displayed in TEXTAREA if hidden
7357	enhancement	Subscriptions titles are replaced by "---" when duplicated
7458	enhancement	New call number allocation plugin
7511	enhancement	Caching Templates
7514	enhancement	Choose OPAC language with URL parameter
7532	enhancement	opac-ics depends on Date::ICal which is largely unmaintained

System requirements
======================

    Changes since 3.4:

    * Perl 5.10 is required

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, only the English version of the
Koha manual is available:

http://manual.koha-community.org/3.6/en/

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 (Taiwan)
  * Danish
  * English (USA)
  * English (UK)
  * French (France)
  * German
  * Italian
  * Portuguese (Brazil)
  * Spanish

Partial translations are available for various other languages.

The Koha team welcomes additional translations; please see

http://wiki.koha-community.org/wiki/Translating_Koha

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.6 is

Release Manager:        Chris Cormack &lt;chrisc@catalyst.net.nz&gt;
Documentation Manager:  Nicole C Engard &lt;nengard@gmail.com&gt;
Translation Manager:    FrÃ©dÃ©ric Demians &lt;frederic@tamil.fr&gt;
QA Manager:             Ian Walls &lt;ian.walls@bywatersolutions.com&gt;
Bug Wranglers:          MJ Ray, Marcel de Rooy, Paul Poulain, Mason James

Release Maintainer (3.4.x):
                        Chris Nighswonger &lt;cnighswonger@foundations.edu&gt;
Release Maintainer (3.6.x):
                        Chris Nighswonger &lt;cnighswonger@foundations.edu&gt;

Credits
======================

We thank the following libraries who are known to have sponsored
new features in Koha 3.6:
  * Los Gatos Public Library
  * NEKLS
  * East Brunswick Public Library
  * Athens County Public Libraries
  * Horowhenua Library Trust
  * Halton Borough Council
  * South Taranaki District Council

We thank the following individuals who contributed patches to
Koha 3.6.4. 

     3	Tomas Cohen Arazi
     1	Alex Arnaud
     2	D Ruth Bavousett
     3	Jared Camins-Esakov
     2	Colin Campbell
     7	Garry Collum
    11	Chris Cormack
     1	Christophe Croullebois
     1	StÃ©phane Delaune
     8	FrÃ©dÃ©ric Demians
     1	Connor Dewar
     1	Jonathan Druart
     1	Nicole Engard
     1	Magnus Enger
     4	Katrin Fischer
     2	Kyle M Hall
     2	Kate Henderson
     7	Srdjan Jankovic
     1	Bart Jorgensen
     1	Janusz Kaczmarek
     1	Jorgia Kelsey
     1	Henri-Damien Laurent
    13	Owen Leonard
     1	Peter Lorimer
     5	Julian Maurice
     1	Matthias Meusburger
     2	Jono Mingard
    31	Chris Nighswonger
     2	Maxime Pelletier
    26	Paul Poulain
     1	MJ Ray
     7	Liz Rea
     5	Marcel de Rooy
     5	Sam Sanders
     3	Adrien Saurat
     6	Robin Sheat
     1	Juan Sieira
     1	Duncan Tyler
     2	Aleksa Vujicic
     1	biblibre

We regret any omissions.  If a contributor has been inadvertantly missed,
please send a patch against these release notes to
koha-patches@lists.koha-community.org.

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.6.x (i.e., this version of Koha and future bugfix
releases) is 3.6.x.

The next major feature release of Koha will be Koha 3.8.0.

Bugs and feature requests
======================

Bug reports and feature requests can be filed at the Koha bug
tracker at

http://bugs.koha-community.org/

Ehara taku toa i te toa takitahi, engari he toa takitini 

##### Autogenerated release notes updated last on 22 Feb 2012 20:14:40 Z #####</pre>
]]></content:encoded>
			<wfw:commentRss>http://koha-community.org/koha-3-6-4/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Koha Release Manager newsletter #4 2012-02</title>
		<link>http://koha-community.org/koha-release-manager-newsletter-4-2012-02/</link>
		<comments>http://koha-community.org/koha-release-manager-newsletter-4-2012-02/#comments</comments>
		<pubDate>Fri, 02 Mar 2012 15:16:53 +0000</pubDate>
		<dc:creator>Paul Poulain</dc:creator>
				<category><![CDATA[Announcements]]></category>
		<category><![CDATA[Koha]]></category>
		<category><![CDATA[Koha News]]></category>

		<guid isPermaLink="false">http://koha-community.org/?p=3192</guid>
		<description><![CDATA[Welcome to the 4th RM newsletter.
First of all, it means i&#8217;ve started this role for 4 months. wow, times passes very quickly.
When I applied, I said I planned to dedicate half of my time to this role. Chris C., the previous RM, said he dedicated more than this. The good news is that I could [...]]]></description>
			<content:encoded><![CDATA[<p>Welcome to the 4th RM newsletter.<br />
First of all, it means i&#8217;ve started this role for 4 months. wow, times passes very quickly.<br />
When I applied, I said I planned to dedicate half of my time to this role. Chris C., the previous RM, said he dedicated more than this. The good news is that I could dedicate a little bit more than half of my time. The bad news is that I could dedicate more, Chris was right. There are so many things that could be done that I could dedicate 2 full time in fact.</p>
<p>So let&#8217;s go with last month news&#8230;</p>
<p>Just one number to begin with: more than 200 patches have been pushed in february. Good job everyone !</p>
<h3>Bugzilla news</h3>
<p>There are 74 bugs that are waiting for a sign-off. That&#8217;s only a few less than last month, but many have been signed, and many have been added.<br />
I see that 12 of them have been submitted in january or before. Maybe we should discuss of setting a very high priority to those &#8220;old&#8221; patches.<br />
Also note that I have submitted a new script that is able to check all patches that &#8220;need signoff&#8221;, and check if they still apply. You can find this script on bug <a href="http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7553" title="bug 7553">http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7553</a></p>
<p>The very good news is that the pile of bugs that have been signed-off and are waiting for QA is now very small: there are only 14, and the oldest one is less than one week old ! Thanks to the hard work of Marcel that helped me a lot QAing.</p>
<h3>Important new features</h3>
<h4>Template Toolkit caching (technical)</h4>
<p>The bug 7511 add a new feature : templates (the layout of Koha pages) can now be cached. It means they are pre-built and can be retrieved very quickly. It results in an overall improvement of speed of 10%, just with 4 lines of code !</p>
<h4>general caching</h4>
<p>After a discussion on the mailing list, we made some changes on the general caching: the reference to memcached is now made in Apache configuration, this let us cache koha configuration file itself, this result in a 10% speed gain once again.<br />
You can find the discussion at: <a href="http://wiki.koha-community.org/wiki/Cache_handling_in_Koha" title="cache handling">http://wiki.koha-community.org/wiki/Cache_handling_in_Koha</a><br />
All patches have been applied on koha code, will be available for Koha 3.8. It means that existing setups using memcached will have to be updated when upgrading to 3.8</p>
<h4>Test suite improved</h4>
<p>Catalyst NZ has organised, in january, an &#8220;OpenSource Academy&#8221;. Some of the students choose to work on Koha test suite, and 5 new contributors have been added during this Academy. They have added some tests to our test suite. Congrats to all of them (and thanks to Catalyst ppl that trained them !)</p>
<h4>Code cleaning</h4>
<p>The effort for cleaning code continued:</p>
<ul>
<li>Owen has written a patch that standardize how we call the book vendor (in the code, not in the interface). It used to be sometimes supplierid, sometimes booksellerid, sometimes id. Now it&#8217;s always booksellerid.
</li>
<li>De nesting effort: All access to database are made through Perl packages that are located in C4 directory. the problem is that circulation needs patrons, that needs catalogue that needs circulation. At the end, almost all packages are loaded for almost all scripts. There is a de-nesting effort i&#8217;ve started on bug 6875, that could be continued, but the first patches have been pushed onto Koha. It&#8217;s a long term effort, but it&#8217;s worth the price, as it also improve speed.</li>
<li>Capitalizing strings: The bug 2780 is back: we had decided a long time ago, to use capital letters only on 1st word. For example, adding an item button should not be spelled &#8220;Add Item&#8221; but &#8220;Add item&#8221;. This may sound a minor thing, but it&#8217;s a consistency things, and it&#8217;s very important for translators. If we have &#8220;Add Item&#8221; and &#8220;Add item&#8221; and &#8220;add item&#8221;, translation must be written 3 times ! There&#8217;s now a strong QA rule for this, and you&#8217;re welcomed to submit patches fixing remaining strings with useless capital letter !</li>
</ul>
<h4>funny and not that small new features</h4>
<ul>
<li>The patron password is now entered as hidden ***** </li>
<li>you can run rebuild_zebra.pl with an offset and a length, to quickly test or reindex a small chunk of your database (bug 7246)</li>
<li>we can now search patrons on their name, but also on their phone or email (bug 7544)</li>
<li>you can now add and remove a biblio to the cart from the biblio itself, not only add it (bug 3215)</li>
<li>you can print transfer slips for transfers without hold (bug 7467)</li>
</ul>
<h3>bugs &#8220;in discussion&#8221;</h3>
<p>The first discussions took place for bugs/patches/enhancement that require a community decisions.<br />
I&#8217;ve added on bugzilla a &#8220;in discussion&#8221; query, if you use it now, you&#8217;ll see that there are 13 bugs set &#8220;in discussion&#8221;. Feel free to start the discussion, by adding a page to the wiki and starting a thread on koha-devel.</p>
<h3>Coding Guidelines</h3>
<p>For those who don&#8217;t know, the coding guidelines describe the rules for coding, that are used for Quality Assurance. For example, we have decided to use 4 spaces to indent the code and have it more readable.<br />
So the following code is OK:<br />
<code>if ($RMnewletter eq '4') {<br />
&nbsp;&nbsp;&nbsp;&nbsp;say "end of february";<br />
}</code><br />
while this one is not:<br />
<code>if ($RMnewletter eq '4') {<br />
&nbsp;&nbsp;say "end of february";<br />
}</code><br />
(yes, it&#8217;s a detail, but when you have 100 000+ lines, it&#8217;s the kind of detail that is important !)</p>
<p>Many things where already made, but not written, now they are. The more things will be written, the easiest it will be to do the QA !</p>
<p>I&#8217;ve added code &#038; number to the guidelines. That will be usefull when QAing, to point a breaking of a guideline. For example [PERL2] rule says &#8220;All scripts and modules should enable the strict and warnings pragmas&#8221;. If the QA team says &#8220;PERL2 rule broken failed QA&#8221;, you know what it refers to.</p>
<p>If you want to look at all those guidelines, it&#8217;s on the wiki: <a href="http://wiki.koha-community.org/wiki/Coding_Guidelines" title="coding guidelines">http://wiki.koha-community.org/wiki/Coding_Guidelines</a></p>
<h3>sandboxes and patch workflow</h3>
<p>The sandbox system is done &#038; has been deployed on 10 BibLibre servers. Head to <a href="http://wiki.koha-community.org/wiki/Sandboxes" title="sandbox">http://wiki.koha-community.org/wiki/Sandboxes</a><br />
What are those sandboxes done for ? That&#8217;s a handy way for non developpers to test and validate patches.<br />
The community workflow is the following:<br />
 1 someone report a problem or announce an enhancement<br />
 2 someone submit a patch to fix the problem or add the enhancement<br />
 3 someone test and validate the fix or the enhancement<br />
 4 someone (from the QA team) validate that the code respect the coding guidelines<br />
 5 the release manager &#8220;push&#8221; the patch into official Koha.<br />
(this workflow is also described here: <a href="http://wiki.koha-community.org/wiki/Bug-enhancement-patch_Workflow" title="wiki page">http://wiki.koha-community.org/wiki/Bug-enhancement-patch_Workflow</a>)</p>
<p>The step 3 (test &#038; validate) is also called &#8220;signing off&#8221;, and can be done by anyone. The best being when it&#8217;s a librarian !<br />
However, it can be tricky to have a working koha, and apply the patch. The sandbox system hope to fix this point, by letting anyone with no technical skill test a patch !</p>
<p>Don&#8217;t hesitate to use it, ask for more information if you want. you can catch me on IRC</p>
<p>Note that the code of this sandbox system will be published soon at <a href="http://git.koha-community.org/gitweb/?p=contrib/global.git;a=summary" title="gitweb">http://git.koha-community.org/gitweb/?p=contrib/global.git;a=summary</a></p>
]]></content:encoded>
			<wfw:commentRss>http://koha-community.org/koha-release-manager-newsletter-4-2012-02/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Update 3 : NZ Koha Trademark</title>
		<link>http://koha-community.org/update-3-nz-koha-trademark/</link>
		<comments>http://koha-community.org/update-3-nz-koha-trademark/#comments</comments>
		<pubDate>Wed, 15 Feb 2012 20:25:41 +0000</pubDate>
		<dc:creator>jransom</dc:creator>
				<category><![CDATA[Koha News]]></category>
		<category><![CDATA[Koha]]></category>
		<category><![CDATA[ptfs]]></category>
		<category><![CDATA[trademark]]></category>

		<guid isPermaLink="false">http://koha-community.org/?p=3159</guid>
		<description><![CDATA[We have received a response from PTFS to our letter outlining the grounds on which we object to their trade mark application and inviting them to transfer their application to the Trust.
The response advised that they are considering organisations as possible candidates to hold the NZ trademark and we were welcome to submit a proposal [...]]]></description>
			<content:encoded><![CDATA[<p>We have received a response from PTFS to our letter outlining the grounds on which we object to their trade mark application and inviting them to transfer their application to the Trust.</p>
<p>The response advised that they are considering organisations as possible candidates to hold the NZ trademark and we were welcome to submit a proposal which would be required to address a number of criteria set by PTFS.</p>
<p>Te Horowhenua Trust, trading as Horowhenua Library Trust, is the nonprofit body elected by the Koha global community to hold community assets in safe keeping. We have spent a number of years negotiating with PTFS and would prefer now to trust a transparent and defined process conducted through IPONZ as to the proper ownership of the mark in New Zealand.</p>
]]></content:encoded>
			<wfw:commentRss>http://koha-community.org/update-3-nz-koha-trademark/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Koha Release Manager newsletter #3 2012-01</title>
		<link>http://koha-community.org/koha-release-manager-newsletter-3-2012-01/</link>
		<comments>http://koha-community.org/koha-release-manager-newsletter-3-2012-01/#comments</comments>
		<pubDate>Fri, 03 Feb 2012 16:00:00 +0000</pubDate>
		<dc:creator>Paul Poulain</dc:creator>
				<category><![CDATA[Koha News]]></category>

		<guid isPermaLink="false">http://koha-community.org/?p=3137</guid>
		<description><![CDATA[I publish, every month since i&#8217;m Release Manager, a newsletter, that is, I hope, usefull for people to discover what is new in the coming Koha. newsletter #1 and #2 have been sent by mail to koha-devel list only.
Everybody should read this newsletter in detail.
If you&#8217;re planning to submit patches, you must. If you&#8217;re just [...]]]></description>
			<content:encoded><![CDATA[<p>I publish, every month since i&#8217;m Release Manager, a newsletter, that is, I hope, usefull for people to discover what is new in the coming Koha. newsletter #1 and #2 have been sent by mail to koha-devel list only.</p>
<p>Everybody should read this newsletter in detail.</p>
<p>If you&#8217;re planning to submit patches, you <strong>must</strong>. If you&#8217;re just a user of Koha, there are some interesting announcements too, you can read it<br />
as well !</p>
<h3>Bugzilla news</h3>
<p>There are 87 bugs waiting to be signed-off.</p>
<p>That&#8217;s too much ! and a problem is that is seems that hard-to-test patches can be lost in the wilderness for a long time.</p>
<p>Small/easy patches are usually quickly signed-off.</p>
<p>The patches to QA pile show a correct 30 patches. Unfortunatly, that&#8217;s the hardest ones too, as I QAed a lot of &#8216;trivial&#8217; patches this month&#8230;</p>
<h3>Bugzilla</h3>
<p>Earlier this month Ian, our QA manager made important changes to our bugzilla setup. The &#8220;patch status&#8221; field has been removed in favor of the &#8220;status&#8221; field. The previous &#8220;patch status&#8221; have all be moved to &#8220;status&#8221;.</p>
<p>2 new status have been added:</p>
<ul>
<li>in discussion = will be used when a patch need a deeper discussion to see if it can/should be added into Koha. The discussion can be functional (is the feature desirable in Koha ?) or technical (is the way it&#8217;s made OK ?) The &#8220;in discussion&#8221; bugs will be discussed on the monthly meeting.</li>
<li>&#8216;pushed to stable&#8217;: pushed has been splitted in &#8220;pushed to master&#8221; and &#8220;pushed to stable&#8221;. The RMaint (Chris N. for now) will use &#8220;Pushed to stable&#8221; when he pushed a patch to stable (3.6). The &#8220;pushed to master&#8221; is used by me when pushing to master (for the future 3.8)</li>
</ul>
<p>The only side effect of this bulkchange is that date of last change of each bug has been reseted to the date of the bulkchange. That&#8217;s annoying if you want to see which patch to signoff is the oldest.</p>
<h3>Coding guidelines</h3>
<p>I&#8217;ve updated the code guideline page on the wiki (<a href="http://wiki.koha-community.org/wiki/Coding_Guidelines">http://wiki.koha-community.org/wiki/Coding_Guidelines</a>)</p>
<p>I&#8217;ve removed all deprecated guidelines, and added some that we already use, and that were not written.</p>
<p>I&#8217;ve added a general rule for QA:</p>
<p>General rule: if you submit code that fixes an existing code that violates those guidelines, the QA can still be passed. You don&#8217;t have to fix everything. If you want to fix more than just your fix, to respect current guidelines, you&#8217;re welcomed of course. But in this case, please to it in a 2nd patch, to have reviewers being able to distinguish easily what&#8217;s related to your bugfix and what is related to your guidelines-violation fixing.</p>
<h3>Important technical patches pushed</h3>
<p>Some important internal changes have been pushed. Those change won&#8217;t be visible for users, but are important for developers</p>
<h4>Date formatting &amp; displaying</h4>
<p>Chris has written a nice Template::Toolkit plugin that will take care of date formatting for you. Before the patch, you had to format dates before sending them to the template, something like:<br />
<code>my $entrydate = C4::Dates-&gt;new( $data-&gt;{'entrydate'}, 'iso' );<br />
$data-&gt;{'entrydate'} = $entrydate-&gt;output("syspref");<br />
# entrydate is now available<br />
</code><br />
Now, you still can do it that way, but that would be a really bad idea: just send the date as it&#8217;s provided by mySQL (iso format), and, in the template, write<br />
<code><br />
[% MyDate | $KohaDates %]<br />
</code><br />
don&#8217;t forget to put [% USE KohaDates %] at the beginning of your page to tell Template::Toolkit you&#8217;ll use this plugin. What must/can be done now is &#8230; update all code &amp; templates displaying dates to use this plugin ! Bug 7444 has been created to reflect all the patches that will be made to switch to KohaDates template.</p>
<p><strong>Coding Guideline rule</strong></p>
<li>all new code displaying date <strong>*MUST*</strong> use this plugin</li>
<li>existing code can still use previous option, but cleaning is highly welcomed</li>
<h4>Datatable jquery plugin</h4>
<p>We&#8217;ve decided some months ago to get rid of the various jquery plugins we use to display large tables, in favor of Datatable.<br />
Datatable has been pushed into master, with a first page using it (patron reading record), and some documentation on the wiki (<a href="http://wiki.koha-community.org/wiki/DataTables_HowTo">http://wiki.koha-community.org/wiki/DataTables_HowTo</a>) </p>
<p><strong>Coding guideline rule</strong></p>
<li>all new code displaying potentially large tables <strong>*MUST*</strong> use this plugin (preferably the &#8220;server side processing&#8221; option)</li>
<li>existing code can still use old plugins, but cleaning is highly welcomed !</li>
</h3>
<p>Important functionnal patches pushed</h3>
<p>Some patches that contains important new features have been pushed. Don&#8217;t hesitate to test them again and again if you&#8217;ve a sandbox. They&#8217;ll be available in Koha 3.8</p>
<h4>UnwantedFields in member entry (bug 6190)</h4>
<p>A new syspref now let you choose fields that you don&#8217;t want to have in patron forms. A very interesting feature as there are <strong>many</strong> fields available. Note that this is a syspref, so you can&#8217;t remove some fields for a given category and keep it for another. But that&#8217;s a nice first step anyway !</p>
<h4>Acquisition changes</h4>
<p>Some changes, coming from the stuff made by BibLibre for StEtienne university have been pushed:</p>
<li>show cancelled order in basket page (bug 5358): after the list of orders, you now also have the list of cancelled lines, on every basket</li>
<li>late order management (bug 5347): Koha now keep track of how many claims you&#8217;ve made on a given order line, and the date of the last claim. The default claim notification has been updated and your claim will have to be updated when upgrading to 3.8</li>
<p>The breakdown of budget spending has also been reintroduced (Bug 929) : on acqui-home.pl page, on each budget you can now see how the budget has been spent.</p>
<h4>Local cover images (bug 1633)</h4>
<p>You can now upload images to your biblios, that will be displayed as cover image. You can also zoom on the image, and, if you&#8217;ve uploaded more than just one, see all of them. This feature can be activated on staff and OPAC independantly.</p>
<h4>j2a.pl script</h4>
<p>The j2a.pl script, that is in misc/cronjobs was previously very basic, upgrading Childs to Adult (hardcoded category) when they reached 18. The script now has many new option to make it much more usefull</p>
<h3>Hackfest in Europe</h3>
<p>Again, in case you missed the news BibLibre (my company, in case you don&#8217;t know) organize a hackfest in Marseille in March. More information at <a href="http://drupal.biblibre.com/en/blog/entry/2012-hackfest-in-europe">http://drupal.biblibre.com/en/blog/entry/2012-hackfest-in-europe</a>, feel free to join, all attendees will get a special thanks on this newsletter after the hackfest. We already have Owen coming from USA, Marc, coming from Switzerland, Katrin coming from Germany, Dobrika and Marijana coming from Croatia, and -probably- Zeno coming from Italy. It&#8217;s still time to join, don&#8217;t hesitate anymore !!! See you next month for the #4 and in the meantime, happy hacking !!!</p>
]]></content:encoded>
			<wfw:commentRss>http://koha-community.org/koha-release-manager-newsletter-3-2012-01/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Koha Trade Mark Usage Policy</title>
		<link>http://koha-community.org/koha-trade-mark-usage-policy/</link>
		<comments>http://koha-community.org/koha-trade-mark-usage-policy/#comments</comments>
		<pubDate>Thu, 02 Feb 2012 00:22:26 +0000</pubDate>
		<dc:creator>jransom</dc:creator>
				<category><![CDATA[Koha News]]></category>
		<category><![CDATA[Koha]]></category>
		<category><![CDATA[trademark]]></category>

		<guid isPermaLink="false">http://koha-community.org/?p=3124</guid>
		<description><![CDATA[On the 18th January 2012, following consultation with the Koha Subcommittee,  Te Horowhenua Library Trust, trading as Horowhenua Library Trust, adopted the following Koha Trademark Usage Policy:
The Horowhenua Library Trust has been elected by the worldwide online Koha user community to be the custodian of Koha intellectual property including the KOHA name and associated [...]]]></description>
			<content:encoded><![CDATA[<p>On the 18th January 2012, following consultation with the Koha Subcommittee,  Te Horowhenua Library Trust, trading as Horowhenua Library Trust, adopted the following Koha Trademark Usage Policy:</p>
<p>The Horowhenua Library Trust has been elected by the worldwide online Koha user community to be the custodian of Koha intellectual property including the KOHA name and associated logos in any form, font or stylisation, and whether alone or in combination with other words or marks, including [insert the Koha logo].</p>
<p>We at the Horowhenua Library Trust love it when people talk about Koha, build businesses around Koha and produce products that make life better for Koha users and developers. We do, however, have a trademark, which we are obliged to protect. The trademark gives us the exclusive right to use the term to promote websites, services, businesses and products. Although those rights are exclusively ours, we are happy to give people permission to use the term under most circumstances.</p>
<p>The following is a general policy that tells you when you can lawfully refer to the KOHA name and associated logos without need of any specific permission from the Horowhenua Library Trust:</p>
<p>First, you must make clear that you are not Horowhenua Library Trust and that you do not represent [Horowhenua Library Trust] or the Koha user community. A simple disclaimer on your home page is an excellent way of doing that.</p>
<p>Second, you may use the KOHA name and logo only in descriptions of your website, product, business or service to provide accurate information to the public about yourself or your website, product, business or service.</p>
<p>If you would like to use the KOHA name or logo for any other use, please contact us and we’ll discuss a way to make that happen. We don’t have strong objections to people using the name for their websites and businesses, but we do need the chance to review such use.</p>
<p>This trade mark usage policy is intended to be legally binding.</p>
<p>Generally, we will approve your use if you agree to a few things, mainly:<br />
(1) our rights to the KOHA trademark are valid and superior to yours and (2) you’ll take appropriate steps to make sure people don’t confuse you with us or your website, product, business or service with ours. In other words, a short conversation (usually done via email) should clear everything up in short order.<br />
If you currently have a website that is using the KOHA name and you have not gotten permission from us, don’t panic. Let us know, and we’ll work it out, as described above.</p>
]]></content:encoded>
			<wfw:commentRss>http://koha-community.org/koha-trade-mark-usage-policy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Update 2 on NZ Koha Trademark Situation</title>
		<link>http://koha-community.org/update-2-nz-koha-trademark-situation/</link>
		<comments>http://koha-community.org/update-2-nz-koha-trademark-situation/#comments</comments>
		<pubDate>Thu, 02 Feb 2012 00:17:50 +0000</pubDate>
		<dc:creator>jransom</dc:creator>
				<category><![CDATA[Koha News]]></category>
		<category><![CDATA[Koha]]></category>
		<category><![CDATA[ptfs]]></category>
		<category><![CDATA[trademark]]></category>

		<guid isPermaLink="false">http://koha-community.org/?p=3122</guid>
		<description><![CDATA[Well things have been very quiet on this front while the lawyers work through the process.
We are being represented by Andrew Matangi from Buddle Findlay with input from Rochelle Furneaux and feel very confident that he has a good understanding of the Koha journey over the last decade or so and how we have got [...]]]></description>
			<content:encoded><![CDATA[<p>Well things have been very quiet on this front while the lawyers work through the process.</p>
<p>We are being represented by Andrew Matangi from Buddle Findlay with input from Rochelle Furneaux and feel very confident that he has a good understanding of the Koha journey over the last decade or so and how we have got to where we are. He is also a specialist in this area so we have been quite relieved to have his hand on the tiller and plotting the course. These things take time and have to be done discretely of course, but a key date has passed and I think it is okay now to update everyone on progress.</p>
<p>A letter was sent to PTFS on the 19th January essentially outlining the grounds on which our objection to their NZ trademark application is based and asking them to assign their NZ trade mark application to the Trust. We also attached a Koha Trademark Usage Policy which the Library Trust recently adopted, following consultation with the Koha Subcommittee. We advised that unless a response was received by noon NZ time on the 1st of February we would file formal opposition.</p>
<p>Well that date has passed without word and so a formal Notice of Opposition is being prepared. The process from here is set out on the <a href="http://www.iponz.govt.nz/cms/trade-marks/the-trade-mark-process/opposing-registration-of-a-trade-mark">IPONZ website</a>.</p>
<p>So there it is, due process being followed and no resolution in sight but we are still very confident that the right decision will be made.</p>
]]></content:encoded>
			<wfw:commentRss>http://koha-community.org/update-2-nz-koha-trademark-situation/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

