[Evergreen-catalogers] RDA search formats

[Jane Sandberg]

I'd actually hesitate at this proposal, since the 33x terms don't
really make a lot of distinctions that patrons would find helpful, for
example:

* Large type vs. standard type have the same 33x
* DVD vs. Blu-ray have the same 33x
* These fields are all repeatable.  Sometimes those combinations can
mean that there are multiple parts, sometimes it means that several
formats are incorporated into a single object.  For example, 336$atext
and 336$images could mean a picture book, a graphic novel, a book of
photographs with captions, an archival collection that includes both
pamphlets and paintings, etc.

I think that having 33x terms in the mix of
what-fields-cause-which-icons is great.  I don't think that they
should ever be used without other MARC fields to determine what icons
display.

On Wed, Nov 8, 2017 at 12:08 PM, Elaine Hardy
<ehardy at georgialibraries.org> wrote:
> LC has handy tables that link the RDA terms in the MARC 33x fields to the
> 007 field codes : 007/01 (for 338), Leader/06 codes (for 336) and 007/00
> (for 337). See http://www.loc.gov/standards/valuelist/index.html. So, for
> those search filters (and icons) that utilize those 007 codes, if a bib
> record has the 33x fields, those terms and codes could be used instead.
>
> To further specify icons, the 007 field will still need to be used to
> distinguish formats for videorecordings (007/04)
>
>
>
>
>
> J. Elaine Hardy
> PINES & Collaborative Projects Manager
> Georgia Public Library Service/PINES
> 1800 Century Place, Ste. 150
> Atlanta, GA 30045
>
> 404.235.7128 Office
> 404.548.4241 Cell
> 404.235.7201 FAX
>
> On Wed, Nov 8, 2017 at 9:17 AM, Rogan Hamby <rhamby at equinoxinitiative.org>
> wrote:
>>
>> Good morning.
>>
>> I've started looking at how we can resolve RDA 336/337/338 tags for search
>> formats.  There has already been community discussion here:
>>
>> https://bugs.launchpad.net/evergreen/+bug/1125621
>>
>> The good news is that we (the Evergreen 'we') already have that data
>> pulled into the database so the next step is to use it.
>>
>> Before the code is written though I think there are some points for the
>> larger community.  The big picture questions are - What combinations should
>> map to existing search formats and which might need new ones?  Also, a
>> logistic question - When new ones are needed where will the icons come from?
>> (I can probably make them if need be.)
>>
>> Additionally, a working practice question.  My instinct (and I think that
>> of many) is to say the code should basically check to see if there are RDA
>> values and if so use those and fall back to AACR2.  Are there scenarios in
>> practice when both should be used?  Following that up, if they do exist are
>> these common enough / follow standards to any degree that we should worry
>> about them or are they edge cases?
>>
>>
>>
>>
>>
>> Rogan Hamby
>>
>> Data and Project Analyst
>>
>> Equinox Open Library Initiative
>>
>> phone:  1-877-OPEN-ILS (673-6457)
>>
>> email:  rogan at EquinoxInitiative.org
>>
>> web:  http://EquinoxInitiative.org
>>
>> _______________________________________________
>> Evergreen-catalogers mailing list
>> Evergreen-catalogers at list.evergreen-ils.org
>>
>> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers
>>
>
>
> _______________________________________________
> Evergreen-catalogers mailing list
> Evergreen-catalogers at list.evergreen-ils.org
> http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers
>



-- 
Jane Sandberg
Electronic Resources Librarian
Linn-Benton Community College
sandbej at linnbenton.edu / 541-917-4655
Pronouns: she/her/hers or they/them/theirs