[Evergreen-catalogers] RDA and the future of Evergreen

Mon May 7 08:53:41 EDT 2012

That's what I had thought since there isn't an alternative way to enter
the fields as there is in the standard editor.

The subfields are purely for ease of entry, just as the fixed field grid
they use is. That way catalogers don't have to worry about byte position
-- the system in OCLC translates the subfields and the labeled elements to
the correct position. A really major problem using the standard editor in
MARC21 display in Evergreen to edit the LDR and 008 field is that not only
are we unaccustomed to tracking byte position, we don't seem to have the
ability to over write rather than insert so we have to make sure we delete
any extra spaces added during entry. Using the OCLC like grid removes that
necessity and makes sure the ff elements are in the correct byte position.
Same with using subfields for the 007.

Elaine

J. Elaine Hardy
PINES Bibliographic Projects and Metadata Manager
Georgia Public Library Service,
A Unit of the University System of Georgia
1800 Century Place, Suite 150
Atlanta, Ga. 30345-4304
404.235-7128
404.235-7201, fax

ehardy at georgialibraries.org
www.georgialibraries.org
http://www.georgialibraries.org/pines/

-----Original Message-----
From: evergreen-catalogers-bounces at list.evergreen-ils.org
[mailto:evergreen-catalogers-bounces at list.evergreen-ils.org] On Behalf Of
Mike Rylander
Sent: Monday, May 07, 2012 8:40 AM
To: Evergreen Community Catalogers
Subject: Re: [Evergreen-catalogers] RDA and the future of Evergreen

On Mon, May 7, 2012 at 8:24 AM, Hardy, Elaine
<ehardy at georgialibraries.org> wrote:
> That's very good. It also makes creating a filter or index in
> Evergreen that would accommodate both standards easier.
>
> I would like to be able to require entry of this field for PINES but I
> don't know if that would be possible for a variety of reasons, not the
> least being that it would add to the costs of those libraries that
> contract catalog.
>
> It does brings up a question -- if the 007 is entered in the flat text
> editor, does it become a control field? In the standard editor, you
> have to right click and add the 007 from the menu  else it will be
> just another field.
>

When switching between the flat and GUI editors, any tag with a numeric
value less than 10 (and the leader, of course) is treated as a control
field.  Which is to say, whatever is to the right of the tag is dumped
directly into the single text entry box for that control field.  It's
unfortunate that the OCLC documentation describes "subfields" for the 007,
because (as you know) they're really just byte positions, and since we're
dealing with what amounts to a raw MARC editor we expect byte-position
encoding instead of subfield delimited values.

IOW, you have to use something like:

007 cocoannnauabu

instead of

007 $ac$bo$dc$eo$fa$gnnn$ha$iu$ja$kb$lu

to describe a CD-ROM (and that's probably not right anyway, but you get
the point).

--miker

>
> Elaine
>
>
> J. Elaine Hardy
> PINES Bibliographic Projects and Metadata Manager Georgia Public
> Library Service, A Unit of the University System of Georgia
> 1800 Century Place, Suite 150
> Atlanta, Ga. 30345-4304
> 404.235-7128
> 404.235-7201, fax
>
> ehardy at georgialibraries.org
> www.georgialibraries.org
> http://www.georgialibraries.org/pines/
>
>
> -----Original Message-----
> From: evergreen-catalogers-bounces at list.evergreen-ils.org
> [mailto:evergreen-catalogers-bounces at list.evergreen-ils.org] On Behalf
> Of Mike Rylander
> Sent: Monday, May 07, 2012 7:55 AM
> To: Evergreen Community Catalogers
> Subject: Re: [Evergreen-catalogers] RDA and the future of Evergreen
>
> On Fri, May 4, 2012 at 2:47 PM, Hardy, Elaine
> <ehardy at georgialibraries.org> wrote:
>> There isn't as of yet, that I have heard of. One of the problems with
>> a conversion matching is that not everything would be a one-to-one
>> because either AACR2 doesn't require it, or one MARC field can have
>> several bits of information that would be separate entry in RDA. For
>> example, for some of the carrier types, it is best expressed in an
>> 007; but 007 isn't a required field so not all records that should
>> have them do. And, the values in an 007 mean different things
>> depending on the record format --
>> 007 |g for a map is Production/ reproduction details. The same
>> subfield for video recording is  Medium for sound.
>
> The lack of 007 fields is a big issue, but (thankfully) where we have
> them we can interpret them correctly.  For 2.0 I encoded the full
> table here[1] in the Evergreen database, and built a stored procedure
> to extract all of the information in the record's 007 -- we use it to
> pull out the videorecording format for indexing.  So if/when an
> approximate AACR2->RDA algorithm is created we should be in a good
position to make use of it.
>
> --miker
>
>>
>> Elaine
>>
>>
>> J. Elaine Hardy
>> PINES Bibliographic Projects and Metadata Manager Georgia Public
>> Library Service, A Unit of the University System of Georgia
>> 1800 Century Place, Suite 150
>> Atlanta, Ga. 30345-4304
>> 404.235-7128
>> 404.235-7201, fax
>>
>> ehardy at georgialibraries.org
>> www.georgialibraries.org
>> http://www.georgialibraries.org/pines/
>>
>>
>> -----Original Message-----
>> From: evergreen-catalogers-bounces at list.evergreen-ils.org
>> [mailto:evergreen-catalogers-bounces at list.evergreen-ils.org] On
>> Behalf Of Galen Charlton
>> Sent: Friday, May 04, 2012 9:28 AM
>> To: evergreen-catalogers at list.evergreen-ils.org
>> Subject: Re: [Evergreen-catalogers] RDA and the future of Evergreen
>>
>> Hi,
>>
>> On 5/4/2012 8:46 AM, Hardy, Elaine wrote:
>>> Thinking out loud here -- what if we used  the 338 (carrier type) as
>>> a filter to further refine a search to more specific formats within
>>> audiobooks. The question then becomes -- how do we craft a similar
>>> filter for AACR2 records when the carrier type is not so readily
>>> defined in one field?
>>
>> Given a (non-brief) AACR2 record, is there a set of rules published
>> for mechanically deducing the RDA carrier type?  If so, a filter
>> potentially could be expressed in terms of the 338 for RDA records
>> and the calculated carrier type for AACR2 records.
>>
>> Regards,
>>
>> Galen
>> --
>> Galen Charlton
>> Director of Support and Implementation Equinox Software, Inc. / The
>> Open Source Experts
>> email:  gmc at esilibrary.com
>> direct: +1 770-709-5581
>> cell:   +1 404-984-4366
>> skype:  gmcharlt
>> web:    http://www.esilibrary.com
>> Supporting Koha and Evergreen: http://koha-community.org &
>> http://evergreen-ils.org
>> _______________________________________________
>> Evergreen-catalogers mailing list
>> Evergreen-catalogers at list.evergreen-ils.org
>> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-cata
>> l
>> oger
>> s
>> _______________________________________________
>> Evergreen-catalogers mailing list
>> Evergreen-catalogers at list.evergreen-ils.org
>> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-cata
>> l
>> ogers
>
>
>
> --
> Mike Rylander
>  | Director of Research and Development
>  | Equinox Software, Inc. / Your Library's Guide to Open Source
>  | phone:  1-877-OPEN-ILS (673-6457)
>  | email:  miker at esilibrary.com
>  | web:  http://www.esilibrary.com
> _______________________________________________
> Evergreen-catalogers mailing list
> Evergreen-catalogers at list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catal
> oger
> s
> _______________________________________________
> Evergreen-catalogers mailing list
> Evergreen-catalogers at list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catal
> ogers

--
Mike Rylander
 | Director of Research and Development
 | Equinox Software, Inc. / Your Library's Guide to Open Source
 | phone:  1-877-OPEN-ILS (673-6457)
 | email:  miker at esilibrary.com
 | web:  http://www.esilibrary.com
_______________________________________________
Evergreen-catalogers mailing list
Evergreen-catalogers at list.evergreen-ils.org
http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-cataloger
s