Re: [Koha] Can't call method "subfield" on an undefined value at /usr/share/koha/lib/C4/Biblio.pm line 2919.

2012-04-18 Thread MJ Ray
Vikas Salunkhe
> i am trying to  edit items and click save changes following error is
> comming
> 
> Software error:
> 
> Can't call method "subfield" on an undefined value at
> /usr/share/koha/lib/C4/Biblio.pm line 2919.

That often signifies an encoding problem in the title tag.  Check
the record.  If you'd like more help, you'll probably need to tell
people where to obtain the record from or how to recreate it.

That error probably should be trapped better, but there are tons
of possible encoding errors and just when we think we got them all...

Hope that helps,
-- 
MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op.
http://koha-community.org supporter, web and library systems developer.
In My Opinion Only: see http://mjr.towers.org.uk/email.html
Available for hire (including development) at http://www.software.coop/
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Koha 4 timeframe

2012-04-18 Thread Ian Walls
We haven't nailed this down with any finality as a community, but the
general idea is that when Solr search indexing is ready, we'll bump from
the 3.X line to 4.0.  Hopefully, that will be soon, like April or Oct of
2013.


-Ian

On Tue, Apr 17, 2012 at 04:01, Chris Cormack wrote:

> On 17 April 2012 11:22, clint.deckard 
> wrote:
> > Greetings,
> > I seem to recall a small discussion at some stage during Kohacon 2010
> about
> > the path to Koha 4, does anyone have anything further on this?
> > An update of perl was floated?
> >
> As far as I know it doesn't exist anywhere :)
>
> 3.8.0 will be released april 23, 3.10.0 will follow in October.
>
> http://koha-community.org/about/release-schedule/
> http://koha-community.org/roles-koha-3-10-0/
>
> Not sure when 4.0.0 would be, maybe April next year, we currently
> require a minimum of perl 5.10 (up from 5.8 in 3.2)
> so upgrading the minimum perl version doesn't mean we have to jump a
> major number.
>
> Chris
> ___
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> http://lists.katipo.co.nz/mailman/listinfo/koha
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha


[Koha] Fwd: Re: File names

2012-04-18 Thread Lenora Oftedahl
Here is what we found while solving the difficulty of our search results not 
showing even though records were there.

>From the tips & tricks: search info page 
>(http://wiki.koha-community.org/wiki/Search_Info )  Didn't understand much of 
>what was said here, but the last few words are a link to "a different post".  
>So, found the file names here (http://www.len.ro/work/koha-search-2/ ) and the 
>IT person helping though to look at the actual files to see what was in them.  
>I sent them to her to check to make sure permissions matched for running the 
>files. We've had issues with permissions before. 

This is what she found:
*

Here is  /etc/koha/zebradb/marc_defs/marc21/biblios/record.abs 

Not sure why melm 090 is commented out. ??


# This is a fairly simple example of a set of MARC21 indexing rules. It
# results in a server which provides a passable Bath level 0 and 1 service
# (author, title, subject, keyword and exact services). Feel free to
# elaborate on it, and if you do, please consider sharing your additions.
# NOTE: This is designed to be used with the grs.marcxml input filter
# for ISO2709 (ANSI Z39.2) or grs.xml for MARCXML-formatted records. It
# won't work for the old grs.marc input filter, which yields a different
# internal structure.
encoding utf-8
name marc21
attset bib1.att
attset gils.att
esetname F @
esetname B @

marc usmarc.mar
systag sysno rank
xpath enable
# Some notes:
# pl = Published Place
# ta = Target Audience 002/22
# ff8-23
# lf = Literary Form 008/33
# bio = Biography 008/34
# fmt = Format
# ln = Language
# ctype = Content type: review, catalog, encyclopedia, dictionary
# pubdate Publication Date
# rtype =  Record type (leader 06)
#
# Date indexing in Koha 3.0 for MARC21:
# Index   Expected format Notes
# date-entered-on-file[yymmdd](008/0-5, indexed in word and sort 
indexes)
# copydate[]  (260$c, indexed in word and sort 
indexes)
# acqdate [-mm-dd](952$d, indexed in date,word,sort 
indexes)
# pubdate []  (008/7-10, indexed in 
year,word,num,sort indexes)

all any
# melm 000  rtype:n:range(data,06,1),Bib-level:w:range(data,07,01)
xelm /record/leader 
llength:w:range(data,0,5),rtype:w:range(data,6,1),Bib-level:w:range(data,7,1)
# example: xelm /record/leader l1:w:range(data,0,5),l2:w:range(data,10,2)

melm 001Control-number
melm 005Date/time-last-modified
melm 007
Microform-generation:n:range(data,11,1),Material-type,ff7-00:w:range(data,0,1),ff7-01:w:range(data,1,1),ff7-02:w:range(data,2,1),ff7-01-02:w:range(data,0,2)

melm 008
date-entered-on-file:n:range(data,0,5),date-entered-on-file:s:range(data,0,5),pubdate:w:range(data,7,4),pubdate:n:range(data,7,4),pubdate:y:range(data,7,4),pubdate:s:range(data,7,4),pl:w:range(data,15,3),ta:w:range(data,22,1),ff8-23:w:range(data,23,1),ff8-29:w:range(data,29,1),lf:w:range(data,33,1),bio:w:range(data,34,1),ln:n:range(data,35,3),ctype:w:range(data,24,4),Record-source:w:range(data,39,0)

melm 010LC-card-number,Identifier-standard
melm 011LC-card-number,Identifier-standard
melm 015
BNB-card-number,BGF-number,Number-db,Number-natl-biblio,Identifier-standard
melm 017Number-legal-deposit,Identifier-standard
melm 018Identifier-standard
melm 020$a  ISBN:w,Identifier-standard:w
melm 020Identifier-standard
melm 022$a  ISSN:w,Identifier-standard:w
melm 022Identifier-standard
melm 023Identifier-standard
melm 024$a  Identifier-other
melm 024Identifier-standard
melm 025Identifier-standard
melm 027Report-number,Identifier-standard
melm 028Number-music-publisher,Identifier-standard
melm 030CODEN,Identifier-standard
#melm 033   Date
melm 034Map-scale
#melm 035   Local-number,Identifier-standard
melm 037Identifier-standard,Stock-number
melm 040Code-institution,Record-source
melm 041$a  ln
melm 041$d  ln
melm 041$e  ln
melm 041$j  ln
melm 043Code-geographic
#melm 046   pubdate
melm 050$b  LC-call-number:w,LC-call-number:p,LC-call-number:s
melm 050LC-call-number:w,LC-call-number:p,LC-call-number:s
melm 052Geographic-class
melm 060NLM-call-number
melm 070NAL-call-number
melm 080UDC-classification
melm 082Dewey-classification:w,Dewey-classification:s
melm 086Number-govt-pub
#melm 942$k LC-card-number:s

## KOHA SPECIFIC
#melm 090$c Local-number:w
#Identifier-standard:w

{TRUNCATED}
**
So, we decided to uncomment the melm 090$c line.  Lo, and behold, our search is 
now functioning.  So, the question is, why is this line commented out on a 
fresh install?

Lenora
StreamNet Regional Librarian
Columbia River Inter-Tribal Fish Commission
___
Koha mailing list  ht

Re: [Koha] Fwd: Re: File names

2012-04-18 Thread Jared Camins-Esakov
Lenora,


Here is what we found while solving the difficulty of our search results
> not showing even though records were there.
> [snip]
> So, we decided to uncomment the melm 090$c line.  Lo, and behold, our
> search is now functioning.  So, the question is, why is this line commented
> out on a fresh install?
>

The reason the 090 line is commented out is that Koha doesn't use 090 for
biblionumbers anymore. 090 is generally used for local call numbers, which
are not suitable alternatives to biblionumbers (which Koha stores by
default in 999$c). Did you upgrade from 2.something?

Regards,
Jared

-- 
Jared Camins-Esakov
Bibliographer, C & P Bibliography Services, LLC
(phone) +1 (917) 727-3445
(e-mail) jcam...@cpbibliography.com
(web) http://www.cpbibliography.com/
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha


[Koha] Reports error message

2012-04-18 Thread Hillyard, Cecil
Hi,

I was trying to run a report that came from the report library,
"Complete shelf list".   It throws back an error message 

The following error was encountered:
The database returned the following error: 
 1
Please check the log for further details.

What is wrong with the report?

Thanks,
__
Cecil Hillyard
Cataloger
Washoe County Library Technical Services
P.O. Box 2151
301 S. Center St.
Reno, NV 89505
tel.: 775-327-8338 or 775-327-8330
fax: 775-327-8334
www.washoecountylibrary.us





___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Reports error message

2012-04-18 Thread Hillyard, Cecil
Nevermind.  I fixed it.  There were extra spaces at the beginnings of
lines.

__
Cecil Hillyard
Washoe County Library
-Tel: 775-327-8338 or 7750-327-8330
fax: 775-327-8334


_
From: Hillyard, Cecil 
Sent: Wednesday, April 18, 2012 9:13 AM
To: koha@lists.katipo.co.nz
Subject: Reports error message


Hi,

I was trying to run a report that came from the report
library, "Complete shelf list".   It throws back an error message 

The following error was encountered:
The database returned the following error: 
 1
Please check the log for further details.

What is wrong with the report?

Thanks,
__
Cecil Hillyard
Cataloger
Washoe County Library Technical Services
P.O. Box 2151
301 S. Center St.
Reno, NV 89505
tel.: 775-327-8338 or 775-327-8330
fax: 775-327-8334
www.washoecountylibrary.us





___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha


[Koha] KohaCon 12 fishing trip

2012-04-18 Thread Wagner, Jane
Planning is underway for all aspects of KohaCon 12
(http://koha-community.org/kohacon12/), including some recreational
excursions.  At MJ Ray's request during today's planning meeting, I'm
sending out a message to let people know that an ocean fishing trip is
proposed:

http://koha-community.org/kohacon12-fishing-trip/

If you're interested in ocean fishing and Scottish coastal scenery, here's
your chance.  The deadline to sign up for the trip is April 30.

Jane Wagner
Senior Project Manager
LibLime, a division of PTFS
Content Management and Library Solutions
11501 Huff Court
North Bethesda, MD  20895
(301) 654-8088 x 151
jwag...@liblime.com
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha


[Koha] Local call number

2012-04-18 Thread Paula Corman
I am embarking on cataloging about 400 CD's and I want to use a locally 
assigned call number.  It appears from the MARC records I have examined that 
libraries are using the 09X field.  However, the template for the version of 
Koha that this library uses does not have that option.  Can someone please tell 
me what to do to add this field to the Koha template?  I do not have a systems 
person and/or programmer who can help, so if possible, please keep the 
directions simple.  Thanks.

Paula Corman |  Acting Librarian |  MIM-Musical Instrument Museum
4725 East Mayo Boulevard  |  Phoenix, AZ 85050  |  480.478.6000 main  |  
480.245.6906 direct
480.471.8690 fax  |  paula.cor...@themim.org  |  
www.themim.org

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha


[Koha] Itherm 280 receipt printers with Koha Circulation

2012-04-18 Thread Randy Smith
Our library consortium is preparing to go live with Koha next week.  We 
want to print receipts for checkout, etc. using our Itherm 280 receipt 
printers, but have searched in vain for any available configuration 
instructions or advice.  Is anyone using Itherm 280 receipt printers for 
patron checkout, hold slips, etc.?  Any help is greatly appreciated.


Randy Smith
Lewiston City Library
208. 743-6519
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Itherm 280 receipt printers with Koha Circulation

2012-04-18 Thread Bernardo Gonzalez Kriegel
Hi Randy,
I think there are two problems: how to print and what to print.

If you can register your thermal printer as a standard windows printer,
capable to print a web page from a browser, then this link can help you:

http://www.nexpresslibrary.org/go-live/configure-your-receipt-printers/

Next, what is printed in the circulation slip is basically in the file

$KOHA_DIR/intranet/htdocs/intranet-tmpl/prog/en/modules/members/
moremember-print.tt

that file could be tailored to your needs (logo, etc), handled with care by
someone who understand html.
It's a sort of html file, but not quite. It's used by Koha to generate the
html of the receipt.

Hope that helps

-- 
Bernardo Gonzalez Kriegel
bgkrie...@gmail.com



On Wed, Apr 18, 2012 at 7:34 PM, Randy Smith  wrote:

> Our library consortium is preparing to go live with Koha next week.  We
> want to print receipts for checkout, etc. using our Itherm 280 receipt
> printers, but have searched in vain for any available configuration
> instructions or advice.  Is anyone using Itherm 280 receipt printers for
> patron checkout, hold slips, etc.?  Any help is greatly appreciated.
>
> Randy Smith
> Lewiston City Library
> 208. 743-6519
> __**_
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> http://lists.katipo.co.nz/**mailman/listinfo/koha
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha


[Koha] Seeking Pacific Island Koha users

2012-04-18 Thread Pamela Bidwell
Dear Koha users,

I would like to hear from users of Koha in the Pacific Islands.

Many small Pacific countries struggle with extra issues when automating their 
libraries, such as unexpected power outages (and damaging power surges), 
intermittent and slow Internet access, old technology and limited IT expertise. 
For many Pacific libraries, Koha is their first automated system, and staff 
training is a real issue. Quite a few Pacific Koha projects have stalled as a 
result of these problems.

We need to develop a supportive local community that shares knowledge and 
offers support.

I hope to set up a smaller discussion forum for the Pacific Koha community 
(while still being involved in the wider Koha community discussions). The forum 
will talk about day to day use of Koha, answer basic questions about using the 
system and share resources such as training materials. I would also like to 
discuss regional training possibilities.

Please email me at: pamela.bidw...@usp.ac.fj 
if you would like to be involved.

I hope to hear from you soon.

Regards
Pam Bidwell, Lecturer Library/Information Studies
School of Education
The University of the South Pacific
Laucala Campus, Suva, FIJI
Tel. (679) 323 2829
Fax: (679) 323 1528
Email: pamela.bidw...@usp.ac.fj
L/IS program website: 
www.usp.ac.fj/library_studies
PacLibEd discussion forum: http://staff.usp.ac.fj/mailman/listinfo/paclibed

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha


[Koha] marc framework and importing records

2012-04-18 Thread smurfett

Hi

We're a small school library and don't really need all the fields used in 
MARC records.  But I would like to import my marc records using the import 
perl script.  I was wondering, if I edit the BOOK MARC framework for 
example, and delete fields that we don't really care about (for example the 
00 fields?) will I run into a problem when I import records?


Put another way, if I import records all from the Library of Congress for 
example, using the import script, will the script fail if the field is not 
defined in my framework?


nancy
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha


[Koha] Custom call-number schemes

2012-04-18 Thread Peter Aronson
Hi,

We're a very specialized library dealing with a very narrow range of subjects, 
so we've created our own classification/call-number system. I'd just like to 
make sure we're doing it right: We've created something like CALLNUM as an 
authorized values category, and then we're putting our general call number 
heading (e.g. BC1100) as the Authorized Value, and then 
"Reference--Dictionaries" as the Description and the Description (OPAC). And 
then we've mapped CALLNUM as a mandatory field on our Marc framework.

Does it sound like we're doing this the right way?

Thanks,
Peter Aronson
DGL Library, India
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha