- Koha - lists.katipo.co.nz

ByWater Solutions and Software.coop Collaborating on Koha EDI Support
by Ian Walls 09 Nov '10

09 Nov '10

Dear Koha Community, It is our pleasure to announce that software.coop of Somerset, England and ByWater Solutions LLC of Santa Barbara CA, USA, are partnering to bring Electronic Data Exchange (EDI) to Koha. EDI will greatly increase the functionality of the acquisitions module of Koha by allowing a direct electronic exchange from one entity to another, making processes such as billing and the transmission of purchase orders seamless. It may optionally accept bibliographic records from a vendor, making cataloguing quicker. It was described in the journal "Program: electronic library and information systems" Vol. 44 No. 3, 2010. The EDI code, which was written by software.coop, will be rebased by ByWater Solutions on the current head of the Koha project. The rebased code will be submitted for possible inclusion in the 3.4 release of Koha. Cheers, -Ian -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls(a)bywatersolutions.com Twitter: @sekjal

6 6

General meeting on IRC: Wednesday, 10 November 2010 at 19:00 UTC+0
by Magnus Enger 09 Nov '10

09 Nov '10

Hi All Our next IRC meeting is on Wednesday, 10 November 2010 at 19:00 UTC+0 on the #koha irc channel on irc.katipo.co.nz. The agenda is here: http://wiki.koha-community.org/wiki/General_IRC_Meeting,_10_November_2010 Currently the agenda looks like this: * Update on Roadmap to 3.2 * Update on Roadmap to 3.0 * Update on Roadmap to 3.4 1. BibLibre branches submitted to QA (roadmap & what's still expected from BibLibre. feedback from librarians) * Community building : 1. RFCs agreement workflow (discussion about the workflow for RFCs to be accepted/validated) 2. git management (branches) 3. jqueryui adoption instead of YUI 4. proposal to form a Technical Committee * Follow-up on actions from General IRC Meeting, 6 October 2010. * Agree times of next meetings. Please feel free to edit the agenda to add any issues you would like to talk about, and feel free to attend the meeting using your favourite irc client. Best regards, Magnus

2 1

error with search.pl
by vimal laxman 09 Nov '10

09 Nov '10

Dear All, i had been running koha sucessfully for the past few months when i got this error last week.tried to fix it but having problems.hope somebody could help me with a solution.The error occurs when i search for an item in OPAC.the Apache error log for your reference. [Sun Nov 07 06:27:02 2010] [notice] Apache/2.2.8 (Debian) configured -- resuming normal operations [Tue Nov 9 14:28:12 2010] opac-search.pl: Undefined subroutine &main::getitemtypeimagelocation called at /usr/share/koha/opac/cgi-bin/opac/ opac-search.pl line 140. [Tue Nov 9 14:30:24 2010] opac-search.pl: Undefined subroutine &main::getitemtypeimagelocation called at /usr/share/koha/opac/cgi-bin/opac/ opac-search.pl line 140. regards, vimal

1 0

Report needed: Number of patrons circulating items in a month
by Kathy Rippel 09 Nov '10

09 Nov '10

3 3

(no subject)
by john smith 08 Nov '10

08 Nov '10

Hi to all I success in install koha 3.0.2 on Ubuntu 10 without any problems , every thing working with me fine except we have in our library more than 15 fields in items like ( library number , faculty , department ,.... beside the basics data in items , i am facing a problem in insert all of these data in item table , even when i created new column in items table and add new record , the mysql table items can't save it i don't know why just i'm asking about when i create new column into mysql tabel and make koha link that column and insert record , the column in table items still empty? can any one help me thanks John Smith Information Technology Specialist

1 0

EZProxy and Koha
by Bob Birchall ＠ Calyx 08 Nov '10

08 Nov '10

Can anyone confirm that EZProxy is being used in conjunction with Koha? Many thanks, Bob

2 1

enter batch of biblio records
by Priyadarsan kp 07 Nov '10

07 Nov '10

I am using koha version 3.2 in ubuntu 10.10 it is very happy to know that koha avilable in the debian repository deb http://debian.koha-community.org/koha squeeze main deb-src http://debian.koha-community.org/koha squeeze main I have customized marc biblio, about 15 entries including items. suppose i made csv file of some 100 books with this 15 columns, can i load this data into koha database. i found that biblio data go to 3 table namely biblio, items and biblioitems. we can directly load datainto biblio and items, you have to give increment to biblionumber, but biblioitems contains marc and marcxml as two data, which is a bit difficut to create. Is there a script to load data into the table biblioietms. -- Priyadarsan K. P. --------------Official Address------------ Lecturer in Mathematics, C. K. G. M. Govt. college, Perambra P. O., Kozhikode Kerala, 676525-PIN 919496166465 Mob 914962610243 off http://ckgmgovcollege.homelinux.com --------------Residential Address------------ Karattillam "Supriya", Kottur P. O. Naduvannur, Kozhikode-673614, Kerala, India. Ph: 91496 2652330

2 1

PDF of English Manual now available at koha-community.org
by Liz Rea 07 Nov '10

07 Nov '10

For those who wish to print the Koha 3.2 Manual, or have an offline copy, you can now download the full manual from http://www.koha-community.org/documentation as a PDF. PDF's of the French and Spanish translations are coming (very) soon, as well, and will be linked from that same URL. Please let me know if you have any issues with the online manual or PDF's. Big thanks to Reed Wade of Catalyst IT for helping get the process of converting from DocBook to PDF ironed out. Liz Rea

2 1

Authority linking problems with 650 records (TOPIC_TERM, local thesaurus)
by Doug Kingston 07 Nov '10

07 Nov '10

As Elaine pointed out in her earlier letter, we basically solved the our initial authority linking problem by fixing the 008 field, but this only fixed the "PERSO_NAME" authorities. Our TOPIC_TERM authority records were still not getting linked. These Names and Term authorities are locally maintained since the "regular" thesaurus's one might use like Library of Congress do not have the level of detail and specificity that this specialist resarch library requires (http://www.efdss.org/front/library-archive/about-the-vaughan-williams-memor…) We have this working now, but there were two issues. First and easiest to fix was that we were placing our TOPIC_TERMs in a 653 record, rather than a 650. C4::Heading::MARC21 has a table of bib_heading_fields, and 653 is not included. We researched 650 a bit and realized that we probably should just use that, but we wanted to be correct and not claim these terms were sourced from someplace like LC. So we created a 650, with a second indicator of '7' (other), and subfields 'a' set to the term, and '2' set to our library identifier 'UkLoVW'. When we tried to use link_bibs_to_authorities.pl, it failed to link these terms. Some debugging and generous printfs indicated that the problem was in the query against the Zebra index. Specifically, the problem was with the line: $limiters .= " AND Subject-heading-thesaurus=$self->{'thesaurus'}"; Commenting out this line (and thus the constraint that the entry in Zebra have a thesaurus of 'UkLoVW') solved the problem. Query before change: authorities:SimpleSearch(Match-heading,ext="Aberdeenshire" AND at='TOPIC_TERM' AND Heading-use-subject-added-entry=a AND Subject-heading-thesaurus=UkLoVW) Query after change: authorities:SimpleSearch(Match-heading,ext="Aberdeenshire" AND at='TOPIC_TERM' AND Heading-use-subject-added-entry=a) I don't know if this was the right thing to do and I suspect if I put in a patch to delete that line, it would be rejected. Here is an example (from marcdump) of one of our terms. This MARC was generated by a python program I wrote to convert from a bespoke term database to MARC so there could definitely be issues with this which I would happily fix. Comments are welcome. LDR 00234nz## 2200109n###### 001 AT-000001 003 UkLoVW 005 20101106220637.0 008 101106|ge|dz||aaan##########||||c###|d 035 _aAT-000001 040 _aUkLoVW _beng _cUkLoVW 150 _aAberdeen The real problem is why did Zebra not have our entries label with the correct thesaurus entry? Thiis code in C4::Heading/_query_limiters() looks a bit suspect anyways with lots of "FIXME" comments by someone. So where is the real problem - does Zebra need fixing? Our authority MARC records? Koha C4::Heading? What should we do to resolve this permanently? Regards, -Doug-

1 0

Opac Availability Limit to currently available items.
by Abdulsalam Yousef 07 Nov '10

07 Nov '10

Hello all, What about this problem *Availability* - *Limit to currently available items.<http://192.168.1.5:82/cgi-bin/koha/opac-search.pl?idx=kw&q=science&limit=av…> * doesn't work at all is there a solution for it ?? i'm facing this problem from the previous versions Thanks

1 0