<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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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:Georgia;
panose-1:2 4 5 2 5 4 5 2 3 3;}
@font-face
{font-family:"Segoe UI Symbol";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
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;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
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.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1216505475;
mso-list-template-ids:29383778;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:1337003447;
mso-list-type:hybrid;
mso-list-template-ids:-1244868362 135462913 135462915 135462917 135462913 135462915 135462917 135462913 135462915 135462917;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l2
{mso-list-id:1343050317;
mso-list-template-ids:761666254;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3
{mso-list-id:1776439604;
mso-list-type:hybrid;
mso-list-template-ids:-680261924 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l3:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l3:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l3:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l3:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l3:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l3:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l3:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l3:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l3:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l4
{mso-list-id:2013486554;
mso-list-type:hybrid;
mso-list-template-ids:-1594301800 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l4:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l4:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l4:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l4:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l4:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l4:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
@list l4:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Symbol;}
@list l4:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l4:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:Wingdings;}
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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Ron,<br>
<br>
My pleasure! I’m glad the example helped get you going for your test instance. Thanks for the follow-up Cory. It’s a shame that functionality was rejected, but understandable.
<br>
<br>
As you pointed out Ron, it’s still a brittle process, not helped by the fact that it’s sometimes difficult to ask colleagues/volunteers to familiarize themselves with XML syntax and EAD tags and attributes. If after considering improvements for internal cross-links
you want to post a ticket and need/want help, just let me know! I’m happy to make suggestions and give a +1.<br>
<br>
Sure, after migrating to ArchivesSpace, we compiled a bunch of tests we did for checking our data. I wrote a
<a href="https://github.com/uga-libraries/aspace_scripts/blob/master/ASpace_Data_Audit.py">
python script</a> to do the tests, create a spreadsheet with the results, email those results to our users, and I worked with our sysadmin to make a cron job to run the script once a year. It checks:<br>
<br>
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l4 level1 lfo7"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">controlled vocabularies for non-permitted terms<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l4 level1 lfo7"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">resources/items with Component Unique IDs (we don’t use them)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l4 level1 lfo7"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">containers with no barcodes or indicators<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l4 level1 lfo7"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">archival objects with multiple containers or digital objects<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l4 level1 lfo7"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">archival objects falsely labeled as “collection” level<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l4 level1 lfo7"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">EAD-IDs (we make these in our EAD.xml exporter)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l4 level1 lfo7"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">duplicate subjects and agents<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l4 level1 lfo7"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">archival objects on the same level but have different labels (i.e. a file and series on the same level together)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l4 level1 lfo7"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">XML errors<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l4 level1 lfo7"><![if !supportLists]><span style="font-family:Symbol;color:#1F497D"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="color:#1F497D">URL errors<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><br>
With a little programming knowledge, you could modify this script or make one yourself. There’s also a number YouTube videos on data cleanup in ArchivesSpace:
<a href="https://www.youtube.com/watch?v=SnZErWH0XmU">ArchivesSpace Data Cleanup Webinar: Tips, Tricks, and Tools</a>,
<a href="https://www.youtube.com/watch?v=PTuROXsEjqo">How to Make Technology Work for You In an ArchivesSpace Data Cleanup Project</a>,
<a href="https://www.youtube.com/watch?v=LupV331hg8E">Someday is Here! ArchivesSpace Projects for Working from Home</a>.<br>
<br>
Corey<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><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>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org>
<b>On Behalf Of </b>Cory Nimer<br>
<b>Sent:</b> Wednesday, May 25, 2022 11:15 AM<br>
<b>To:</b> Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] linking to related Resources / Archival Objects in ArchivesSpace<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#BA0C2F">[EXTERNAL SENDER - PROCEED CAUTIOUSLY]</span><span style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<div>
<p class="MsoNormal">Ron,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I would agree that it would be preferable to have a more EAD3-friendly configuration for related materials notes, at least in order to reduce/remove the need for mixed content within these notes. I don't know if there is widespread interest
in moving implementing something more like the Agents module's Sources subrecord or the Metadata Rights Declarations with their fields for recording a descriptive note and a URL separately. It looks like the project has already rejected the idea of being allowing
linking between different records within the database, though (ANW-763; <a href="https://archivesspace.atlassian.net/browse/ANW-763">
https://archivesspace.atlassian.net/browse/ANW-763</a>). <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Cory Nimer<o:p></o:p></p>
<p class="MsoNormal">University Archivist<o:p></o:p></p>
<p class="MsoNormal">Brigham Young University <o:p></o:p></p>
<p class="MsoNormal"><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>From:</b> <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">
archivesspace_users_group-bounces@lyralists.lyrasis.org</a> <<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>>
<b>On Behalf Of </b>Ron Van den Branden<br>
<b>Sent:</b> Wednesday, May 25, 2022 10:05 AM<br>
<b>To:</b> Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a>><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] linking to related Resources / Archival Objects in ArchivesSpace<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="NL-BE">Hi Corey,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="NL-BE"><o:p> </o:p></span></p>
<p class="MsoNormal">Many thanks for your helpful reply! In our current data, these structured links are indeed connected to a field that maps to <relatedmaterial> in ArchivesSpace, so that’s indeed the destination we had in mind.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Your example for embedding ArchivesSpace-internal links via the ArchivesSpace ID for a @href attribute was really helpful and finally made me get it working in the test instance, great! That’s a useful mechanism, though I fully agree the
manual input process is brittle, even with the (limited) “mixed content” completion help. In order to make the most semantic sense, as you exemplified with the <archref> example, our colleagues and volunteers describing the archives would have to be knowledgeable
of XML syntax rules, and the suitable EAD structures for the information they’d want to enter. Yet, even if a new structured resource-to-resource link field would be too far off the implementation horizon, perhaps a general improvement for adding such internal
cross-links in text fields in a more guided way could be of interest. I’ll think about it!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Finally, your data audit remark sounds intriguing and -considering the amount of data cleanup this data migration project has confronted us with- a vital part of best practice. Would you mind elaborating on that, or pointing me to any available
documentation?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Ron<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span lang="NL">Van:</span></b><span lang="NL"> <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">
archivesspace_users_group-bounces@lyralists.lyrasis.org</a> <<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>>
<b>Namens </b>Corey Schmidt<br>
<b>Verzonden:</b> woensdag 25 mei 2022 14:57<br>
<b>Aan:</b> Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a>><br>
<b>Onderwerp:</b> Re: [Archivesspace_Users_Group] linking to related Resources / Archival Objects in ArchivesSpace<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="NL-BE"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span style="color:#1F497D">Hey Ron,<br>
<br>
Glad to see you reaching out! I’m not sure if others have emailed you regarding this, so I’ll put in my 2 cents worth.<o:p></o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:#1F497D;mso-list:l3 level1 lfo3">From what I understand, there is no mechanism within ArchivesSpace that provides a structured “Agents/Related Accessions” type link from one resource to another, nor one archival object to
another.<o:p></o:p></li><li class="MsoNormal" style="color:#1F497D;mso-list:l3 level1 lfo3">Have you considered using the “Related Materials” note (<a href="https://www.loc.gov/ead/tglib/elements/relatedmaterial.html"><relatedmaterial></a>)? The advantage with this is the note is
made specifically for related materials either within the repository or without and you don’t need a full URL, just the ArchivesSpace ID if you’re using the PUI, like so: <archref><unittitle href="/repositories/2/resources/100">Related Collection title</unittitle>.
The problem with this is you have to enter the info by hand, which is error prone (we’ve scheduled a yearly “data audit” to help us catch errors like these).<o:p></o:p></li><li class="MsoNormal" style="color:#1F497D;mso-list:l3 level1 lfo3">I don’t know of any institution that has developed a
<a href="https://github.com/archivesspace/awesome-archivesspace">plugin</a>, nor is this on the roadmap I think. Nevertheless, you can submit a
<a href="https://archivesspace.atlassian.net/jira/software/c/projects/ANW/issues/ANW-1334">
JIRA ticket</a> for this feature (<a href="https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/19202060/How+to+Request+a+New+Feature">how to do that linked here</a>) – explaining how you want it to work with as much detail as possible. The Development
Priority Team will then determine if the ArchivesSpace development team or community can/should prioritize it in future releases. The more attention a ticket gets (comments, clarifications, etc.) the more likely it is to be implemented (<a href="https://www.youtube.com/watch?v=jlquifRXwmA">great
YouTube video here about the process</a>).<o:p></o:p></li></ul>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I hope this is helpful, but if you’d like to talk more about it, feel free to email me:
<a href="mailto:Corey.Schmidt@uga.edu">Corey.Schmidt@uga.edu</a>. To everyone on the listserv, please feel free to correct any of this info if it’s incorrect/misleading.<br>
<br>
Sincerely,<br>
<br>
Corey<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><b><span style="font-size:9.0pt;font-family:"Georgia",serif;color:#1F497D">Corey Schmidt</span></b><span style="font-size:9.0pt;font-family:"Georgia",serif;color:#1F497D">
<br>
Special Collections Libraries | <i>Project Management Librarian/Archivist</i> <o:p>
</o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><span style="font-size:9.0pt;font-family:"Georgia",serif;color:#1F497D">300 S Hull St | Athens, GA 30605
<br>
<a href="mailto:Corey.Schmidt@uga.edu"><span style="color:blue">Corey.Schmidt@uga.edu</span></a></span><span style="color:#1F497D"><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>From:</b> <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">
archivesspace_users_group-bounces@lyralists.lyrasis.org</a> <<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>>
<b>On Behalf Of </b>Ron Van den Branden<br>
<b>Sent:</b> Wednesday, May 18, 2022 3:45 PM<br>
<b>To:</b> <a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a><br>
<b>Subject:</b> [Archivesspace_Users_Group] linking to related Resources / Archival Objects in ArchivesSpace<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span lang="NL-BE" style="font-size:12.0pt;font-family:"Times New Roman",serif;color:#BA0C2F">[EXTERNAL SENDER - PROCEED CAUTIOUSLY]</span><span lang="NL-BE" style="font-size:12.0pt;font-family:"Times New Roman",serif"><o:p></o:p></span></p>
<div>
<p class="MsoNormal"><span lang="NL-BE">Hi all,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="NL-BE"><o:p> </o:p></span></p>
<p class="MsoNormal">This is my first message to this group; apologies if this has been addressed before (tried my best researching the list archive at
<a href="https://www.mail-archive.com/archivesspace_users_group@lyralists.lyrasis.org/">
https://www.mail-archive.com/archivesspace_users_group@lyralists.lyrasis.org/</a>). At my institution, we’re preparing a migration of data from a previous archival description system to ArchivesSpace. The previous system allowed for structured links between
archival descriptions within the system. For example, resource A could point to resource B within the same system by means of a system identifier, which the system would resolve to a full link in the PUI. This is functioning in a similar way as Agents Links
or Related Accessions sections in ArchivesSpace; only with a different record type (resources / archival objects instead of agents, resp. accessions).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Please correct me if I’m wrong, but I don’t see an immediate equivalent mechanism in ArchivesSpace. This raises some questions:<o:p></o:p></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="mso-list:l1 level1 lfo6">Am I overlooking the obvious, and
<i>does </i>ArchivesSpace provide a structured mechanism to point from a Resource / Archival Object to another Resource / Archival Object?<o:p></o:p></li><li class="MsoNormal" style="mso-list:l1 level1 lfo6">If not, I do see the External Documents section as a close fit, with the semantic drawback that these linked resources are not really external but rather internal. More substantially, though, External Documents
only allows for a literal URL, which is less elegant, more error-prone, and less sustainable than the dynamically generated links provided via Agent Links or Related Accessions.<o:p></o:p></li><li class="MsoNormal" style="mso-list:l1 level1 lfo6">If not, is this something that’s on a development roadmap, or have others implemented this as a plug-in?<o:p></o:p></li></ul>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Many thanks for your thoughts!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Ron<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="line-height:125%"><b><span lang="NL-BE" style="font-size:9.0pt;line-height:125%;font-family:"Arial",sans-serif;color:#4D4D4D">Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis</span></b><span lang="NL-BE" style="font-size:9.0pt;line-height:125%;font-family:"Arial",sans-serif;color:#4D4D4D"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:125%"><span lang="NL-BE" style="font-size:9.0pt;line-height:125%;font-family:"Arial",sans-serif;color:#4D4D4D">Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving</span><span lang="NL-BE" style="font-size:9.0pt;line-height:125%;font-family:"Arial",sans-serif">
<span style="color:#4D4D4D">| Musea en Erfgoed <o:p></o:p></span></span></p>
<p class="MsoNormal" style="line-height:125%"><span lang="NL-BE" style="font-size:9.0pt;line-height:125%;font-family:"Arial",sans-serif;color:#4D4D4D">Minderbroedersstraat 22, 2000 Antwerpen<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="NL-BE" style="font-size:9.0pt;font-family:"Segoe UI Symbol",sans-serif;color:#4D4D4D">✉</span><span lang="NL-BE" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#4D4D4D"> Grote Markt 1, 2000 Antwerpen<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="NL-BE" style="font-size:9.0pt;font-family:"Arial",sans-serif;color:#4D4D4D">gsm +32 0485 02 80 50 | tel. +32 3 222 93 30</span><span lang="NL-BE" style="font-size:9.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:125%"><span lang="NL-BE"><a href="http://www.letterenhuis.be/"><span style="font-size:9.0pt;line-height:125%;font-family:"Arial",sans-serif;color:#4D4D4D">letterenhuis.be</span></a></span><span lang="NL-BE" style="font-size:9.0pt;line-height:125%;font-family:"Arial",sans-serif;color:#4D4D4D">
| </span><span lang="NL-BE"><a href="https://www.instagram.com/letterenhuis/"><span style="font-size:9.0pt;line-height:125%;font-family:"Arial",sans-serif;color:#4D4D4D">instagram</span></a></span><span lang="NL-BE" style="font-size:9.0pt;line-height:125%;font-family:"Arial",sans-serif;color:#4D4D4D">
| </span><span lang="NL-BE"><a href="https://www.facebook.com/Letterenhuis"><span style="font-size:9.0pt;line-height:125%;font-family:"Arial",sans-serif;color:#4D4D4D">facebook</span></a><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:125%"><span lang="NL-BE" style="font-size:9.0pt;line-height:125%;font-family:"Arial",sans-serif;color:#4D4D4D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="line-height:125%"><b><span lang="NL-BE" style="font-size:7.0pt;line-height:125%;font-family:"Arial",sans-serif;color:#4D4D4D">Proclaimer</span></b><span lang="NL-BE" style="font-size:7.0pt;line-height:125%;font-family:"Arial",sans-serif;color:#4D4D4D"><o:p></o:p></span></p>
<p class="MsoNormal" style="line-height:125%"><span lang="NL-BE" style="font-size:7.0pt;line-height:125%;font-family:"Arial",sans-serif;color:#4D4D4D">Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet voor u bestemd is, vragen
we u vriendelijk om dat te melden aan de afzender. Deze e-mail en de bijlagen zijn namelijk officiële documenten van de stad Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als stad nemen we privacy heel serieus en willen we als een
goede huisvader waken over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te verwijderen en het niet verder te verspreiden of te kopiëren.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="NL-BE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="NL-BE"><o:p> </o:p></span></p>
</div>
</div>
</div>
</div>
</body>
</html>