<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 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* 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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle18
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.apple-tab-span
{mso-style-name:apple-tab-span;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1842307875;
mso-list-type:hybrid;
mso-list-template-ids:-7576128 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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-size:12.0pt;color:black">One of the more interesting items on the agenda of the CC:DA meetings at Annual was a discussion paper on machine-actionable data elements in RDA chapter 3. I encourage everyone to take a look:<br>
<a href="http://www.libraries.psu.edu/tas/jca/ccda/docs/tf-MRData3.pdf"><span style="color:#1155CC">http://www.libraries.psu.edu/tas/jca/ccda/docs/tf-MRData3.pdf</span></a><br>
<br>
>From the Summary and Recommendations section of the paper:</span><span style="font-size:12.0pt;color:black"><br>
<br>
</span><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F497D">The Task Force was charged to evaluate the structure of data elements in RDA Chapter 3 that contain quantitative information.
<br>
<br>
After studying the elements for Extent and Dimension, the Task Force recommends an overhaul of RDA’s treatment of these elements. Our study of this issue has also highlighted the ambiguity in RDA between content and carrier, especially in regards to extent.
We therefore have two recommendations:<br>
<br>
1. We recommend that RDA add a treatment of extent that is machine-actionable, using this report and the Aspect–Unit–Quantity model described here as a basis of discussion and detailed recommendations.<br>
<br>
2. We recommend a review of the treatment of extent of content (“extent of Expression” in FRBR terminology) at the same time, to strengthen its representation in RDA and provide a more coherent treatment of extent.<br>
<br>
The Task Force asks CC:DA to send this report to the JSC for discussion at the JSC’s 2012 meeting.</span><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:black"><br>
<br>
</span><span style="font-size:12.0pt;font-family:"Arial","sans-serif";color:black">…</span><span style="font-size:12.0pt;color:black"><br>
<br>
</span><span style="font-size:12.0pt;color:black">The paper proposes a model for recording extent and dimensions using granular data elements. A (very simple) example from the paper illustrates the proposal:</span><span style="font-size:12.0pt;color:black"><br>
<br>
</span><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F497D">Currently, and using ISBD punctuation, RDA would have us describe a printed volume as:<br>
245 pages ; 23 cm<br>
<br>
The Aspect–Unit–Quantity model would break up that statement into its separate parts:<br>
<br>
Aspect: <span class="apple-tab-span"> </span>extent/number of subunits<br>
Unit: <span class="apple-tab-span"> </span>pages<br>
Quantity: <span class="apple-tab-span"> </span>245<br>
<br>
Aspect: <span class="apple-tab-span"> </span>height<br>
Unit: <span class="apple-tab-span"> </span>centimeters<br>
Quantity: <span class="apple-tab-span"> </span>23</span><span style="font-size:12.0pt;color:black"><br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">…<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><br>
</span><span style="font-size:12.0pt;color:black">Here, aspect and unit are based on controlled vocabularies, and quantity is always a numerical value. I think it is assumed that if data is recorded in this fashion, it would probably be rendered in a different
form (via algorithm) when presented in the catalog. <br>
<br>
A couple of points merit emphasis:<br>
1. The paper leaves unanswered the question of whether or not the proposed machine-readable version of these elements would replace the current model or exist in parallel. Given the vast amount of legacy records using the traditional model for recording these
elements (i.e. with text strings), it seems unlikely that discarding the old model would be a reasonable alternative (nor does it seem likely that the data recorded in textual strings could be automatically converted to machine-actionable form).<br>
2. This is just a discussion paper, not a revision proposal.<br>
<br>
At Annual, CC:DA approved the TF’s request to send the paper to JSC for discussion at their upcoming 2012 meeting.<br>
<br>
Peter Rolla, chair of the TF, indicated that he still welcomes comments (and possible examples) from various cataloging communities. I would be happy to collect and forward such comments.</span><span style="font-size:12.0pt;font-family:"Arial","sans-serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><br>
I think the paper is an interesting exercise, but I wish it had included several complex examples. I’m not entirely convinced the proposed model, as-is, could handle aspects of the extent and dimensions elements that are quite common in catalog records for
early printed material. Take, for example, the following made-up statement of extent:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Courier New";color:black">x, [8], 15-32, 186 [i.e. 168] p., 12 leaves of plates ([2] folded)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Courier New";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">In RDA, using the alternatives for early printed material and the policy statement proposed by PCC for early printed material, I think this would be described as:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Courier New";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Courier New";color:black">x, [8], 15-32, 186, that is 168, pages, 12 leaves of plates ([2] folded)
</span><span style="font-size:12.0pt;color:black"><br>
<br>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">An attempt to encode this description in the Aspect-Unit-Quantity model proposed in the paper reveals a number of concerns.
<i>Some</i> of these include:<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="font-size:12.0pt;font-family:Symbol;color:black"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:12.0pt;color:black">It’s not clear how the model would handle numbered ranges in an extent statement, such as “15-32” in this example.
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="font-size:12.0pt;font-family:Symbol;color:black"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:12.0pt;color:black">How would the model handle corrections to misleading numbering, as in “186, that is 168, pages” in the example?<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="font-size:12.0pt;font-family:Symbol;color:black"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:12.0pt;color:black">At times, it seems a qualifier element would be useful, to handle data such as “([2] folded)”.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2"><![if !supportLists]><span style="font-size:12.0pt;font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:12.0pt">If we are recording each subunit as a granular data element, then must we also hard-code the sequence of those subunits? That is, we must specify that “x” comes before “[8]” which comes before “15-32,”
etc. This is one place where the order of data values very much matters. Even if the specification is hidden from the cataloging interface, shouldn’t this be recorded in a distinct field, as part of the model?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black">Those who find this interesting may wish to see the similar treatment of this topic in CCO (Cataloging Cultural Objects), which also employs a comparable data model for physical descriptions:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:13.5pt;color:black"><a href="http://cco.vrafoundation.org/downloads/PartTwo_3-PhysicalCharacteristics.pdf"><span style="font-size:11.5pt;color:#1155CC">http://cco.vrafoundation.org/downloads/PartTwo_3-PhysicalCharacteristics.pdf</span></a></span><span style="font-size:12.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Again, I’d be happy to forward any thoughts from our community to the task force.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Best,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Francis<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">RBMS Liaison to CC:DA<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">_________________________________<o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:12.0pt">Francis Lapka, Catalog Librarian<o:p></o:p></span></b></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Yale Center for British Art, Department of Rare Books and Manuscripts<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">1080 Chapel Street, PO Box 208280, New Haven, CT 06520<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">203.432.9672 </span><a href="mailto:francis.lapka@yale.edu"><span style="font-size:12.0pt">francis.lapka@yale.edu</span></a><span style="font-size:12.0pt"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
</div>
</body>
</html>