<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=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Orator Std";
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 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:Consolas;
panose-1:2 11 6 9 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.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
span.EmailStyle19
{mso-style-type:personal-compose;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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;}
--></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="MsoPlainText"><span style="font-family:"Cambria","serif";color:#1F497D">Elizabeth,<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-family:"Cambria","serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-family:"Cambria","serif";color:#1F497D">I am pleased you brought this to our attention, and I think you make a number of excellent points, including the idea that attribution is probably best considered as a distinct
qualifier element, separate from role (or relationship). As you point out, CCO (and the LIDO schema) have logically created a separate element for qualification data. Other example values given in LIDO for qualification include: studio of, workshop of, atelier
of, office of, assistant of, associate of, pupil of, follower of, school of, circle of, style of, after copyist of, manner of. I think some of these qualifiers might be of use to our community too.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-family:"Cambria","serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-family:"Cambria","serif";color:#1F497D">To my mild surprise, I notice now that MARC has even defined an “attribution qualifier” field already, in $j (of x00 fields). See:<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-family:"Cambria","serif";color:#1F497D"><a href="http://www.loc.gov/marc/bibliographic/bdx00.html"><span style="color:#1F497D">http://www.loc.gov/marc/bibliographic/bdx00.html</span></a><o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-family:"Cambria","serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-family:"Cambria","serif";color:#1F497D">Should the RBMS relator term for “attributed name” be used in $j? I’ve only ever seen it in $e.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-family:"Cambria","serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-family:"Cambria","serif";color:#1F497D">This item has not yet generated discussion among CC:DA, so far as I know, but I would be happy to convey our concerns.<o:p></o:p></span></p>
<p class="MsoPlainText"><span style="font-family:"Cambria","serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span style="font-family:"Cambria","serif";color:#1F497D">Francis<o:p></o:p></span></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">-----Original Message-----<br>
From: <a href="mailto:dcrm-l-bounces@lib.byu.edu">dcrm-l-bounces@lib.byu.edu</a> <a href="mailto:[mailto:dcrm-l-bounces@lib.byu.edu]">
[mailto:dcrm-l-bounces@lib.byu.edu]</a> On Behalf Of Elizabeth O'Keefe<br>
Sent: Wednesday, August 01, 2012 12:35 PM<br>
To: <a href="mailto:dcrm-l@lib.byu.edu">dcrm-l@lib.byu.edu</a><br>
Subject: [DCRM-L] BL Proposal 6JSC/BL/8 on relationships with works of unknown or uncertain origin<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">A paper on recording relationships of persons, families, and corporate bodies to works of unknown or uncertain origin was recently posted on the JSC website by the British Library:<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><a href="http://www.rda-jsc.org/docs/6JSC-BL-8.pdf"><span style="color:windowtext;text-decoration:none">http://www.rda-jsc.org/docs/6JSC-BL-8.pdf</span></a>
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">This situation probably occurs more frequently in special collections cataloging than in any other type of library cataloging, so I wanted to share my observations on the proposal with others on this list.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Special collections contain many resources that cannot be attributed with certainty to a person, family, or corporate body, so the new instruction in Proposal 6JSC/Bl/8, 19.3.1.4, is very welcome. But I have reservations about the use
of the relationship designator field to carry this information, and about limiting the scope of the proposal to the work level.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">The new instruction reads:<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">19.3.1.4 Other Person, Family, or Corporate Body Associated with Works of Uncertain or Unknown Origin If a work of uncertain or unknown origin has been attributed to one or more person, family, or corporate body, but the person, family,
or corporate body actually responsible for creation of the work, in [typo for "is"] uncertain, record the persons, families, and corporate bodies attributed to the work, in accordance with the general guidelines on recording relationships to persons, families,
and corporate bodies associated with a resource given under 18.4 RDA.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">The proposed term is:<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">attributed creator A person, family, or corporate body for whom there is, or once was, substantial authority for designating as creator of the related work<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">All the other relationship designators in Appendix I identify roles.<o:p></o:p></p>
<p class="MsoPlainText">Attribution information is not the same as role information. It does not identify a role, it indicates present uncertainty about whether the named entity performed that role, or the fact that the role was previously but incorrectly attributed
to the entity. This is a separate type of information, and should be treated separately. Cf. the treatment of attribution information in Cataloging Cultural Objects, a standard for describing art and cultural works. CCO treats attribution as a separate data
element qualifying the names of creators and other entities responsible for or associated with an object.
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Example:<o:p></o:p></p>
<p class="MsoPlainText">Name: Ricci, Marco<o:p></o:p></p>
<p class="MsoPlainText">Role: painter<o:p></o:p></p>
<p class="MsoPlainText">Qualifier: attributed to<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">RDA does not define uncertainty as a separate data element. Doing so would be very useful, not just for relationships between persons, families, and corporate bodies and resources, but for relationships between resources and relationships
between persons, families, and corporate bodies. Perhaps RDA will do this someday. In the meantime, this information has to be carried somewhere, and there is precedent for using a relator term, "attributed name", to carry attribution information, so the
relationship designator seems the only viable option for now. <o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">However, the proposed term, "attributed creator", limits its use to works. This is the intention of the authors of the proposal: "based on our experience we see no compelling justification for equivalent changes at expression or manifestation
level." <o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">But attributed names are not associated solely with works. Looking only at the OPACS of the Morgan Library and the Folger, I was able to find attributed names on the expression, manifestation, and item level:<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Expression level: translator, compiler, illustrator, illuminator<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Manifestation level: printer, publisher, writer of manuscript (as opposed to creator of its content)<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Item level: binder, annotator<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">I'm sure subscribers to this list could come up with many more examples.
<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">There is no generic equivalent to "creator" for persons associated with expressions, manifestations, and items. The relator term currently appearing in the RBMS and MARC code list, "attributed name" would be preferable to "attributed
creator", since it could be used for relationships on all four FRBR levels.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">One other point: The proposed term does not distinguish between current and former attributions. This is an extremely useful distinction, especially for art works, where attributions frequently change, and where it is desirable to record
previous attributions. Using two different terms, "attributed name" and "formerly attributed name" would save users having to scan the notes to discover whether the attribution is current or rejected.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">I would be very interested in hearing what other special collections catalogers think about the BL proposal.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Liz O'Keefe<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Elizabeth O'Keefe<o:p></o:p></p>
<p class="MsoPlainText">Director of Collection Information Systems The Morgan Library & Museum<o:p></o:p></p>
<p class="MsoPlainText">225 Madison Avenue<o:p></o:p></p>
<p class="MsoPlainText">New York, NY 10016-3405<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">TEL: 212 590-0380<o:p></o:p></p>
<p class="MsoPlainText">FAX: 212-768-5680<o:p></o:p></p>
<p class="MsoPlainText">NET: <a href="mailto:eokeefe@themorgan.org"><span style="color:windowtext;text-decoration:none">eokeefe@themorgan.org</span></a><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Visit CORSAIR, the Library’s comprehensive collections catalog, now on the web at
<a href="http://corsair.themorgan.org"><span style="color:windowtext;text-decoration:none">http://corsair.themorgan.org</span></a><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
</div>
</body>
</html>