<div dir="ltr">Thanks to everyone who has commented so far. A reminder that comments are due tomorrow, Thursday, August 20 so that our comments can be part of the CC:DA discussion before their vote on Friday. And if you have any comments after the deadline, I'll try to make sure they are heard too. Our collective expertise really does make a difference in shaping the ALA responses and JSC decisions on these proposals in November, so thank you again! <div><br></div><div><div style="font-size:13px"><a href="http://www.rda-jsc.org/sites/all/files/6JSC-LC-32.pdf" target="_blank">6JSC/LC/32: <span style="font-size:14.666666666666666px;font-family:Calibri;color:rgb(0,0,0);background-color:transparent;text-decoration:none;vertical-align:baseline">Revision to instructions for devised titles in RDA 2.3.2.11</span></a><br></div><div style="font-size:13px">This proposal seeks to provide greater flexibility for devising titles proper for manuscripts, ephemera, choreographic works, art, collections, etc.<br></div><div style="font-size:13px"><br>2.<br><a href="http://www.rda-jsc.org/sites/all/files/6JSC-BL-rep-2.pdf" target="_blank"></a></div><div style="font-size:13px"></div><div style="font-size:13px"><a href="http://www.rda-jsc.org/sites/all/files/6JSC-BL-rep-2.pdf" target="_blank">6JSC/BL rep/2 Simplification of RDA 2.7-2.10</a><br></div><div style="font-size:13px"><a href="http://www.rda-jsc.org/sites/all/files/6JSC-BL-rep-2-Appendix-B.pdf" target="_blank">6JSC/BL rep/2/Appendix </a><span style="font-size:14.666666666666666px;font-family:Calibri;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline"><a href="http://www.rda-jsc.org/sites/all/files/6JSC-BL-rep-2-Appendix-B.pdf" target="_blank">Simplification of RDA 2.7-2.10. Follow up/Appendix B</a><br></span></div><div style="font-size:13px"><span style="font-size:14.666666666666666px;font-family:Calibri;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline">This proposal and appendix are a follow-up to the much-discussed <a href="http://rda-jsc.org/6JSC/BL%20rep/1" target="_blank">6JSC/BL rep/1</a> from last year, which proposed significant changes to instructions for production/publication/distribution/manufacture (PPDM) statements; among other changes, the follow-up now treats production statements separately (see following proposal).<br><br>3.<br></span><a href="http://www.rda-jsc.org/sites/all/files/6JSC-BL-26.pdf" target="_blank">6JSC/BL/26: 2.7 Production statement: Changing method of recording</a><br></div><div style="font-size:13px">This related proposal treats production statements separately from<span style="font-size:14.666666666666666px;font-family:Calibri;color:rgb(0,0,0);background-color:transparent;vertical-align:baseline"> publication/distribution/manufacture statements, and regards recording of production elements for unpublished and non-self-describing resources.<br></span></div><div style="font-size:13px"><br>4.<br><a href="http://www.rda-jsc.org/sites/all/files/6JSC-CCC-18-rev.pdf" target="_blank">6JSC/CCC/18/rev Recording numbering for a series (2.12.9.3)</a><br></div><div style="font-size:13px">This proposal recommends a change from transcription to recording numbering for series, so as to be more consistent with numbering of serials<br></div><div style="font-size:13px"><br></div><div style="font-size:13px"></div><b style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:14px">Please share your comments on the DCRM-L list or send them directly to me at <a href="mailto:matthew.haugen@columbia.edu" target="_blank">matthew.haugen@columbia.edu</a></b><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 17, 2015 at 12:49 PM, Lapka, Francis <span dir="ltr"><<a href="mailto:francis.lapka@yale.edu" target="_blank">francis.lapka@yale.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d">The BL discussion papers concerning Publication (etc.) information are not easy to digest, but I will take a stab at summarizing some of the major suggestions; and
I append my responses.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d">1. Add entities for Place and Timespan, which may be used to record places and dates of publication (etc.) as related entities.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d">-- This is logical and deserves our full support (I think). The warrant is apparent in our current practice (e.g., our use of the 752 field to record places).<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d">2. Create an *<b>Imprint</b>* element to record complete (unparsed) statements concerning publication, distribution, or manufacture.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d">-- I favor this suggestion. If we have a means to record places, agents, and dates as related entities, I don’t think we gain much by parsing the sub-elements of imprint
statements. Recording the information in the form and order that it appears, unparsed, would better serve the principle of representation. For non-rare material, it might be sensible to record the place/agent/date as related entities, in addition to, or instead
of, the Imprint transcription. In a DCRM description, we likely want to require both.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d">-- I assume that if imprint information appears in more than one location within the resource, we would need to record more than one Imprint element. The paper says
to record each “in the order indicated …”. I wonder if we should consider, as a universal convention with any transcribed element,
<i>always</i> recording the source of the transcription (in a related data element). This may sound onerous, but with a well-designed cataloging client and a default array of sources, it could be simple.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d">3. Create a *<b>Colophon</b>* element to record complete (unparsed) statements concerning production (for unpublished resources).<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d">-- For the same reasons as above, this seem sensible. However the proposed name for the element is problematic.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d">4. Associate a copyright date – as data – with the Expression, not the Manifestation. Allow for
<i>transcription</i> of copyright dates for a Manifestation.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d">-- I agree with this suggestion. Might it also make sense to broaden the scope of copyright information to include the agents involved, so that a copyright transcription
can include the date and/or name of the copyright holder?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d">5. Remove (deprecate) the existing *<b>aggregate statements</b>* for PPDM information. Provide generic instructions to record elements for place, name and date associated
with the manifestation.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d">-- This is the portion of the paper that confuses me most. I think it proposes to retain the sub-elements in RDA 2.7 – 2.10 (e.g., Place of Publication) while reordering
the instructions so that all place elements – for publication, distribution, manufacture, and production -- are grouped together, and so on for names and dates. Places and names would remain transcribed; dates recorded.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d">-- The change would provide *<b>three</b>* options for recording PPDM information: a) as related entities; b) as unparsed Imprint or Colophon transcriptions; or c)
as transcribed sub-elements (parsed). I wonder if this is one alternative too many. While we have a ton of legacy data with PPDM data in the form of parsed transcriptions, I don’t see the benefit of providing that option going forward.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d">I am keen to hear other thoughts. I’m going to respond to the paper on Production Statements in a separate thread.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d">Francis<u></u><u></u></span></p><span class="">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Georgia",serif;color:#1f497d"><u></u> <u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <a href="mailto:dcrm-l-bounces@lib.byu.edu" target="_blank">dcrm-l-bounces@lib.byu.edu</a> [mailto:<a href="mailto:dcrm-l-bounces@lib.byu.edu" target="_blank">dcrm-l-bounces@lib.byu.edu</a>]
<b>On Behalf Of </b>Matthew C. Haugen<br>
<b>Sent:</b> Tuesday, August 11, 2015 3:04 PM<br>
<b>To:</b> DCRM Users' Group<br>
<b>Subject:</b> [DCRM-L] Review of RDA proposals: Week 2<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
</span><div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hello all,<u></u><u></u></p>
</div><div><div class="h5">
<p class="MsoNormal">Thank you for your insightful comments on the RDA proposals so far! Additional comments are still encouraged through Thursday. Next week's batch has a lot more to digest, including four with potentially significant rare materials implications,
so I'm posting them now to give you a head start. But the good news is, that's the last of them!<br>
<br>
<b><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Your feedback is especially valuable on these four proposals by</span></b>
<b><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">THURSDAY, AUGUST 20:</span></b><br>
<br>
1.<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.rda-2Djsc.org_sites_all_files_6JSC-2DLC-2D32.pdf&d=AwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=t7GDkvcZa922K6iya7a6MxgVxxw7OjL0m1rPBXkflk4&m=q_SIp8JGvAd7OYu2GHKZ2ZKnuQqjD052ZRnq0YD7V8Y&s=w5vPuCiYORboIDuHQef2-u3ZbbU6GvKjoLu-KJuonh8&e=" target="_blank"><br>
</a><u></u><u></u></p>
</div></div></div><div><div class="h5">
<div>
<p class="MsoNormal"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.rda-2Djsc.org_sites_all_files_6JSC-2DLC-2D32.pdf&d=AwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=t7GDkvcZa922K6iya7a6MxgVxxw7OjL0m1rPBXkflk4&m=q_SIp8JGvAd7OYu2GHKZ2ZKnuQqjD052ZRnq0YD7V8Y&s=w5vPuCiYORboIDuHQef2-u3ZbbU6GvKjoLu-KJuonh8&e=" target="_blank">6JSC/LC/32:
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black;text-decoration:none">
Revision to instructions for devised titles in RDA 2.3.2.11</span></a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">This proposal seeks to provide greater flexibility for devising titles proper for manuscripts, ephemera, choreographic works, art, collections, etc.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><br>
2.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.rda-2Djsc.org_sites_all_files_6JSC-2DBL-2Drep-2D2.pdf&d=AwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=t7GDkvcZa922K6iya7a6MxgVxxw7OjL0m1rPBXkflk4&m=q_SIp8JGvAd7OYu2GHKZ2ZKnuQqjD052ZRnq0YD7V8Y&s=Z-mBJI5XwEPraxAWOFSjeNPIyyPrhRQAHPJ9DoblvBA&e=" target="_blank">6JSC/BL
rep/2 Simplification of RDA 2.7-2.10</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.rda-2Djsc.org_sites_all_files_6JSC-2DBL-2Drep-2D2-2DAppendix-2DB.pdf&d=AwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=t7GDkvcZa922K6iya7a6MxgVxxw7OjL0m1rPBXkflk4&m=q_SIp8JGvAd7OYu2GHKZ2ZKnuQqjD052ZRnq0YD7V8Y&s=9LgXaGhb_6jp_WiYbqkT33UbvjHKRZ-gpjX0zqtNFnQ&e=" target="_blank">6JSC/BL
rep/2/Appendix </a><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.rda-2Djsc.org_sites_all_files_6JSC-2DBL-2Drep-2D2-2DAppendix-2DB.pdf&d=AwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=t7GDkvcZa922K6iya7a6MxgVxxw7OjL0m1rPBXkflk4&m=q_SIp8JGvAd7OYu2GHKZ2ZKnuQqjD052ZRnq0YD7V8Y&s=9LgXaGhb_6jp_WiYbqkT33UbvjHKRZ-gpjX0zqtNFnQ&e=" target="_blank">Simplification
of RDA 2.7-2.10. Follow up/Appendix B</a></span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">This proposal and appendix are a follow-up to the much-discussed
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__rda-2Djsc.org_6JSC_BL-2520rep_1&d=AwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=t7GDkvcZa922K6iya7a6MxgVxxw7OjL0m1rPBXkflk4&m=q_SIp8JGvAd7OYu2GHKZ2ZKnuQqjD052ZRnq0YD7V8Y&s=imjtM2blfZ9bUckePzaU3TbtFeLg67PEEpQ4wIBzVdc&e=" target="_blank">
6JSC/BL rep/1</a> from last year, which proposed significant changes to instructions for production/publication/distribution/manufacture (PPDM) statements; among other changes, the follow-up now treats production statements separately (see following proposal).<br>
<br>
3.<br>
</span><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.rda-2Djsc.org_sites_all_files_6JSC-2DBL-2D26.pdf&d=AwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=t7GDkvcZa922K6iya7a6MxgVxxw7OjL0m1rPBXkflk4&m=q_SIp8JGvAd7OYu2GHKZ2ZKnuQqjD052ZRnq0YD7V8Y&s=WSVKaPiaZfsaT4P6K6X2sH_hQhIIIqIVyP8u80mTn-8&e=" target="_blank">6JSC/BL/26:
2.7 Production statement: Changing method of recording</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">This related proposal treats production statements separately from<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> publication/distribution/manufacture statements, and regards recording of production elements
for unpublished and non-self-describing resources.</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><br>
4.<br>
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.rda-2Djsc.org_sites_all_files_6JSC-2DCCC-2D18-2Drev.pdf&d=AwMFaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=t7GDkvcZa922K6iya7a6MxgVxxw7OjL0m1rPBXkflk4&m=q_SIp8JGvAd7OYu2GHKZ2ZKnuQqjD052ZRnq0YD7V8Y&s=QgdIjKvmQQDLPkxQxoppI39AOUv3xCPb3qrx34gN1HU&e=" target="_blank">6JSC/CCC/18/rev
Recording numbering for a series (2.12.9.3)</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">This proposal recommends a change from transcription to recording numbering for series, so as to be more consistent with numbering of serials<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Please share your comments on the DCRM-L list or send them directly to me at
<a href="mailto:matthew.haugen@columbia.edu" target="_blank">matthew.haugen@columbia.edu</a></span></b><u></u><u></u></p>
</div></div></div><div><div class="h5">
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">The remaining proposals to be considered by CC:DA over the next few weeks seem to be out of scope for DCRM, so I won't be nagging the
list any further, but I'm still happy to post any comments to the CC:DA blog on your behalf. You can access all of the current proposals here:
<a href="http://rda-jsc.org/newjscdocs" target="_blank">http://rda-jsc.org/newjscdocs</a></span><u></u><u></u></p>
</div></div></div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Thanks again!</span><u></u><u></u></p>
</div><div><div class="h5">
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Matt</span><u></u><u></u></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><br>
-- <u></u><u></u></p>
<div>
<div>
<pre>-- <br>Matthew C. Haugen<br>Rare Book Cataloger<br>102 Butler Library<br>Columbia University Libraries<br>E-mail: <a href="mailto:matthew.haugen@columbia.edu" target="_blank">matthew.haugen@columbia.edu</a><br>Phone: <a href="tel:212-851-2451" target="_blank">212-851-2451</a><u></u><u></u></pre>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div></div></div>
</div>
</div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><pre cols="72">-- <br>Matthew C. Haugen<br>Rare Book Cataloger<br>102 Butler Library<br>Columbia University Libraries<br>E-mail: <a href="mailto:matthew.haugen@columbia.edu" target="_blank">matthew.haugen@columbia.edu</a><br>Phone: 212-851-2451</pre>
</div></div>
</div>