<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;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Aptos;}
@font-face
{font-family:YaleNew;}
@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;
font-size:11.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#467886;
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;
font-size:11.0pt;
font-family:"Aptos",sans-serif;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@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:384454709;
mso-list-template-ids:-1672078688;}
@list l1
{mso-list-id:948314160;
mso-list-template-ids:422323020;}
@list l1:level1
{mso-level-start-at:2;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2
{mso-list-id:1775511666;
mso-list-type:hybrid;
mso-list-template-ids:-409537504 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l2:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l2:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l2:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l2:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
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="#467886" vlink="#96607D" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt">I'm late to the game on this…. A system upgrade bumped DCRM-L off my 'favorites' list and I hadn't realized I was missing the conversation!<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">I think 655 in the Holdings format makes excellent logical sense, assuming it can be indexed properly.<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">Our TIND ILS provides the equivalent already, thanks to having holdings data "embedded" in the bib record. We can use $8 to link particular headings to a particular copy (not just 655s but also copy-specific
5XX and 7XX fields). <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">Scroll down to the bottom of <a href="https://catalog.folger.edu/record/162814">
https://catalog.folger.edu/record/162814</a> for an example: copy 1 has copy-specific 655s, copy 2 has a 700 for former owner.<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">Erin<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">---------------------<br>
</span>Erin Blake, PhD | Senior Cataloger | she/her | Folger Shakespeare Library | eblake@folger.edu<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>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:"Calibri",sans-serif">From:</span></b><span style="font-family:"Calibri",sans-serif"> DCRM-L <dcrm-l-bounces@lib.byu.edu>
<b>On Behalf Of </b>Lapka, Francis via DCRM-L<br>
<b>Sent:</b> Friday, May 17, 2024 10:27 AM<br>
<b>To:</b> DCRM Users' Group <dcrm-l@lib.byu.edu><br>
<b>Cc:</b> Lapka, Francis <francis.lapka@yale.edu><br>
<b>Subject:</b> Re: [DCRM-L] A Holdings 655<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif">Bob, you rightly highlight questions related to how systems would handle a Holdings 655. I wonder if the problem is chicken-and-eggy: perhaps our systems are weak in this domain
because our expectations have always been too low. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif">The Yale context includes a migration to Alma in 2025 and a concurrent review of practices for copy-specific data. For indexing and display, we plan on maintaining a Blacklight-based
catalog, which gives us more control for customized outcomes. For cataloging, you’d want a Holdings-based genre/form field to be controllable, like access points in a Bib record. A little bit of tinkering in our Alma sandbox suggests we could do this by making
use of Alma’s </span><a href="https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/Metadata_Management/210Metadata_Management_Configuration/Configuring_Cataloging#Configuring_Controlled_Vocabulary_Registry"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif">Controlled
Vocabulary Registry</span></a><span style="font-size:12.0pt;font-family:"Calibri",sans-serif">. So the elements seem there to make a Holdings 655 feasible and useful, here at least. But I’d hesitate to propose a new MARC field in the absence of wider interest.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif">I share your interest in former owner access points in Holdings. Here I think the recently introduced
</span><a href="https://www.loc.gov/marc/holdings/hd361.html"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif">361 field</span></a><span style="font-size:12.0pt;font-family:"Calibri",sans-serif"> could suffice, even if the structures don’t exactly
parallel the 7xx fields. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif">Francis<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif"><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><span style="font-family:"Calibri",sans-serif">From:</span></b><span style="font-family:"Calibri",sans-serif"> DCRM-L <</span><a href="mailto:dcrm-l-bounces@lib.byu.edu"><span style="font-family:"Calibri",sans-serif">dcrm-l-bounces@lib.byu.edu</span></a><span style="font-family:"Calibri",sans-serif">>
<b>On Behalf Of </b>Robert Maxwell via DCRM-L<br>
<b>Sent:</b> Thursday, May 16, 2024 5:27 PM<br>
<b>To:</b> DCRM Users' Group <</span><a href="mailto:dcrm-l@lib.byu.edu"><span style="font-family:"Calibri",sans-serif">dcrm-l@lib.byu.edu</span></a><span style="font-family:"Calibri",sans-serif">><br>
<b>Cc:</b> Robert Maxwell <</span><a href="mailto:robert_maxwell@byu.edu"><span style="font-family:"Calibri",sans-serif">robert_maxwell@byu.edu</span></a><span style="font-family:"Calibri",sans-serif">><br>
<b>Subject:</b> Re: [DCRM-L] A Holdings 655<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I think that sounds like a good idea but I don’t think our system (or any other?) would index it, which is important. But maybe that could be overcome. Actually it would also be nice if holdings records could contain “local” added access
points, e.g. for former owners. With the same caveat, needs to index.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Bob<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">Robert L. Maxwell<br>
Ancient Languages and Special Collections Cataloger<br>
6728 Harold B. Lee Library<br>
Brigham Young University<br>
Provo, UT 84602<br>
(801)422-5568 <br>
<br>
"We should set an example for all the world, rather than confine ourselves to the course which has been heretofore pursued"--Eliza R. Snow, 1842.</span><o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-family:"Calibri",sans-serif">From:</span></b><span style="font-family:"Calibri",sans-serif"> DCRM-L <</span><a href="mailto:dcrm-l-bounces@lib.byu.edu"><span style="font-family:"Calibri",sans-serif">dcrm-l-bounces@lib.byu.edu</span></a><span style="font-family:"Calibri",sans-serif">>
<b>On Behalf Of </b>Lapka, Francis via DCRM-L<br>
<b>Sent:</b> Thursday, May 16, 2024 1:24 PM<br>
<b>To:</b> DCRM Users' Group <</span><a href="mailto:dcrm-l@lib.byu.edu"><span style="font-family:"Calibri",sans-serif">dcrm-l@lib.byu.edu</span></a><span style="font-family:"Calibri",sans-serif">><br>
<b>Cc:</b> Lapka, Francis <</span><a href="mailto:francis.lapka@yale.edu"><span style="font-family:"Calibri",sans-serif">francis.lapka@yale.edu</span></a><span style="font-family:"Calibri",sans-serif">><br>
<b>Subject:</b> [DCRM-L] A Holdings 655<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif">Two questions:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo3"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif">If the MARC Holdings format included a field 655 for copy-specific genre/form terms, such as those in the
</span><a href="https://id.loc.gov/vocabulary/rbmscv/cv00017.html"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif">Provenance facet of the RBMS CV</span></a><span style="font-size:12.0pt;font-family:"Calibri",sans-serif">, would your library
think about using it?<o:p></o:p></span></li></ol>
<p class="MsoListParagraph"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<ol style="margin-top:0in" start="2" type="1">
<li class="MsoListParagraph" style="margin-left:0in;mso-list:l2 level1 lfo3"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif">Would the MARC community scoff at a proposal for such a field?<o:p></o:p></span></li></ol>
<p class="MsoListParagraph"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif">Francis<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:YaleNew">Francis Lapka<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:YaleNew">Senior Catalog Librarian<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:YaleNew">Department of Rare Books and Manuscripts<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:YaleNew">Yale Center for British Art<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:YaleNew">203-432-9672 · </span><a href="http://britishart.yale.edu/"><span style="font-family:YaleNew;color:#0563C1">britishart.yale.edu</span></a><span style="font-family:YaleNew"><o:p></o:p></span></p>
<p class="MsoNormal"> <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>