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

Installer, SAX parser check ?
by Bünzli Daniel 08 Jan '08

08 Jan '08

Le 8 janv. 08 à 08:48, Frédéric DEMIANS a écrit : > Are you sure using XML::LibXML SAX parser? Verify with this script: > > <koha-root>/misc/sax_parser_print.pl > > which should display something like XML::LibXML..... Shouldn't maybe the perl installer check that ? Best, Daniel

1 0

various questions (mainly around zebra config & stuff)
by Paul POULAIN 05 Jan '08

05 Jan '08

~#perl -e 'print "Hello world\n"; Investigating liblime recent or less recent commits I have some questions : ==== 1 ==== - the koha-conf.xml now contains <listen id="biblioserver" >unix:__ZEBRA_RUN_DIR__/bibliosocket</listen> so, no more tcp@blabla:port iirc, unix sockets are much more faster than tcp. but : - does that means we "loose" the z3950 public server in the process ? - Is it replaced by the SRU/SRW that is just after ? (ie : can we query the SRU/SRW server with PQF queries ?) ==== 2 ==== How to check that the SRU/SRW works fine ? I tried a yaz-client @:9998/Biblios and get : Connecting...error = System (lower-layer) error: Connection refused ==== 3 ==== The opensearch & unapi things uses SRU/SRW, but the port is hardcoded to 9998, were it can be changed in the install process. can we consider that as a bug ? ==== 4 ==== misc/zebraqueue_start.pl & misc/update_items.pl afaik : - zebraqueue_start was written to update the zebra DB when a biblio is updated/added/deleted - update_items was written to update on a daily basis all items that have been updated (to update issuing status of the item) now that zebra is quick, a line is added into zebraqueue and the "position status" of each item is updated everytime zebraqueue_start is run. so do we still need misc/update_items.pl ? ==== 5 ==== It seems that issuing a book results in 2 lines in zebraque. Isn't this a bug ? ==== 6 ==== Now that zebra indexes quickly, do we still need zebraqueue_start ? couldn't we update in real time ? (that wouldn't solve the multiple access problem joshua faced 2 years ago, when updating the DB from 2 processes resulted in a DB crash. But myabe this issue is solved as well now.) ==== 7 ==== couldn't we transform zebraqueue_start to a daemon, and not let is as cronjob ? having to wait for 1mn in the worst case seems very long to most librarians (when they add an authority and have to wait for 1mn to be able to find it in the biblio) would that daemon-ization be a problem for MS-windows servers ? -- Paul POULAIN BibLibre SARL Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19

3 3

Position announcement: Koha Application Developer
by Joshua Ferraro 04 Jan '08

04 Jan '08

apologies for cross posting. LibLime, the leader in open-source solutions in libraries, is seeking to hire Application Developers and Project Managers to work on development and implementation of the Koha Integrated Library System (http://koha.org) To learn more about the positions, please visit our Careers site: http://liblime.com/about/careers About LibLime LibLime is a company dedicated to providing open-source software solutions to libraries via a service-oriented business model. We're an equal opportunity employer offering excellent compensation packages, including health, dental, paid leave, and a 401(k) retirement plan. If you have the personal and professional skills for this position and want to work in a rapidly growing technology company, we invite you to send your resume to careers(a)liblime.com along with a brief cover letter. Meet us at ALA Midwinter 2008! If you're interested in this position and are attending ALA Midwinter, we'd love to meet you. Send us an email at the address above, or use the Web form to schedule a discussion: http://liblime.com/news-items/events/schedule-meeting -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS

1 0

Item-level hold blocked for checked-out item?
by Owen Leonard 03 Jan '08

03 Jan '08

I noticed a behavior in 3.0 that seems incorrect to me, so I wanted to ask paul and hdl in particular, since this may be a SAN-OP feature: If I'm trying to place a hold on a title which has checked-out items attached to it, I'm blocked from placing an item-level hold on the checked-out items. This seems contrary to the idea of holds--why shouldn't I be able to place the hold and wait until the item is returned for my hold to be fulfilled? A library at NPL would generally be using item-level holds /only/ for items which are checked out--because otherwise they could go to the shelf and find the particular copy they're looking for! This may be another system pref requirement, but I wanted to ask about the motivation behind it first. Thanks, Owen

1 0

Release Date for Koha 3 Alpha
by Joshua Ferraro 03 Jan '08

03 Jan '08

Hi folks, Happy new year everyone! As you may be aware from the huge volume of commits[1], several of the Koha development team members have been grinding away at getting 3.0 ready for general release, and the good news is that we're getting there; Major Kudos to the whole team! So with that in mind, I'd like to schedule an Alpha release of Koha 3 this Friday, January 4th. There are a few remaining acquisition, circulation and serials issues I'd like to get wrapped up before that happens; I'd also like to give the French team enough time to get the fr-FR translation polished up. For now, here's a teaser from the "Release Notes": ----------- This alpha release of Koha 3.0 will be followed by a beta release on Feb 1, 2008, including fixes to the following components: * General Bugfixing (everyone) * New API for item management (gmcharlt) * MARC21 Authorities (gmcharlt) * I18N/L10N, BiDi, lang detection (kados) * OPAC Templates re-design (oleonard) * Documentation and Translations (everyone) The final stable release of Koha 3.0 is slated for March 1 2008 and will include bugfixes to 3.0 beta. Subsequent releases of 3.0 will be bugfix releases, and won't include any new features. New features will be available in Koha 3.2 and subsequent releases. ----------- As always, any questions, comments, feel free to let us know. Cheers, -- Joshua Ferraro Koha 3.0 Release Manager -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS [1] http://git.koha.org

4 5

value builders, spaces in window names
by Ignacio Javier 02 Jan '08

02 Jan '08

Hi all: Seems that due to a restriction in "not standard DHTML javascript window object open method argument values" could exist (and in fact exists (*) in some internet explorer versions, my 7.0.5730.13), an "informal behaviour" that avoids opening of MARC assistants in Internet Explorer (those that commonly open when clicking in underlined text '...' links at http://.../cgi-bin/koha/cataloguing/addbiblio.pl, for example). In order to be let's say "more than concise but less than exhaustive" , this is from mozilla developer site, window open: (...) strWindowName This is the string that just names the new window. Such string can be used to be the target of links and forms when the target attribute of an <a> element or of a <form> is specified. This string parameter should not contain any blank space. strWindowName does not specify the title of the new window. (...) http://developer.mozilla.org/en/docs/DOM:window.open#Return_value_and_parame ters ..."should not contain any blank spaces" seems to be a **must not...** in IE7 This is the list of files and strings I've found that seem to be affected in a 02jan07 (3.00.00.040) git snapshot (*): cataloguing/value_builder/unimarc_field_125b.pl: \"unimarc field 125b\" cataloguing/value_builder/unimarc_field_120.pl: \"unimarc field 120\" cataloguing/value_builder/unimarc_field_125.pl: \"unimarc field 100\" cataloguing/value_builder/unimarc_field_225a.pl: \"unimarc 225a\" cataloguing/value_builder/unimarc_field_124b.pl: \"unimarc field 124b\" cataloguing/value_builder/marc21_leader_authorities.pl: \"unimarc field 100\" cataloguing/value_builder/marc21_leader_book.pl: \"unimarc field 100\" cataloguing/value_builder/unimarc_field_128a.pl: \"unimarc field 128a\" cataloguing/value_builder/unimarc_field_124c.pl: \"unimarc field 124c\" cataloguing/value_builder/unimarc_field_124g.pl: \"unimarc field 124g\" cataloguing/value_builder/unimarc_field_123f.pl: \"unimarc field 123g\" cataloguing/value_builder/unimarc_field_115a.pl: \"unimarc field 115a\" cataloguing/value_builder/unimarc_field_4XX.pl: \"unimarc field 4\"+i+\"\" cataloguing/value_builder/unimarc_field_110.pl: \"unimarc field 110\" cataloguing/value_builder/unimarc_field_210c.pl: \"unimarc 225a\" cataloguing/value_builder/marc21_field_008.pl: \"unimarc field 100\" cataloguing/value_builder/unimarc_field_135a.pl: \"unimarc field 135a\" cataloguing/value_builder/unimarc_field_128c.pl: \"unimarc field 128c\" cataloguing/value_builder/unimarc_field_127.pl: \"unimarc field 127\" cataloguing/value_builder/unimarc_field_124.pl: \"unimarc field 100\" cataloguing/value_builder/marc21_field_008_authorities.pl: \"unimarc field 100\" cataloguing/value_builder/unimarc_field_123d.pl: \"unimarc field 123g\" cataloguing/value_builder/unimarc_field_140.pl: \"unimarc field 140\" cataloguing/value_builder/unimarc_field_60X.pl: \"unimarc 600\" cataloguing/value_builder/unimarc_field_122.pl: \"unimarc field 122\" cataloguing/value_builder/unimarc_field_116.pl: \"unimarc field 116\" cataloguing/value_builder/unimarc_field_128b.pl: \"unimarc field 128b\" cataloguing/value_builder/unimarc_field_123e.pl: \"unimarc field 123g\" cataloguing/value_builder/unimarc_field_121a.pl: \"unimarc field 121a\" cataloguing/value_builder/unimarc_field_700-4.pl: \"value builder\" cataloguing/value_builder/unimarc_field_117.pl: \"unimarc field 117\" cataloguing/value_builder/unimarc_field_123j.pl: \"unimarc field 123j\" cataloguing/value_builder/unimarc_field_121b.pl: \"unimarc field 121b\" cataloguing/value_builder/unimarc_field_124f.pl: \"unimarc field 124f\" cataloguing/value_builder/marc21_leader_video.pl: \"unimarc field 100\" cataloguing/value_builder/marc21_field_006.pl: \"unimarc field 100\" cataloguing/value_builder/unimarc_field_126b.pl: \"unimarc field 126b\" cataloguing/value_builder/unimarc_field_124e.pl: \"unimarc field 124e\" cataloguing/value_builder/marc21_field_007.pl: \"unimarc field 100\" cataloguing/value_builder/unimarc_field_115b.pl: \"unimarc field 115b\" cataloguing/value_builder/unimarc_field_126a.pl: \"unimarc field 126a\" cataloguing/value_builder/unimarc_field_123i.pl: \"unimarc field 123i\" cataloguing/value_builder/unimarc_field_130.pl: \"unimarc field 130\" cataloguing/value_builder/unimarc_field_124a.pl: \"unimarc field 124a\" cataloguing/value_builder/unimarc_leader.pl: \"unimarc field 100\" cataloguing/value_builder/unimarc_field_123g.pl: \"unimarc field 123g\" cataloguing/value_builder/unimarc_field_123a.pl: \"unimarc field 123a\" cataloguing/value_builder/unimarc_field_126.pl: \"unimarc field 100\" cataloguing/value_builder/unimarc_field_141.pl: \"unimarc field 141\" cataloguing/value_builder/unimarc_field_125a.pl: \"unimarc field 125a\" cataloguing/value_builder/unimarc_field_700_701_702.pl: \"unimarc 700\" cataloguing/value_builder/unimarc_field_100.pl: \"unimarc field 100\" cataloguing/value_builder/marc21_leader_computerfile.pl: \"unimarc field 100\" cataloguing/value_builder/unimarc_field_124d.pl: \"unimarc field 124d\" cataloguing/value_builder/marc21_leader.pl: \"unimarc field 100\" cataloguing/value_builder/labs_theses.pl: \"unimarc field 328\" cataloguing/value_builder/unimarc_field_106.pl: \"unimarc field 106\" cataloguing/value_builder/unimarc_field_105.pl: \"unimarc field 105\" koha-tmpl/intranet-tmpl/prog/en/includes/error-top.inc: "Koha Help" koha-tmpl/intranet-tmpl/prog/en/modules/cataloguing/value_builder/labs_these s.tmpl: "Koha Help" koha-tmpl/intranet-tmpl/prog/en/modules/cataloguing/addbiblio.tmpl: "value builder" koha-tmpl/intranet-tmpl/prog/en/modules/cataloguing/addbiblio.tmpl: "value builder" koha-tmpl/intranet-tmpl/prog/en/modules/cataloguing/additem.tmpl: "value builder" koha-tmpl/intranet-tmpl/prog/en/modules/authorities/searchresultlist.tmpl: "Koha Help" koha-tmpl/intranet-tmpl/prog/en/modules/authorities/detail.tmpl: "Koha Help" koha-tmpl/intranet-tmpl/prog/en/modules/authorities/authorities.tmpl: "value builder" koha-tmpl/intranet-tmpl/prog/en/modules/authorities/authorities-home.tmpl: "Koha Help" koha-tmpl/intranet-tmpl/prog/en/modules/tools/holidays.tmpl: "Koha Help" koha-tmpl/intranet-tmpl/prog/en/modules/tools/inventory.tmpl: 'Catalogue -- Biblio ' ????????? >> By the way, is window name used anywhere as target of any kind or simply replacing by underscores will do the thing? Hope it helps, and being helped... Ignacio Javier Gómez Rodríguez Área de Consultoría Tfno: 902905590 - Fax: 981571425 ignacio.gomez(a)coremain.com www.coremain.com

1 0

updates to koha3 nozebra search indexing for MARC21
by Mason James 21 Dec '07

21 Dec '07

Hi koha-devel people, Ive been updating the marc index mapping for koha3-nozebra. The French team did a nice job on the UNIMARC stuff and ive had a go at padding out the currently pretty minimal MARC21 mapping. FYI: the *'s are wildcards, so, subject = '600*' means all 600 level subfields are used, when doing a 'subject' search any obvious errors or suggestions? thd, how does this look to your sharp arnd eagle-like gaze? ------------------------------------------------------------------------ ------------------------------------------------- 'title' => '210a,222a,240a,243a,245a,245b,246a,246b,247a,247b,250a, 250b,440a', 'author' => '100a,110a,245c,600a,610a,611a,700a710a,711a,800a,810a, 811a', 'isbn' => '020a', 'issn' => '022a', 'lccn' => '010a', 'biblionumber => '999c', 'itemtype' => '942c', 'publisher' => '260b', 'date' => '260c', 'note' => '500a, 501a,504a,505a,508a,511a,518a,520a,521a,522a,524a, 526a,530a,533a,538a,541a,546a,555a,556a,562a,563a,583a,585a,582a', 'subject' => '600*,610*,611*,630*,650*,651*,653*,654*,655*,662*,690*', 'dewey' => '082', 'bc' => '952p', 'host-item' => '952a,952c' ------------------------------------------------------------------------ ------------------------------------------------- Cheers, Mason -- Mason James mason.james(a)liblime.com Programmer www.liblime.com LibLime +64 21 542 117

5 5

C4 and date formats
by Ryan Higgins 21 Dec '07

21 Dec '07

Hey folks Just looking for a quick consensus on passing dates to C4 modules. Some expect iso, some expect local format. memberentry.pl is currently not working because the date is double iso'ed... I suggest the coding guideline that scripts maintain the date in local syspref-defined format, and that all public methods in C4::* should expect dates to be passed in local format. So format_date_in_iso should be rare at the script level. comments ? -- Ryan Higgins LibLime * Open-Source Solutions for Libraries Featuring KohaZOOM ILS 888-564-2457 x704

5 4

koha.org and kohadocs.org
by Bünzli Daniel 21 Dec '07

21 Dec '07

Both sites are routinely unavailable from this part of the world (europe). This is quite annoying (git.koha.org is, however, always up). Best, Daniel

5 8

Error message from bulkmarcimport.pl
by Bradley Peters 18 Dec '07

18 Dec '07

Hello, I was poking around the installation of koha that I made using the tarball linked earlier by Galen Charlton. Once I got the install done and entered some settings I tried to use the bulkmarcimport.pl command. Which failed with the following message: Undefined subroutine &main::GetMarcFromKohaField called at ./bulkmarcimport.pl line 219. I haven't figured out how to setup the Zebra index yet because the examples I've looked at so far all refer to there being records, but I don't have any yet. I was hoping that maybe running this command would give me some useful hints. Regards, Bradley Peters

6 13