- Koha - lists.katipo.co.nz

Editing Biblio deletes the attached items?
by mjoyner＠EWC.EDU 12 Jan '05

12 Jan '05

Version 2.2.0 a) We edited a biblio to make a change to the ISBN # and it deleted all the attached items? b) In previous version, data entry prevented duplicate items numbers, how to activate this feature for version 2.2.0 ? Background: We run a text book library for a college, and have as much as 150+ items per biblio record. Editing biblio and losing all 150 items currently on loan is not a pleasant thought. :(

1 0

marc mapping questions.
by Tim McMahon - West Liberty Public Library 12 Jan '05

12 Jan '05

What koha fields should I map to marc fields to get the format and subtitle to display? I was also wondering if bulkmarcimport.pl was replaced with bulkauthimport.pl. -- Tim McMahon Technical Services West Liberty Public Library http://www.wlpl.org

3 3

Re: abt koha
by Paul POULAIN 12 Jan '05

12 Jan '05

Shebina K a écrit : > hi............ > > is ther any problem for updating koha 2.0.1 to 2.2 ????? Not that I know. you will just have to rewritte issuing rules and rebuild your authorty structure if you used one. This last being really complex, but let us know if you need some help. Just one note : pls send question to a mailing list, not directly to me -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Re: Re: [Koha] marc mapping questions
by Steven F. Baljkas 12 Jan '05

12 Jan '05

Tuesday, January 11, 2005 19:52 CST Hi, Stephen, Tim, et al., Actually, Stephen there is almost a single 'tag' that performs the function, but it would require that Koha analyse it in relation to position 06 of the Leader and then to display it in some kind of human-meaningful form. That tag, of course, is the 008. This would require a limited number of if--then statements to determine the exact type of material being coded for. My reading of the 008 with all its various specifications for different types of materials (via positions which are SUPPOSED to be coded in every MARC record that seeks to meet minimum national standards) would suggest that the level of detail in the 008 alone would suffice for most library patrons' needs. Although this next bit would go beyond the straightforward, one could, I assume, also construct further if--then statements to check for 006 and 007 tags and parse the even more detailed coding that can be provided with those tags. **More straightforward, there is also the 245h which is prescribed for General Material Designation.** Some libraries bend the formal rules (AACR2R 1.1C1) and apply terms that they know are more meaningful to patrons (e.g. DVDs, CD-ROMs, etc.). One library I know locally was able to customise their ILS to add [text] to the display in the absence of a 245h, just so everything would be parallel (no matter the type of material a displayed record was for, there would be a GMD term ... and a little graphic actually; I kinda liked the latter). Alternatively, the individual library or the Koha community as a whole could also decide to designate one of the x9x tags for a Specific Material Designation or something similar to it, and to set aside a column in Koha for that information (unless I missed something though, Stephen, you were basically telling Tim there is nowhere for the info to be mapped to?). I know that there is a lack of will to limit people's options, but it mightn't hurt to decide on a field that Koha could use as a default for this kind of thing. It would make Koha slightly more user-friendly for those of us who aren't programmers. Tim, I would take a look at the Leader and 008 details and see if their coding could work for you. Steven F. Baljkas library tech at large Koha neophyte Winnipeg, MB, Canada > From: "Stephen Hedges" <shedges(a)skemotah.com> > Date: 2005/01/11 Tue PM 07:33:00 CST > To: "Tim McMahon - West Liberty Public Library" <tmcmahon(a)wlpl.org> > CC: koha(a)lists.katipo.co.nz > Subject: Re: [Koha] marc mapping questions. > > Tim McMahon - West Liberty Public Library said: > > What koha fields should I map to marc fields to get the format and > > subtitle to display? > > Subtitle is easy -- map MARC tag 245b (MARC21) to bibliosubtitle.subtitle. > > Format is tougher. There's no single MARC tag that contains format > information. Nor is there any good column in the biblioitems table for > storing such information. Probably your best solution is careful > selection of your item types. Choose itemtype codes that are meaningful > -- like "CD" or "DVD" or "Cass." > > -- > Stephen Hedges > Skemotah Solutions, USA > www.skemotah.com -- shedges(a)skemotah.com > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha

1 0

POSIX error in Windows98SE/XP !!!
by Dana Huff 11 Jan '05

11 Jan '05

This is just the first error of many you will get when you try to use the install script under Windows. At least, I haven't been able to get it to work even after a lot of hacking. No vale la pena. Are you doing a new install or an upgrade? If it's an upgrade, copy the files manually to the correct directories and either try running the DB update script by itself or just examine it and create a SQL script from it to update the DB. For a new install, you could use the Windows installer script for Koha 2.0.0, get that working and then follow the upgrade instructions above. Or wait until someone creates a Windows installer script for 2.2.0. Dana Huff World Link Ministries/SEFOVAN www.worldlinkministries.org www.sefovan.org

2 1

POSIX error in Windows98SE/XP !!!
by Adalid Ortiz 11 Jan '05

11 Jan '05

The installer/upgrade scripts send this message when try to upgrade or install Koha. Any help? POSIX::termios not implemented on this architecture at install.pm line 109. Compilation failed in require at installer.pl line 5. BEGIN failed--compilation aborted at installer.pl line 5. FELIPE ADALID ORTIZ ANZALDO Area de Medios Electrónicos Biblioteca Loyola http://www.loyola.tij.uia.mx UNIVERSIDAD IBEROAMERICANA TIJUANA Ave. Centro Universitario 2501 Playas de Tijuana Tijuana, B.C., México 22200 Tel. 664 630-1577 Ext. 623 Fax 664 630-1591 eMail adalid(a)tij.uia.mx "No sobreviven los más fuertes, ni los más inteligentes, sino aquellos que tienen una mayor capacidad para adaptarse a los cambios." --Charles Darwin--

2 1

speed
by Jared Jennings 11 Jan '05

11 Jan '05

i've got a koha 2.0.2 installation on two servers running OpenBSD 3.5; a pentium 120 and a pentium 166. it's soon to become a 2.2.0 installation, because i can run 2.2.0 with mod_perl. with 2.0.2, it takes 13-15 seconds to get from one OPAC page to another; with 2.2.0, it takes 15 sec to start a session and 5-8 sec. to get from one page to another. does anyone have any tips on how i can optimize my setup other than with mod_perl?

3 3

2.2 printer settings page shown as plain text
by Jared Jennings 10 Jan '05

10 Jan '05

i've got my 2.2 install up, and i'm poking around in the settings. when i pick printers, i see HTML markup. it's filled out (no ), and looks like it would make a pretty good printer picking page; but i see the markup not the rendering. the z3950 settings (also in the /cgi-bin/koha/admin/ dir) work fine; the .tmpl and the .pl for the printers have the same permissions as everything else. i haven't dug deeply into the printers.pl. it might be useful to know i'm running on mod_perl.

1 1

mysql 3.x problems
by Jared Jennings 10 Jan '05

10 Jan '05

(garthus i forwarded this to the list for the benefit of future archive searchers) On Thu, 30 Dec 2004 11:02:46 -0500, Gerry Arthus <garthus(a)lilrc.org> wrote: > What does this mean, > > unknown column lock_tables_priv in 'field list' > > I get this message when trying to install the latest r5 version of koha > in a Debian environment. It does not allow the database to be installed. lock_tables_priv is a column in one of the tables that has to do with access control. These tables (host, user, db, etc.) are part of the 'mysql' database. The lock_tables_priv field is not found in versions of MySQL prior to 4.0.2. The current stable version of MySQL is 4.1.8. Debian's stable distribution has 3.23.49 in it. To use a newer version while keeping debian stable on your system, see http://www.debian.org/doc/manuals/apt-howto/ch-apt-get sections 3.8, 3.9 and 3.10, or google "pinning debian" or some such. You might be able to ignore this error if it doesn't cause the updater to die, or remove the reference to lock_tables_priv in the updater script; but mysql 4.x is good to have anyway.

1 0

server address 404 error
by mike re-v 08 Jan '05

08 Jan '05

hi for 404 errors point your browser to http://localhost:80 for koha[opac] and http://localhost:8080 for koha[admin] hth re-v __________________________________ Do you Yahoo!? The all-new My Yahoo! - What will yours do? http://my.yahoo.com

1 0