On Wed, Aug 27, 2003 at 09:15:25AM -0300, Brian Cassidy wrote:
> * normalize()
>
> inputs: either a MARC::Record object or a string. This should probably
> accept an arbitrary number of inputs so, you can do
>
> my @normrecs = normalize( @records );
>
> rather than
>
> my @normrecs;
> foreach m
From: Brian Cassidy [mailto:[EMAIL PROTECTED]
Subject: RE: NACO Normalization and Text::Normalize
> * normalize()
>
> inputs: either a MARC::Record object or a string. This should probably
> accept an arbitrary number of inputs so, you can do
> * compare()
>
> inputs: eithe
Hi Ed,
> I think this is a great idea. At first I was thinking that it would be
> nice to be able to pass your normalize() function a MARC::Record
object,
> which would magically normalize all the relevant fields (like a good
> cataloger). This could be a subclass MARC::Record::NACO which adds
Hi Brian: thanks for writing,
On Mon, Aug 25, 2003 at 04:29:37PM -0300, Brian Cassidy wrote:
> As part of a previous project I was importing MARC records into an RDBMS
> structure. In order to facilitate better searching, it was suggested to
> me that I do some normalization on my data and that NA
> -Original Message-
>
> > I now wonder if this code would have greater utility as a module on
> > CPAN.
>
> Yes, please! (You're not BRICAS on cpan.org, are you?)
Yes, I am BRICAS on CPAN...is that a bad thing? :)
> I would recommend putting it in the MARC::* namespace, since it's
> s
On Monday, August 25, 2003, at 03:29 PM, Brian Cassidy wrote:
The basis for this message is to get a feeling whether or not I should
submit a module that will do NACO normalization
(http://lcweb.loc.gov/catdir/pcc/naco/normrule.html) to CPAN.
[...]
So, away I went and came back with normalize() s
