<div dir="ltr"><div><div>Thanks, Mike! This was so much help! I have the pieces in place to look at tag 347 in my Coded MARC value mapping, added an MP3 format search based on it and got 600 bibs to come up. I also adjusted our CD audiobook format search to ignore the MP3 mapping to filter them out in the OPAC results. I still have to do some data massaging on 300 more bibs to add the 3xx tags, then a quick reingest, and I'll finally have my longed-for MP3 audiobook search ready. I just need to find a good .png icon to represent it, then my oldest helpdesk ticket can be closed. <br><br></div>Awesome resource, this community!<br><br></div>Mary<br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 14, 2017 at 12:09 PM, Mike Rylander <span dir="ltr"><<a href="mailto:mrylander@gmail.com" target="_blank">mrylander@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">All,<br>
<br>
This is a great discussion!<br>
<br>
I just wanted to note that, since the values that can be used in the<br>
347$b are not (yet -- is there an authoritative list?) included in the<br>
Coded Value Map table, they can't yet be used in combination with the<br>
33x RDA values or fixed fields. However, all that is required is<br>
configuration (adding a Digital File Characteristics coded value map,<br>
and the record attribute definition to extract the values from<br>
records) to make that work. With that, an MP3 CD search and icon<br>
entry for records encoded as described upthread could work the same<br>
way as any other composite attribute.<br>
<br>
This sounds like a wishlist bug to seed and maintain the required<br>
coded value map entries, at least, I think.<br>
<br>
Thanks,<br>
<br>
--<br>
Mike Rylander<br>
| President<br>
| Equinox Open Library Initiative<br>
| phone: 1-877-OPEN-ILS (673-6457)<br>
| email: <a href="mailto:miker@equinoxinitiative.org">miker@equinoxinitiative.org</a><br>
| web: <a href="http://equinoxinitiative.org" rel="noreferrer" target="_blank">http://equinoxinitiative.org</a><br>
<br>
<br>
On Tue, Nov 14, 2017 at 11:47 AM, Kathy Lussier <<a href="mailto:klussier@masslnc.org">klussier@masslnc.org</a>> wrote:<br>
> Hi,<br>
><br>
> You can add a new icon by doing the following:<br>
><br>
> - If you haven't done so already, configure the attributes for this icon in<br>
> the Coded Value Maps interface. You will want to add this definition with<br>
> the OPAC Format Icons record attribute type. Documentation for creating<br>
> these can be found at<br>
> <a href="http://docs.evergreen-ils.org/2.6/_marc_record_attributes.html" rel="noreferrer" target="_blank">http://docs.evergreen-ils.org/<wbr>2.6/_marc_record_attributes.<wbr>html</a>.<br>
><br>
> - Give the image the same name as is used for the code field when you<br>
> configured the format in the Coded Value Maps interface. As an example, the<br>
> image for the cassette audiobook icon in stock evergreen is named<br>
> casaudiobook.png because the code for this definition is 'casaudiobook.'<br>
><br>
> - Put the image on the server in the<br>
> /openils/var/web/images/<wbr>format_icons/icon_format/<br>
><br>
> Kathy<br>
><br>
><br>
><br>
> On 11/14/2017 11:01 AM, Mary Llewellyn wrote:<br>
><br>
> We've done likewise for the coding, but didn't manage a new icon. I'd love<br>
> to know how to get new icons and put them into place.<br>
><br>
> We've also made sure that all our downloadable ebooks/audiobooks/etc. get<br>
> coded as "o". So many of the vendor files use "s" so we change them before<br>
> loading, so our indexes for those format searches are not muddied with<br>
> whatever "s" should be assigned to.<br>
><br>
> On Mon, Nov 13, 2017 at 9:06 AM, Elaine Hardy <<a href="mailto:ehardy@georgialibraries.org">ehardy@georgialibraries.org</a>><br>
> wrote:<br>
>><br>
>> We created an icon to use for playaways -- see<br>
>> <a href="https://gapines.org/eg/opac/record/5000978?query=playaways;qtype=keyword;locg=1;detail_record_view=0" rel="noreferrer" target="_blank">https://gapines.org/eg/opac/<wbr>record/5000978?query=<wbr>playaways;qtype=keyword;locg=<wbr>1;detail_record_view=0</a><br>
>><br>
>> First we made sure that all playaways had the current Form (008/23) q<br>
>> (Direct electronic. Storage on a directly accessible tangible recording<br>
>> medium, e.g. disc, tape, Playaway device, flashdrive, portable hard drive,<br>
>> etc.) along with the appropriate Type (Leader/06). You will most likely find<br>
>> some with old or incorrect codes for Form -- blank, o, or s.<br>
>><br>
>><br>
>><br>
>><br>
>> J. Elaine Hardy<br>
>> PINES & Collaborative Projects Manager<br>
>> Georgia Public Library Service/PINES<br>
>> 1800 Century Place, Ste. 150<br>
>> Atlanta, GA 30045<br>
>><br>
>> <a href="tel:404.235.7128" value="+14042357128">404.235.7128</a> Office<br>
>> <a href="tel:404.548.4241" value="+14045484241">404.548.4241</a> Cell<br>
>> <a href="tel:404.235.7201" value="+14042357201">404.235.7201</a> FAX<br>
>><br>
>> On Mon, Nov 13, 2017 at 8:00 AM, Jonathan Furr <furrjt@forsyth.cc> wrote:<br>
>>><br>
>>> +1 - on the need for conjunction between fixed fields and 33x tags<br>
>>><br>
>>> I also like Sarah's idea about using the 347$b for the MP3 vs. Playaway<br>
>>> distinction issue. That might work.<br>
>>><br>
>>> Best,<br>
>>><br>
>>> Jonathan Furr<br>
>>> Technical Services<br>
>>> Forsyth County Public Library<br>
>>> <a href="tel:336.703.3045" value="+13367033045">336.703.3045</a><br>
>>><br>
>>> On Thu, Nov 9, 2017 at 4:33 PM, Jennifer Weston<br>
>>> <<a href="mailto:Jennifer.Weston@davidsoncountync.gov">Jennifer.Weston@<wbr>davidsoncountync.gov</a>> wrote:<br>
>>>><br>
>>>> +1 – I agree that the RDA fields can currently only be used in<br>
>>>> conjunction with codes in 008 and 007/006. I do think it is great that we<br>
>>>> are having this conversation. The RDA fields are powerful but they can’t<br>
>>>> stand on their own (yet) because we do find ourselves describing multiple<br>
>>>> content/media/carrier types on the same record sometimes.<br>
>>>><br>
>>>> Janet asks a question that draws attention to what makes this “hybrid”<br>
>>>> cataloging world so interesting. I am not aware of a code that identifies a<br>
>>>> MP3 but I do include a digital file characteristic on the 347‡b to add MP3<br>
>>>> as the audio encoding format. At least, this is an authorized term from RDA<br>
>>>> 3.19.3.3. Trying to use a subfield may not be effective or efficient (or<br>
>>>> possible) for filtering but it is there.<br>
>>>><br>
>>>> Best,<br>
>>>><br>
>>>> Jennifer<br>
>>>><br>
>>>> Jennifer Weston<br>
>>>> Davidson County Public Library<br>
>>>> Technical Services Manager<br>
>>>> <a href="mailto:jennifer.weston@davidsoncountync.gov">jennifer.weston@<wbr>davidsoncountync.gov</a><br>
>>>> <a href="tel:%28336%29%20242-2941" value="+13362422941">(336) 242-2941</a><br>
>>>><br>
>>>><br>
>>>><br>
>>>> From: Evergreen-catalogers<br>
>>>> [mailto:<a href="mailto:evergreen-catalogers-bounces@list.evergreen-ils.org">evergreen-catalogers-<wbr>bounces@list.evergreen-ils.org</a><wbr>] On Behalf Of<br>
>>>> Janet Schrader<br>
>>>> Sent: Thursday, November 9, 2017 3:50 PM<br>
>>>> To: Evergreen Community Catalogers<br>
>>>> <<a href="mailto:evergreen-catalogers@list.evergreen-ils.org">evergreen-catalogers@list.<wbr>evergreen-ils.org</a>><br>
>>>> Subject: Re: [Evergreen-catalogers] RDA search formats<br>
>>>><br>
>>>><br>
>>>><br>
>>>> +1.<br>
>>>><br>
>>>><br>
>>>><br>
>>>> These fields can only be used in conjunction with codes in the 008 and<br>
>>>> 007/006 fields.<br>
>>>><br>
>>>><br>
>>>><br>
>>>> While on this topic, I'd like to know if anyone has created a format<br>
>>>> filter for MP3 CD audiobooks. The 007 field code for SMD is the same as<br>
>>>> regular CDs. Is there some other code(s) I could use?<br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>> Thanks,<br>
>>>><br>
>>>> Janet<br>
>>>><br>
>>>><br>
>>>><br>
>>>> On Thu, Nov 9, 2017 at 1:30 PM, Elaine Hardy<br>
>>>> <<a href="mailto:ehardy@georgialibraries.org">ehardy@georgialibraries.org</a>> wrote:<br>
>>>><br>
>>>> +1<br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>> J. Elaine Hardy<br>
>>>><br>
>>>> PINES & Collaborative Projects Manager<br>
>>>><br>
>>>> Georgia Public Library Service/PINES<br>
>>>><br>
>>>> 1800 Century Place, Ste. 150<br>
>>>><br>
>>>> Atlanta, GA 30045<br>
>>>><br>
>>>> <a href="tel:404.235.7128" value="+14042357128">404.235.7128</a> Office<br>
>>>><br>
>>>> <a href="tel:404.548.4241" value="+14045484241">404.548.4241</a> Cell<br>
>>>><br>
>>>> <a href="tel:404.235.7201" value="+14042357201">404.235.7201</a> FAX<br>
>>>><br>
>>>><br>
>>>><br>
>>>> On Thu, Nov 9, 2017 at 10:32 AM, Jane Sandberg <<a href="mailto:sandbej@linnbenton.edu">sandbej@linnbenton.edu</a>><br>
>>>> wrote:<br>
>>>><br>
>>>> I'd actually hesitate at this proposal, since the 33x terms don't<br>
>>>> really make a lot of distinctions that patrons would find helpful, for<br>
>>>> example:<br>
>>>><br>
>>>> * Large type vs. standard type have the same 33x<br>
>>>> * DVD vs. Blu-ray have the same 33x<br>
>>>> * These fields are all repeatable. Sometimes those combinations can<br>
>>>> mean that there are multiple parts, sometimes it means that several<br>
>>>> formats are incorporated into a single object. For example, 336$atext<br>
>>>> and 336$images could mean a picture book, a graphic novel, a book of<br>
>>>> photographs with captions, an archival collection that includes both<br>
>>>> pamphlets and paintings, etc.<br>
>>>><br>
>>>> I think that having 33x terms in the mix of<br>
>>>> what-fields-cause-which-icons is great. I don't think that they<br>
>>>> should ever be used without other MARC fields to determine what icons<br>
>>>> display.<br>
>>>><br>
>>>> On Wed, Nov 8, 2017 at 12:08 PM, Elaine Hardy<br>
>>>> <<a href="mailto:ehardy@georgialibraries.org">ehardy@georgialibraries.org</a>> wrote:<br>
>>>> > LC has handy tables that link the RDA terms in the MARC 33x fields to<br>
>>>> > the<br>
>>>> > 007 field codes : 007/01 (for 338), Leader/06 codes (for 336) and<br>
>>>> > 007/00<br>
>>>> > (for 337). See <a href="http://www.loc.gov/standards/valuelist/index.html" rel="noreferrer" target="_blank">http://www.loc.gov/standards/<wbr>valuelist/index.html</a>. So,<br>
>>>> > for<br>
>>>> > those search filters (and icons) that utilize those 007 codes, if a<br>
>>>> > bib<br>
>>>> > record has the 33x fields, those terms and codes could be used<br>
>>>> > instead.<br>
>>>> ><br>
>>>> > To further specify icons, the 007 field will still need to be used to<br>
>>>> > distinguish formats for videorecordings (007/04)<br>
>>>> ><br>
>>>> ><br>
>>>> ><br>
>>>> ><br>
>>>> ><br>
>>>> > J. Elaine Hardy<br>
>>>> > PINES & Collaborative Projects Manager<br>
>>>> > Georgia Public Library Service/PINES<br>
>>>> > 1800 Century Place, Ste. 150<br>
>>>> > Atlanta, GA 30045<br>
>>>> ><br>
>>>> > 404.235.7128 Office<br>
>>>> > 404.548.4241 Cell<br>
>>>> > 404.235.7201 FAX<br>
>>>> ><br>
>>>> > On Wed, Nov 8, 2017 at 9:17 AM, Rogan Hamby<br>
>>>> > <<a href="mailto:rhamby@equinoxinitiative.org">rhamby@equinoxinitiative.org</a>><br>
>>>> > wrote:<br>
>>>> >><br>
>>>> >> Good morning.<br>
>>>> >><br>
>>>> >> I've started looking at how we can resolve RDA 336/337/338 tags for<br>
>>>> >> search<br>
>>>> >> formats. There has already been community discussion here:<br>
>>>> >><br>
>>>> >> <a href="https://bugs.launchpad.net/evergreen/+bug/1125621" rel="noreferrer" target="_blank">https://bugs.launchpad.net/<wbr>evergreen/+bug/1125621</a><br>
>>>> >><br>
>>>> >> The good news is that we (the Evergreen 'we') already have that data<br>
>>>> >> pulled into the database so the next step is to use it.<br>
>>>> >><br>
>>>> >> Before the code is written though I think there are some points for<br>
>>>> >> the<br>
>>>> >> larger community. The big picture questions are - What combinations<br>
>>>> >> should<br>
>>>> >> map to existing search formats and which might need new ones? Also,<br>
>>>> >> a<br>
>>>> >> logistic question - When new ones are needed where will the icons<br>
>>>> >> come from?<br>
>>>> >> (I can probably make them if need be.)<br>
>>>> >><br>
>>>> >> Additionally, a working practice question. My instinct (and I think<br>
>>>> >> that<br>
>>>> >> of many) is to say the code should basically check to see if there<br>
>>>> >> are RDA<br>
>>>> >> values and if so use those and fall back to AACR2. Are there<br>
>>>> >> scenarios in<br>
>>>> >> practice when both should be used? Following that up, if they do<br>
>>>> >> exist are<br>
>>>> >> these common enough / follow standards to any degree that we should<br>
>>>> >> worry<br>
>>>> >> about them or are they edge cases?<br>
>>>> >><br>
>>>> >><br>
>>>> >><br>
>>>> >><br>
>>>> >><br>
>>>> >> Rogan Hamby<br>
>>>> >><br>
>>>> >> Data and Project Analyst<br>
>>>> >><br>
>>>> >> Equinox Open Library Initiative<br>
>>>> >><br>
>>>> >> phone: 1-877-OPEN-ILS (673-6457)<br>
>>>> >><br>
>>>> >> email: rogan@EquinoxInitiative.org<br>
>>>> >><br>
>>>> >> web: <a href="http://EquinoxInitiative.org" rel="noreferrer" target="_blank">http://EquinoxInitiative.org</a><br>
>>>> >><br>
>>>> >> ______________________________<wbr>_________________<br>
>>>> >> Evergreen-catalogers mailing list<br>
>>>> >> <a href="mailto:Evergreen-catalogers@list.evergreen-ils.org">Evergreen-catalogers@list.<wbr>evergreen-ils.org</a><br>
>>>> >><br>
>>>> >><br>
>>>> >> <a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/<wbr>cgi-bin/mailman/listinfo/<wbr>evergreen-catalogers</a><br>
>>>> >><br>
>>>> ><br>
>>>> ><br>
>>>> > ______________________________<wbr>_________________<br>
>>>> > Evergreen-catalogers mailing list<br>
>>>> > <a href="mailto:Evergreen-catalogers@list.evergreen-ils.org">Evergreen-catalogers@list.<wbr>evergreen-ils.org</a><br>
>>>> ><br>
>>>> > <a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/<wbr>cgi-bin/mailman/listinfo/<wbr>evergreen-catalogers</a><br>
>>>> ><br>
>>>><br>
>>>><br>
>>>><br>
>>>> --<br>
>>>> Jane Sandberg<br>
>>>> Electronic Resources Librarian<br>
>>>> Linn-Benton Community College<br>
>>>> <a href="mailto:sandbej@linnbenton.edu">sandbej@linnbenton.edu</a> / <a href="tel:541-917-4655" value="+15419174655">541-917-4655</a><br>
>>>> Pronouns: she/her/hers or they/them/theirs<br>
>>>> ______________________________<wbr>_________________<br>
>>>> Evergreen-catalogers mailing list<br>
>>>> <a href="mailto:Evergreen-catalogers@list.evergreen-ils.org">Evergreen-catalogers@list.<wbr>evergreen-ils.org</a><br>
>>>><br>
>>>> <a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/<wbr>cgi-bin/mailman/listinfo/<wbr>evergreen-catalogers</a><br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>> ______________________________<wbr>_________________<br>
>>>> Evergreen-catalogers mailing list<br>
>>>> <a href="mailto:Evergreen-catalogers@list.evergreen-ils.org">Evergreen-catalogers@list.<wbr>evergreen-ils.org</a><br>
>>>><br>
>>>> <a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/<wbr>cgi-bin/mailman/listinfo/<wbr>evergreen-catalogers</a><br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>> --<br>
>>>><br>
>>>> Janet Schrader<br>
>>>><br>
>>>> BIbliographic Services Supervisor<br>
>>>><br>
>>>> C/W MARS Inc.<br>
>>>><br>
>>>> 67 Millbrook Street, Suite 201<br>
>>>><br>
>>>> Worcester, MA<br>
>>>><br>
>>>> tel: <a href="tel:508-755-3323%20ext.%20325" value="+15087553323">508-755-3323 ext. 325</a><br>
>>>><br>
>>>> fax: <a href="tel:508-757-7801" value="+15087577801">508-757-7801</a><br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>> ______________________________<wbr>__<br>
>>>><br>
>>>> If you are not the intended recipient, you must destroy this message and<br>
>>>> inform the sender immediately. This electronic mail message and any<br>
>>>> attachments, as well as any electronic mail message(s) sent in response to<br>
>>>> it may be considered public record and as such subject to request and review<br>
>>>> by anyone at any time. It also may contain information which is confidential<br>
>>>> within the meaning of applicable federal and state laws.<br>
>>>><br>
>>>> Davidson County Government, PO Box 1067, Lexington, NC, USA,<br>
>>>> <a href="http://www.co.davidson.nc.us" rel="noreferrer" target="_blank">www.co.davidson.nc.us</a><br>
>>>><br>
>>>> ______________________________<wbr>_________________<br>
>>>> Evergreen-catalogers mailing list<br>
>>>> <a href="mailto:Evergreen-catalogers@list.evergreen-ils.org">Evergreen-catalogers@list.<wbr>evergreen-ils.org</a><br>
>>>><br>
>>>> <a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/<wbr>cgi-bin/mailman/listinfo/<wbr>evergreen-catalogers</a><br>
>>>><br>
>>><br>
>>><br>
>>> ______________________________<wbr>_________________<br>
>>> Evergreen-catalogers mailing list<br>
>>> <a href="mailto:Evergreen-catalogers@list.evergreen-ils.org">Evergreen-catalogers@list.<wbr>evergreen-ils.org</a><br>
>>><br>
>>> <a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/<wbr>cgi-bin/mailman/listinfo/<wbr>evergreen-catalogers</a><br>
>>><br>
>><br>
>><br>
>> ______________________________<wbr>_________________<br>
>> Evergreen-catalogers mailing list<br>
>> <a href="mailto:Evergreen-catalogers@list.evergreen-ils.org">Evergreen-catalogers@list.<wbr>evergreen-ils.org</a><br>
>><br>
>> <a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/<wbr>cgi-bin/mailman/listinfo/<wbr>evergreen-catalogers</a><br>
>><br>
><br>
><br>
><br>
> --<br>
> Mary Llewellyn<br>
> Database Manager<br>
> Bibliomation, Inc.<br>
> 24 Wooster Ave.<br>
> Waterbury, CT 06708<br>
> <a href="mailto:mllewell@biblio.org">mllewell@biblio.org</a><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> Evergreen-catalogers mailing list<br>
> <a href="mailto:Evergreen-catalogers@list.evergreen-ils.org">Evergreen-catalogers@list.<wbr>evergreen-ils.org</a><br>
> <a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/<wbr>cgi-bin/mailman/listinfo/<wbr>evergreen-catalogers</a><br>
><br>
><br>
> --<br>
> Kathy Lussier<br>
> Project Coordinator<br>
> Massachusetts Library Network Cooperative<br>
> <a href="tel:%28508%29%20343-0128" value="+15083430128">(508) 343-0128</a><br>
> <a href="mailto:klussier@masslnc.org">klussier@masslnc.org</a><br>
> Twitter: <a href="http://www.twitter.com/kmlussier" rel="noreferrer" target="_blank">http://www.twitter.com/<wbr>kmlussier</a><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> Evergreen-catalogers mailing list<br>
> <a href="mailto:Evergreen-catalogers@list.evergreen-ils.org">Evergreen-catalogers@list.<wbr>evergreen-ils.org</a><br>
> <a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/<wbr>cgi-bin/mailman/listinfo/<wbr>evergreen-catalogers</a><br>
><br>
______________________________<wbr>_________________<br>
Evergreen-catalogers mailing list<br>
<a href="mailto:Evergreen-catalogers@list.evergreen-ils.org">Evergreen-catalogers@list.<wbr>evergreen-ils.org</a><br>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-catalogers" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/<wbr>cgi-bin/mailman/listinfo/<wbr>evergreen-catalogers</a><br>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div><div><div><div>Mary Llewellyn<br></div>Database Manager<br></div>Bibliomation, Inc.<br></div>24 Wooster Ave.<br></div>Waterbury, CT 06708<br></div><a href="mailto:mllewell@biblio.org" target="_blank">mllewell@biblio.org</a><br></div></div>
</div>