new()

new_from_usmarc( $marcblob [, \&filter_func($tagno,$tagdata)] )

The "wanted_func()" is optional. See MARC::File::USMARC::decode for details.

title()

title_proper()

author()

edition()

publication_date()

fields()

field( tagspec(s) )

The field specifier can be a simple number (i.e. "245"), or use the "." notation of wildcarding (i.e. subject tags are "6..").

subfield( $tag, $subfield )

  my $title = $marc->field('245')->subfield("a");
  my $title = $marc->subfield('245',"a");

If either the field or subfield can't be found, "undef" is returned.

append_fields( @fields )

    my $field = MARC::Field->new('590','','','a' => 'My local note.');
    $record->append_fields($field);

Returns the number of fields appended.

insert_fields_before( $before_field, @new_fields )

    my $before_field = $record->field('260');
    my $new_field = MARC::Field->new('250','','','a' => '2nd ed.');
    $record->insert_fields_before($before_field,$new_field);

insert_fields_after( $after_field, @new_fields )

insert_fields_ordered( @new_fields )

insert_grouped_field( $field )

    my $field = MARC::Field->new( '510', 'Indexed by Google.' );
    $record->insert_grouped_field( $field );

For example, if a '650' field is inserted with "insert_grouped_field()" it will be inserted at the end of the 6XX group of tags. After discussion most people wanted the ability to add a new field to the end of the hundred group where it belonged. The reason is that according to the MARC format, fields within a record are supposed to be grouped by block (hundred groups). This means that fields may not necessarily be in tag order.

delete_fields( $field )

    # delete all note fields
    my @notes = $record->field('5..');
    $record->delete_fields(@notes);

delete_fields() will return the number of fields that were deleted.

delete_field()

as_usmarc()

as_formatted()

leader()

encoding()

If you want to set the encoding for a MARC::Record object you can use the string values:

    $record->encoding( 'UTF-8' );

NOTE: MARC::Record objects created from scratch have an a default encoding of MARC-8, which has been the standard for years...but many online catlogs and record vendors are migrating to UTF-8.

WARNING: you should be sure your record really does contain valid UTF-8 data when you manually set the encoding.

set_leader_lengths( $reclen, $baseaddr )

clone()

    my $newmarc = $oldmarc;

This just makes a copy of the reference, not a new object. You must use the "clone()" method like so:

    my $newmarc = $oldmarc->clone;

You can also specify field specs to filter down only a certain subset of fields. For instance, if you only wanted the title and ISBN tags from a record, you could do this:

    my $small_marc = $marc->clone( 245, '020' );

The order of the fields is preserved as it was in the original record.

warnings()

    my @warnings = $record->warnings();

The warnings are items that you might be interested in, or might not. It depends on how stringently you're checking data. If you're doing some grunt data analysis, you probably don't care.

A side effect of calling warnings() is that the warning buffer will be cleared.

add_fields()

"add_fields()" adds MARC::Field objects to the end of the list. Returns the number of fields added, or "undef" if there was an error.

There are three ways of calling "add_fields()" to add data to the record.

1 Create a MARC::Field object and add it

  my $author = MARC::Field->new(
                100, "1", " ", a => "Arnosky, Jim."
                );
  $marc->add_fields( $author );
    

2 Add the data fields directly, and let "add_fields()" take care of the objectifying.

  $marc->add_fields(
        245, "1", "0",
                a => "Raccoons and ripe corn /",
                c => "Jim Arnosky.",
                );
    

3 Same as #2 above, but pass multiple fields of data in anonymous lists

  $marc->add_fields(
        [ 250, " ", " ", a => "1st ed." ],
        [ 650, "1", " ", a => "Raccoons." ],
        );