<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
hi every one <br>please i need documentation about koha 3 install on centos 5<br><br>> From: koha-request@lists.katipo.co.nz<br>> Subject: Koha Digest, Vol 48, Issue 72<br>> To: koha@lists.katipo.co.nz<br>> Date: Fri, 23 Oct 2009 08:18:05 +1300<br>> <br>> Send Koha mailing list submissions to<br>>         koha@lists.katipo.co.nz<br>> <br>> To subscribe or unsubscribe via the World Wide Web, visit<br>>         http://lists.katipo.co.nz/mailman/listinfo/koha<br>> or, via email, send a message with subject or body 'help' to<br>>         koha-request@lists.katipo.co.nz<br>> <br>> You can reach the person managing the list at<br>>         koha-owner@lists.katipo.co.nz<br>> <br>> When replying, please edit your Subject line so it is more specific<br>> than "Re: Contents of Koha digest..."<br>> <br>> <br>> Today's Topics:<br>> <br>> 1. Re: Liblime, Koha, BibLibre and FLOSS (Chris Cormack)<br>> 2. Re: Emailed Overdue Notices (Agnes Rivers-Moore)<br>> 3. Re: Add&Dublicate,Add Multiple Copies (nengard@gmail.com)<br>> 4. Re: Invalid Login on SIP2 Server... why? (ankita)<br>> 5. Again: delete MARC records (stefan)<br>> 6. Re: Emailed Overdue Notices (Susan Bennett)<br>> 7. Re: Emailed Overdue Notices (Josh Westbrook)<br>> <br>> <br>> ----------------------------------------------------------------------<br>> <br>> Message: 1<br>> Date: Fri, 23 Oct 2009 07:38:11 +1300<br>> From: Chris Cormack <chris@bigballofwax.co.nz><br>> Subject: Re: [Koha] Liblime, Koha, BibLibre and FLOSS<br>> To: MJ Ray <mjr@phonecoop.coop><br>> Cc: Koha@lists.katipo.co.nz<br>> Message-ID:<br>>         <606aab810910221138o2064a33cj784bb40c7f337cb8@mail.gmail.com><br>> Content-Type: text/plain; charset=ISO-8859-1<br>> <br>> 2009/10/23 MJ Ray <mjr@phonecoop.coop>:<br>> > Nicolas Morin <nicolas.morin@biblibre.com><br>> >> [...] we at BibLibre<br>> >> posted an article on our web site about this issue:<br>> >> http://www.biblibre.com/content/liblime-koha-biblibre-and-floss<br>> ><br>> > Amongst other things, that says:<br>> ><br>> > ?"BibLibre decided we needed to modify our standard hosting contract<br>> > ?to close the GPL loophole used by LibLime: in our future contracts,<br>> > ?and when the current contracts are renewed, an extra article is<br>> > ?added to the contract which specifies that even though the software<br>> > ?is hosted, the library has access to the source code, GPLed."<br>> ><br>> > I'm surprised because software.coop's usual contract terms have said<br>> > that we "grant permission to the Buyer to use, copy, modify, adapt or<br>> > enhance the material supplied in the performance of the Services, so<br>> > far as [the co-op] is permitted to grant that permission" since at<br>> > least 2006 and probably before (I'd need to check paper files to be<br>> > sure).<br>> ><br>> > For Koha, that means you get a copy under the GPL, basically.<br>> ><br>> > What with all the flaming of LibLime for hosting lock-in, I didn't<br>> > expect that other Koha vendors weren't making at least that promise<br>> > already. ?So - would the other vendors like to state their current<br>> > contract permissions? ?Anyone else want to follow the co-op and<br>> > BibLibre and make this promise to your buyers?<br>> ><br>> > Also, I'd like to know whether anyone else's hosting-source-access<br>> > clause forbids evil tricks like public key encryption? ?Offering<br>> > access alone isn't sufficient. ?Also, what about the data?<br>> ><br>> As far as Im aware Liblime is the only vendor in the history of Koha,<br>> certainly the only vendor listed on the Koha support page, to refuse<br>> to give the source code, and database access to their customers.<br>> For me thats where the flames are coming from.<br>> I will find out what the Catalyst contracts say, but we don't have and<br>> Software as a Service Koha clients, they are all self hosted. But I<br>> will look just for curiosity sake.<br>> <br>> Chris<br>> <br>> <br>> ------------------------------<br>> <br>> Message: 2<br>> Date: Thu, 22 Oct 2009 14:49:34 -0400<br>> From: Agnes Rivers-Moore <arm@hanover.ca><br>> Subject: Re: [Koha] Emailed Overdue Notices<br>> To: Josh Westbrook <joshw@wwrurallibrary.com><br>> Cc: Koha List <koha@lists.katipo.co.nz><br>> Message-ID: <4AE0A93E.6060200@hanover.ca><br>> Content-Type: text/plain; charset=UTF-8; format=flowed<br>> <br>> Hi Josh<br>> <br>> Library email addresses are set in two places. One in Admin which is <br>> specifically for patron update requests, and the other in Libraries, <br>> Branches & Groups, for other messages especially overdue notices. You <br>> may of course set both to be the same address.<br>> <br>> As you say, the addresses set for the branches receive a huge email <br>> including a concatenation of all the notices that could not be sent <br>> because Koha had no email in the patron's account. I have a single <br>> library site so I am not certain how Koha chooses which email to send <br>> the notice to if, say, the patron belongs to one branch and the book <br>> belongs to another.<br>> <br>> HTH<br>> Agnes<br>> <br>> <br>> Josh Westbrook wrote:<br>> > Reading the Koha documentation, it looked like there was one email<br>> > address that all overdue notices would go to if the patron did not<br>> > have an email address in their account.<br>> ><br>> > But It looks like when a patron makes changes to their account in the<br>> > OPAC an email is sent to the email address that is associated with<br>> > their "Home Library" in the "Libraries and Groups" parameters about<br>> > the changes. Is this the way Overdue Notices for patrons without<br>> > email addresses work also? Is an email sent to the home library's<br>> > email address with all of the overdue notices for patrons<br>> > at_that_branch without an email address?<br>> ><br>> > Our Koha system isn't live yet to test this - any feedback would be appreciated!<br>> ><br>> ><br>> > Josh Westbrook<br>> > Prescott Library Mngr/District Technology Mngr<br>> > Walla Walla County Rural Library District<br>> > joshw@wwrurallibrary.com<br>> > http://www.wwrurallibrary.com<br>> > _______________________________________________<br>> > Koha mailing list<br>> > Koha@lists.katipo.co.nz<br>> > http://lists.katipo.co.nz/mailman/listinfo/koha<br>> ><br>> > <br>> <br>> -- <br>> <br>> Agnes Rivers-Moore<br>> Assistant Librarian<br>> Hanover Public Library<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 3<br>> Date: Thu, 22 Oct 2009 11:57:03 +0000<br>> From: nengard@gmail.com<br>> Subject: Re: [Koha] Add&Dublicate,Add Multiple Copies<br>> To: "Twinamatsiko matsiko Smith" <twimithee@gmail.com>,<br>>         koha-bounces@lists.katipo.co.nz, "koha" <koha@lists.katipo.co.nz>,<br>>         "Nicole Engard" <nicole.engard@liblime.com><br>> Message-ID:<br>>         <1123442022-1256212655-cardhu_decombobulator_blackberry.rim.net-647826045-@bda876.bisx.prod.on.blackberry><br>>         <br>> Content-Type: text/plain<br>> <br>> That is the manual for 3.2 so if need that feature you can get it from git or wait for 3.2.<br>> <br>> Sorry to not be of more help.<br>> <br>> Nicole <br>> ------Original Message------<br>> From: Twinamatsiko matsiko Smith<br>> Sender: koha-bounces@lists.katipo.co.nz<br>> To: koha<br>> To: Nicole Engard<br>> Subject: [Koha] Add&Dublicate,Add Multiple Copies<br>> Sent: Oct 22, 2009 7:49 AM<br>> <br>> Hello colleagues,<br>> Iam running koha 3.0.3 on a debian box but its short of:-<br>> "Add&Dublicate" and "Add Multiple Copies" "Number of copies to add" as<br>> per the documentation;<br>> <br>> http://koha.org/documentation/manual/3.2/cataloging/adding-and-deleting-items<br>> <br>> Meanwhile, its a very big requirement esp when adding lot of copies.....<br>> <br>> Have your say<br>> Thanx<br>> <br>> <br>> -- <br>> ..............<br>> Smith Matsiko<br>> Database Administrator<br>> Mob:071525507<br>> Sparklink Systems Ltd<br>> Bg Road,Plot 42<br>> _______________________________________________<br>> Koha mailing list<br>> Koha@lists.katipo.co.nz<br>> http://lists.katipo.co.nz/mailman/listinfo/koha<br>> <br>> <br>> Sent from my Verizon Wireless BlackBerry<br>> <br>> ------------------------------<br>> <br>> Message: 4<br>> Date: Thu, 22 Oct 2009 04:58:40 -0700 (PDT)<br>> From: ankita <amruta.arti@gmail.com><br>> Subject: Re: [Koha] Invalid Login on SIP2 Server... why?<br>> To: koha@lists.katipo.co.nz<br>> Message-ID: <26008694.post@talk.nabble.com><br>> Content-Type: text/plain; charset=us-ascii<br>> <br>> <br>> <br>> ankita wrote:<br>> > <br>> > hello,<br>> > i am install koha successfully on linux but i got an error when configure<br>> > sip2 sever.<br>> > Error like this...Can't locate UNIVERSAL/require.pm in @INC (@INC<br>> > contains: ./ /usr/share/koha/lib /etc/perl /usr/local/lib/perl/5.10.0<br>> > /usr/local/share/perl/5.10.0 /usr/lib/perl5 /usr/share/perl5<br>> > /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl .) at<br>> > /usr/share/koha/lib/C4/SIP/SIPServer.pm line 11.<br>> > but i already install UNIVERSAL/require.pm module<br>> > <br>> > when i comment UNIVERSAL/require.pm in<br>> > /usr/share/koha/lib/C4/SIP/SIPServer.pm then is successfully configure and<br>> > telnet connection. <br>> > <br>> > after connection when set login and password to get invalid password<br>> > administrator@administrator-desktop:/usr/share/koha/lib/C4/SIP$ telnet<br>> > localhost 8023<br>> > Trying ::1...<br>> > Trying 127.0.0.1...<br>> > Connected to localhost.<br>> > Escape character is '^]'.<br>> > login: koha<br>> > password: koha<br>> > Invalid login<br>> > login: koha<br>> > password: koha<br>> > Invalid login<br>> > login: koha<br>> > password: koha<br>> > Invalid login<br>> > Login OK. Initiating SIP<br>> > <br>> > means 3rd time login ok<br>> > <br>> > please Help me.<br>> > <br>> > thank u!<br>> > <br>> > <br>> <br>> -- <br>> View this message in context: http://www.nabble.com/Invalid-Login-on-SIP2-Server...-why--tp21951242p26008694.html<br>> Sent from the Koha - Discuss mailing list archive at Nabble.com.<br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 5<br>> Date: Thu, 22 Oct 2009 21:02:30 +0200<br>> From: stefan <herrkandera@gmx.ch><br>> Subject: [Koha] Again: delete MARC records<br>> To: koha@lists.katipo.co.nz<br>> Message-ID: <4AE0AC46.4050500@gmx.ch><br>> Content-Type: text/plain; charset=ISO-8859-15; format=flowed<br>> <br>> Dear List,<br>> <br>> I've imported different .mrc files using the graphical interface of Koha <br>> and was able to delete them with the "undo import" button in "staged <br>> records".<br>> Without manipulation of the source the "undo import" button desapeard. <br>> So I tried:<br>> <br>> bulkmarcimport.pl -d -file zm42a_1995_2000.mrc<br>> <br>> Now the extranet OPAC is down, giving the error:<br>> <br>> Can't call method "leader" on an undefined value at <br>> /usr/share/koha/lib/C4/Biblio.pm line 1051.<br>> <br>> In the Intranet OPAC the search results the records still apeare. When I <br>> click on a bib record I get following error:<br>> <br>> Can't call method "fields" on an undefined value at <br>> /usr/share/koha/intranet/cgi-bin/catalogue/MARCdetail.pl line 124.<br>> <br>> I ran rebuild_zebra.pl without success.<br>> <br>> Can you tell me a method how to delete MARC records/items permanetely <br>> and savely?<br>> <br>> Thank you.<br>> <br>> Stefan<br>> <br>> Specs:<br>> <br>> Koha 3.01.00.052<br>> Debian Lenny minimal<br>> MySQL and Apache up to date<br>> <br>> P.S. The Zebra features are just glorious! <br>> <br>> <br>> <br>> ------------------------------<br>> <br>> Message: 6<br>> Date: Thu, 22 Oct 2009 15:13:11 -0400<br>> From: Susan Bennett <susan.bennett@geaugalibrary.info><br>> Subject: Re: [Koha] Emailed Overdue Notices<br>> To: Agnes Rivers-Moore <arm@hanover.ca><br>> Cc: Koha List <koha@lists.katipo.co.nz>,        Josh Westbrook<br>>         <joshw@wwrurallibrary.com><br>> Message-ID:<br>>         <f00af31b0910221213ia5c6656sd352a4749d625f7a@mail.gmail.com><br>> Content-Type: text/plain; charset="iso-8859-1"<br>> <br>> My understanding, and how it seems to be working here, is that the emails<br>> come from the library were the items checked out.<br>> One side effect of this is if the patron checks out items at two libraries<br>> on the same day and they are late enough to get overdue notices for both,<br>> they will get 2 notices, one from each library. Both notices listing all the<br>> items meeting the requirements for the overdue notices.<br>> <br>> Susan Bennett<br>> ILS System Administrator<br>> Geauga County Public Library<br>> 440 286-6811 x 125<br>> 440 286-7419 FAX<br>> <br>> <br>> On Thu, Oct 22, 2009 at 2:49 PM, Agnes Rivers-Moore <arm@hanover.ca> wrote:<br>> <br>> > Hi Josh<br>> ><br>> > Library email addresses are set in two places. One in Admin which is<br>> > specifically for patron update requests, and the other in Libraries,<br>> > Branches & Groups, for other messages especially overdue notices. You<br>> > may of course set both to be the same address.<br>> ><br>> > As you say, the addresses set for the branches receive a huge email<br>> > including a concatenation of all the notices that could not be sent<br>> > because Koha had no email in the patron's account. I have a single<br>> > library site so I am not certain how Koha chooses which email to send<br>> > the notice to if, say, the patron belongs to one branch and the book<br>> > belongs to another.<br>> ><br>> > HTH<br>> > Agnes<br>> ><br>> ><br>> > Josh Westbrook wrote:<br>> > > Reading the Koha documentation, it looked like there was one email<br>> > > address that all overdue notices would go to if the patron did not<br>> > > have an email address in their account.<br>> > ><br>> > > But It looks like when a patron makes changes to their account in the<br>> > > OPAC an email is sent to the email address that is associated with<br>> > > their "Home Library" in the "Libraries and Groups" parameters about<br>> > > the changes. Is this the way Overdue Notices for patrons without<br>> > > email addresses work also? Is an email sent to the home library's<br>> > > email address with all of the overdue notices for patrons<br>> > > at_that_branch without an email address?<br>> > ><br>> > > Our Koha system isn't live yet to test this - any feedback would be<br>> > appreciated!<br>> > ><br>> > ><br>> > > Josh Westbrook<br>> > > Prescott Library Mngr/District Technology Mngr<br>> > > Walla Walla County Rural Library District<br>> > > joshw@wwrurallibrary.com<br>> > > http://www.wwrurallibrary.com<br>> > > _______________________________________________<br>> > > Koha mailing list<br>> > > Koha@lists.katipo.co.nz<br>> > > http://lists.katipo.co.nz/mailman/listinfo/koha<br>> > ><br>> > ><br>> ><br>> > --<br>> ><br>> > Agnes Rivers-Moore<br>> > Assistant Librarian<br>> > Hanover Public Library<br>> ><br>> > _______________________________________________<br>> > Koha mailing list<br>> > Koha@lists.katipo.co.nz<br>> > http://lists.katipo.co.nz/mailman/listinfo/koha<br>> ><br>> -------------- next part --------------<br>> An HTML attachment was scrubbed...<br>> URL: http://lists.katipo.co.nz/pipermail/koha/attachments/20091022/99c5d667/attachment-0001.htm <br>> <br>> ------------------------------<br>> <br>> Message: 7<br>> Date: Thu, 22 Oct 2009 12:17:57 -0700<br>> From: Josh Westbrook <joshw@wwrurallibrary.com><br>> Subject: Re: [Koha] Emailed Overdue Notices<br>> To: Agnes Rivers-Moore <arm@hanover.ca>,<br>>         susan.bennett@geaugalibrary.info<br>> Cc: Koha List <koha@lists.katipo.co.nz><br>> Message-ID:<br>>         <d5f920d0910221217w69582c06y65155ec7c70c9b09@mail.gmail.com><br>> Content-Type: text/plain; charset=ISO-8859-1<br>> <br>> Thanks Agnes and Susan - I had some of this confirmed through other<br>> channels as well.<br>> <br>> I was hoping that the notice would be attached to the library where<br>> the item checked out - so that is good to hear. We do have patrons<br>> that go between the seven libraries in our consortium - but usually<br>> not on the same day (to my knowledge) so that shouldn't be a problem!<br>> <br>> It's nice to hear that most of my assumptions of how the system works<br>> are actually how it works - that wasn't the way it worked with our<br>> Voyager system at all ...<br>> <br>> Josh Westbrook<br>> Prescott Library Mngr/District Technology Mngr<br>> Walla Walla County Rural Library District<br>> joshw@wwrurallibrary.com<br>> http://www.wwrurallibrary.com<br>> <br>> <br>> <br>> On Thu, Oct 22, 2009 at 11:49 AM, Agnes Rivers-Moore <arm@hanover.ca> wrote:<br>> > Hi Josh<br>> ><br>> > Library email addresses are set in two places. One in Admin which is<br>> > specifically for patron update requests, and the other in Libraries,<br>> > Branches & Groups, for other messages especially overdue notices. You may of<br>> > course set both to be the same address.<br>> ><br>> > As you say, the addresses set for the branches receive a huge email<br>> > including a concatenation of all the notices that could not be sent because<br>> > Koha had no email in the patron's account. I have a single library site so I<br>> > am not certain how Koha chooses which email to send the notice to if, say,<br>> > the patron belongs to one branch and the book belongs to another.<br>> ><br>> > HTH<br>> > Agnes<br>> ><br>> ><br>> > Josh Westbrook wrote:<br>> >><br>> >> Reading the Koha documentation, it looked like there was one email<br>> >> address that all overdue notices would go to if the patron did not<br>> >> have an email address in their account.<br>> >><br>> >> But It looks like when a patron makes changes to their account in the<br>> >> OPAC an email is sent to the email address that is associated with<br>> >> their "Home Library" in the "Libraries and Groups" parameters about<br>> >> the changes. ?Is this the way Overdue Notices for patrons without<br>> >> email addresses work also? ?Is an email sent to the home library's<br>> >> email address with all of the overdue notices for patrons<br>> >> at_that_branch without an email address?<br>> >><br>> >> Our Koha system isn't live yet to test this - any feedback would be<br>> >> appreciated!<br>> >><br>> >><br>> >> Josh Westbrook<br>> >> Prescott Library Mngr/District Technology Mngr<br>> >> Walla Walla County Rural Library District<br>> >> joshw@wwrurallibrary.com<br>> >> http://www.wwrurallibrary.com<br>> >> _______________________________________________<br>> >> Koha mailing list<br>> >> Koha@lists.katipo.co.nz<br>> >> http://lists.katipo.co.nz/mailman/listinfo/koha<br>> >><br>> >><br>> ><br>> > --<br>> ><br>> > Agnes Rivers-Moore<br>> > Assistant Librarian<br>> > Hanover Public Library<br>> ><br>> ><br>> <br>> <br>> ------------------------------<br>> <br>> _______________________________________________<br>> Koha mailing list<br>> Koha@lists.katipo.co.nz<br>> http://lists.katipo.co.nz/mailman/listinfo/koha<br>> <br>> <br>> End of Koha Digest, Vol 48, Issue 72<br>> ************************************<br>                                            <br /><hr />Windows Live: Keep your friends up to date <a href='http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_1:092010' target='_new'>with what you do online.</a></body>
</html>