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

Re: [Koha-devel] Koha 3.4.1 upgarde - failed: Access denied for user 'kohaadmin'@'localhost' (using password: YES)
by Fridolyn SOMERS 30 May '11

30 May '11

Your welcome. On Mon, May 30, 2011 at 10:56 AM, ISM KIS <Ism(a)kis.in> wrote: > Yes, thanks, got it. > There was a spelling mistake for the password in the .xml > > I guess I installed it too many times. > The remove_items_from_biblioitems.pl is now running. > > Thanks again for pointing me to the right file. > > Rudy Wuthrich > > > >>> Fridolyn SOMERS <fridolyn.somers(a)gmail.com> 5/30/2011 2:04 PM >>> > Hie, > > Database name, host, port, user ... > are stored into Koha main configuration file koha-conf.xml (mostly in > /etc/koha/) > look at the end of the XML. > > On Fri, May 27, 2011 at 11:01 AM, ISM KIS <ism(a)kis.in> wrote: > > > Yes, I can access mysql -u -p -Dkoha > > Where does remove_items_from_biblioitems.pl --run take the username and > > password from? > > > > Rudy > > > > > > >>> Fridolyn SOMERS <fridolyn.somers(a)gmail.com> 5/27/2011 1:55 PM >>> > > Check if kohaadmin can access (via mysql -u -p -D<base name>) the Koha > > database. > > > > Regards, > > > > On Thu, May 26, 2011 at 12:44 PM, ISM KIS <Ism(a)kis.in> wrote: > > > > > I am still in the process of upgrading our Koha from 3.00.06 to 3.4.1 > > > > > > Installation is ok. I could import the data from 3.0.6 and did the > > database > > > update from the :8080 interface. > > > > > > But then when I run the script to remove the biblioitems I get the > > > following error message: > > > > > > koha34:/opt/kohaclone/misc/maintenance # perl > > > remove_items_from_biblioitems.pl --run > > > DBI connect('dbname=koha;host=localhost;port=3306','kohaadmin',...) > > failed: > > > Access denied for user 'kohaadmin'@'localhost' (using password: YES) > at > > > /opt/kohaclone/koha-tmpl/lib/C4/Context.pm line 692 > > > Access denied for user 'kohaadmin'@'localhost' (using password: YES) > at > > > /opt/kohaclone/koha-tmpl/lib/C4/Context.pm line 692. > > > > > > What does that mean? > > > ( By the way: I' m able to access mysql -ukohaadmin -pxxxxx ) > > > > > > Any ideas? > > > > > > Rudy Wuthrich > > > Kodaikanal International School > > > > > > _______________________________________________ > > > Koha-devel mailing list > > > Koha-devel(a)lists.koha-community.org > > > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > > website : http://www.koha-community.org/ > > > git : http://git.koha-community.org/ > > > bugs : http://bugs.koha-community.org/ > > > > > > > > > > > -- > > Fridolyn SOMERS > > ICT engineer > > PROGILONE - Lyon - France > > fridolyn.somers(a)gmail.com > > > > > > > -- > Fridolyn SOMERS > ICT engineer > PROGILONE - Lyon - France > fridolyn.somers(a)gmail.com > > -- Fridolyn SOMERS ICT engineer PROGILONE - Lyon - France fridolyn.somers(a)gmail.com

1 0

Re: [Koha-devel] Koha 3.4.1 upgarde - failed: Access denied for user 'kohaadmin'@'localhost' (using password: YES)
by Fridolyn SOMERS 30 May '11

30 May '11

Hie, Database name, host, port, user ... are stored into Koha main configuration file koha-conf.xml (mostly in /etc/koha/) look at the end of the XML. On Fri, May 27, 2011 at 11:01 AM, ISM KIS <ism(a)kis.in> wrote: > Yes, I can access mysql -u -p -Dkoha > Where does remove_items_from_biblioitems.pl --run take the username and > password from? > > Rudy > > > >>> Fridolyn SOMERS <fridolyn.somers(a)gmail.com> 5/27/2011 1:55 PM >>> > Check if kohaadmin can access (via mysql -u -p -D<base name>) the Koha > database. > > Regards, > > On Thu, May 26, 2011 at 12:44 PM, ISM KIS <Ism(a)kis.in> wrote: > > > I am still in the process of upgrading our Koha from 3.00.06 to 3.4.1 > > > > Installation is ok. I could import the data from 3.0.6 and did the > database > > update from the :8080 interface. > > > > But then when I run the script to remove the biblioitems I get the > > following error message: > > > > koha34:/opt/kohaclone/misc/maintenance # perl > > remove_items_from_biblioitems.pl --run > > DBI connect('dbname=koha;host=localhost;port=3306','kohaadmin',...) > failed: > > Access denied for user 'kohaadmin'@'localhost' (using password: YES) at > > /opt/kohaclone/koha-tmpl/lib/C4/Context.pm line 692 > > Access denied for user 'kohaadmin'@'localhost' (using password: YES) at > > /opt/kohaclone/koha-tmpl/lib/C4/Context.pm line 692. > > > > What does that mean? > > ( By the way: I' m able to access mysql -ukohaadmin -pxxxxx ) > > > > Any ideas? > > > > Rudy Wuthrich > > Kodaikanal International School > > > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel(a)lists.koha-community.org > > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : http://www.koha-community.org/ > > git : http://git.koha-community.org/ > > bugs : http://bugs.koha-community.org/ > > > > > > -- > Fridolyn SOMERS > ICT engineer > PROGILONE - Lyon - France > fridolyn.somers(a)gmail.com > > -- Fridolyn SOMERS ICT engineer PROGILONE - Lyon - France fridolyn.somers(a)gmail.com

1 0

How to gather better popularity data?
by MJ Ray 27 May '11

27 May '11

We're often asked for better data on who is using Koha. For full disclosure listings, there are good places (like wiki.koha-community.org, when account registration works again) and so-so places (like libwebcats with its incomplete representation of library-support relationships and potential for helping Social Engineering attacks), but what about collecting basic usage data? A side-effect of the use of debian packages is that koha appears on http://popcon.debian.org/ (14 installations) and http://popcon.ubuntu.com/ (3 installations). Do other distributions have similar things? Have many koha package users installed and activated the popularity-contest package? Can we get more data consensually? How should we do this? A question in the web installer/upgrader? Plus a weekly heartbeat cronjob? What data should we ask for? Can we leave it up to libraries how anonymous they will be? Basic return is "Koha in use" with some generated unique identifier, semi-anonymous response adds which country they are in and how many branches they have, full response includes catalogue name? I assume this can go in 3.6. Would the 3.4 RM accept it? Thanks for any feedback, -- 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

9 16

FW: Code simplicity document
by Marcel de Rooy 27 May '11

27 May '11

Liked that article! As relative new member of the community, I am wondering if the current signoff/passed_qa procedure really encourages new members to keep sending patches. It could happen easily now that a patch does not get any attention. What makes someone now select a patch for signoff? Coincidence, contacts, application feature? imo we need some more structure at the signoff side. We have the Bugzilla categories that define the default assignment for a new bug. Would it be useful to assign a default signer per category too? Such assignments could be evaluated regularly to see if they still work. Marcel ________________________________________ Van: koha-devel-bounces(a)lists.koha-community.org [koha-devel-bounces(a)lists.koha-community.org] namens Paul Poulain [paul.poulain(a)biblibre.com] Verzonden: maandag 9 mei 2011 15:46 Aan: koha-devel(a)lists.koha-community.org Onderwerp: [Koha-devel] Document to read Hello, chris gave this url on IRC, I think it's worth sharing : http://www.codesimplicity.com/post/open-source-community-simplified/ it's a great document. I think it's worth asking ourself : "what are we doing well, what could we improve" This question is specifically sent to new contributors: what did we well, what could be improve for new/future newbies ? -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/

7 7

Access 2011: Registration is now open
by Shirley Lew 27 May '11

27 May '11

Registration is now open for the *Access 2011 Conference*, to be held October 19-22 in Vancouver, British Columbia. See http://access2011.library.ubc.ca/registration/ for more details. Some other goodies now available on the conference website include a preliminary schedule, information on the preconference event "Open Source for Library Decision Makers," information on social events, and a link to the Hyatt's room reservation form. We're also accepting suggestions for the Hackfest (http://access2011.library.ubc.ca/hackfest/) The organizing committee gratefully acknowledges the following sponsors for their kind support (in alphabetical order): GOLD: Canadiana.org, Gibson Library Connections, Serials Solutions, Simon Fraser University Library, University of British Columbia, University of Victoria SILVER: Discovery Garden, Equinox Software, OCLC Digital Collection Services BRONZE: Andornot Consulting, BC Electronic Library Network, BC Libraries Cooperative, Dell Canada, Innovative Interfaces, Microcom, Relais International, Richmond Public Library, Vancouver Community College. On behalf of the organizing committee, Shirley Shirley Lew Coordinator, Library Systems Vancouver Community College 250 West Pender, Vancouver, BC, V6B 1S9 604.443.8519 | slew(a)vcc.ca

1 0

Coming to ALA? Join the social gathering! See attached flyer
by David Schuster 26 May '11

26 May '11

Saturday evening June 25th 8-11 - rsvp requested to terlaga(a)biblio.org -- David Schuster Plano ISD Library Technology Coordinator

1 0

patches with DB change, workflow
by Paul Poulain 26 May '11

26 May '11

Hi all, I think there are some things unclear (at least for me ;-) ) about submitting bugs with DB changes. We said various things, I don't know which one is the correct one. * http://wiki.koha-community.org/wiki/Tutorial_for_Updating_Database_Files is the wiki page about this * we spoke of using XXXX in updatedatabase.pl to have te RM pick the right number when needed. * We also spoke of using atomicupdate, and let the RM append to updatedatabase when applying to master. What I see is that updatedatabase.pl changes a lot, making patches including them "does not apply" quite quickly. I'm wondering if it would not be easier to have "atomicupdate" and kohastructure.sql, the RM moving from atomicupdate to updatedatabase when applying. I think it would be easier to sign-off -just run atomicupdate attached to the bug- too. I already have encountered the problem twice today (I work on bugzilla). Your opinion ? -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

6 8

Re: [Koha-devel] Z39.50 server authentication
by Fridolyn SOMERS 25 May '11

25 May '11

No, you can keep it, default Koha configuration seems good in zebra-biblios.cfg : perm.anonymous:ar > perm.__ZEBRA_USER__:rw > The anonymous user has only read perm. By the way, I think your conf is not correct : > <listen id="publicserver" >tcp:@:9999</listen> > And change this line: > <server id="biblioserver" listenref="biblioserver"> > to > <server id="biblioserver"> > I think you should set the listen ref on "pulicserver" : <listen id="publicserver" >tcp:@:9999</listen> <server id="biblioserver" listenref="publicserver"> Regards, On Wed, May 25, 2011 at 12:25 PM, Altaf Mahmud <altaf.mahmud(a)gmail.com>wrote: > I mean, do I need to comment out 'perm.anonymous' in zebra-biblios.cfg file > at /etc/koha/zebradb/ directory as LAURENT suggested? > > > On Wed, May 25, 2011 at 4:23 PM, Altaf Mahmud <altaf.mahmud(a)gmail.com>wrote: > >> Hi Fridolyn, In that case do I need to comment out zebra-biblios.cfg file >> in /etc/koha/zebradb/ directory? I just added this tag in koha-conf.xml file >> but it's not working. >> >> Thanks. >> >> >> On Wed, May 25, 2011 at 2:07 PM, Fridolyn SOMERS < >> fridolyn.somers(a)gmail.com> wrote: >> >>> Hie, >>> >>> In our configuration, authentification is managed by "serverinfo" tag in >>> koha-conf.xml : >>> >>> <serverinfo id="publicserver"> >>> <ccl2rpn>/etc/koha/zebradb/ccl.properties</ccl2rpn> >>> <user>username</user> >>> <password>userpassword</password> >>> </serverinfo> >>> >>> Regards, >>> >>> 2011/5/24 Altaf Mahmud <altaf.mahmud(a)gmail.com> >>> >>>> Dear community, >>>> >>>> I've enabled the Z39.50 server in my Koha server following these steps: >>>> >>>> 1. Edited /etc/koha/koha-conf.xml file and uncommented the publicserver >>>> line: >>>> <listen id="publicserver" >tcp:@:9999</listen> >>>> And change this line: >>>> <server id="biblioserver" listenref="biblioserver"> >>>> to >>>> <server id="biblioserver"> >>>> It forces Zebra to listen on unix socket (for Koha) and on TCP port >>>> 9999 (for external usage). >>>> >>>> 2. Restarted Zebra server. >>>> >>>> MARC data can now accessed from my z39.50 server. Now I want to >>>> implement the authentication process so that user id and login required to >>>> connect to my server. I don't know how to do it, could you please give me an >>>> advise? >>>> >>>> Thank you. >>>> >>>> >>>> -- >>>> Altaf Mahmud >>>> System Programmer >>>> Ayesha Abed Library >>>> BRAC University >>>> Bangladesh. >>>> >>>> >>>> _______________________________________________ >>>> Koha-devel mailing list >>>> Koha-devel(a)lists.koha-community.org >>>> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel >>>> website : http://www.koha-community.org/ >>>> git : http://git.koha-community.org/ >>>> bugs : http://bugs.koha-community.org/ >>>> >>> >>> >>> >>> -- >>> Fridolyn SOMERS >>> ICT engineer >>> PROGILONE - Lyon - France >>> fridolyn.somers(a)gmail.com >>> >> >> >> >> -- >> Altaf Mahmud >> System Programmer >> Ayesha Abed Library >> BRAC University >> Bangladesh. >> >> > > > -- > Altaf Mahmud > System Programmer > Ayesha Abed Library > BRAC University > Bangladesh. > > -- Fridolyn SOMERS ICT engineer PROGILONE - Lyon - France fridolyn.somers(a)gmail.com

2 1

Official Koha Newsletter: Volume 2, Issue 5: May 2011
by Nicole Engard 25 May '11

25 May '11

Below is the text of the newsletter, for active links please visit the Koha site: http://koha-community.org/koha-newsletter-volume-2issue-5-may-2011/ Official Koha Newsletter (ISSN 2153-8328) Volume 2, Issue 5: May 2011 Table of Contents Koha Developments Koha 3.2.9 Available Koha 3.4.1 Available Koha Community Farmington Sponsors Facebook/Twitter Share Development Standards Organisation of Nigeria implements Koha supported by Projektlink Konsult Ltd. University of Guyana Chooses Koha Koha Tips & Tricks Increase Koha Performance Configure Automatic Receipt Printing Koha Developments Koha 3.2.9 Available by Chris Nighswonger The package can be retrieved from: http://download.koha-community.org/koha-3.02.09.tar.gz You can use the following checksum and signature files to verify the download: http://download.koha-community.org/koha-3.02.09.tar.gz.MD5 http://download.koha-community.org/koha-3.02.09.tar.gz.MD5.asc http://download.koha-community.org/koha-3.02.09.tar.gz.sig Come and get it, quick! Read More Koha 3.4.1 Available by Chris Nighswonger It is with pleasure that I announce the release of Koha 3.4.1. The package can be retrieved from: http://download.koha-community.org/koha-3.04.01.tar.gz You can use the following checksum and signature files to verify the download: http://download.koha-community.org/koha-3.04.01.tar.gz.MD5 http://download.koha-community.org/koha-3.04.01.tar.gz.MD5.asc http://download.koha-community.org/koha-3.04.01.tar.gz.sig Come and get it! Read More Koha Community Farmington Sponsors Facebook/Twitter Share Development by Hall Bright ByWater Solutions has provided a Facebook and Twitter application for the Farmington Libraries to allow patrons to tweet and facebook what they are reading. When you go into the details VIEW of an item, the patron sees the Facebook and Twitter icons on the right menu where a Hold is placed. See: http://catalog.farmingtonlibraries.org/cgi-bin/koha/opac-detail.pl?biblionu… By clicking the Facebook “Like” button, a patron is prompted to log in to Facebook. Then, a patron can write commentary or such and the commentary and the title [with a link to the catalog] appears on their Wall. The library’s address also appears. The Twitter “Tweet” button also prompts a log in screen and then brings up a customizable message with an automatically generated TinyURL type link back to the catalog. We are still in testing, but we are excited for this customization. Standards Organisation of Nigeria implements Koha supported by Projektlink Konsult Ltd. by Olugbenga Adara The Standards Organisation of Nigeria (SON) Library, established in 1971, has adopted Koha for managing it’s library collections. The SON library has the responsibility to assemble and maintain a collection of standards, normative documents, books and other relevant materials it considers appropriate and relevant for a standards management in Nigeria. The implementation was carried out in conjunction with Projectlink Konsult Limited (PKL) Full details can be found online. University of Guyana Chooses Koha by Sekhar Mallampati University of Guyana (uog.edu.gy), Berbice Campus (South America) has launched it’s Library Automation System Koha on 12th May, 2011. The collection size is around 13000. We are also working on implementing Koha for University’s main campus (Turkeyen) Library which has a collection size of 140000. This is first of it’s kind in the country (Guyana). University of Guyana is the first one to implement this world’s leading Open Source Library Software (Koha) in the Caribbean. We have started helping the National Library of Guyana to start their journey with Koha. University of Guyana, Berbice Campus Library’s “Online Public Access Catalog (OPAC)” service can be accessed at: http://ugbclibrary.uog.edu.gy Dept. of Software Services has provided technical support for University of Guyana automation project. I am a software engineer and HOD for Dept. of Software Services, University of Guyana. We want to thank you all for this feature-rich product. We have been benefiting from the mailing lists, etc. Koha Tips & Tricks Increase Koha Performance by Fridolyn SOMERS Here is a little technical trick : In koha-conf.xml, the address of the database server is stored : <hostname>__DB_HOST__</hostname> If you use its host name (mysql.mydomaine.com for example), the DNS will be used for each database connection. Using the IP address will pass-by DNS and may increase a little bit the Koha server performance. Configure Automatic Receipt Printing by Koha Community Did you know that you can set Koha to automatically print receipts for circulation? There is a guide on the wiki that will walk you through the process with different printers and browsers. Learn more on the Koha wiki. Newsletter edited by Nicole C. Engard, Koha Documentation Manager. Please send future story ideas to me.

1 0

Z39.50 server authentication
by Altaf Mahmud 25 May '11

25 May '11

Dear community, I've enabled the Z39.50 server in my Koha server following these steps: 1. Edited /etc/koha/koha-conf.xml file and uncommented the publicserver line: <listen id="publicserver" >tcp:@:9999</listen> And change this line: <server id="biblioserver" listenref="biblioserver"> to <server id="biblioserver"> It forces Zebra to listen on unix socket (for Koha) and on TCP port 9999 (for external usage). 2. Restarted Zebra server. MARC data can now accessed from my z39.50 server. Now I want to implement the authentication process so that user id and login required to connect to my server. I don't know how to do it, could you please give me an advise? Thank you. -- Altaf Mahmud System Programmer Ayesha Abed Library BRAC University Bangladesh.

2 1