<div dir="ltr"><div>We are in the vetting stage of the Member Merge project, and although I can't find it in writing, I seem to remember being told that we were not supposed to be merging rare materials (which at this stage seemed fine, but not indefinitely). I certainly would be happy to see some more information, and, frankly, I'm sick of reporting all of the duplicates and crossing my fingers. I would be thrilled if additional training were available, and if possible RBMS BSC guidance.</div><div><br></div><div>Best,</div><div><br></div><div>Jennifer<br></div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Jan 4, 2019 at 4:18 PM Robert Maxwell <<a href="mailto:robert_maxwell@byu.edu">robert_maxwell@byu.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div class="gmail-m_-7801179504737698637WordSection1">
<p class="MsoNormal"><span style="color:rgb(31,73,125)">Ryan,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">We have been participating for a bit more than a year now. I think OCLC is aware of treatment of rare materials, and I did bring it up when we were doing our training, but it certainly wouldn’t hurt to ask OCLC
to emphasize it more in their training. I have merged a few records for early printed books, I believe correctly (!), so I don’t think it would be right for training just to say “never merge records coded ‘dcrmb’” or pre-1801 or whatever, there are plenty
of inappropriate duplicates in OCLC for early and rare materials that really should be merged (and since their machine-merge programs—I think—do take a hands-off approach to these materials, it is appropriate for human catalogers to have look and merge if
appropriate). Perhaps some of us could work with OCLC to develop a short addition to the training concerning this issue.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)">Bob<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10pt;color:rgb(31,73,125)">Robert L. Maxwell<br>
Ancient Languages and Special Collections Librarian<br>
6728 Harold B. Lee Library<br>
Brigham Young University<br>
Provo, UT 84602<br>
(801)422-5568</span><span style="color:rgb(31,73,125)"><u></u><u></u></span></p>
</div>
<p class="MsoNormal"><span style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
<div>
<div style="border-color:rgb(225,225,225) currentcolor currentcolor;border-style:solid none none;border-width:1pt medium medium;padding:3pt 0in 0in">
<p class="MsoNormal"><b>From:</b> DCRM-L <<a href="mailto:dcrm-l-bounces@lib.byu.edu" target="_blank">dcrm-l-bounces@lib.byu.edu</a>> <b>On Behalf Of
</b>Ryan Hildebrand<br>
<b>Sent:</b> Friday, January 4, 2019 1:04 PM<br>
<b>To:</b> 'DCRM Users' Group' <<a href="mailto:dcrm-l@lib.byu.edu" target="_blank">dcrm-l@lib.byu.edu</a>><br>
<b>Subject:</b> [DCRM-L] OCLC Member Merge and rare materials<u></u><u></u></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I am wondering if there are others who have completed OCLC’s Member Merge program (which allows us to merge duplicates in OCLC) and were left feeling concerned over the treatment of rare/special materials in the documentation. Throughout
the training, I was surprised that there was little discussion of rare materials, or the significance of 040 |e codes for rare/special standards. They are mentioned in the documentation and in a training video, but I am not aware of deeper treatment.
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I’ve linked to the documentation is below, but have also pasted in the relevant parts below my signature. My concern is that it appears one is guided to potentially merge rare-coded records based on guidelines that are at odds with DCRM
and its predecessors (although to be clear, catalogers are to consult Bibliographic Formats and Standards Chapter 4: When to input a new record). There is an explicit rare materials exception, but one is not guided to evaluate duplication in terms of cataloging
codes. At least that is how I read it. The exception is also problematic in that it correlates rare rules with only pre-1801 materials.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">I hope I do not sound overly critical, as Member Merge is an extremely valuable program. But I am curious to know what others think, and if outreach to OCLC seems appropriate.
<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Best,<u></u><u></u></p>
<p class="MsoNormal">Ryan<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Ryan Hildebrand<u></u><u></u></p>
<p class="MsoNormal">Authorities & Special Collections Cataloging Librarian<u></u><u></u></p>
<p class="MsoNormal">University of Oregon Libraries<u></u><u></u></p>
<p class="MsoNormal">1299 University of Oregon<u></u><u></u></p>
<p class="MsoNormal">Eugene OR 97403-1299<u></u><u></u></p>
<p class="MsoNormal">(541) 346-1844<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Link: <a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.oclc.org%2FWorldCat%2FMetadata_Quality%2FMember_Merge%2FGuidelines_for_merging_duplicate_books_records%253A_A_field-by-field_comparison&data=02%7C01%7Cfrancis.lapka%40yale.edu%7Cf5df418ff5f146ffe0e908d67268e8c0%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636822192260506293&sdata=syUWeADtb1NE%2F0GE02rlXwJ7%2BwXglKsZk%2BibUiQpD2I%3D&reserved=0" target="_blank">
https://help.oclc.org/WorldCat/Metadata_Quality/Member_Merge/Guidelines_for_merging_duplicate_books_records%3A_A_field-by-field_comparison</a><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Copy/paste:<u></u><u></u></p>
<h2><span style="font-family:"Calibri",sans-serif">Introduction<u></u><u></u></span></h2>
<p><span style="font-family:"Calibri",sans-serif">Complete instructions are to be used in conjunction with
<a href="https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.oclc.org%2Fbibformats%2Fen%2Finput.html&data=02%7C01%7Cfrancis.lapka%40yale.edu%7Cf5df418ff5f146ffe0e908d67268e8c0%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636822192260516306&sdata=eLiCxbbwhlBXNVOFkDX%2BOv%2BBvhX4%2FZEOns%2BgmVOWwoU%3D&reserved=0" title="https://www.oclc.org/bibformats/en/input.html" target="_blank">
Bibliographic Formats and Standards (BFAS) Chapter 4: When to input a new record</a>.<u></u><u></u></span></p>
<p><span style="font-family:"Calibri",sans-serif">Regardless of cataloging rules, there should only be one bibliographic record representing the same item, per language of cataloging.<u></u><u></u></span></p>
<h2><span style="font-family:"Calibri",sans-serif">Variable fields<u></u><u></u></span></h2>
<h3><span style="font-family:"Calibri",sans-serif">010<u></u><u></u></span></h3>
<ul type="disc">
<li class="MsoNormal">
Records may be merged regardless of the absence or presence of a 010 field. Records with a difference in control numbers issued by the same agency may be potential duplicate records. Compare fields 245 through 5xx to justify a merge.<u></u><u></u></li><li class="MsoNormal">
<strong><span style="font-family:"Calibri",sans-serif">Do not merge</span></strong> two DLC records with different LCCNs if neither is ELvl "J", report these to AskQC. Otherwise, add the LCCN from the ELvl "J" record in a subfield $z to the 010 field of the
retained record.<u></u><u></u></li></ul>
<h3><span style="font-family:"Calibri",sans-serif">006 and 007<u></u><u></u></span></h3>
<ul type="disc">
<li class="MsoNormal">
Records may be considered duplicates for merge even with the absence or presence of field 006 or 007. Compare fields 300, 500, and 533 to justify a merge.<u></u><u></u></li><li class="MsoNormal">
Specific differences in the physical format of the item may justify leaving the records separate.<u></u><u></u></li></ul>
<h3><span style="font-family:"Calibri",sans-serif">020<u></u><u></u></span></h3>
<ul type="disc">
<li class="MsoNormal">
Make sure they match. But be aware that multiple ISBNs may apply to the same item. A different 020 alone does not justify separate records. The records could still be potential duplicates to be merged. Compare fields 245 through 5xx to justify a merge.<u></u><u></u></li></ul>
<h3><span style="font-family:"Calibri",sans-serif">100<u></u><u></u></span></h3>
<ul type="disc">
<li class="MsoNormal">
Records may be considered duplicates for merge even with the absence, presence, or difference in choice or form of the 1xx field. However, be careful of reversed order of names (see AACR2 21.6C1 and RDA 6.27.1.3).<br>
<br>
<strong><span style="font-family:"Calibri",sans-serif">Example:</span></strong><br>
100 1 Rosenbaum, Michael, $d 1972-<br>
24510 Working on the set of Smallville / $c by Michael Rosenbaum and Tom Welling.<br>
700 1 Welling, Tom, $d 1977-<br>
<br>
<span style="color:rgb(31,55,99)">DOES NOT MATCH</span><br>
<br>
100 1 Welling, Tom, $d 1977-<br>
24510 Working on the set of Smallville / $c by Tom Welling and Michael Rosenbaum.<br>
700 1 Rosenbaum, Michael, $d 1972-<br>
<u></u><u></u></li><li class="MsoNormal">
These records would <strong><span style="font-family:"Calibri",sans-serif">not</span></strong> be considered candidates for merging because we do not have the items in hand and therefore cannot be sure what the title page of each item looks like.<u></u><u></u></li><li class="MsoNormal">
If an author changed his or her name it is okay to merge. Retain the latest form of name.<u></u><u></u></li><li class="MsoNormal">
Always consult the authority file for the latest form of the name.<br>
<u></u><u></u></li></ul>
<h3><span style="font-family:"Calibri",sans-serif">245<u></u><u></u></span></h3>
<ul type="disc">
<li class="MsoNormal">
Subfield $a (title proper) should match exactly. Subfield $n and subfield $p are cataloger's interpretation - *use judgment.<u></u><u></u></li><li class="MsoNormal">
It is usually okay if one has subfield $b and the other does not (placement of subfield $b is arbitrary).<u></u><u></u></li><li class="MsoNormal">
Subfield $c should have same author.<u></u><u></u></li><li class="MsoNormal">
Two records can be merged if there is a typo difference in the title and it is <strong>
<span style="font-family:"Calibri",sans-serif">clearly</span></strong> a typo as opposed to an alternate spelling (i.e. color vs. colour).<u></u><u></u></li></ul>
<h3><span style="font-family:"Calibri",sans-serif">250<u></u><u></u></span></h3>
<ul type="disc">
<li class="MsoNormal">
Should match exactly.<u></u><u></u></li><li class="MsoNormal">
You may merge if one says 1<sup>st</sup> edition and other says nothing. However, do not merge if one says 2<sup>nd</sup> edition, or 3<sup>rd</sup> edition, etc. and the other has no edition statement.<u></u><u></u></li><li class="MsoNormal">
Compare 245 through 5xx for other differences to justify a merge.<u></u><u></u></li></ul>
<h3><span style="font-family:"Calibri",sans-serif">260 and 264<u></u><u></u></span></h3>
<h4><span style="font-family:"Calibri",sans-serif">Subfield $a guidelines<u></u><u></u></span></h4>
<ul type="disc">
<li class="MsoNormal">
Records may be considered duplicates for merge even with the absence or presence of the subfield $a.<u></u><u></u></li><li class="MsoNormal">
Always match 1<sup>st</sup> place of publication within the same country.<u></u><u></u></li></ul>
<p class="gmail-m_-7801179504737698637mt-indent-1"><strong><span style="font-family:"Calibri",sans-serif">Examples:</span></strong><span style="font-family:"Calibri",sans-serif"><u></u><u></u></span></p>
<p class="gmail-m_-7801179504737698637mt-indent-1"><span style="font-family:"Calibri",sans-serif">New York ; $a Hamburg, Germany : $b Tokyopop
<span style="color:rgb(31,55,99)">MATCHES</span> Los Angeles, Calif. ; $a Hamburg, Germany : $b Tokyopop [First places of publication are within the same country]<br>
<br>
but<br>
<br>
Hamburg, Germany ; $a New York : $b Tokyopop <span style="color:rgb(31,55,99)">DOES NOT MATCH</span> Los Angeles, Calif. ; $a Hamburg, Germany : $b Tokyopop [First places of publication are in different countries]<u></u><u></u></span></p>
<h4><span style="font-family:"Calibri",sans-serif">Subfield $b guidelines<u></u><u></u></span></h4>
<ul type="disc">
<li class="MsoNormal">
Publisher should be the same.<u></u><u></u></li><li class="MsoNormal">
Do not merge if the publisher's name changed.<u></u><u></u></li></ul>
<h4><span style="font-family:"Calibri",sans-serif">Subfield $c guidelines<u></u><u></u></span></h4>
<ul type="disc">
<li class="MsoNormal">
1970, c1961 <span style="color:rgb(31,55,99)">DOES NOT MATCH</span> c1961<u></u><u></u></li><li class="MsoNormal">
[1854] <span style="color:rgb(31,55,99)">DOES NOT MATCH</span> [1860] – different decades<u></u><u></u></li><li class="MsoNormal">
[197-?] <span style="color:rgb(31,55,99)">DOES NOT MATCH</span> [19--?] – *use judgment<u></u><u></u></li><li class="MsoNormal">
[2012] <span style="color:rgb(31,55,99)">DOES NOT MATCH</span> [2015] – *use judgment<u></u><u></u></li><li class="MsoNormal">
[194-] <span style="color:rgb(31,55,99)">MATCHES</span> [1940-9] – within the same decade<u></u><u></u></li><li class="MsoNormal">
[2013] <span style="color:rgb(31,55,99)">MATCHES</span> [2014] – one year difference in brackets<u></u><u></u></li><li class="MsoNormal">
c2001 <span style="color:rgb(31,55,99)">MATCHES</span> [2000 or 2001]<u></u><u></u></li><li class="MsoNormal">
[1929] <span style="color:rgb(31,55,99)">MATCHES</span> [date of publication not identified] or [n.d.]<u></u><u></u></li><li class="MsoNormal">
[196-?] <span style="color:rgb(31,55,99)">MATCHES</span> [ date of publication not identified] or [n.d.]<u></u><u></u></li><li class="MsoNormal">
Printing dates are not considered dates of publication and are ignored<u></u><u></u></li></ul>
<h3><span style="font-family:"Calibri",sans-serif">300<u></u><u></u></span></h3>
<h4><span style="font-family:"Calibri",sans-serif">Subfield $a guidelines<u></u><u></u></span></h4>
<ul type="disc">
<li class="MsoNormal">
1 v. various pages <span style="color:rgb(31,55,99)">MATCHES</span> 60 p. in various pages<u></u><u></u></li><li class="MsoNormal">
unpaged <span style="color:rgb(31,55,99)">MATCHES</span> [any number of pages in brackets]<u></u><u></u></li><li class="MsoNormal">
1 v. <span style="color:rgb(31,55,99)">MATCHES</span> [any number of pages in brackets]<u></u><u></u></li><li class="MsoNormal">
1 v. <span style="color:rgb(31,55,99)">DOES NOT MATCH</span> 27 p. – *use judgment<u></u><u></u></li><li class="MsoNormal">
1 v. (loose-leaf) <span style="color:rgb(31,55,99)">DOES NOT MATCH</span> 253 leaves – *use judgment<u></u><u></u></li><li class="MsoNormal">
3 v. <span style="color:rgb(31,55,99)">DOES NOT MATCH</span> 3 v. in 1<u></u><u></u></li><li class="MsoNormal">
473 p. <span style="color:rgb(31,55,99)">DOES NOT MATCH</span> 2 v. in 1 – *use judgment<u></u><u></u></li><li class="MsoNormal">
473 p. <span style="color:rgb(31,55,99)">MATCHES</span> 2 v. in 1 [473] because gives number of pages<u></u><u></u></li><li class="MsoNormal">
unpaged <span style="color:rgb(31,55,99)">DOES NOT MATCH</span> a number of pages<u></u><u></u></li></ul>
<h4><span style="font-family:"Calibri",sans-serif">Subfield $b guidelines<u></u><u></u></span></h4>
<ul type="disc">
<li class="MsoNormal">
Merge if one has plates and the other does not<u></u><u></u></li><li class="MsoNormal">
Do <strong><span style="font-family:"Calibri",sans-serif">not</span></strong> merge if number of plates is way off (i.e. $b 5 pages of plates vs. $b 17 pages of plates)<u></u><u></u></li><li class="MsoNormal">
Absence or presence of illustrations does not justify a new record. Records may be merged if one has illustrations and the other does not. However, do not merge if one has colored illustrations and the other has black and white illustrations.<u></u><u></u></li></ul>
<h4><span style="font-family:"Calibri",sans-serif">Subfield $c guidelines<u></u><u></u></span></h4>
<ul type="disc">
<li class="MsoNormal">
Size should not differ by more than 2 cm.<u></u><u></u></li></ul>
<h4><span style="font-family:"Calibri",sans-serif">Subfield $e guidelines<u></u><u></u></span></h4>
<ul type="disc">
<li class="MsoNormal">
Absence or presence of subfields indicating substantive accompanying material may justify a new record. Records that represent a resource issued without accompanying material and the same resource issued with substantive accompanying material are no longer
considered to be duplicates.<u></u><u></u></li><li class="MsoNormal">
The accompanying material may be cataloged separately or described in a note. Compare fields 006 through 5xx to justify a merge.<u></u><u></u></li><li class="MsoNormal">
Do <strong><span style="font-family:"Calibri",sans-serif">not</span></strong> merge those with a difference in subfield $e.<u></u><u></u></li></ul>
<h3><span style="font-family:"Calibri",sans-serif">490<u></u><u></u></span></h3>
<ul type="disc">
<li class="MsoNormal">
Guidelines regarding series retention can be found in the Record Merge Field Transfers document.<u></u><u></u></li><li class="MsoNormal">
Records may be considered duplicates for merge even with the absence or presence of the 490 field.<u></u><u></u></li><li class="MsoNormal">
Examples of situations that may justify a merge, use judgment. <u></u><u></u>
<ul type="circle">
<li class="MsoNormal">
Variation in form of series statement<u></u><u></u></li><li class="MsoNormal">
Variation in tracing decision or form (i.e., 490 vs. 490 with 830)<u></u><u></u></li><li class="MsoNormal">
Absence, presence, or difference in series statement of responsibility<u></u><u></u></li><li class="MsoNormal">
Change of series among issues or parts of a serial or multipart item. Do <strong>
<span style="font-family:"Calibri",sans-serif">not</span></strong> merge if the item is issued in a different series.<u></u><u></u></li></ul>
</li></ul>
<h3><span style="font-family:"Calibri",sans-serif">501<u></u><u></u></span></h3>
<ul type="disc">
<li class="MsoNormal">
Do <strong><span style="font-family:"Calibri",sans-serif">not</span></strong> merge if one has 501 and other does not, unless there are 7xx fields representing the works in 501.<u></u><u></u></li></ul>
<p><span class="gmail-m_-7801179504737698637mt-icon-info2"><span style="font-family:"Calibri",sans-serif"> </span></span><span style="font-family:"Calibri",sans-serif">Note: The issue of field 501 is currently under reconsideration.<u></u><u></u></span></p>
<h3><span style="font-family:"Calibri",sans-serif">533<u></u><u></u></span></h3>
<ul type="disc">
<li class="MsoNormal">
Do <strong><span style="font-family:"Calibri",sans-serif">not </span></strong>merge if one has 533 and other does not, unless the records represent electronic resources.<u></u><u></u></li><li class="MsoNormal">
Some older records have 533 information in a 500 field.<u></u><u></u></li><li class="MsoNormal">
Do <strong><span style="font-family:"Calibri",sans-serif">not </span></strong>merge if the series differ.<u></u><u></u></li><li class="MsoNormal">
Make sure type, place, and agency of reproduction matches.<u></u><u></u></li></ul>
<h3><span style="font-family:"Calibri",sans-serif">6xx<u></u><u></u></span></h3>
<ul type="disc">
<li class="MsoNormal">
Records may be considered duplicates for merge even with the absence, presence, or difference in 6xx fields.<u></u><u></u></li></ul>
<h3><span style="font-family:"Calibri",sans-serif">7xx<u></u><u></u></span></h3>
<ul type="disc">
<li class="MsoNormal">
Records may be considered duplicates for merge even with the absence, presence, or difference in 7xx fields.<u></u><u></u></li></ul>
<p><strong><span style="font-family:"Calibri",sans-serif">Use judgment: </span></strong><span style="font-family:"Calibri",sans-serif">More leeway is given if the 'delete' record is a batchloaded Vendor record. For a list of participating vendors to go: <a href="https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.oclc.org%2Fen%2Fpartnerships%2Fmaterial%2Fparticipants.html&data=02%7C01%7Cfrancis.lapka%40yale.edu%7Cf5df418ff5f146ffe0e908d67268e8c0%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C636822192260526314&sdata=aJCG94HeYNXIUZGYGGENMECWEztp8z6diw7DaMFIe28%3D&reserved=0" title="Guidelines for merging duplicate books records: A field-by-field comparison" target="_blank">http://www.oclc.org/en/partnerships/material/participants.html</a>.
See table below.<u></u><u></u></span></p>
<h2><span style="font-family:"Calibri",sans-serif">Exceptions<u></u><u></u></span></h2>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">…<u></u><u></u></p>
<p class="MsoNormal"><b><span style="font-size:13.5pt">Rare Materials (pre-1801)<u></u><u></u></span></b></p>
<p class="MsoNormal"><span style="font-size:12pt">Items that are published pre-1801 are considered rare materials items.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:12pt">These items may be cataloged using various Rare Materials cataloging rules which will be coded in the 040 $e (i.e., dcrb, dcrmb); however, records
may be considered duplicates regardless of the absence or presence of the 040 $e. Determine the record to be retained based on the following guidelines:<u></u><u></u></span></p>
<ul type="disc">
<li class="MsoNormal">
<span style="font-size:12pt">If one of the records is coded as Rare Materials in the 040 $e and the potential duplicates are not, but it is evident from all fields (including note fields) that they represent the same item – merge and retain the record coded
as Rare Materials in the 040 $e<u></u><u></u></span></li><li class="MsoNormal">
<span style="font-size:12pt">If the records are coded as the same Rare Materials cataloging rules in the 040 $e, compare all records (including note fields) to determine whether or not they are duplicates and if appropriate, merge retaining the most complete
record (based on content, <b>not</b> holdings)<u></u><u></u></span></li><li class="MsoNormal">
<span style="font-size:12pt">If the records are coded as different Rare Materials cataloging rules in the 040 $e –
<b>do not merge</b><u></u><u></u></span></li><li class="MsoNormal">
<span style="font-size:12pt">If none of the records are coded as rare materials cataloging, compare all records (including note fields) to determine whether or not they are duplicates and if appropriate, merge retaining the most complete record (based on
content, <b>not</b> holdings)<u></u><u></u></span></li></ul>
<p class="MsoNormal"><span style="font-size:12pt">In all cases, be aware of fields that will not auto-transfer during the merge process and manually transfer, as appropriate – such as unique 510 fields.<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><img style="display: inline;" src="http://www.udel.edu/ocm/signature/images/ud-logo-sml.png" alt="University of Delaware" width="130" height="55">
<p style="margin-top:0px;margin-bottom:0px;font-family:"Arial",sans-serif;color:rgb(0,83,159);font-size:15px;font-weight:bold;display:block">Jennifer MacDonald <font size="1"><span style="color:rgb(0,0,0)"><span style="font-weight:normal">MA, PhD, MSLIS</span></span></font><br></p>
<p style="margin-top:0px;margin-bottom:0px;font-family:"Times New Roman",Times,serif;font-size:13px;color:rgb(10,10,10);font-style:italic;display:block">Associate Librarian and Coordinator, Special Collections Cataloging Unit</p>
<p style="margin-top:0px;margin-bottom:0px;font-family:"Times New Roman",Times,serif;font-size:13px;color:rgb(10,10,10);display:block">Cataloging Department</p>
<p style="margin-top:0px;margin-bottom:0px;font-family:"Times New Roman",Times,serif;font-size:13px;color:rgb(10,10,10)">University of Delaware</p>
<span style="margin-top:0px;margin-bottom:0px;font-family:"Times New Roman",Times,serif;font-size:13px;color:rgb(10,10,10);display:inline-block">(302) 831-1512</span></div></div></div></div></div></div></div></div></div></div>