<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: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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
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="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<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""> Program for Cooperative Cataloging [mailto:PCCLIST@LISTSERV.LOC.GOV]
<b>On Behalf Of </b>Chew Chiat Naun<br>
<b>Sent:</b> Friday, December 21, 2012 3:16 PM<br>
<b>To:</b> PCCLIST@LISTSERV.LOC.GOV<br>
<b>Subject:</b> Re: [PCCLIST] RBMS Bibliographic Standards Committee response to PCC Relationship Designator Guidelines TG Report<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The posting by RBMS Controlled Vocabularies and the RBMS Bibliographic Standards Committee raises a number of important points. I'd like to make an initial response on behalf of the PCC Relationship Designator Guidelines Task Group. Please
regard this message as commentary and not as an official PCC response, since clearly final authority for policy decisions rests with the PCC Policy Committee.<br>
<br>
We said early in our report (2.1) that it will be important for relationship designator vocabularies to continue to be developed within specialist domains. The relationship between the needs of specialist communities, including in some cases their need for
supplementary or independent vocabularies, and general RDA practice occupied a large part of the task group's time. It seemed to us that, in addition to specific guidelines that cataloguers would need for the initial implementation of RDA, this issue would
require long-term attention as our environment and practices evolve. Our recommendations should be seen as an initial step in that longer-term effort.<br>
<br>
We made a proposal in 5.1 for changes or additions to be submitted via the Standing Committee on Standards, but we also envisaged that specialist communities might prefer to establish a separate process to submit their proposals. We included language to cover
the latter scenario with communities like RBMS in mind, though we did not propose any specific mechanism. I have heard in recent days that some ideas for such a process have been discussed within PCC, and I look forward to further exploration of the possibilities
by all parties. In hindsight, our report did not adequately distinguish between two quite different cases: one in which an individual cataloguer working with the RDA relationship designator vocabulary makes a proposal which may or may not be accepted, and
the other in which a community has already approved a term for use in an independent vocabulary but submits a proposal for RDA in the interest of harmonizing the vocabularies. It was not our intention to suggest that SCS or JSC should have the power of veto
over any non-RDA vocabularies. I hope this will allay at least some of RBMS's concerns about our recommendations.
<br>
<br>
I'd like to make a few broader points about the thinking behind the task group's recommendations. The RBMS submission points out that "the special collections community has a long history of using relationship designators, and identification of the source of
a term has not been an issue". That is certainly true. However, RDA brings the prospect of much wider use of relationship designators by the general cataloguing community, and the increased scope for conflict brings greater urgency to the need to manage relationship
designator vocabularies from multiple sources. This issue has already arisen in other contexts, such as with genre/form vocabularies. However, relationship designators pose a special problem in that MARC does not currently allow us to specify source vocabularies
at the subfield level. We'd be interested if others have proposals about how this could be done. But it is a significant obstacle and we did not feel confident about proposing any approach that would be contingent on any potential solution finding acceptance,
particularly at this late stage of MARC's life cycle. This is why our report emphasizes the need for a way to minimize conflicts by aligning alternative vocabularies wherever possible. Even so, that will not eliminate all potential inconsistencies among vocabularies,
and we do not pretend that it is in itself a long-term solution to the problem. It is true that, if RDA relationship designators are not adopted by the general community, the problem of source vocabularies will be no worse than in the past. But as I hope our
report makes evident, we see the widespread adoption of relationship designators as something to be encouraged. In addition to the additional information relationship designators provide about various parties' contribution to a resource, they also allow records
to be parsed so as to allow responsibility to be attributed for the appropriate entity - WEMI in the case of FRBR/RDA, work/instance in the case of Bibframe.
<br>
<br>
The RBMS submission goes on to point out that "Creator" and "Publisher" are not true RDA relationship designators. We recommended that these terms nonetheless be used in that fashion because we felt it would be advantageous, for the reasons just given, to be
able to assign a relationship designator for entities in those roles even in circumstances where the cataloguer is unable to ascertain a more specific relationship. Although the terms are not defined in Appendix I, they are elements in RDA and are defined
in the element set itself, in the scope notes in 19.2.1.1 and 21.3.1.1 respectively.
<br>
<br>
Finally, the RBMS submission points out several errors in our presentation of their list of relationship designators. We'll of course be happy to make the necessary corrections.<br>
<br>
I'd welcome any further discussion of these issues or any others raised in the report.<br>
<br>
-- <br>
Chew Chiat Naun<br>
University of Minnesota Libraries<br>
160 Wilson Library<br>
Minneapolis, MN 55455<br>
<a href="tel:%28612%29%20625-5615" target="_blank">(612) 625-5615</a><o:p></o:p></p>
<div>
<p class="MsoNormal">On 19 December 2012 14:00, Lapka, Francis <<a href="mailto:francis.lapka@yale.edu" target="_blank">francis.lapka@yale.edu</a>> wrote:<o:p></o:p></p>
<div>
<div>
<p>[Please excuse multiple postings]<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">Posted on behalf of the RBMS Bibliographic Standards Committee and Ryan Hildebrand, editor, RBMS Controlled Vocabularies. Please CC Ryan Hildebrand
<a href="mailto:ryan.hildebrand@austin.utexas.edu" target="_blank">ryan.hildebrand@austin.utexas.edu</a> on any discussion.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">---<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">The RBMS Bibliographic Standards Committee (BSC) objects to several assertions and recommendations contained in the PCC Relationship Designator Guidelines Task Group Report.
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Specific areas of the report are addressed below, but we would like to preface our comments by stating that the BSC and its Controlled Vocabulary Subcommittee are committed to harmonizing
our terminology with that of RDA whenever possible, within the necessary constraints of ANSI/NISO Z39.19 Guidelines for the Construction, Format, and Management of Monolingual Controlled Vocabularies and excepting rare-materials reasons for departure.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">On the topic of Z39.19, we are concerned that no mention was made of a guiding standard for the work of the PCC SCS. It is paramount that the Task Group considers the role of Z39.19
in the creation of controlled vocabularies, and that the RDA appendices conform to this standard.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">3.2
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">“The need for a process to manage the development of the lists is made more urgent by the absence in MARC 1XX and 7XX of any way to identify a term’s source vocabulary.”<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">The special collections community has a long history of using relationship designators, and identification of the source of a term has not been an issue. We question the level of
concern, which is certainly not present in RDA, over identifying sources of terms. Nowhere is it implied that relationship designators in an RDA record will be sourced from an RDA list. Concern over terminology sources would be better handled by a MARC proposal.
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">4.1.1
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">“If you cannot ascertain a more specific relationship, assign the element term, e.g., Creator or Publisher.”<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Although the BSC is strongly in favor of using “publisher” as a relationship designator, and acknowledges the importance of “creator” in the archival community, the above statement
seems to violate principles of the Task Group’s report, as neither “creator” nor “publisher” is an RDA relationship designator. Neither is a discrete term appearing in the appendices with a scope note to guide in its application.
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">5.1<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">“Specialist communities may establish their own methods for vetting new relationship designators from their communities and submitting those terms to the JSC.”<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">The special collections community has been developing its own controlled vocabulary since 1983 through the concerted efforts of RBMS and ACRL. Guidelines appropriate to the construction
and maintenance of the vocabulary have been firmly in place for decades. Changes to guidelines and workflows, specifically requisite approval of terminology by an additional agency, will impede our progress, limit our effectiveness, and perhaps limit our terminology.
If our list were submitted to the JSC at present, there is considerable doubt that several key terms (publisher, bookseller, and distributor) would be accepted.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Several months ago, the BSC discussed and rejected the option of submitting our relationship designators for inclusion in RDA, as we prefer to retain control of RBMS Controlled
Vocabularies: Relationship Designators, a cataloging resource in its own right. <o:p>
</o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">5.2<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">“PCC catalogers may use a term not in the RDA lists if they have also submitted the term to PCC SCS for inclusion in RDA.”<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">As the RBMS Controlled Vocabularies are developed by and according to the needs of the special collections community, it is not logical to have terms we have been using for years,
or our new proposals, vetted by another body before we are permitted to use them.
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">This restriction leaves specialist communities no recourse if a proposal is rejected. Examples of particular importance to the special collections community are “publisher,” “distributor,”
and “bookseller.” None of these are RDA relationship designators, and it is our understanding that the JSC has no interest in adding these terms to Appendix I. Implementation of the guidelines recommended in the report would mean that these relationship designators,
some of which are acknowledged by the TG in C5 as core to the special collections community, could no longer be used. This is not an acceptable outcome and is wholly contrary to the intentions of the JSC.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Appendix A:<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">“A.2.3 Charge a PCC group to evaluate relationship designator terms that are used by specialist communities but are not currently in the RDA appendices.”<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">We strongly agree with A.2.3, but regret that this was not central to the TGs initial charge. It would seem prudent to consult with specialist communities, particularly those with
a strong history of using relationship designators, before codifying instructions that will affect those communities. Charging such a group is an essential next step.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">“A.2.7 Undertake a review of OCLC and other available data on usage of relationship designators after the first year of implementation and survey libraries and specialist cataloging
communities on extent of adoption and obstacles encountered. Reevaluate guidelines in the light of the information gathered and consider issues requiring further work.”<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">We strongly agree with A.2.7.
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Appendix C:<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">C.5 Rare books and manuscripts<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">“The RBMS Controlled Vocabularies subcommittee has proposed scope notes to guide application of relationship designators by rare books and manuscripts catalogers.”<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">To be clear, these are not proposed scope notes; these are the actual scope notes associated with terms in the RBMS list of relationship designators, which have been reviewed and
approved by the BSC.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Although the special collections community benefits from the use of the terms “publisher” and “bookseller” we are confused by the presence of non-RDA terms in a list of PCC-recommended
relationship designators. <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">There are also a few errors in the chart. As the scope note for “honouree” suggests, the term is item-level. “Honouree of item” is the appropriate RDA term. The term also represents
a critical area in which RDA and RBMS terminologies diverge. The RDA term uses British spelling, while RBMS uses American spelling (Z39.19 recommends dialectical consistency throughout a vocabulary).<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">The RBMS relationship designator “binder” can be either manifestation-level or item-level, depending on whether one is tracing the binder for all of the copies in a particular manifestation
or the binder for a unique binding on a single copy. The RBMS relationship designator "bookseller" may also be either manifestation-level or item-level depending on whether one is adding the tracing for a name in 260 subfield b, or one is adding a local tracing
for the seller of a specific copy.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">We request that the PCC Relationship Designator Guidelines Task Group reconsider the above areas of its report, and specifically, that it endorse rather than forbid the use of relationship
designators found in other controlled lists, without subjecting such terms to vetting by PCC SCS. Adopting the recommendations of the Task Group’s report will force special collections catalogers (and their institutions) into the position of having to choose
whether to follow their communal standards (developed after a great deal of thought and discussion) or those of PCC. That will likely result in fewer records being coded PCC, creating problems for shared record use.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Sincerely,<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Ryan Hildebrand, editor, RBMS Controlled Vocabularies<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Jane Carpenter, chair, RBMS Bibliographic Standards Committee<o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<br>
-- <br>
Chew Chiat Naun<br>
University of Minnesota Libraries<br>
160 Wilson Library<br>
Minneapolis, MN 55455<br>
<a href="tel:%28612%29%20625-5615" target="_blank">(612) 625-5615</a><o:p></o:p></p>
</div>
</body>
</html>