<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)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        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;}
tt
        {mso-style-priority:99;
        font-family:"Courier New";}
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.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:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></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="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">To add to this thread, a gap in the current functionality of ArchivesSpace is a place to note actual Processing actions – more than just in a Processing Notes
 field.  For me, this would include being able to trace items back to an accession record, noting what’s been weeded, moved, etc. especially after a collection has been actively used by researchers (this would give a trace for when a citation says xx is in
 box 5 but it’s now in box 10 or has been removed due to additional processing work.)  In most cases, I would want this information not Public, but in structured data so it could be queried or reported.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Is anyone working on a Processing module?  I know there has been a Collection Assessment module in the works.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Kari<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">--------------------------------------------------------------------------<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Kari R. Smith<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Institute Archivist and Program Head, Digital Archives<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Institute Archives & Special Collections, MIT Libraries<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Massachusetts Institute of Technology, Cambridge, Massachusetts 02139<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Calibri",sans-serif;color:#1F497D">IASC office: 617.258.5568 
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><a href="http://libraries.mit.edu/archives/"><span style="font-size:9.0pt;color:#0563C1">http://libraries.mit.edu/archives/</span></a></span><span style="font-size:9.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> 
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Calibri",sans-serif;color:#1F497D">she | her | hers   @karirene69  [smithkr at mit.edu]<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;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><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> archivesspace_users_group-bounces@lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org]
<b>On Behalf Of </b>VivianLea.Solek@Kofc.Org<br>
<b>Sent:</b> Tuesday, November 28, 2017 12:38 PM<br>
<b>To:</b> Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Cc:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Linking related accessions below collection level<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Hi Jordon,</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">I would be interested in this functionality.  I seldom get a complete record group in one accession, so I am constantly adding accessions to my record groups.  Sign me up as someone willing to push
 for this functionality!</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Sincerely,</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">VivianLea</span><br>
<br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">VivianLea Solek</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Archivist</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Knights of Columbus Supreme Council Archives</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif"><br>
Knights of Columbus Museum<br>
1 State Street<br>
New Haven, CT 06511-6702</span><br>
<span style="font-size:10.0pt;font-family:"Arial",sans-serif">Phone 203 752-4578<br>
Fax 203 865-0351</span><br>
<br>
<img border="0" width="16" height="16" style="width:.1666in;height:.1666in" id="_x0000_i1025" src="cid:image001.gif@01D36855.F43836F0" alt="Inactive hide details for Jordon Steele ---11/28/2017 11:57:30 AM---Hi all, We have an interest in linking archival objects (i."><span style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#424282">Jordon
 Steele ---11/28/2017 11:57:30 AM---Hi all, We have an interest in linking archival objects (i.e. the levels below collection level) in</span><br>
<br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">From: </span>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif">Jordon Steele <<a href="mailto:jsteele@jhu.edu">jsteele@jhu.edu</a>></span><br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">To: </span>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif">Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a>>,
</span><br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Date: </span>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif">11/28/2017 11:57 AM</span><br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Subject:
</span><span style="font-size:7.5pt;font-family:"Arial",sans-serif">[Archivesspace_Users_Group] Linking related accessions below collection level</span><br>
<span style="font-size:7.5pt;font-family:"Arial",sans-serif;color:#5F5F5F">Sent by:
</span><span style="font-size:7.5pt;font-family:"Arial",sans-serif"><a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-bounces@lyralists.lyrasis.org</a></span><o:p></o:p></p>
<div class="MsoNormal">
<hr size="2" width="100%" noshade="" style="color:#8091A5" align="left">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Hi all,</span><br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif"> </span><br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif">We have an interest in linking archival objects (i.e. the levels below collection level) in resource records back to the accessions they came from. The situation that precipitated discussion about
 this possibility was that we have one series of materials that is associated with multiple accession records.</span><br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif"> </span><br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Unless I’m missing something, the only way one can currently link to accessions from resource records is at the collection level. There is no “Related accessions” feature at levels below that.</span><br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif"> </span><br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif">The way we’re doing this now is creating an accruals note at the appropriate level and typing the accession number into the free text field, but having a direct link between the two would be handy.
 For born-digital collections, we are also linking the original containers from which the digital content came to the appropriate level in the resource record using the instance module.</span><br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif"> </span><br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif">I’m wondering if others in the community have discussed or considered this before.</span><br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif"> </span><br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Thanks!</span><br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif"> </span><br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Best,</span><br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif"> </span><br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Jordon</span><br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif"> </span><br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Jordon Steele</span><br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Hodson Curator of the University Archives</span><br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Special Collections</span><br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif">The Sheridan Libraries</span><br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Johns Hopkins University</span><br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif">3400 N Charles St</span><br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif">Baltimore, MD 21218</span><br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif">410-516-5493</span><br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif"><a href="mailto:jsteele@jhu.edu">jsteele@jhu.edu</a></span><br>
<span style="font-size:10.0pt;font-family:"Calibri",sans-serif"> </span><tt><span style="font-size:10.0pt">_______________________________________________</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>Archivesspace_Users_Group mailing list</tt><br>
<tt><a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@lyralists.lyrasis.org</a></tt><br>
<tt><a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=C90XguLnqhMT2ADRaOs3gQ&r=balEICFvGrVJ8Sr6vcdFtVtZaJWT42A5myJ4zXSQILc&m=zrLa9yi6Jz939dKTz3tRUTucZ7ONMd-S1nBNWY_f7lY&s=BR3jeXZt1A7AoWvxkDjYNt9Y8PigD1yLpwGadXpKZWI&e=">https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=C90XguLnqhMT2ADRaOs3gQ&r=balEICFvGrVJ8Sr6vcdFtVtZaJWT42A5myJ4zXSQILc&m=zrLa9yi6Jz939dKTz3tRUTucZ7ONMd-S1nBNWY_f7lY&s=BR3jeXZt1A7AoWvxkDjYNt9Y8PigD1yLpwGadXpKZWI&e=</a> </tt></span><o:p></o:p></p>
<div>
<p class="MsoNormal">CONFIDENTIALITY NOTICE: This message and any attachments may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee or addressees named above for its intended purpose. If you
 are not the intended recipient of this message, this message constitutes notice that any review, retransmission, distribution, copying or other use or taking any action in reliance on the information in this message and its attachments, is prohibited. If you
 receive this communication in error, please immediately advise the sender by reply e-mail and delete this message and its attachments from your system without keeping a copy. Unless expressly stated in this e-mail, nothing in this message may be construed
 as a digital or electronic signature. Thank you.<o:p></o:p></p>
</div>
</div>
</body>
</html>