Re: [Koha] 403 After Upgrade (Fwd: [Koha Library Software Community] Comment: Koha 3.2.2 is now available)
I have this problem with koha 3.4. I don't think it's to do with file permissions, but rather apache configuration. Does anyone have an idea how this could be fixed? -- View this message in context: http://koha.1045719.n5.nabble.com/403-After-Upgrade-Fwd-Koha-Library-Software-Community-Comment-Koha-3-2-2-is-now-available-tp3331835p4778098.html Sent from the Koha - Discuss mailing list archive at Nabble.com. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] 403 error with Koha 3.4.4
I've put them in pastebin: Here's httpd.conf: http://pastebin.com/8Wy07Vns It's pretty much unchanged, except for the servername (which I removed from pastebin, but it's set) and the inclusion of the koha-httpd.conf. koha-httpd.conf is here: http://pastebin.com/tQKC0Sfj Apache runs as apache:apache and koha files are owned by koha:users. -- View this message in context: http://koha.1045719.n5.nabble.com/403-error-with-Koha-3-4-4-tp4778142p4778309.html Sent from the Koha - Discuss mailing list archive at Nabble.com. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] OPAC error
Thanks, but either this is not the problem or I don't know how to set the cookie properly. How can I properly check whether the KohaOpacLanguage cookie is set? Thanks, Tom On 09/06/2011 07:49 PM, Robin Sheat wrote: Tom Hanstra schreef op di 06-09-2011 om 15:06 [-0400]: Can someone point me to some clues on what is going on to cause this error? Possibly this: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6205 Check your cookies. -- - Tom Hanstra Systems Administrator Hesburgh Libraries of Notre Dame Phone: (574)631-4686 213 Hesburgh Library Email: t...@nd.edu Notre Dame, IN 46556 Every day, from here to there, funny things are everywhere. Dr. Seuss - ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Checked In Status on Reports
On Thu, Sep 1, 2011 at 8:57 PM, Chris Cormack ch...@bigballofwax.co.nz wrote: SELECT title,author,barcode FROM biblio,items WHERE biblio.biblionumber=items.biblionumber AND items.itype ='you item type goes here' AND (items.onloan is NULL or items.onloan = '') Thats two ' not one :) Or you can do this: SELECT title,author,barcode FROM biblio,items WHERE biblio.biblionumber=items.biblionumber AND items.itype = Item Type|itemtypes AND (items.onloan is NULL or items.onloan = '') So that it asks you for an item type and you don't have to edit again later. Nicole ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] KohaCon 2012 Voting
Kia ora! Apologies to all, I screwed up. I thought voting for KohaCon 2012 started on 1 October. It's meant to close then. That's a big oops. We're hoping that nengard will ride to the rescue and get the survey out and about based on what we did last time for KohaCon 2011. If you don't want to, Nicole, we will figure out a fall back. Humbly, Brooke ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Migration from Heritage to Koha
Dear Koha mailing list members, like anywhere else, from time to time, a success story is greatly welcomed. In the case of our small library, until last month, we were using Heritage[1], a Windows based proprietary ILS. We didn't like it, both for technical reasons and functional reasons. It took the combined efforts of the IT-guy (myself) and the librarian to export the data and process it in a way that was importable in Koha. After a few weeks, overcoming many small and big challenges, we are very happy to introduce our new system to our users, and to this date, no complain at all. If you are interested in the result and the steps of the migration, you can have a look at theses addresses: http://library.stp.dias.ie http://www.stp.dias.ie/library/Heritage2Koha/howto.txt Thanks a lot to the Koha community! Kind regards, Jef [1] http://www.isoxford.com/ -- Jean-Francois Bucas IT System Administrator School of Theoretical Physics Dublin Institute for Advanced Studies 10 Burlington Road Dublin 4 Tel. +353 1 614 0132 ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Migration from Heritage to Koha
Wow, Congratulations, and welcome to Koha. James Ghiorzi Library Assistant II San Benito County Free Library 470 Fifth St. Hollister, CA 95023 From: koha-boun...@lists.katipo.co.nz [koha-boun...@lists.katipo.co.nz] On Behalf Of Jean Francois Bucas [jfbu...@stp.dias.ie] Sent: Wednesday, September 07, 2011 5:01 AM To: koha@lists.katipo.co.nz Subject: [Koha] Migration from Heritage to Koha Dear Koha mailing list members, like anywhere else, from time to time, a success story is greatly welcomed. In the case of our small library, until last month, we were using Heritage[1], a Windows based proprietary ILS. We didn't like it, both for technical reasons and functional reasons. It took the combined efforts of the IT-guy (myself) and the librarian to export the data and process it in a way that was importable in Koha. After a few weeks, overcoming many small and big challenges, we are very happy to introduce our new system to our users, and to this date, no complain at all. If you are interested in the result and the steps of the migration, you can have a look at theses addresses: http://library.stp.dias.ie http://www.stp.dias.ie/library/Heritage2Koha/howto.txt Thanks a lot to the Koha community! Kind regards, Jef [1] http://www.isoxford.com/ -- Jean-Francois Bucas IT System Administrator School of Theoretical Physics Dublin Institute for Advanced Studies 10 Burlington Road Dublin 4 Tel. +353 1 614 0132 ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Migration from Heritage to Koha
Kia ora! Up Baile Átha Cliath! Bail ó Dhia ar an obair. Thanks for the documentation. :D Cheers, Brooke http://library.stp.dias.ie http://www.stp.dias.ie/library/Heritage2Koha/howto.txt Thanks a lot to the Koha community! Kind regards, Jef [1] http://www.isoxford.com/ -- Jean-Francois Bucas IT System Administrator School of Theoretical Physics Dublin Institute for Advanced Studies 10 Burlington Road Dublin 4 Tel. +353 1 614 0132 ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] New to the list-- questions about BISAC
Our library consortium is in the initial stages of moving from Ex Libris to Koha with an entirely new LIS administrator. The administrator we are considering suggested that I join the list as a place to get answers and advice from people who are using a Koha generated LIS.I am a reference librarian assigned the task of coming up with the right questions to ask as we go through the process of setting up the profile of what we want our Koha system to do. The list moderator suggested I introduce myself in my first post. Thanks for your patience. Now for my first question. We have also decided to drop DDC as a classification system and change to a modification of the BISAC (Book Industry Study Group) headings. For example, instead of 579.17 Dunn we will have Medical--Microbiology--Dunn. Does anyone have any experience using BISAC instead of DDC when using Koha? What MARC field(s) did you use for classification? Is there any reason to include the BISAC alpha-numeric code that accompanies each term in the MARC field? (in this example MED 052000). Thanks. Randy Smith Lewiston City Library 208. 743-6519 ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Commentary on Paul's Koha 3.8 Release Manager proposal
Everyone, Enclosed is my response to Paul Poulain's proposal for Koha 3.8 Release Manager. The details of his document can be found here: http://wiki.koha-community.org/wiki/Proposal_paul_p_RM38 I thoroughly agree that the time has come to start thinking beyond the next stable release, and on to Koha 4.0. Those of you who have seen either my presentation at KohaCon 2010's hackfest or KUDOScon 2011 know I'm very excited about the possibilities of where we can take Koha in it's next major iteration. However, I disagree with a couple of the details of Paul's proposal. The major disagreement is with the timeline. The proposal as it stands is to start working on Koha 3.8 and Koha 4.0 in parallel, with Koha 3.8 releasing April 2012, and Koha 4.0 releasing Oct. 2012. I feel that going from Koha 3.8 directly to 4.0 is unwarranted. To my mind, there are many possible releases between 3.8 and 4.0, like 3.10, 3.12, 3.14 and so forth. This is supported by the actual database version numbers in Koha: the current release is actually 3.04.04; the zeros are squashed out for convenience. I would counter that, while we should continue releasing new features every 6 months on the 3.X line, Koha 4.0 should be defined by it's features. Paul's proposal calls several features to be key, including Solr integration, database abstraction, updated online help, improved authentication stack and automated tests. I agree that all these things are important and should be worked towards, but I'm not convinced they should be the sum total of the changes that define Koha 4.0 I would like to see the following in Koha 4.0: - arbitrary metadata formats (beyond MARC) - arbitrary biblio relationships - full support for authority records, including uploading through the GUI, automatic linking, explode searching and more - improvements to the borrower data structure (fewer pre-defined data fields, more flexibility) - separation of receiving and payment in acquisitions - serials import and export (MFHD, prediction patterns, etc) - many, many more things I think that the community should meet and discuss what features are both desirable and reasonably likely to be completed in the next few years (is there interest by libraries to sponsor these developments, or from developers to code it for fun?). Once a feature set is agreed on to define Koha 4.0, the developers of these features would meet to hash out what underlying structural changes would be required to make them happen. Hopefully commonalities could be found, so that the underlying structure could be developed in a way that accommodates multiple developments at once. Identifying these prerequisite changes early on would reduce the difficulties of rebasing developments, since we'd all be working off a similar set of base assumptions. It would also provide a reasonable basis for excluding or delaying developments that don't fit into the overall plan. Once the features were chosen and a framework for their development agreed upon, it would be time to code. The development and submission process would be the same as it is now (basing patches off master and submitting to the patches listserv and Bugzilla). As new features become ready, they would be incorporated into the time-based 3.X releases by the release manager for that particular cycle. This way, what works is made available, and what needs more time continues to be tested until it's stable for production use. Once all the agreed upon features were ready, it would be time to release Koha 4.0. Hopefully, that would be with 1-2 years, but there would be flexibility here. One of my other issues with the proposal was the lightening of Quality Assurance standards for the first 3 months of the 3.8 release cycle. If operating under the 1 year time frame for Koha 4.0 as outlined in Paul's proposal, this would seem necessary in order to get everything included in time. Unfortunately, while the next 3 months would be dedicated to clean up of features rolled in, there is never any guarantee of bug fixes being generated in a timely fashion. You cannot force people to write or sign off on bug fixes; we're all free agents here. So code that has not been rigourously tested could get in and stay in for a long time, long after 4.0 would release, because no one knows how to test it or fix it. However, if we operate under my proposed model, all code could continue to operate under the same quality assurance standards, and nothing that is broken or otherwise incomplete would make it in until it was ready. Releases would still come out every 6 months, even if a major development was inoperable, until that development could be completed. This has been a long email, so let me sum up. I think: - we should continue to release Koha 3.8, 3.10, 3.12 etc on 6 month cycles using the current community practices for feature inclusion - we should, as a community, meet and decide what features we want to
Re: [Koha] Migration from Heritage to Koha
Congratulations and thanks for making your contribution! Lori On Wed, Sep 7, 2011 at 5:01 AM, Jean Francois Bucas jfbu...@stp.dias.iewrote: Dear Koha mailing list members, like anywhere else, from time to time, a success story is greatly welcomed. In the case of our small library, until last month, we were using Heritage[1], a Windows based proprietary ILS. We didn't like it, both for technical reasons and functional reasons. It took the combined efforts of the IT-guy (myself) and the librarian to export the data and process it in a way that was importable in Koha. After a few weeks, overcoming many small and big challenges, we are very happy to introduce our new system to our users, and to this date, no complain at all. If you are interested in the result and the steps of the migration, you can have a look at theses addresses: http://library.stp.dias.ie http://www.stp.dias.ie/library/Heritage2Koha/howto.txt Thanks a lot to the Koha community! Kind regards, Jef [1] http://www.isoxford.com/ -- Jean-Francois Bucas IT System Administrator School of Theoretical Physics Dublin Institute for Advanced Studies 10 Burlington Road Dublin 4 Tel. +353 1 614 0132 ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Migration from Heritage to Koha
Dear Jef, I appreciate your effort behind Koha migration from Heritage. You have customized Koha OPAC well. Can you tell how to: display book covers? display of subject cloud? Regards, -- Vimal Kumar V. Mahatma Gandhi University Library Kottayam, Kerala- 686 560 Web: www.vimalkumar.org Blog: http://linuxhalwa.blogspot.com --- I forget what I was taught. I only remember what I have learnt -Patrick White ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
