<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hello,</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
We've recently begun asking those very same questions, and I am interested in hearing what others have to say. </div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
For replacing problematic headings, I think we will need to keep a list of the problematic authority records to prevent them from re-entering our system during authority record loads. We will probably track both the (LCSH) IDs as well as the heading, so that
we can be alerted if the problematic record has changed (for instance, to something less problematic, so we could go back to using it). Since we aren't (yet?) using an authority vendor, this'll likely be done in custom python scripts... but all this is still
hypothetical!</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I'm eager to hear if/how we can improve the Author and Subject searches by indexing non-preferred headings. </div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Evergreen-general <evergreen-general-bounces@list.evergreen-ils.org> on behalf of Szwagiel, Will via Evergreen-general <evergreen-general@list.evergreen-ils.org><br>
<b>Sent:</b> Tuesday, February 6, 2024 10:05 AM<br>
<b>To:</b> evergreen-general@list.evergreen-ils.org <evergreen-general@list.evergreen-ils.org><br>
<b>Cc:</b> Szwagiel, Will <william.szwagiel@dncr.nc.gov><br>
<b>Subject:</b> [Evergreen-general] Indexing =400 Authority MARC Fields in Author and Subject Searches</font>
<div> </div>
</div>
<style type="text/css" style="display:none">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr"><br>
<div style="background-color:#ffe599; padding:10px; margin-left:0px; margin-right:0px">
<span style="font-size:9pt; font-family:Arial,sans-serif; color:#17202A"><b>CAUTION:</b></span>
<span style="font-size:9pt; line-height:10pt; font-family:Arial,sans-serif; color:#17202A">
This email originated from outside of UPEI. Do not click links or open attachments unless you recognize the sender and know the content is safe. If you are uncertain, please forward to phishing@upei.ca and delete this email.
<p></p>
</span></div>
<br>
<div>
<div class="x_elementToProof" style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
Good morning,</div>
<div class="x_elementToProof" style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
<br>
</div>
<div class="x_elementToProof" style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
We have been discussing ways to try and make authority records more useful in Evergreen for staff and patrons when searching the catalog. As it currently stands, if you select Author as the Catalog Field in a search and search for a version of an author's
name that appears in a =400 field in the authority record, you will not receive any results. However, if you search for that same version of the author's name with Keyword selected as the Catalog Field, you will receive results.</div>
<div class="x_elementToProof" style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
<br>
</div>
<div class="x_elementToProof" style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
One potential solution that has been suggested is to index the =400 fields in the Author search.</div>
<div class="x_elementToProof" style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
<br>
</div>
<div class="x_elementToProof" style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
This led to a broader discussion regarding a project we are currently undertaking to introduce less problematic or offensive local subject headings into our MARC records. Basically we are planning to put together a list of terms that we feel are outdated or
problematic and then come up with a separate list of terms with which to replace them. Instead of simply adding our local subject headings to the records and leaving the problematic ones present as is, we intend to replace the problematic ones with the new
terms.</div>
<div class="x_elementToProof" style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
<br>
</div>
<div class="x_elementToProof" style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
This returned to the discussion of how best to handle authority records. The thinking is that we would add these new terms to the existing authority records (presumably in =400 fields) and potentially index these fields in the Subject search, as well, similar
to how we discussed potentially doing this with the Author search.</div>
<div class="x_elementToProof" style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
<br>
</div>
<div class="x_elementToProof" style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
Has anyone else done anything like this before? If so, how has it worked out for you? If you have not had much luck with it, what would you recommend as an alternative?</div>
<div class="x_elementToProof" style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
<br>
</div>
<div class="x_elementToProof" style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
Thank you in advance for any insight you may be able to provide.</div>
<div class="x_elementToProof" style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)">
<br>
</div>
<div id="x_Signature">
<p><span style="font-family:Arial,sans-serif; font-size:12pt; color:black"><b>William C. Szwagiel</b></span></p>
<p><span style="font-family:Arial,sans-serif; font-size:10pt; color:black">NC Cardinal Project Manager</span></p>
<p><span style="font-family:Arial,sans-serif; font-size:10pt; color:black">State Library of North Carolina</span></p>
<p><span style="font-family:Arial,sans-serif; font-size:10pt; color:black"><a href="mailto:william.szwagiel@ncdcr.gov" id="OWA6e901766-71ef-fb51-a304-3ab573ee76a5" class="x_OWAAutoLink" style="margin-top:0px; margin-bottom:0px">william.szwagiel@ncdcr.gov</a> |
919.814.6721</span></p>
<p><span style="font-family:Arial,sans-serif; font-size:10pt; color:black"><a href="https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal" id="OWA871087a8-3042-72fa-2fac-d128059d6263" class="x_OWAAutoLink" style="margin-top:0px; margin-bottom:0px">https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal</a></span></p>
<p><span style="font-family:Arial,sans-serif; font-size:10pt; color:black">109 East Jones Street | 4640 Mail Service Center </span></p>
<p><span style="font-family:Arial,sans-serif; font-size:10pt; color:black">Raleigh, North Carolina 27699-4600</span></p>
<p style="margin-top:6pt"><span style="font-family:Arial,sans-serif; font-size:10pt; color:rgb(0,0,0)">The State Library is part of the NC Department of Natural & Cultural Resources.</span></p>
<p><span style="font-family:Arial,sans-serif; font-size:10pt; color:black"><i>Email correspondence to and from this address is subject to the North Carolina Public Records Law and may be disclosed to third parties.</i></span></p>
<p><span style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:11pt; color:rgb(0,0,0)"> </span></p>
</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1"><br>
Email correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties by an authorized state official.<br>
</font></div>
</div>
</body>
</html>