[Evergreen-catalogers] RDA and the future of Evergreen

[Mike Rylander]

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-cataloger
> s
> _______________________________________________
> Evergreen-catalogers mailing list
> Evergreen-catalogers at list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers



-- 
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