<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">The JSC recently posted the final version of the approved proposal 6JSC/CILIP/4: <a href="http://www.rda-jsc.org/docs/6JSC-CILIP-4-Sec-final.pdf" class="">http://www.rda-jsc.org/docs/6JSC-CILIP-4-Sec-final.pdf</a><div class="">
<div class="page" title="Page 1">
<div class="layoutArea">
<div class="column"><p class=""><span style="font-size: 10.000000pt; font-family: 'Verdana'" class="">So, in the April 2015 update of RDA toolkit, the instruction at 7.17.1.1 will read as follows:</span></p><p class=""><span style="font-size: 10.000000pt; font-family: 'Verdana'" class="">For instructions on recording item-specific colour information, see 3.22. </span></p><div class="">An example of a note describing a hand-colored resource was not added to 7.17.1.4 on details of colour content.</div><div class=""><br class=""></div><div class="">Matthew</div><div class=""><br class=""></div>
</div>
</div>
</div><div><blockquote type="cite" class=""><div class="">On Mar 1, 2015, at 5:57 PM, Manon Théroux <<a href="mailto:manon.theroux@gmail.com" class="">manon.theroux@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class=""><div class="">Matthew, let's hope your suggested revisions were approved. They sound good to me.</div><div class=""><br class=""></div><div class="">Manon</div><div class=""><br class="">On Mar 1, 2015, at 5:01 PM, Matthew Haugen <<a href="mailto:mch2167@columbia.edu" class="">mch2167@columbia.edu</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class="">Yes, 6JSC/CILIP/4 was accepted with revisions. Final versions of accepted proposals have begun to trickle in to the JSC wesbite but this one doesn’t appear to have been posted yet.<div class=""><br class=""><div class="">The troublesome sentence Manon mentions was indeed removed in the original proposal. However, I responded on behalf of DCRM with the comment copied below, which sought to restore it with amendments. These suggestions were carried forward into the ALA response to 6JSC/CILIP/4 (<a href="http://www.rda-jsc.org/docs/6JSC-CILIP-4-ALA-response.pdf" class="">http://www.rda-jsc.org/docs/6JSC-CILIP-4-ALA-response.pdf</a>), though it is not clear to me whether the JSC accepted those revisions.</div><div class=""><br class=""></div><div class="">Matthew</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><span style="color: rgb(51, 51, 51); font-family: Calibri, Arian, sans-serif; line-height: 24px; background-color: rgb(249, 249, 249);" class="">I’m wondering why the line in 7.17.1.1 was removed: “For instructions on recording information on hand-coloured items, see 3.21.”</span></div><div class=""><span style="color: rgb(51, 51, 51); font-family: Calibri, Arian, sans-serif; line-height: 24px; background-color: rgb(249, 249, 249);" class="">On behalf of DCRM, I suggest restoring it, with some changes. While we can still point to 3.21 for item-specific coloring, some resources were issued hand-colored at the manifestation level and would be better addressed here, perhaps under 7.17.1.4 (Details of color content), even if just in an example such as:</span></div><div class=""><font color="#333333" face="Calibri, Arian, sans-serif" class=""><span style="line-height: 24px; background-color: rgb(249, 249, 249);" class=""><br class=""></span></font><p style="font-family: Calibri, Arian, sans-serif; background-color: rgb(249, 249, 249); border: 0px; margin: 0px 0px 1.1em; padding: 0px; vertical-align: baseline; color: rgb(51, 51, 51); line-height: 24px;" class="">hand coloured<br class=""><b style="background-color: transparent; border: 0px; margin: 0px; padding: 0px; vertical-align: baseline;" class="">Map issued with hand coloring. Color content recorded as:</b> polychrome</p><p style="font-family: Calibri, Arian, sans-serif; background-color: rgb(249, 249, 249); border: 0px; margin: 0px 0px 1.1em; padding: 0px; vertical-align: baseline; color: rgb(51, 51, 51); line-height: 24px;" class="">Meanwhile, it’s also possible that some item-specific coloring may not have been hand applied, so the instruction pointing to 3.21 might better read:</p><div style="font-family: Calibri, Arian, sans-serif; background-color: rgb(249, 249, 249); border: 0px; margin: 0px; padding: 0px; vertical-align: baseline; color: rgb(51, 51, 51); line-height: 24px;" class="">For instructions on recording item-specific colour information, see 3.21</div><div style="font-family: Calibri, Arian, sans-serif; background-color: rgb(249, 249, 249); border: 0px; margin: 0px; padding: 0px; vertical-align: baseline; color: rgb(51, 51, 51); line-height: 24px;" class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div class="">On Mar 1, 2015, at 4:20 PM, Manon Theroux <<a href="mailto:manon.theroux@gmail.com" class="">manon.theroux@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class="">Here is how I would summarize the thinking behind the instructions in the DCRM(C) draft, based on my recollection of the discussions of the DCRM(C) editorial team (the other editors are welcome to chime in as well!):<br class=""><br class=""></div>The editors wanted to follow the default instructions in DCRM(B) Appendix E, which say to create a new bib record for each ISSUE. We agreed that if a resource is known to have been issued in both colored and uncolored form (e.g. it bears text such as "Price ten dollars plain, twelve dollars coloured"), the two versions would represent separate issues. Following Appendix E, separate records would thus be in order (with different 300 $b). Other differentiating information could be added to the record as well, depending on cataloger judgment, institutional policy, etc. <br class=""></div><br class=""></div>The harder question for us was what to do in cases of doubt about whether hand-colored material had been issued that way or not, both in our Appendix E and Area 5 (300 $b) instructions. <span style="font-size:12pt;font-family:"Palatino Linotype"" class=""></span>Our research suggested that it was very common for cartographic material to be issued with hand-coloring, that early map-sellers often offered hand-coloring as an option at the point of sale, that the resulting color might vary somewhat from copy to copy, and that color wasn't added simply for decorative reasons but also to serve informational purposes - to delineate boundaries, show routes of travel, differentiate between land and water masses, etc. On the other hand, we also recognized that it was always possible for someone to have purchased a map
uncolored and then decided after the fact to add some color to it, and the cataloger could not know if that was the case. In the end, we were swayed by how common the issuing of maps with hand-coloring seemed to be in the trade. We decided that, in cases of doubt, the cataloger should assume material with hand-coloring had been issued that way (for the purposes of area 5) and assume the material had been issued both with and without hand-coloring (for the purposes of Appendix E). It was not an easy decision though.<br class=""></div><div class=""><br class=""></div>Because DCRM(C) is AACR2-based, we did not have to grapple with some of the RDA and WEMI issues now facing the DCRM2 group. I note that RDA chapter 7, which covers "the attributes of works and expressions that are associated with the
intellectual or artistic content of a resource", includes RDA 7.17 (Colour Content). This suggests that a resource issued in both colored and uncolored formats would be represented by two different expressions (in WEMI terms), and separate records might therefore be justified, but I confess I have not given the matter a great deal of thought. <br class=""><br class="">It is my understanding that the April 2015 update of RDA will remove the troublesome sentence in RDA 7.17.1.1 ("For instructions on recording information on hand-coloured items, see RDA 3.21") that mistakenly assumes all hand-coloring must be item-level information; see 6JSC/CILIP/4.<br class=""><br class="">The FRBR model doesn't always work well for rare materials. Francis has passed along a citation to a
2012 article by by Patrick Le Boeuf called "Modeling Rare and Unique
Documents: Using FRBRoo/CIDOC CRM" (Journal of Archival Organization, 10:96-106) that sounds interesting. I will have to find time to read it.<br class=""><br class=""></div><div class="">Manon<br class=""><br class=""></div><div class="">--<br class=""></div></div><div class=""><div class=""><div class="">Manon Théroux<br class=""></div><div class="">Head of Technical Services<br class=""></div><div class="">U.S. Senate Library<br class=""></div><div class="">Washington, DC<br class=""></div><div class=""><br class="">
</div><div class=""><br class=""></div></div></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Thu, Feb 26, 2015 at 12:44 PM, Lapka, Francis <span dir="ltr" class=""><<a href="mailto:francis.lapka@yale.edu" target="_blank" class="">francis.lapka@yale.edu</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div link="#0563C1" vlink="#954F72" lang="EN-US" class="">
<div class=""><p style="margin-left:0in" class=""><span style="font-family:"Georgia",serif" class="">On behalf of the DCRM2 task force, I would like community thoughts on what appears to be an inconsistency on the matter of Variations requiring a new record (Appendix
E).<u class=""></u><u class=""></u></span></p><p style="margin-left:0in" class=""><span style="font-family:"Georgia",serif" class=""><u class=""></u> <u class=""></u></span></p><p style="margin-left:0in" class=""><span style="font-family:"Georgia",serif" class="">The draft of DCRM(C), rule E1.2 says: “…
</span><span style="font-family: 'Palatino Linotype', serif;" class="">generally consider that a new bibliographic record is required whenever the material distinguishes itself from other variants by one or more of the following characteristics: …</span><span style="font-family:"Georgia",serif" class=""><u class=""></u><u class=""></u></span></p><p style="margin-left:0in" class=""><span style="font-family:"Georgia",serif" class=""><u class=""></u> <u class=""></u></span></p><p style="margin-left:1.0in" class="">
<u class=""></u><span style="font-family:Symbol" class=""><span class="">·<span style="font:7.0pt "Times New Roman"" class="">
</span></span></span><u class=""></u><span style="font-family:"Georgia",serif" class="">change in the presence of hand coloring, if there is evidence that the resource was issued both with and without the hand coloring (in case of doubt, assume the material was issued both
ways)”<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span style="font-family:"Georgia",serif" class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span style="font-family:"Georgia",serif" class="">Contrast this to DCRM(G), rule E1.3, which says: “Examples of differences that do not in themselves necessarily signal the need for a new record in the absence of other differences include: …<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span style="font-family:"Georgia",serif" class=""><u class=""></u> <u class=""></u></span></p><p style="margin-left:1.0in" class="">
<u class=""></u><span style="font-family:Symbol" class=""><span class="">·<span style="font:7.0pt "Times New Roman"" class="">
</span></span></span><u class=""></u><span style="font-family:"Georgia",serif" class="">the presence or absence of hand-coloring<u class=""></u><u class=""></u></span></p><p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Georgia",serif" class=""><u class=""></u> <u class=""></u></span></p><p style="margin-left:1.0in" class="">
<u class=""></u><span style="font-family:Symbol" class=""><span class="">·<span style="font:7.0pt "Times New Roman"" class="">
</span></span></span><u class=""></u><span style="font-family:"Georgia",serif" class="">a difference in printed colors”<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span style="font-family:"Georgia",serif" class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span style="font-family:"Georgia",serif" class="">The other DCRM manuals do not explicitly treat the issue of color in this context. That said, the matter is still relevant to other formats. It is common, for example, for publishers of color-plate
books to announce (on the item) the availability of the book in colored and uncolored versions, at different prices. In this circumstance, it is uncommon practice (as far as I know) to create separate records for the colored and uncolored versions.<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span style="font-family:"Georgia",serif" class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span style="font-family:"Georgia",serif" class="">The default DCRM guideline is to “assume that a separate bibliographic record [i.e. a new Manifestation?] will be created for each bibliographic variant that represents what is referred to as an
‘edition’ in AACR2 and an ‘issue’ in bibliographic scholarship.” It’s not a leap to argue that a difference in coloring meets the definition of a distinct
<i class="">issue</i> (from DCRMB): “<span style="" class="">A group of published copies which constitutes a consciously planned publishing unit, distinguishable from other groups of published copies by one or more differences designed expressly to identify the group
as a discrete unit</span>.”<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span style="font-family:"Georgia",serif" class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span style="font-family:"Georgia",serif" class="">I would like DCRM2 to take a consistent (and principled) stand on the matter, allowing (as DCRM does) for agencies to vary when it makes sense to do so. What, then, would make most sense as the
<i class="">default</i> approach?<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span style="font-family:"Georgia",serif" class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span style="font-family:"Georgia",serif" class="">I’ve already received useful comments from members of the Cartographic team on this question, and I encourage them to chime in again here.<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span style="font-family:"Georgia",serif" class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span style="font-family:"Georgia",serif" class="">Thanks,<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span style="font-family:"Georgia",serif" class="">Francis<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span style="font-family:"Georgia",serif" class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span style="font-family:"Georgia",serif" class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span style="font-family:"Georgia",serif" class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span style="font-family:"Georgia",serif" class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span style="font-family:"Georgia",serif" class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span style="font-family:"Georgia",serif" class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span style="font-family:"Georgia",serif" class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span style="font-family:"Georgia",serif" class=""><u class=""></u> <u class=""></u></span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri Light",sans-serif" class="">Francis Lapka · Catalog Librarian<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri Light",sans-serif" class="">Department of Rare Books and Manuscripts<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri Light",sans-serif" class="">Yale Center for British Art<u class=""></u><u class=""></u></span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri Light",sans-serif" class=""><a href="tel:203.432.9672" value="+12034329672" target="_blank" class="">203.432.9672</a> ·
<a href="mailto:francis.lapka@yale.edu" target="_blank" class=""><span style="color:blue" class="">francis.lapka@yale.edu</span></a><u class=""></u><u class=""></u></span></p><p class="MsoNormal"><u class=""></u> <u class=""></u></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri Light",sans-serif" class="">BUILDING CONSERVATION PROJECT<br class="">
The Center will be closed from January 2, 2015 through February 2016 for its <a href="http://britishart.yale.edu/architecture/building-conservation-project" target="_blank" class="">
<span style="color:blue" class="">Building Conservation Project</span></a>. </span><span style="font-size:10.0pt;font-family:"Calibri Light",sans-serif" lang="EN-GB" class="">Please email the
</span><span style="font-size:10.0pt;font-family:"Calibri Light",sans-serif" class=""><a href="mailto:ycba.studyroom@yale.edu" target="_blank" class=""><span style="color:blue" lang="EN-GB" class="">Study Room</span></a> and/or the
<a href="mailto:ycba.reference@yale.edu" target="_blank" class=""><span style="color:blue" lang="EN-GB" class="">Reference Library</span></a>
</span><span style="font-size:10.0pt;font-family:"Calibri Light",sans-serif" lang="EN-GB" class="">to request an appointment, which will be accommodated on a limited basis Tuesday-Friday, 10 am-4 pm, contingent upon the construction schedule.
</span><span style="font-size:10.0pt;font-family:"Calibri Light",sans-serif" class=""><u class=""></u><u class=""></u></span></p><p class="MsoNormal"><u class=""></u> <u class=""></u></p>
</div>
</div>
</blockquote></div><br class=""></div>
</div></blockquote></div><br class=""></div></div></div></blockquote></div></div></blockquote></div><br class=""></div></body></html>