<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<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);">
Hi Sarit,</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);">
Miloche's reply came in as I was writing mine, and I have only a little to add to it:</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);">
This may have changed, but I <i>think</i> you can import two subject headings with the same name if they have different term types. At Denver we had instances where we needed to import the same term as a Topical heading and a Genre/Form heading, and if I remember
correctly we were able to do that even in cases where the terms were local headings only (so they wouldn't have had Getty or LCSH URIs in the Authority ID field).</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 imported Subjects and Agents before Resources and Archival Objects at Denver when we migrated from Re:Discovery. That was so that we were able to pair terms and term types with their new ArchivesSpace URIs when we imported resources and archival objects
that needed to link to them.</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);">
hopefully that helps / is still accurate information! -k<br>
</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> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of Kottman, Miloche
<mkottman@ku.edu><br>
<b>Sent:</b> Friday, October 20, 2023 3:41 PM<br>
<b>To:</b> Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Formatting Agents and Subjects</font>
<div> </div>
</div>
<style>
<!--
@font-face
{font-family:Wingdings}
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
a:link, span.x_MsoHyperlink
{color:#0563C1;
text-decoration:underline}
p.x_MsoListParagraph, li.x_MsoListParagraph, div.x_MsoListParagraph
{margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
span.x_EmailStyle21
{font-family:"Calibri",sans-serif;
color:#4472C4}
.x_MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
div.x_WordSection1
{}
ol
{margin-bottom:0in}
ul
{margin-bottom:0in}
-->
</style>
<div lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="x_WordSection1">
<p class="x_MsoNormal"><span style="color:#4472C4">Sarit,</span></p>
<p class="x_MsoNormal"><span style="color:#4472C4"> </span></p>
<p class="x_MsoNormal"><span style="color:#4472C4">Here are my answers to some of your questions:</span></p>
<p class="x_MsoNormal"><span style="color:#4472C4"> </span></p>
<ol start="1" type="1" style="margin-top:0in">
<li class="x_MsoNormal" style="color:#4472C4">To my knowledge, there is no bulk updater for subjects and/or agents. I do not use the API, as I have not had the time to dive in like I have been wanting to. Am I missing a way to do this via the SUI?</li></ol>
<p class="x_MsoNormal"><span style="color:#4472C4"> </span></p>
<p class="x_MsoNormal" style="margin-left:.5in"><span style="color:#4472C4">You can bulk
<i>load</i> but you can’t bulk <i>update</i> without the API.</span></p>
<p class="x_MsoNormal"><span style="color:#4472C4"> </span></p>
<ol start="2" type="1" style="margin-top:0in">
<li class="x_MsoNormal" style="color:#4472C4">Our agents have not displayed dates. I just edited one agent name and found there had been dates entered. When I saved the record, the dates suddenly appeared, however, the dates appear in parenthesis, not with
a comma as found in LOC. I.e., Smith, John, 1967-2014, instead I get Smith, John (1967-2014). What am I missing? Can this be changed?</li></ol>
<p class="x_MsoNormal"><span style="color:#4472C4"> </span></p>
<p class="x_MsoNormal" style="margin-left:.5in"><span style="color:#4472C4">The display of the date with the name will depend on
<i>which</i> date field has the date. There is a Dates field in the Name Forms section and there’s a Dates of Existence section a littler further down.</span></p>
<ul type="disc" style="margin-top:0in">
<li class="x_MsoListParagraph" style="color:#4472C4">If there is a date in the Dates field in the Name Forms section, it will display as part of the name in whatever format you’ve entered it in</li><li class="x_MsoListParagraph" style="color:#4472C4">If there is not a date in the Dates field in the Name Forms section but there is a date in the Dates of Existence section, the Dates of Existence date will display in parentheses after the name.</li><li class="x_MsoListParagraph" style="color:#4472C4">If you want to keep the Dates of Existence in the record but you don’t want it to display, remove the checkmark next to “automatically generate” under the Sort Name field in the Name Forms section and manually
edit the Sort Name to the display you’d like to see.</li></ul>
<p class="x_MsoNormal"><span style="color:#4472C4"> </span></p>
<ol start="3" type="1" style="margin-top:0in">
<li class="x_MsoNormal" style="color:#4472C4">If I recall correctly, if I do a bulk importer including all the subjects and agents, the system will not identify duplicates and will instead create a new record unless I have the ID and use that instead of text.
Do I have that correct?</li></ol>
<p class="x_MsoNormal"><span style="color:#4472C4"> </span></p>
<p class="x_MsoNormal" style="margin-left:.5in"><span style="color:#4472C4">The Agent records were made less restrictive when the “light mode” features were added so, yes, the way to avoid duplicates is to have a Record ID</span></p>
<p class="x_MsoNormal"><span style="color:#4472C4"> </span></p>
<ol start="4" type="1" style="margin-top:0in">
<li class="x_MsoNormal" style="color:#4472C4">I’ve not delved too deep into Subjects and Agents in ASpace other than very basic stuff so I am unsure how to handle subjects that start with an agent name and has subject qualifiers, would that be a subject, or
an agent? i.e. Smith, John, 1967-2014 -- pictorial works</li></ol>
<p class="x_MsoNormal" style="margin-left:.5in"><span style="color:#4472C4"> </span></p>
<p class="x_MsoNormal" style="margin-left:.5in"><span style="color:#4472C4">This is an Agent with the Role of Subject. You would link to the existing agent record and then Add Term/Subdivision by just typing it in.</span></p>
<p class="x_MsoNormal" style="margin-left:.5in"><span style=""><img width="337" height="231" id="x_Picture_x0020_3" style="width:3.5104in; height:2.4062in" data-outlook-trace="F:1|T:1" src="cid:image003.png@01DA0363.388E33A0"></span><span style="color:#4472C4"></span></p>
<p class="x_MsoNormal"><span style="color:#4472C4"> </span></p>
<p class="x_MsoNormal"><span style="color:#4472C4"> </span></p>
<p class="x_MsoNormal"><span style="color:#4472C4">I have no opinion on how to import a large file of records.</span></p>
<p class="x_MsoNormal"><span style="color:#4472C4"> </span></p>
<p class="x_MsoNormal"><span style="color:#4472C4">--Miloche</span></p>
<p class="x_MsoNormal"><span style="color:#4472C4"> </span></p>
<p class="x_MsoNormal"><span style="font-family:Symbol; color:#4472C4">»»»»»»»»»»»»»»»»»»»»»»»»»»»»»»</span><span style="font-size:10.0pt; color:#4472C4"></span></p>
<p class="x_MsoNormal"><span style="font-size:10.0pt; color:#4472C4">Miloche Kottman</span></p>
<p class="x_MsoNormal"><span style="font-size:10.0pt; color:#4472C4">Head of Cataloging & Archival Processing</span></p>
<p class="x_MsoNormal"><span style="font-size:10.0pt; color:#4472C4">University of Kansas Libraries</span></p>
<p class="x_MsoNormal"><span style="font-size:10.0pt; color:#4472C4">Lawrence, KS 66045</span></p>
<p class="x_MsoNormal"><span style="font-size:10.0pt; color:#4472C4"><a href="mailto:mkottman@ku.edu"><span style="color:blue">mkottman@ku.edu</span></a></span></p>
<p class="x_MsoNormal"><span style="font-size:10.0pt; color:#4472C4">785-864-3916</span></p>
<p class="x_MsoNormal"><span style="color:#4472C4"> </span></p>
<p class="x_MsoNormal"><span style="color:#4472C4"> </span></p>
<p class="x_MsoNormal"><span style="color:#4472C4"> </span></p>
<div>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="x_MsoNormal"><b><span style="">From:</span></b><span style=""> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org>
<b>On Behalf Of </b>Hand, Sarit<br>
<b>Sent:</b> Friday, October 20, 2023 12:16 PM<br>
<b>To:</b> archivesspace_users_group@lyralists.lyrasis.org<br>
<b>Subject:</b> [Archivesspace_Users_Group] Formatting Agents and Subjects</span></p>
</div>
</div>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">Hello,</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">I’ll apologize in advance for the chaos I am unleashing here. I am working on a project migrating an old access database collection listing to ASpace. There is a lot of subject and agent cleanup, most of which I have done. I am now trying
to identify what is already in ASpace so I can use the URIs in the bulk importer. However, I am finding that our subjects and agents in ASpace were not uniformly created, so, a) finding matches is difficult, b) I’d like to clean up the records in ASpace and
after all that, c) I need to get the collection uploaded, subjects, agents and all.</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">I have questions I need help on, either, how to… or confirming what I think I know:</p>
<ol start="1" type="1" style="margin-top:0in">
<li class="x_MsoListParagraph" style="margin-left:0in">To my knowledge, there is no bulk updater for subjects and/or agents. I do not use the API, as I have not had the time to dive in like I have been wanting to. Am I missing a way to do this via the SUI?</li><li class="x_MsoListParagraph" style="margin-left:0in">Our agents have not displayed dates. I just edited one agent name and found there had been dates entered. When I saved the record, the dates suddenly appeared, however, the dates appear in parenthesis,
not with a comma as found in LOC. I.e., Smith, John, 1967-2014, instead I get Smith, John (1967-2014). What am I missing? Can this be changed?</li><li class="x_MsoListParagraph" style="margin-left:0in">If I recall correctly, if I do a bulk importer including all the subjects and agents, the system will not identify duplicates and will instead create a new record unless I have the ID and use that instead
of text. Do I have that correct?</li><li class="x_MsoListParagraph" style="margin-left:0in">I’ve not delved too deep into Subjects and Agents in ASpace other than very basic stuff so I am unsure how to handle subjects that start with an agent name and has subject qualifiers, would that be a subject,
or an agent? i.e. Smith, John, 1967-2014 -- pictorial works</li></ol>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">Last but not least (and I could probably ask a million more questions)</p>
<p class="x_MsoNormal">With over a thousand new terms to be attached to almost a thousand archival object records, would I be better off first bulk importing the subjects and agents and then bulk importing the collection and link terms later? How would you
handle this part?</p>
<p class="x_MsoNormal"> </p>
<p class="x_MsoNormal">Thank you for taking the time to read this, advise and/or answer my questions.</p>
<p class="x_MsoNormal"> </p>
<div>
<p class="x_MsoNormal"><span style="font-size:10.0pt">Cheers,</span><span style=""></span></p>
</div>
<div>
<p class="x_MsoNormal"><span style="font-size:9.0pt; font-family:"Arial",sans-serif; color:red"><img border="0" width="61" height="70" id="x_Picture_x0020_1" style="width:.6354in; height:.7291in" data-outlook-trace="F:1|T:1" src="cid:image001.png@01DA0360.E511BE60"></span><span style="">
</span><span style="font-size:9.0pt; font-family:"Arial",sans-serif; color:red"><img border="0" width="87" height="46" id="x_Picture_x0020_2" style="width:.9062in; height:.4791in" data-outlook-trace="F:1|T:1" src="cid:image002.jpg@01DA0360.E511BE60"></span><span style=""></span></p>
</div>
<div>
<p class="x_MsoNormal"><span style="font-size:10.0pt">Sarit Hand <span style="color:#323130">200 Liberty St.</span></span><span style="color:#323130"></span></p>
<div>
<p class="x_MsoNormal"><span style="font-size:10.0pt; color:#323130">Digital Archivist New York, NY 10281</span><span style=""></span></p>
</div>
<div>
<p class="x_MsoNormal"><span style="font-size:10.0pt">Corporate Archives <span style="color:#323130">T 212.621.7035</span></span><span style=""></span></p>
</div>
<div>
<p class="x_MsoNormal"><span style="font-size:10.0pt"> </span><span style=""></span></p>
</div>
<div>
<p class="x_MsoNormal"><span style="font-size:10.0pt"><br>
<a href="mailto:shand@ap.org">shand@ap.org</a> </span><span style=""></span></p>
</div>
<div>
<p class="x_MsoNormal"><span style=""><a href="http://www.ap.org/" originalsrc="http://www.ap.org/" shash="zVrdQFRaJDvEXNnpcycRlV4HwyvZUYTOIyOvG3RxdeRzwFFq1LjeFit6dfBnxIjAQHqaTi27Jiy60DTnbN9fn3GY9cW3nD6P6730hzw79G+Ro6ehqDN+VI0tvFwdmuZtVqKHCrHeLykvUPSL6oqLqrmndfHwAR7rzQim9WqohSU="><span style="font-size:10.0pt; color:blue">www.ap.org</span></a></span></p>
</div>
</div>
<p class="x_MsoNormal"><span style="">The information contained in this communication is intended for the use of the designated recipients named above. If the reader of this communication is not the intended recipient, you are hereby notified that you have
received this communication in error, and that any review, dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify The Associated Press immediately by telephone at
+1-212-621-1500 and delete this email. Thank you. </span></p>
</div>
</div>
</body>
</html>