<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:"Calibri Light";
panose-1:2 15 3 2 2 2 4 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
@font-face
{font-family:Corbel;
panose-1:2 11 5 3 2 2 4 2 2 4;}
@font-face
{font-family:ArialMT;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Georgia",serif;
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Georgia",serif;
color:#1F497D;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Georgia",serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Georgia",serif;
color:#993366;
font-weight:normal;
font-style:normal;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Georgia",serif;
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-compose;
font-family:"Georgia",serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">Thanks Deborah.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">I assume that you are advocating for the infinitely more sensible: [12], 72, [10], 48, [6], 228, [16] pages<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">If RDA adopts the idea of a separate element for pagination and foliation, I wonder if there’s now a stronger argument for reverting to the traditional form for such statements. That
is, if pagination is a sort of transcription (now divorced from extent), and if the identification of unnumbered pages is a form of supplied information within a transcription,
<i>then</i> RDA (per 2.2.4) tells us that the use of square brackets is a valid way to indicate that the information is supplied. So the traditional format for recording pagination would actually be more in tune with RDA principles (for transcription) than
the “unnumbered pages” nonsense.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D">I’d be happy to raise this idea when we present the proposal to CC:DA (what fun that discussion might be!); and/or Matthew or I could post such an argument on the CC:DA blog, in advance
of the meeting.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> dcrm-l-bounces@lib.byu.edu [mailto:dcrm-l-bounces@lib.byu.edu]
<b>On Behalf Of </b>Deborah J. Leslie<br>
<b>Sent:</b> Thursday, June 11, 2015 3:24 PM<br>
<b>To:</b> DCRM Users' Group<br>
<b>Subject:</b> Re: [DCRM-L] revision of extent, dimensions, etc. (ALA proposal)<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:ArialMT">I think the general proposal makes excellent sense. However, I am dismayed to see that the pagination and foliation element would still leave us with this ungainly
statement: <o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:ArialMT"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:ArialMT">12 unnumbered pages, 72 pages, 10 unnumbered pages, 48<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:ArialMT">pages, 6 unnumbered pages, 228 pages, 16 unnumbered<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:ArialMT">pages</span><span style="font-family:"Georgia",serif;color:#993366"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#993366"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;color:#31849B">Deborah J. Leslie | Folger Shakespeare Library |
</span><a href="mailto:djleslie@folger.edu"><span style="font-size:9.0pt">djleslie@folger.edu</span></a><span style="font-size:9.0pt;color:#31849B"> | 202.675-0369 | 201 East Capitol St., SE, Washington, DC 20003 | www. folger.edu<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-family:"Georgia",serif;color:#993366"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">
</span><a href="mailto:dcrm-l-bounces@lib.byu.edu"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">dcrm-l-bounces@lib.byu.edu</span></a><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif"> [</span><a href="mailto:dcrm-l-bounces@lib.byu.edu"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">mailto:dcrm-l-bounces@lib.byu.edu</span></a><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">]
<b>On Behalf Of </b>Lapka, Francis<br>
<b>Sent:</b> Wednesday, 10 June 2015 10:04<br>
<b>To:</b> </span><a href="mailto:dcrm-l@lib.byu.edu"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">dcrm-l@lib.byu.edu</span></a><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif"><br>
<b>Subject:</b> [DCRM-L] revision of extent, dimensions, etc. (ALA proposal)<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif">Hi all.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif">I call your attention to an RDA revision proposal that will be discussed in the CC:DA meeting at Annual:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Georgia",serif">Task Force on Machine-Actionable Data Elements in RDA Chapter 3 : Revision Proposal<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__alcts.ala.org_ccdablog_-3Fp-3D2032&d=AwMFAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=t7GDkvcZa922K6iya7a6MxgVxxw7OjL0m1rPBXkflk4&m=AIMB40I0lcZrVq_HfybnwsKNYFjzXEqHWIEqujk9Jy0&s=B1LZA2oMP_sCOiM2VXJuP5xz7CiFf9ouiFBkXbFTPJU&e="><span style="font-family:"Georgia",serif">http://alcts.ala.org/ccdablog/?p=2032</span></a><span style="font-family:"Georgia",serif"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-family:"Georgia",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif">The proposal suggests major changes to RDA for Extent and Dimensions, as well as Duration. The primary aim is to allow numerical measurements to be recorded in a machine-actionable fashion, applying
controlled vocabularies for measurement types, units, etc. In so doing, RDA would incorporate changes already introduced in cataloging standards of the museum and archival communities. The potential benefits are best outlined in the task force’s first discussion
paper: </span><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__alcts.ala.org_ccdablog_wp-2Dcontent_uploads_2012_06_tf-2Dmrdata3.pdf&d=AwMFAg&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=t7GDkvcZa922K6iya7a6MxgVxxw7OjL0m1rPBXkflk4&m=AIMB40I0lcZrVq_HfybnwsKNYFjzXEqHWIEqujk9Jy0&s=mUAA8fwJAa4VOKNgCjaiMyyJ4eR49OKUP4FaDa5Ds0M&e="><span style="font-family:"Georgia",serif">http://alcts.ala.org/ccdablog/wp-content/uploads/2012/06/tf-mrdata3.pdf</span></a><span style="font-family:"Georgia",serif">.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif">Now let’s get to the fun stuff.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif">In its review of Extent, the task force proposes greater adherence to the FRBR model by creating a new data element for Extent of the Content. For some formats, it has long been standard practice
to record a quantification of content as Extent, e.g. 3 maps, 1 drawing, or 2 scores. The proposal suggests that such information should now be recorded as an attribute of the Expression. For the DCRM community, this change most impacts descriptions for Cartographic,
Graphic, and Music resources. Extent of the <i>carrier</i> for such material would now be recorded in terms of sheets, volumes, etc., as appropriate (for more, see page 134 of the proposal).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif">The proposal also suggests a change that would impact all DCRM formats: a new element for Pagination and Foliation, which would re-purpose many of the instructions in RDA 3.4.5 Extent of Text. We
suggest this change because pagination and foliation data is fundamentally different than that recorded for other varieties of Extent of the Carrier. That is, only for subunits of volumes do we emphasize how the resource
<i>self-represents</i> its numeration. This practice is more like transcription than true measurement (for more, see pages 9-11 and 56 of the proposal).
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif">I’m happy to explain (and/or reconsider) anything in the proposal that is unclear or troublesome.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif">For those of you thinking “Egad!” or other oaths, rest assured that these changes are too major to be introduced quickly; and in places, there’s still obvious work to do. You will have plenty of
opportunity to shape how the proposal goes forward. Matthew Haugen (RBMS Liaison to CC:DA), Liz O’Keefe (ARLIS/NA Liaison to CC:DA, and contributor the proposal), and I are all keen to convey your sentiments.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif">Francis<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Georgia",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Corbel",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Corbel",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Corbel",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri Light",sans-serif">Francis Lapka · Catalog Librarian<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri Light",sans-serif">Department of Rare Books and Manuscripts<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri Light",sans-serif">Yale Center for British Art<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Calibri Light",sans-serif">203.432.9672 ·
</span><a href="mailto:francis.lapka@yale.edu"><span style="font-size:10.0pt;font-family:"Calibri Light",sans-serif">francis.lapka@yale.edu</span></a><span style="font-size:10.0pt;font-family:"Calibri Light",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>