problem with insert_grouped_field

I am having trouble using insert_grouped_field(). The code below returns a "Undefined subroutine &main::insert_grouped_field called at ./test line 11." As you can see from the code, I am testing for the version of the perl module I'm using and the program prints out the VERSION as 1.29. Suggestions

need help adding a 006

I am trying to add a Continuing Resource 006 field, conditionally, to an existing group of bib records. The program checks to see if a Continuing Resource exists, and if no, adds the default version of the field. Based on Example 17 in the MARC::Record tutorial, which adds a 005 field, I thought I

as formatted method with one line per field

Would it be possible to take advantage of the as_formatted method to print one line per field rather than one line per subfield? I personally would find the one line per field much more useful because the display is more compact and it would then allow you to do greps within a field. For instance

Re: [patch] Accept # as Blank Indicator

Quoting from "MARC 21 Specifications for Record Structure, Character Sets, and Exchange Media RECORD STRUCTURE", http://www.loc.gov/marc/specifications/specrecstruc.html#varifields "Indicators may be any ASCII lowercase alphabetic, numeric, or blank" Period. As mentioned by others, the '#' or '

Re: [patch] Accept Letters as Indicator

Yup, looks like it. This is a new one on me, who haven't really studied MARC since I escaped from MARBI in 1992. Maybe this is a USMARC->MARC 21 change, i.e. something that came in with MARC 21? Or was it a change in the ANSI or ISO standards? I don't think lowercase alphabetics were valid indicato

Re: MARC::Field::new_from_usmarc problems

It shouldn't really be necessary to have different flavors of MARC for this. Unlikes other leader positions, Base address of data is NOT defined to be implementation-specific or implementation-defined. Bytes 12/16 are supposed to contain base address of data, and in this case, simply appear to be i

working with mrc2xml.pl

Our sysadmin just got mrc2xml.pl installed for me and I'm trying to work with it. Have a coupla questions, if anyone can help. First, I thought, upon reading the documentation, that it would product xml output of bib records according to the current Library of Congress standard. But I don't think

Re: working with mrc2xml.pl

ortia Systems Coordinator 5000 TAMU Evans Library Texas A&M University College Station, TX 77843-5000 [EMAIL PROTECTED] 979-862-4234 979-845-6238 (fax) >>> "Anne Highsmith" <[EMAIL PROTECTED]> 03/09/04 10:04AM >>> Our sysadmin just got mrc2xml.pl installed for

Skipping batch erroneous record on batch input

I am reading a series of MARC records in from a file, making a small change, and printing them out to a revised file. At the end of my program I get an error message: Invalid indicators " a[4],18,130,149-388,397-398,391-194,403-404,397-548,579-5 80,551-554,585-596,745-979,[1],980,[1],981,[1],982,

RE: MARC::Record and UTF-8 & related threads

Sorry I didn't make it clear in my original posting that the record that I modifed, using MARC::Record, DID have unicode-encoding. I didn't just change the leader/09 to try to fool it into thinking it was Unicode; the record came out of a database that had been converted to Unicode. And the 245 fie

Re: web/news/rss for perl4lib

I was just reviewing some old emails, ran across this and checked out the url for the archives. Was a search interface ever created? Anne L. Highsmith Consortia Systems Coordinator 5000 TAMU Evans Library Texas A&M University College Station, TX 77843-5000 [EMAIL PROTECTED] 979-862-4234 979-845-

Re: Fwd: Module update for MARC::Record

There's a MARC::Record version with Unicode support that Ed Summers developed for us and gave the version number 2.0. We've been using it for quite a while. Might the latest, greatest need a 2.0.1 or something higher, perhaps? Anne L. Highsmith Consortia Systems Coordinator 5000 TAMU Evans Library

Re: Module update for MARC::Record

Based on datestamps of various scripts, looks like I received and tested it in May 2005 and started using it in production scripts in August 2005. Anne L. Highsmith Consortia Systems Coordinator 5000 TAMU Evans Library Texas A&M University College Station, TX 77843-5000 [EMAIL PROTECTED] 979-862

z39.50 queries to OCLC server

These questions may be more appropriate to another list, so if you have any suggestions as to where they should be re-directed, I'd appreciate it. I have 2 questions regarding sending z39.50 queries to the worldcat z39.50 server. 1. Using yaz or the perl z3950 module, is there any way to get the

Re: z39.50 queries to OCLC server

(local number) will work. > Use attribute 1211 may also work, but 12 is probably what you want. > http://www.oclc.org/support/documentation/z3950/searchtips/ > http://www.rlg.org/en/page.php?Page_ID=20985 > > I can't answer #1. > > --Andy > > On 8/22/07, Anne High

Question for voyager libraries

We use the Voyager ILS but we do not use their default perl installation. We have always used an "external" perl installation maintained by our computer center sysadmins and located in /usr/local. I have asked the sysadmin to install an additional perl module. She tells me that for various reas

Turning MARC record object back into a string

I am running a perl program that uses an API to update MARC records in an ILS. Voyager & BatchCat, for you Voyager folks. I have to pass a bunch of parameters to the API, of course, including the updated marc record as a string. The input record is UTF8, so the output must be also. Previously, I

RE: Turning MARC record object back into a string

Thanks to everyone who replied. And to all those who said I could simply use "my $new_marc = $bib_rec->as_usmarc();" you were correct. Now happily "MARCing" up more records.

Basic questions -- skipping records that don't pass muster

Through various programs, when I've been processing MARC records and found 1 that didn't pass muster (couldn't pass structural or character set requirements) I generally slogged through, found it, and fixed it. But now I have passed on some of my code to someone who doesn't have the time or the

Finding non-unicode characters

Can someone suggest a way to identify if a MARC record, coded at LDR/09 = ‘a’ has non-unicode characters in it? I tried the following, kind of grasping at straws, against a record that I know has non-unicode characters. It didn’t report any errors. # $bib_id is defined as 001 field