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

RE: [Koha-devel] Fedora 4
by Shawn Romine 22 Jun '05

22 Jun '05

Thanks for the quick reply. Also, I wanted to commend you on your excellent and professional documentation. It is the quality work being done by you and others on this project that is making this a viable solution. Once I saw KOHA itself, the documentation, and the excellent support on this listserv, I was able to go to the college and say this is something we should be researching. Thanks! -----Original Message----- From: Joshua Ferraro [mailto:jmf@liblime.com] Sent: Wednesday, June 22, 2005 7:12 AM To: Shawn Romine Cc: koha-devel(a)lists.sourceforge.net Subject: Re: [Koha-devel] Fedora 4 Hi Shawn, I haven't had a chance to install FC4 yet so I haven't updated the installation manual. I can't think of any reason it wouldn't work though. -- Joshua Ferraro VENDOR SERVICES FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Koha ILS, Mambo Intranet, DiscrimiNet Filter jmf(a)liblime.com | Full Demos at http://liblime.com | 1(888)KohaILS

1 0

Fedora 4
by Shawn Romine 22 Jun '05

22 Jun '05

Does anyone know if Koha will install on Fedora 4 using the Fedora 3 install instructions?

2 1

Koha 2.2.3 is out
by Paul POULAIN 22 Jun '05

22 Jun '05

http://sourceforge.net/project/shownotes.php?release_id=336931 ======== WARNINGS ======== * READ the following NOTES carefully. Look at BORROWERS especially if you want to know why your circulation won't work after update !!! * The installer is *wrong* on languages available. In this release, french & english are uptodate. Polish is uptodate for OPAC. Some other .po files are provided (chinese & italian, in $KOHAROOT/intranet/scripts/misc/translator/po) but they are not uptodate & need some work to be useable again. * The librarian interface is tested only with mozilla/firefox. Should work (partially) with IE. OPAC should work fine with any navigator. KNOWN BUG : ****** in MARC setup, if you have more than once a field mapped to a give authorised value, when you duplicate a field (whatever the field), all authorised values are defaulted to the same value. Bug still unexplained. Don't occur if you just modify a biblio, or when you have only once a given authorised value category. Bug detected by EMN, that has a "LANG" authorised value for both "text language" and "original text language". ======= DIFFS ======= Diff 2.2.2 => 2.2.3 ******************* DB MODIFS : *********** DB structure : none DB content : 4 systempreferences (see below) Koha opac stylesheets : some changes and at least 4 added entries. BUGFIXES ***** Critical & Minor mixed === ACQUISITION === * adding supplier info to basket.pl (for order printing) * adding a date filter on acquisition history search === OPAC === * minor fix in subject link (normal view) === CATALOGUE === * it's possible to change a framework type when editing a biblio * (critical) bugfix in authorities : in biblio repeated fields, when you choosed an authority entries, it was copied in all the fields, not only in one. * bugfix : when you duplicate a MARC field (for the 2nd time or more), the last field was duplicated too. * bugfix in subject link, in normal view * bugfix when duplicate authority suspected, the link to see the other authority was wrong. * bugfix in items : the Edit biblio button was wrong. * bugfix when MARC=OFF, subject modifs were not stored in MARC database. * bugfix in z3950 client, for BNF (problem probably due to upgrading of some sofwtare in UNIMARC) * fix in z3950 server. Now works correctly === AUTHORITIES === * bugfix in "next page" in authority search (was buggy under certain circumstances only) === CIRCULATION === * bugfix : checking issuing rules under certain circumstances was buggy (reported issuing OK where it should not) * bugfix : renewal by issuing a book again did not work correctly. === BORROWERS === * better management of joining & expiry dates : - dates can be manually typed when adding a borrower. - Empty fields are automatically calculated (joining = today & expiry date calculated from borrower category) - Expiry date can be modified * checking expiry date when trying to issue a book & forbidding issuing when expiry date reached. ** IMPORTANT ** This check was not done before. Thus, you may be unable to issue books where you could before. You can update your database borrower by borrower or with the following SQL command on the server : "update borrowers set expiry='2005-31-12'". You can limit the update to a borrower category with "update borrowers set expiry='2005-31-12' where categorycode='A'" (all SQL commands must be typed without any ") * template improvements & some bugfixes in fines management. === PARAMETERS === * in marctagstructure, next & previous button no more loose frameworkcode & link to default framework IMPROVEMENTS === ACQUISITION === * in history search, a filter has been added on order date. * there are now 2 differents totals : one for rrp column & one for est column === CATALOGUE === * There is also a FindDuplicate feature for MARC Authorities * Dictionnary search : for titles, author & subject, there is now a "dictionnary search". when the user clic on ..., a popup appear, that enable search in biblios as well as in authorities. For example, if user clic on author, and enter "Hugo", he will fing all authors & authority having "Hugo". He then can choose the Hugo he want and run the search with what he has found (& other criteria as well if he want) * it's now possible to change the framework of a biblio * the overduenotice.pl script (that sends a mail to borrowers with late issues) contains the list of late items (title, author) === PARAMETERS === * a new button in marctagstructure.pl has been added : if selected, only actived fields/subfields are shown. Subfields used are in a summary just under the tag. Strongly limits the number of lines shown & more user friendly. * Adding 2 checks in marc parameter checking : only 1 MARC tag must be mapped to item tab and warning if there is NULL in a frameworkcode' === REPORTS === * in "borrowers with no issues" wizard, adding "without issues since" === OPAC === * basket / bookbag sending now has item list and an iso2709 file attached * links to reach suggestions & virtual shelves from any OPAC page * improvements in style sheet for better standard compliance. OPAC works perfectly under opera & konqueror. * added a systempref to define an alternate image as logo (for main page & top-left image on each page) * added a systempref to choose either to show or hide "lost" items. Note that "lost items" can be related to an authorised value list, so does not necessary mean "item definetly lost". Even here, some libraries want to see lost items, and some don't want. This parameter will make everybody happy ! * adding a "complete historyview" for subscription. Show year by year all issues, whatever the status (arrived, missing...). A new systempref as been added to choose between simple & complete history view. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Summary 2005-06-20
by MJ Ray 22 Jun '05

22 Jun '05

What have the koha developers been putting in koha 2.3 this week? tipaul bugfixed the Z39.50 server and client, added some missing UNIMARC editor plugins, improved the MARC migration tools, updated opac history and login pages, bugfixed css/en opac templates, updated date formatting and history of bulletins. joshferraro added a favicon to npl/en opac templates, added a readme for the usmarc sample. hellen translated more of default/de intranet templates. hdl made overdues red in css/en opac templates, made the ISBN opac display dashed, added quick links to the default/en intranet templates, added deleted and "not issued" states for serials, improved the opac display of serials, bugfixed MARC searching. Detailed changelog at http://www.ttllp.co.uk/koha/20050620.changelog -- MJ Ray (slef), K. Lynn, England, email see http://mjr.towers.org.uk/ http://www.ttllp.co.uk/koha/

1 0

Re: [Koha-devel] koha 2.2.3 ?
by Thomas D 21 Jun '05

21 Jun '05

20 June 2005 Does 2.2.3RC finally include MARC fixed fields as part of the standard MARC Framework install? Some of the fixed fields are required for MARC and the contents are not redundant with the content of other fields. Better MARC support is still needed for Koha to be taken more seriously as a solution for libraries using MARC. Fixed fields are just one small part of the gap in proper MARC support. Certainly, progress has been very significant during the past year. Thomas D Quoting Paul POULAIN <paul.poulain(a)free.fr> : > ---------------- Beginning of the original message ------------------ > > Rachel Hamilton-Williams a écrit : > > Hi guys, > > > > I've just been to visit a local school who'd managed to > install koha 2.0 > > rather than 2.2.2 - and I was recommending she upgrade - but > wondered if > > 2.2.3 was out/going to be out this week in which case she > could hold > > off for a few more days > > Koha 2.2.3RC is installed since thursday in "Ecole des Mines > de Nantes". > [*] Unless they report a major problem, 2.2.3 should be > officially here > on wednesday morning (i'm GMT+2, so it means late wednesday > for you, so > probably thursday ;-) ) > > > [*] i've added this RC internal release to avoid 2.2.2 > problem, a > blocking bug that needed a 2.2.2b 2-3 days after, boring at > least some > french libraries. I'll probably continue with RC installed on > 1 library > from minor release to minor release. > > -- > Paul POULAIN > Consultant indépendant en logiciels libres > responsable francophone de koha (SIGB libre > http://www.koha-fr.org) > > > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration > Strategies > from IBM. Find simple to follow Roadmaps, straightforward > articles, > informative Webcasts and more! Get everything you need to get > up to > speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op¿ick > _______________________________________________ > Koha-devel mailing list > Koha-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/koha-devel > > ------------------- End of the original message --------------------- --------------------------------------------- Protect your mails from viruses thanks to Alinto Premium services http://www.alinto.com

2 1

about html templates writing :
by Paul POULAIN 21 Jun '05

21 Jun '05

Hi, koha-developpers, Just a reminder for everybody, as i had some problems with french translation for 2.2.3 : REMEMBER that TRANSLATOR tool really HATES  inside a standard html tag, like : <td > or <input ...  checked> pls alway write :  <input ... checked>  <input ...>  thanks. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

RE: [Koha-devel] Koha installation procedure
by Jared Camins-Esakov 21 Jun '05

21 Jun '05

> Basically, what I think he means is that the sysadmin should be able to > do a "rpm --install", then say "my job's done, over to you" to the koha > admin. That is what I was trying to say. In hindsight, I should've just said that, as it probably makes a lot more sense to a lot more people than my rather poor illustration. > Certainly that makes sense, but whether it's practical is another matter > ... you can't always cleanly separate the system from the app, as I've > found on having to bugger about with default installs that don't have > sensible (for us) defaults ... That's another question. Any thoughts? My thought was that the "sensible defaults" should not necessarily be a full set-up, merely enough that it can be passed off to the Koha admin (e.g. all files exist, but the configuration files are empty, or only the options that can't currently be changed using installer.pl are set...). Having Koha work "out of the box" without any configuration seems like an unreasonable goal. There are too many options, and guessing the wrong configuration (e.g. UNIMARC versus MARC21) would leave the admin in a much worse spot than leaving the system unconfigured would, in my opinion. Does this make sense? Thanks. -- Jared Camins-Esakov -- Jared Camins-Esakov E-mail: camins2(a)tcnj.edu

1 0

RE: [Koha-devel] Koha installation procedure
by Anthony Youngman 21 Jun '05

21 Jun '05

Basically, what I think he means is that the sysadmin should be able to do a "rpm --install", then say "my job's done, over to you" to the koha admin. Certainly that makes sense, but whether it's practical is another matter ... you can't always cleanly separate the system from the app, as I've found on having to bugger about with default installs that don't have sensible (for us) defaults ... Cheers, Wol -----Original Message----- From: koha-devel-admin(a)lists.sourceforge.net [mailto:koha-devel-admin@lists.sourceforge.net] On Behalf Of MJ Ray Sent: 21 June 2005 09:54 To: camins2(a)tcnj.edu; koha-devel(a)lists.sourceforge.net Subject: Re: [Koha-devel] Koha installation procedure Jared Camins-Esakov <camins2(a)tcnj.edu> wrote: > * Configuration should be possible at any time after installation (so on > systems where the sysadmin is not also the Koha admin, the sysadmin > doesn't have to wait for the Koha admin) Can you elaborate on this, please? **************************************************************************** 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

Koha installation procedure
by Jared Camins-Esakov 21 Jun '05

21 Jun '05

Hello all. I am interested in reimplementing the Koha installation procedure to meet the following requirements: * File installation and configuration should be separate from each other (necessary for creating a port compliant with the FreeBSD ports system's unspoken best practices, and probably other packaging systems' best practices as well) * Configuration should be possible at any time after installation (so on systems where the sysadmin is not also the Koha admin, the sysadmin doesn't have to wait for the Koha admin) * It should be possible to specify ALL options to the installation and configuration scripts using command line switches or environment variables, or something else that doesn't require user intervention (so that the setup process for the entire system could be scripted [I've done this, so I imagine other people do it too]; the auto-configuration file doesn't really lend itself to scripting, in my opinion) * It should be possible to install Koha without having GRANT privileges on the MySQL server (or root access to the server), if an account has already been created for Koha's use My plan is to start by separating the installation and configuration into two separate scripts, both using the Install.pm module. I am not sure how to implement the second issue. Perhaps have the installation set up the intranet module temporarily, and then use a one-time web-based configurator a la Refbase (refbase.sourceforge.net)? My first thought was to install the Install.pm module in site_perl and the configuration script in $PREFIX/sbin (for example), but I guess installing anything outside of Apache's area should be avoided? My preference on the third issue is to use command line arguments, so I'll also look into that if I get the go-ahead. It looks like my fourth requirement is fairly easy to fill by just adding a command line argument (or environment variable) to specify "use existing database user so-and-so." Any thoughts on this? Anything I've suggested that is a Really Bad Idea? Anything that should be done differently than I suggested? Anything that you'd like to see implemented in the installer? If no one has any problems with my suggestions, and the current maintainer of the installer is willing to consider my patches, I'll start work on this. Please let me know what you think. Thanks. -- Jared Camins-Esakov P.S. If the consensus of the list is that I should go forward, volunteers who would be willing to test my changes under Linux/Windows/anything-besides-FreeBSD would be most appreciated! -- Jared Camins-Esakov E-mail: camins2(a)tcnj.edu

2 2

Barcodes Barcodes
by Joshua Ferraro 21 Jun '05

21 Jun '05

Hi all, I attempted to get the barcode generation going this afternoon and failed. My problems started with the error everyone else has reported: Can't locate PDF/API2/PDF/Utils.pm in @INC I found that Fedora was having trouble installing PDF::API2 (but it was not giving any useful errors). So I installed the Fedora package for PDF::API2's one major dependency: Compress::Zlib (the package name is perl-Compress-Zlib). After that installed I was able to install PDF::API2. But I still got the same error and I noticed the following: /usr/lib/perl5/site_perl/5.8.5/PDF/API2/Basic/PDF/Utils.pm I replaced use PDF::API2::PDF::Utils; with PDF::API2::Basic::PDF::Utils; in barcodesGenerator.pl and printerConfig.pl. Now I'm getting: Can't locate object method "barcode" via package "PDF::API2" at /home/koha001/koha/intranet/cgi-bin/barcodes/barcodesGenerator.pl line 239 I don't see a barcode method anywhere on CPAN for the PDF::API2 modules. Is there another library that has this method? Has anyone use the barcode generation successfully? Any tips for getting it going? Thanks, -- Joshua Ferraro VENDOR SERVICES FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Koha ILS, Mambo Intranet, DiscrimiNet Filter jmf(a)liblime.com | Full Demos at http://liblime.com | 1(888)KohaILS

3 2