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

Katipo is Visiting Sydney
by Rachel Hamilton-Williams 19 Jan '05

19 Jan '05

Hi all Chris (original Koha Programmer), Russel (QA), and I (Kaitiaki) will be in Sydney in about 10 days time for a week... We are demonstrating Koha at the ONLINE Conference... http://conferences.alia.org.au/online2005/ And would love to see you if you're either going to be at the conference, OR if you're in Sydney and would like to meet us for dinner/drinks etc. We will be giving away free Koha installs at the event, so if you know anyone who wants one send them along. Cheers Rachel

1 0

Re: [Koha-devel] New Koha Logo
by Owen Leonard 19 Jan '05

19 Jan '05

I'm not going to argue about what the best terminology is, and I don't think any of us necessarily should. I think we've already established that whatever term we use, it's language- specific and therefore should be left out of any official logo. Let's divert the discussion towards looking at the logo itself and deciding whether we like it, and if not what we would suggest be done differently. Whatever the outcome, hopefully we can then provide the logo in as many formats as possible (Photoshop, Freehand, Illustrator, etc.) so that folks can download and modify for their own use. -- Owen ---- Web Developer Nelsonville Public Library http://www.athenscounty.lib.oh.us

1 0

RE: [Koha-devel] New Koha Logo
by Anthony Youngman 19 Jan '05

19 Jan '05

Note that the acronym FOSS has an alternative (which I always use) of FLOSS - Free/Libre Open Source Source. So yes, I would support the use of the word Libre, and if people complain "that's French, and American is the universal language", I would respond with "It's not French, it's Latin" (which *was* the universal language). Cheers, Wol -----Original Message----- From: koha-devel-admin(a)lists.sourceforge.net [mailto:koha-devel-admin@lists.sourceforge.net] On Behalf Of Paul POULAIN Sent: 19 January 2005 09:23 To: Rachel Hamilton-Williams Cc: Koha-devel; Rebecca Holden Subject: Re: [Koha-devel] New Koha Logo > The Free/Open Source debate has raged on and off - and so a version with > "free" in it would be possible I think if some would rather use that - > here both are confusing which is why I was thinking of droping them - > but again YMMV, so let me know and I'll do a couple of versions. My opinion here : * the "free library system" sentence must be out of the logo. For translation purposes (worst : in french a "librairie" is a bookseller, a "library" is a "bibliotheque". A non translated word could be a real trouble for many ppl) * I heavily prefer having the word free in it. In french, it's "libre", and "libre" (=free as speach) is different from "gratuit" (=free as beer), so no risks here. And "free" is shorter than "open source" (in french like in english). And, last, "open source" is not enough. It should be written "open source in the Open Source Initiative sense". **************************************************************************** This transmission is intended for the named recipient only. It may contain private and confidential information. If this has come to you in error you must not act on anything disclosed in it, nor must you copy it, modify it, disseminate it in any way, or show it to anyone. Please e-mail the sender to inform us of the transmission error or telephone ECA International immediately and delete the e-mail from your information system. Telephone numbers for ECA International offices are: Sydney +61 (0)2 8272 5300, Hong Kong + 852 2121 2388, London +44 (0)20 7351 5000 and New York +1 212 582 2333. ****************************************************************************

1 0

abt koha....
by Shebina K 19 Jan '05

19 Jan '05

hi..... this is a MARC21 doubt to what kohafield , i should map source of aquisition, edition statement etc.... in the marc structure 2. how can i change koha admin's password ?? a suggestion i think it will be very useful if the users(through opac interface) can change thier own password.. bye shebina

1 0

koha installation
by Shebina K 19 Jan '05

19 Jan '05

hi.... as i found errors in koha upgradation to 2.2 (in searhing ,and in opac) i want to know whether i can install it directly and use the previous data ( that is in 2.0.2) i have the backup created by backup.sh is there any other way???? plz help me soon shebina

1 0

abt koha
by shebina 18 Jan '05

18 Jan '05

hi............ i upgraded koha 2.0.2 to koha2.2 but some searching are not working properly...like barcode and i think opac is not upgraded shebina

1 0

abt koha
by Shebina K 17 Jan '05

17 Jan '05

hi......... i am going to upgrade koha 2.0.2 to koha 2.2.0 and i want know how can i use ldap server some borrower details are stored in an another system but not in the order....(not entered into koha 2.0.2) so plz help me.... shebina

1 0

Koha 2.2.1 roadmap
by Paul POULAIN 14 Jan '05

14 Jan '05

Hi (again...) Here are my actual release notes for the future 2.2.1 version : BUGFIXES ============================ ***** Critical * fix for http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=811 : The OPAC requires uses to log in to view virtual shelves, and it requires a user with librarian privileges ***** Minor * in serials module >> add subscription >> select biblio : The next / previous page were invalid. * in serials module >> add subscription >> select biblio : impossible to report the biblio when there is a quote in it (' was not escaped) * issn were not stored correctly in non-MARC DB on biblio modification * in catalogue, modifs were not stored properly the non-MARC item DB. Affect only libraries without barcodes. * in thesaurus structure, deleting a tag delete the tag in each authtype, not only in the selected authtype. * plugin unimarc_225a (seriestitle) did not show the seriestitle list, when there was no ISBN IMPROVEMENTS ***** Major * serial subscriptions : modifs to handdle correctly more than 1 subscription of the same biblio. Enter subscription detail in subscription notes (like "for branch XX" or "for 2nd floor"). The subscription details are all shown in OPAC. * serial subscriptions : you can now delete a subscription that is not yet active (= has only 1 issue in "waiting" state) * adding series title and publication year limits in opac-search form. * improvements and fixes in Nelsonville templates **** Minor * adding publicationyear and series title in opac advanced search form * in biblio basket, adding the possibility to open a biblio (in the main window) by clicking on the title * circulation >> issue : showing borrowernumber code just after the borrower name. * the search on barcodes has been changed to "start" instead of "contains". It's more logic =============================== (+ some improvements in french translation) That's good, but no need to release a 2.2.1 urgently. I plan to release the 2.2.1 at the beginning of February. Any opinion on this roadmap ? Don't hesitate to open other bugs on bugzilla if needed. Don't hesitate to commit other bugfixes or minor improvements. NOTE : For nelsonville & translators : I think I'll try to add a flag on each line to say : * CODE : the fix is in code only, no need to do anything on templates * TMPL : the fix changed at least a template. Need to rerun translation and/or modify non default templates. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Owen, about some of your commits
by Paul POULAIN 14 Jan '05

14 Jan '05

Hi owen et al, I've seen your commits. Most of them are both in rel_2_2 and HEAD. Except the nice member-quick-search.pl, that is in HEAD only. As this seems to me a nice feature, and does not affect DB stability, I think you should commit it in rel_2_2 too. My opinion as Release Maintainer about rel_2_2 / HEAD : * if something changes a lot the DB & code => in HEAD, without any doubt. * if something improves a feature or add a minor one (like member-quick-search) => in rel_2_2 undoubtfully too. For other cases (minor change in the DB or major feature), I think the best way is to ask me (on koha-dev). Depending on the common interest for the idea, we can decide : * to put it in HEAD * to put it in HEAD until it's stable enough then backport it to rel_2_2 * to put it in rel_2_2. This last case meaning a new official 2.2.x will not be release 1 or 2 days after the commit, to have enough time to test it ;-) I begin immediatly by asking the list in another mail on a requested feature done by a french library. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

KOHA on FC3, OK?
by Bruffey, Mark 11 Jan '05

11 Jan '05

Will KOHA run OK on FC3? I'm installing clean from FC1. I'm assuming I'll install the new 2.2 [!] I'm hoping existing data can move over easily. Thanks, Mark L. Mark Bruffey Director Library Services Central Baptist Theological Seminary 900 Forestview Lane N Plymouth MN 55441 763 417 8264 mbruffey(a)centralseminary.edu Central Seminary www.centralseminary.edu <http://www.centralseminary.edu/> Fourth Baptist Church www.fourthbaptist.org <http://www.fourthbaptist.org/> WCTS Radio AM 1030 Online www.centralseminary.edu/wcts <http://www.centralseminary.edu/wcts> *************************************** Have you experienced the good news? "Every one who calls on the name of the Lord will be saved!" [Romans 10:13] ***************************************

2 1