- Koha - lists.katipo.co.nz

Re: [Koha] Koha trademarks
by COURYHOUSE＠aol.com 10 May '09

10 May '09

sounds like crap to me... liblime is a persons company trying to take ownership of koha logos? I am sure the one with the slice of lime is theirs....but do not believe they are entitled to rights on any thing that came as a result of the opensource project gosh is there a Fascist amongst us? In a message dated 5/10/2009 4:13:34 P.M. Pacific Daylight Time, jransom(a)library.org.nz writes: Can someone please help me understand what this statement at the bottom of the new Koha website means for the Koha community: "The Koha -- Open Source Library System is © 1999-2009 by LibLime & the Koha Development Team Koha^® and the Koha logo are trademarks or registered trademarks of LibLime <http://new.koha.org/liblime.com> and BibLibre <http://biblibre.com> in the United States, France and other countries. Distributed under the GNU GPL license <http://creativecommons.org/licenses/GPL/2.0/>." Thanks, Jo. _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha **************The Average US Credit Score is 692. See Yours in Just 2 Easy Steps! (http://pr.atwola.com/promoclk/100126575x1222376999x1201454299/aol?redir=htt… ay51009AvgfooterNO62)

3 2

On leave
by Wei Wei LEE 10 May '09

10 May '09

I will be out of the office starting 11/05/2009 and will not return until 19/05/2009. I will respond to your message when I return. For urgent matters, please contact Ms Ho Lam Fong at 6332 1812 for assistance.

1 0

Call for Wkshop Proposals: BossEd Bangkok Conference Oct 31-Nov 1 @ KIS.AC.TH
by David M. Bucknell 10 May '09

10 May '09

Dear Friends and Colleagues, Education is being challenged to change with the times. Lately, we hear words like "transparency," "community," "teamwork," "project-based," and "networked" in the same context as we used to hear, simply, reading, writing and math(s). Project-based, teamwork led by students themselves has come to the fore. This is the kind of learning, we are told, that enables students to develop the social learning skills and intellectual flexibility that is needed in this brave new world. Such learning requires a different kind of software, a different kind of text as well as a different classroom-process than we used to use. While some struggle to create new Web2 technologies that enable the kind of learning and teaching deemed necessary, many have noticed that Free and Open Software (LAMP.org) and Content (e.g. Wikipedia.org) already embody the very lessons we are trying to teach. After all, they are made by teams via the Internet with flexible leadership positions gained by proven capabilities and dedication. Respect in these groups is based on skill, accomplishment and social-networking effectiveness. What's more, the tools and artefacts produced by these groups are open to scrutiny, dissection, and adaptation and exist at the pleasure of those interested. They encourage curiosity, creativity and sharing: they embody what schools' mission statements say is important: lifelong learning, curiosity, respect across borders, etc. In the day-to-day work of schools, teachers, students and school administrators look for "soulutions" to various problems in the Office, the library, the classroom or at home: a text, a puzzle, a tool for reporting, creating or analyzing; something else for organizing, sending and printing; another for storing, searching and dissecting. There are now Free/Open Source (FLOSS) tools for almost anything that can be done on a computer. This is no surprize given that they are generally created to fulfill specific needs or, as Eric Raymond observed, "to scratch an itch." We know that system admins have long used FLOSS; programmers too; now, more and more teachers are using FLOSS. FlOSS itself is a product of idea-sharing; so we would like to extend the FLOSS development process with a technology-assisted physical gathering designed for sharing ideas, problems and Solutions which are being used now or planned for the near future in your schools. Your ideas are welcome. To the idealist: What does Freedom and Openness mean for education? Is your "practice" as a teacher or administrator or student being challenged to be more "open" in some way than before? Does Free and/or Open Source Software (a.k.a. FLOSS) and Free and Open Content (e.g. wikipedia.org) play a part? Should it? Can it? Propose a Session: Show, Tell and/or Teach us how you think/have experience using FLOSS can help you and colleagues meet students needs more effectively than with closed, proprietary solutions. To the pragmatist: Are you saving money while staying legal as a result of using free/open tools or resources? What about security? Viruses and Hacking under control as a result of free/open strategies? Do you find that the tools you need are less stress-producing than the alternatives? http://opensourceschools.org/bossed2009callforproposals Propose a Session: Show, Tell and/or Teach us how you saved money (or plan to do so), increased security, stability and/or power and ease of use with FLOSS. http://opensourceschools.org/bossed2009callforproposals -- * IKN (International Knowledge Networks, Co., Ltd. Thailand) * http://intknowledge.com * Web Ideas, Tools and Sites for Teachers, Schools, Businesses and You. * Cell: +66(0*)84 329 1183; Office: +66(0*)2 980 9464 (*No "0" if calling from overseas.)* Skype: dbucknell ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

1 0

Stuff
by BWS Johnson 09 May '09

09 May '09

Salvete! I didn't want to copy and paste, and I didn't want to reply in the same thread, because I think the discussion is turning back on itself again. Josh wasn't at KohaCon, so he couldn't have heard me say this recently, even though I think I've mentioned this in past, at least in passing. >From an organisational standpoint, I think the project is going through growing pains. A lot of new folks are here, which is great, and we still have a lot of people on board that have been here forever. Also good. One of the things that we didn't do at the last convention that I think needs to happen from now on is some sort of community recognition of contributions. It's hard for a newbie to navigate the straits of the community at the moment, and I think that sucks. I've heard a good deal of folks complain about a good deal of issues, and I've seen other newer folks treating the project in a similar fashion to a traditional vendor situation. Neither of these things are healthy. I also do not like seeing more English and less other languages on this list. I'm American, and I don't want to see this become an American project; I joined for an international effort. I didn't join for a meritocracy, I joined for a more Habitat for Humanity based hands on feel. Even if I did join for a meritocracy, I think we're leaning towards plutocracy and oligarchy the way things are headed. As far as the vendor pages are concerned, I'm for alphabetical order (or RNG even!) by geography. Mimic the UN sort of. (We know their mistakes now, yeah?) I think it would be very worthwhile to *as a community* on the listserv asynchronously develop a sort of bill of rights and a planning document for the project that's not a technical roadmap. I think we need a few very easy to comprehend concise vision sort of statements as a reaffirmation of where we're coming from and where we want to go. Sunlight and no sleepy eyes this way... I also think we have a good kaitiaki and haven't been observing her wisdom of late (or consulting to figure out what it may be.) Or we could argue forever and start forking left and right. My two beads, Brooke

4 3

Re: [Koha] Stuff
by BWS Johnson 09 May '09

09 May '09

Salvete! These are my stream of consciousness thoughts. There are some things in here that will doubtless bring the wrath of Paul and Josh down on me, but they're in here in the interests of community discussion, not picking a fight. (If I wanted to pick a fight, I'd wager I can take both Paul and Josh by sitting on them. They're entirely too skinny, and I'm traditionally built. :) ) That being said, I also think there might be enough starting material here to get someone more eloquent to take them up and refine them. I'm hopeful too, Nicole. We're not your mother's ILS. (Don't forget to phone yer Mums tomorrow Yanks.) Planning is a really keen Librarian project, in my opinion. It's not that developers and release managers shouldn't offer feedback, it's that we're very dorky over here in the stacks and would love to help plot a course since it's something we can assist with. (It's also got to have the added benefit of getting us out of your hair while coding, too! Not too mention less bothering in future.) Cheers, Brooke Koha is a gift with a string attached. While it's wonderful to enjoy a free product, it's even better to leave the ILS in a better condition than you found it. So: At the start, it's good to use Koha, feel free to download it. You might have some convincing to do just to put this step into action. After you've adopted it at your Library, think of your personal strengths, and how you might put part of you back into Koha. Thinking about giving back is better than never considering it, and the smallest contribution is better than not helping at all. Many hands make light work. If you're more fortunate than others and can contribute substantially, please do so with the good of all users in mind. The ideal user does this, whether by donation, coding, or other means. ___________________ Ranganathan's Laws apply. Koha is for use. We aren't researching or developing in a vacuum. Every system his user. Our origins are in a public Library, Horowhenua Library Trust. Koha has been adopted by every type of Library (Public, Academic, School, and Special) all sizes of Library (small, medium, and large), and even in consortial situations, true to the spirit of Open Source. Every user his system. Koha is not for everyone, and we should foster and maintain relationships with other OSILSs and not hesitate to recommend one should it fit a user better. Save the time of the user. The order of operations MUST remain Patron focused if time saving concerns are in conflict. Save the time of the reader, then save the time of the Librarian, then save the time of the developer. Koha is a growing organism. Time wears on and needs change, but consultation should be made with the community before doing away with features. Effort should be made to take a step back and widen the circle as new talent comes to join us. Development originates within the community and is carried out by the developers under the guidance of the current release manager. The full process occurs under the guidance of the community elected Kaitaiki. The process of innovation should never be unilateral nor top down. The Kaitaiki and Release Manager should not be from the same corporation in the interests of neutrality. Time and money are precious commodities. Care should be taken to assign priorities to development so that efforts are not unnecessarily replicated and that features that would appeal to the widest swath of users are bundled first. While everyone is free to contribute, and we greatly appreciate monetary contributions, the scales of innovation should not tilt to the needs of the wealthy over the needs of the wider user base. Independent contributors should not be overlooked for pride of corporation. Koha as a name and the koru as a symbol are not the sole property of LibLime or BibLibre, regardless of being registered as trademarks. Users of Koha, providers of support, and anyone in general should not have the threat of legal action hanging over their heads in reference to using the Koha name or koru symbol. These rights should be relinquished and released by LibLime and BibLibre and registered as a Share Alike under Creative Commons with immediacy. There is no single or best Koha support provider. Your bibliographic data and Patron data are your own. Care should be taken in development to ensure that export of data is clean and easy to accomplish in the event that a user decides on a different future ILS. ____________________ We are innovative We want the best ILS possible and are willing to work hard to make it We are collabourative We are open not proprietary We are lovers of chocolate and damn fine drinkers who believe in fun

1 0

Re: [Koha] Export and Import Data
by Quanzhong Zhang 08 May '09

08 May '09

Hi, I tried to install Koha3. Everything is Ok for the command "make test" on version 3.00.00. But I encounter an error message of the command "make test" on version 3.00.01. I can not find out a solution from Koha mailing list. Could you kindly share your experience for me? Think you very much for your help! Error message: ================================= [root@libtest koha-3.00.01-stable]# make test PERL_DL_NONLAZY=1 KOHA_CONF=blib/KOHA_CONF_DIR/koha-conf.xml /usr/local/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/PERL_MODULE_DIR', 'blib/arch')" t/*.t t/Amazon.......................ok t/Barcodes_PrinterConfig.......ok t/Bookfund.....................ok t/Bookseller...................ok t/Boolean......................ok t/Branch.......................ok t/Calendar.....................ok t/Charset......................ok t/Circulation_barcodedecode....ok t/Dates........................ok 1/126# # In order to run without DB access, this test will substitute 'us' # as your default date format. Export environmental variable KOHA_TEST_DATE_FORMAT # to override this default, or pass the value as an argument to this test script. # # NOTE: we test for the system handling dd=00 and 00 for TIME values, # therefore you *should* see some warnings 'Illegal date specified' related to those. # # Testing Legacy Functions: format_date and format_date_in_iso # Illegal date specified (year = 1952, month = 1, day = 00) at t/Dates.t line 58 Illegal date specified (year = 1952, month = 1, day = 00) at t/Dates.t line 61 # # Testing 4 formats. # Testing no input (defaults): # # Testing with valid inputs: Illegal date specified (year = 1952, month = 1, day = 00) at t/Dates.t line 80 Illegal date specified (year = 1952, month = 1, day = 00) at t/Dates.t line 80 Illegal date specified (year = 1952, month = 1, day = 00) at t/Dates.t line 80 Illegal date specified (year = 1952, month = 1, day = 00) at t/Dates.t line 80 # # Testing object independence from class # done. # Looks like you planned 126 tests but ran 9 extra. t/Dates........................dubious Test returned status 255 (wstat 65280, 0xff00) DIED. FAILED tests 127-135 Failed 9/126 tests, 92.86% okay t/Debug........................# BEFORE use: $debug is not defined # BEFORE use: $cgi_debug is not defined t/Debug........................ok 1/3# AFTER use: $debug is 0 # AFTER use: $cgi_debug is 0 # Done. t/Debug........................ok t/dummy........................ok t/Input........................ok t/Koha.........................ok t/Languages....................ok t/Maintainance.................ok t/Output.......................ok t/Record.......................ok t/Review.......................ok t/Scrubber.....................ok 1/10# Note: scrubber test output will have whitespace collapsed for readability # done. t/Scrubber.....................ok t/Stats........................ok Failed Test Stat Wstat Total Fail List of Failed ------------------------------------------------------------------------ ------- t/Dates.t 255 65280 126 9 127-135 Failed 1/21 test scripts. -9/189 subtests failed. Files=21, Tests=189, 2 wallclock secs ( 1.93 cusr + 0.16 csys = 2.09 CPU) Failed 1/21 test programs. -9/189 subtests failed. make: *** [test_dynamic] Error 255

2 2

Re: [Koha] Anyone using tag clouds?
by BWS Johnson 08 May '09

08 May '09

Salvete! Might not properly be holdings, but what say folks about having them there if we're talking about kind of sort of major kerfuffle? Cheers, Brooke

1 0

Re: [Koha] Anyone using tag clouds?
by Kathy Rippel 08 May '09

08 May '09

I can think of some application of tagging that would help me in my professional capacity, so I would definitely be interested in being able to assign tags. I would prefer it to be on the items screen, for ease, but realize it may make more sense to be on the biblio detail screen, like the LISTS and HOLD buttons. Kathy At 07:01 AM 5/7/2009, Nicole Engard wrote: >I don't know if anyone is doing this, but I have had librarians >express an interest in being able to add tags using the Koha tagging >tools at the cataloging level. They want this for 2 reasons. > >1st - they have some non-authorized terms they want to apply to books >as the librarian and don't want to have to go in and add them via the >OPAC > >2nd - they find that patrons aren't tagging much and figure that by >adding tags themselves it might jump start some interest - or at least >provide tags for people to browse via the tag cloud. > >In both cases they're not talking about using the 690 - but the >tagging mechanism that is in Koha so that things show in the tags list >and the tag cloud. > >--- > >Nicole C. Engard >Open Source Evangelist, LibLime >(888) Koha ILS (564-2457) ext. 714 >nce(a)liblime.com >AIM/Y!/Skype: nengard > >http://liblime.com >http://blogs.liblime.com/open-sesame/ > > > >2009/5/7 Nelson Fredsell -CCE <nelson(a)cfce.org.za>: > > Hi everyone, > > > > > > > > Is anyone using the tag / tag cloud feature for cataloguing > purposes? We're > > considering the use of tags during the catalogue process, to allow use of > > additional subject/keyword material not part of MARC and Z39.50. > > > > > > > > I'm aware that 690 would allow us to put in local Subject assignments, and > > the cataloguer could enter the 690 AFTER a Z39.50 search. The problem we > > have is that we think we'd like to enter 690 BEFORE the Z39.50 search. I > > say BEFORE, because we'd map proprietary Subjects and Keywords during our > > initial migration from the legacy system, then slowly as we have time run > > z39.50 searches on all our records. > > > > > > > > If you're happily using tags for cataloguing, I'd appreciate a > link to your > > OPAC so that I could see what this actually looks like in Koha. > > > > > > > > Thanks, > > > > Nelson > > > > _______________________________________________ > > Koha mailing list > > Koha(a)lists.katipo.co.nz > > http://lists.katipo.co.nz/mailman/listinfo/koha > > > > >_______________________________________________ >Koha mailing list >Koha(a)lists.katipo.co.nz >http://lists.katipo.co.nz/mailman/listinfo/koha Kathleen D. Rippel Dept. Head/Consultant--Resource Sharing and Access ; Pathfinder Central (Manager) Central Kansas Library System 1409 Williams Great Bend, KS 67530 (620-792-4865) phone (800-362-2642) toll-free, KS (620-792-5495) fax kdr(a)ckls.org ******************************************************************************************** I'm currently reading: Destroyer, by C. J. Cherryh I'm currently listening to: Ain't She Sweet, by Susan Elizabeth Phillips.

4 3

Clearing "in house" OPACs
by Adrea Lund 08 May '09

08 May '09

I added an entry to Bugzilla... - Inactivity "timeout" for OPAC - enhancement idea http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=3208 Thanks to all for clarifying some of the issues with this request. Adrea Adrea Lund Head of Adult Services Grand County Public Library 257 E. Center St. Moab, UT 84532 435-259-1111 ext11

1 0

Koha Fines Not Calculating
by Imran Mohamed 08 May '09

08 May '09

Hello, I am from the University of Guyana and I am part of the team that customized Koha. However, we are experiencing a problem. When an item is overdue, Koha does not automatically calculate the fine, however, it says the item is overdue. Circulation and fine rules have already been set up and finesMode set to production. Fines.pl was also run. Please help!!! Regards, Imran Mohamed

2 1