Re: MARC::Record leader

2003-09-20 Thread Joshua Ferraro
Paul and folks, MARCgetbiblio is the sub in Biblio.pm that contains the SQL queries that are supposed to generate a MARC record. I use it thusly: my $MARCRecord = &MARCgetbiblio($dbh,$bibid); my $recordstring=$MARCRecord->as_usmarc(); When I use

Re: MARC::Record leader

2003-09-19 Thread Ed Summers
On Fri, Sep 19, 2003 at 07:58:01PM +0530, Saiful Amin wrote: > I never had to worry about the record_length (pos 00-04) or the > base_address (pos 12-16) in the leader. I think they are automagically > updated while writing the record via $rec->as_usmarc(). saiful++ Yes, they should be automatic

Re: MARC::Record leader

2003-09-19 Thread Saiful Amin
Hi Paul, > (notes i speak here of UNIMARC. loc is down at the moment, but i think > leaders are the same in marc21 and in unimarc) Since LoC is still down you can refer to http://search.cpan.org/src/PETDANCE/MARC-Record-1.29/etc/ecbdlist.html > So my question : > Am I wrong or could we add $rec

Re: MARC::Record leader

2003-09-19 Thread paul POULAIN
OK, i've a BIG problem with record leader. Joshua makes me discover that MARC::Record didn't set anything in the record leader ! I think he could (or there's smth I don't understand) pos 0-4 are "record length" => they could be calculated no ? pos10 is always 2 pos 12-16 should be calculated too

Re: MARC::Record leader

2003-09-12 Thread paul POULAIN
Joshua Ferraro wrote: Your code looks to be creating a bunch of fields each with one subfield in them. right 1/1 This is not correct. right 2/2 Furthermore, it is unlikely that the order that the subfields come back from MySQL is the order in which you will want to build your field...but I m

Re: MARC::Record leader

2003-09-11 Thread Chuck Bearden
On Thu, Sep 11, 2003 at 10:49:37AM -0500, Ed Summers wrote: > On Thu, Sep 11, 2003 at 08:40:48AM -0500, Chuck Bearden wrote: > > I hope this helps. > > This helps for the order of the fields, but from looking at his > program it looks like the more pernicious problem is the order of the > subfie

Re: MARC::Record leader

2003-09-11 Thread Ed Summers
On Thu, Sep 11, 2003 at 08:40:48AM -0500, Chuck Bearden wrote: > I hope this helps. This helps for the order of the fields, but from looking at his program it looks like the more pernicious problem is the order of the subfields within each field! //Ed

Re: MARC::Record leader -- notes field order

2003-09-11 Thread Jackie Shieh
On Thu, 11 Sep 2003, Chuck Bearden wrote: > > On Wed, Sep 10, 2003 at 05:30:37PM -0400, Joshua Ferraro wrote: > > On Wed, Sep 10, 2003 at 02:05:24PM -0500, Ed Summers wrote: > [...] > > > > > > The call to as_usmarc() will populate the record length for you. So you > > > shouldn't have to do it y

Re: MARC::Record leader

2003-09-11 Thread Chuck Bearden
On Wed, Sep 10, 2003 at 05:30:37PM -0400, Joshua Ferraro wrote: > On Wed, Sep 10, 2003 at 02:05:24PM -0500, Ed Summers wrote: [...] > > > > The call to as_usmarc() will populate the record length for you. So you > > shouldn't have to do it yourself when building a record on the fly. We're you > >

Re: MARC::Record leader

2003-09-10 Thread Joshua Ferraro
On Wed, Sep 10, 2003 at 02:05:24PM -0500, Ed Summers wrote: > On Wed, Sep 10, 2003 at 01:57:31PM -0400, Joshua Ferraro wrote: > > sub fetch_handler { > > my ($args) = @_; > > # warn "in fetch_handler"; ## troubleshooting > > my $offset = $args->{OFFSET}; > > $of

Re: MARC::Record leader

2003-09-10 Thread Ed Summers
On Wed, Sep 10, 2003 at 01:57:31PM -0400, Joshua Ferraro wrote: > sub fetch_handler { > my ($args) = @_; > # warn "in fetch_handler"; ## troubleshooting > my $offset = $args->{OFFSET}; > $offset -= 1; ## because $args->{OFFSET} 1 = record #1 >

MARC::Record leader

2003-09-10 Thread Joshua Ferraro
Hello everyone, I am new to this list. I'm also very new to Perl so please bear with me:-). I am working on a Z3950 Server for my library (which is using Koha for ILS) and I am having trouble generating MARC records using MARC::Record. I am generatingthe records from a MySQL database and I don't