Re: Koha - copyright date

Bernadette Cassidy said:
> Since the upgrade of Koha to version 2.0, I've noticed when adding new
> items that Koha doesn't display the publication date - see attached
> catalogue record. Does anyone know why?!

What do you have mapped to biblio.copyrightdate?  (Should be 260c if
you're using MARC21.)

--

-- 
Stephen Hedges
Skemotah Solutions, USA
www.skemotah.com  --  shedges@...

How to get MARC biblio export to work?

Hi all

I installed Koha last weekend. Installation went fine, its a nice 
program. Im evaluating it for use by the Royal Society of NSW's library.
http://nsw.royalsoc.org.au so thought I'd better join the list.

Most things seems to be working fine. I have gone through and setup most 
of the things in the "System parameters". I tried the "MARC biblio 
export" and as it says "leave blank to export every biblio" thats what I 
did. I had loaded the sample data and so I have biblio info in there - I 
can search for and find it. But when I click Export it just saves an 
empty 'marc.pl' file. I expected lots of MARC stuff.

If I goto: koha/intranet/cgi-bin/export and try

export$ perl -I /home/rsnsw/koha/intranet/modules ./marc.pl

I get:

DBI connect(':','',...) failed: Access denied for user: 
'mikel <at> localhost' (Using password: NO) at 
/home/rsnsw/koha/intranet/modules/C4/Context.pm line 368
DBI connect(':','',...) failed: Access denied for user: 
'mikel <at> localhost' (Using password: NO) at 
/home/rsnsw/koha/intranet/modules/C4/Context.pm line 368
Can't call method "selectrow_array" on an undefined value at 
/home/rsnsw/koha/intranet/modules/C4/Context.pm line 320.
export$

What should I try/look at to solve this?

Re: How to get MARC biblio export to work?

Hi again

One more bit of info that is prob important.

Michael Lake wrote:
> If I goto: koha/intranet/cgi-bin/export and try
> export$ perl -I /home/rsnsw/koha/intranet/modules ./marc.pl
> 
> I get:
> 
> DBI connect(':','',...) failed: Access denied for user: 
> 'mikel <at> localhost' (Using password: NO) at 
> /home/rsnsw/koha/intranet/modules/C4/Context.pm line 368
> DBI connect(':','',...) failed: Access denied for user: 
> 'mikel <at> localhost' (Using password: NO) at 
> /home/rsnsw/koha/intranet/modules/C4/Context.pm line 368
> Can't call method "selectrow_array" on an undefined value at 
> /home/rsnsw/koha/intranet/modules/C4/Context.pm line 320.
> export$

The mikel above is my login name for the laptop running Koha. The name 
of the Administrator for using the Intranet part is a different name.
I have a .my.cnf file in my root dir which provides shell access to 
MySQL so the script should be able to access the koha database. I can 
access it via mysql at the command line as mikel.

Mike
--

-- 
Mike Lake
Caver, Linux enthusiast and interested in anything technical.

Koha future

Hi all,

I tried to put all suggestions for Koha future into a wiki page.
It's on :
http://www.saas.nsw.edu.au/koha_wiki/index.php?page=KohaRoadmap2.2.x

I merged 2.2.x and 2.4.0 features. But the table shows in which version 
it should be done. Feel free to complete this page, I will add features 
myself if you post only on this list.

--

-- 
Paul POULAIN
Consultant indépendant en logiciels libres
responsable francophone de koha (SIGB libre http://www.koha-fr.org)

2.0.0 release date

Hi,

My goal here is to ask for a 2.0.0 release date. It may sound strange to 
have the Release Manager asking users for a release date, but let me 
explain :
The 2.1.3 works fine since some weeks in EMN, in France.
My opinion is that the 2.1.3 can be used in production. Not 100% bug 
free with a UNIMARC DB, but works.
The question is : how works 2.1.3 with a MARC21 installation ?
Important question, but I don't know it's answer yet. Nelsonville or 
Katipo, did you do some tests ?

So, when do you think I could publish a 2.2.0RC1 in the stable tree ?

My opinion is ASAP : I don't want to wait for months like I did for 
2.0.0. As I said previously, I realize delaying the 2.0.0 version had a 
very bad effect on french libraries, that didn't want to install 
2.0.0RCx, thinking it was too unstable.
The DB schema didn't change from 2.1.2 to 2.1.3 and still has no change. 
I think this is the most important point : the DB IS stable, so Koha is 
on the road to be stable.
Feel free to argue if you don't agree & have any other opinion/idea.

--

-- 
Paul POULAIN
Consultant indépendant en logiciels libres
responsable francophone de koha (SIGB libre http://www.koha-fr.org)

Re: How to get MARC biblio export to work? 2.0.1RC1

On 2004-11-02 06:26:25 +0000 Michael Lake <Mike.Lake@...> wrote:

[...]
> loaded the sample data and so I have biblio info in there - I can 
> search for 
> and find it. But when I click Export it just saves an empty 'marc.pl' 
> file. I 
> expected lots of MARC stuff.

I'll take a look at this when testing 2.0.2beta0. It used to work.

> If I goto: koha/intranet/cgi-bin/export and try
> 
> export$ perl -I /home/rsnsw/koha/intranet/modules ./marc.pl
> I get:
> DBI connect(':','',...) failed: Access denied for user: 
> 'mikel <at> localhost' 
> (Using password: NO) at 
> /home/rsnsw/koha/intranet/modules/C4/Context.pm line 
> 368

You may need to put KOHACONF=/hoem/rsnsw/koha.conf on the start of 
that line, as it looks like Context.pm isn't finding the login 
details. This is a direct connect, so I think my.cnf hasn't anything 
to do with it.

--

-- 
MJR/slef    My Opinion Only and not of any group I know
  Creative copyleft computing - http://www.ttllp.co.uk/
  Unsolicited attachments to the pipex address deleted

Re: 2.0.0 release date

Hi Paul,

On Tue, 2004-11-02 at 11:32 +0100, Paul POULAIN wrote:
> Hi,
> 
> My goal here is to ask for a 2.0.0 release date.
                               ^^^^^

Err... you mean 2.2.0... ? 

> The question is : how works 2.1.3 with a MARC21 installation ?

I am test running 2.1.3 at my installation (WBUT) and we are on MARC21.
So far it looks good. 

I have a question, with L10N support on Koha, is there a specific reason
why the default charset defined in the meta tags is iso-8859-1 and not
utf-8?

I needed to change it to utf-8 for BN translated templates and include
files.

I did get a funny bug cropping up while testing the BN translation of
Koha. A particular vowel used as conjunct was being rendered in the
drop-down list as U+8249 unicode codepoint, whereas the data is
correctly stored in the MySQL db (v4.0.20) and displayed correctly when
viewed through phpmyadmin interface.

The bug shows up both on Konqueror 3.3.0 as well as cvs Mozilla 1.8a5. I
have checked and its not a widget rendering problem as the same vowel

Re: 2.0.0 release date

Considering Open Source Software ( for lib. article smecc got a mention)

Re: How to get MARC biblio export to work? 2.0.1RC1

MJ Ray wrote:
> On 2004-11-02 06:26:25 +0000 Michael Lake <Mike.Lake@...> wrote:
> 
> [...]
> 
>> loaded the sample data and so I have biblio info in there - I can 
>> search for and find it. But when I click Export it just saves an empty 
>> 'marc.pl' file. I expected lots of MARC stuff.
> 
> 
> I'll take a look at this when testing 2.0.2beta0. It used to work.
> 
>> If I goto: koha/intranet/cgi-bin/export and try
>>
>> export$ perl -I /home/rsnsw/koha/intranet/modules ./marc.pl
>> I get:
>> DBI connect(':','',...) failed: Access denied for user: 
>> 'mikel <at> localhost' (Using password: NO) at 
>> /home/rsnsw/koha/intranet/modules/C4/Context.pm line 368
> 
> 
> You may need to put KOHACONF=/hoem/rsnsw/koha.conf on the start of that 
> line, as it looks like Context.pm isn't finding the login details. This 
> is a direct connect, so I think my.cnf hasn't anything to do with it.

My koha.conf is still in /etc/koha.conf
I see in Context.pm that there is
	"use constant CONFIG_FNAME => "/etc/koha.conf";
so that should be fine.
The koha directory is under a /home/rsnsw/ user.

I can see though that /etc/koha.conf wasn't readable by the user rsnsw 
so I have changed for now the permissions of koha.conf to be readable 
(it's not a production system yet).
I no longer get the DBI connect error. I get:
Can't locate object method 'config' via package C4::Context at Output.pm 
line 78. I can see that config is a defined method in Context.pm and 
there is a 'use Context;' in Output.pm so it should have found it.

The error is prob something else unrelated.
I'd best get some real work done and get back to looking at this later 
 Any ideas in the meantime appreciated.

Mike
-- 
Michael Lake
Chemistry, Materials & Forensic Science, UTS
Ph: 9514 1725 Fx: 9514 1460

--

-- 
UTS CRICOS Provider Code:  00099F
DISCLAIMER: This email message and any accompanying attachments may contain
confidential information.  If you are not the intended recipient, do not
read, use, disseminate, distribute or copy this message or attachments.  If
you have received this message in error, please notify the sender immediately
and delete this message. Any views expressed in this message are those of the
individual sender, except where the sender expressly, and with authority,
states them to be the views the University of Technology Sydney. Before
opening any attachments, please check them for viruses and defects.