Harvey Hahn wrote:
>
> Unfortunately, the most limiting aspect of the 24-character leader is
> that fact that only 5 digits (the first 5 characters of the leader) were
> specified as the maximum length of a MARC record. Manipulating the
> various possible values of specific positions in the leader
On Jun 25, 2008, at 7:27 PM, Hahn, Harvey wrote:
Eric Lease Morgan wrote:
Who ever heard of an indicator being longer than two characters long?
Byte 10 (zero origin) of the MARC leader specifies the number of
indicator characters. MARC21 and its predecessors have always
specified
2, but
You get the "invalid indicator" message with the FMT tag because ALEPH uses
it as a control field, with no subfields or indicators and MARC::Record is
treating it as a variable field (it's making the assumption that unless a
tag is a control tag, ie < 010, a field should have indicators and
subfie
Eric Lease Morgan wrote:
|Who ever heard of an indicator being longer than two characters long?
Byte 10 (zero origin) of the MARC leader specifies the number of
indicator characters. MARC21 and its predecessors have always specified
2, but the possible range is 0 to 9. The 24-character leader is
On Jun 25, 2008, at 4:37 PM, Steve Oberg wrote:
Ok. What's allowable/possible vs. what is actually defined as part of
variable MARC data fields in say MARC21. I'm amused by the
hairsplitting. The bottom line is these particular fields are ALEPH
specific and are not part of MARC21. I agree with
Ok. What's allowable/possible vs. what is actually defined as part of
variable MARC data fields in say MARC21. I'm amused by the
hairsplitting. The bottom line is these particular fields are ALEPH
specific and are not part of MARC21. I agree with others that
accounting for these in whatever parsi
I believe that alpha characters for field names ARE legal according to
(most of the various) MARC standard(s). But they are not generally used
in library MARC data.
Jonathan
Eric Lease Morgan wrote:
Are alpha characters used for field names valid in MARC records?
When we do dumps of MARC rec
> From: Code for Libraries [mailto:[EMAIL PROTECTED] On Behalf Of
> Eric Lease Morgan
> Sent: Wednesday, June 25, 2008 3:21 PM
> To: CODE4LIB@LISTSERV.ND.EDU
> Subject: [CODE4LIB] alpha characters used for field names
>
> Are alpha characters used for field names valid in MARC records?
>
> When w
> Are alpha characters used for field names valid in MARC records?
>
> When we do dumps of MARC records our ILS often dumps them with FMT and CAT
> field names. So not only do I have glorious 246 fields and 100 fields but I
> also have CAT fields and FMT fields. Are these features of my ILS --
> ex
Why don't systems use the 900 fields for local stuff like this? That's what
they're there for, right?
--Casey
On Wed, Jun 25, 2008 at 12:23 PM, Steve Oberg <[EMAIL PROTECTED]> wrote:
> Eric,
>
> This is definitely not a feature of MARC but rather a feature of your local
> ILS (Aleph 500). Thos
Eric, You might want to look at ISO 2709 - the standard giving the
format underlying MARC records. It allows alpha values for the tags. But
MARC does not allow alpha values. Wikipedia give a brief summary,
although the ISO standard is only 6 pages long.
Peter Noerr
> -Original Message-
>
On Wed, Jun 25, 2008 at 2:20 PM, Eric Lease Morgan <[EMAIL PROTECTED]> wrote:
> Moreover, does something like Marc4J or MARC::Batch and friends deal
> with these alpha field names correctly?
I believe the Perl modules MARC::Batch/MARC::Record accept records with
alphabetic characters as tags. Sea
Eric,
This is definitely not a feature of MARC but rather a feature of your local
ILS (Aleph 500). Those are local fields for which you'd need to make a
translation to a standard MARC field if you wanted to move that information
to another system that is based on MARC.
Steve
On Wed, Jun 25, 200
13 matches
Mail list logo