<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 style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
Just chiming in to say the data model doesn't allow a digital object to be a child of an archival object - only an AO can be a child of an AO.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
I totally get what you're saying about the redundancy aspect though. Its frustrating that you have to have both an AO and a DO. I think the DO model might have been represented better as a complex/repeating subrecord of an AO rather than as an analog to a top
container. I think the likelihood of someone having an unattached DO described in AS is
<b>very</b> small and I don't think its likely that a DO would be shared across multiple AOs the same way that different things can all be stuffed into a single top container/box. That's my take anyway!<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
jds<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 Kendall Aughenbaugh
<kaughenbaugh@hillwoodmuseum.org><br>
<b>Sent:</b> Wednesday, July 12, 2023 11:59 AM<br>
<b>To:</b> Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] [External Message] Re: Digital Objects as children of Archival Objects</font>
<div> </div>
</div>
<style type="text/css" style="display:none">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div class="x_elementToProof" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Hi Kate, </div>
<div class="x_elementToProof" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div class="x_elementToProof" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
There might've been some confusion with my original question. Digital object records are capable of capturing the same descriptive information as the archival object -- the two object types have nearly the same exact sub-records available (digital objects may
have several more). I plan to have a digital object for each individual item, with extent, title, date, etc. information included. Our digital objects link out to the asset in our DAM, which includes extended item-level metadata in view. So, there would be
no a loss of descriptive information and there would definitely be clarity in the folder-level archival object regarding extent and portion. </div>
<div class="x_elementToProof" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div class="x_elementToProof" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Example:</div>
<div class="x_elementToProof" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
The archival object would be at the folder-level, and the extent sub-record for that archival object would say the folder includes 5 items (images). The date sub-record would explain the full contents are dated between 1971-1981. The children of that archival
object would, ideally, be the digital object records for each of those 5 images. The date sub-record for each digital object would describe that singular item, as would the extent sub-record. </div>
<div class="x_elementToProof" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div class="x_elementToProof" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
The only thing I am looking to avoid is creating an archival object for each digital object, as it seems unnecessary when the digital object record can record the same descriptive information. My question is: Is it possible to have a digital object related
to an archival object <i>as a child</i> rather than the digital object only existing as an
<i>instance of</i> an archival object?</div>
<div class="x_elementToProof" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div class="x_elementToProof" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Cheers,</div>
<div class="x_elementToProof" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div class="x_elementToProof" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Kendall</div>
<div class="x_elementToProof">
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div id="x_Signature">
<div><br>
<span style="font-family:calibri,sans-serif"><strong>Kendall Aughenbaugh</strong>
<i></i><br>
Digital Services Archivist<br>
202.243.3912<br>
<a href="mailto:kaughenbaugh@hillwoodmuseum.org">kaughenbaugh@hillwoodmuseum.org</a><br>
<br>
Hillwood Estate, Museum & Gardens<br>
4155 Linnean Ave NW<br>
Washington, DC 20008<br>
<a href="http://www.hillwoodmuseum.org/" originalsrc="http://www.hillwoodmuseum.org/" shash="txnGuKCvPXeyRchTUfWPFz2ZbiSnyz11nT0v1TUjEnE0vPvSkbEmJ67xwEsxxwgCSDhrRO1UzlNtYzvqQMMeZOmTl+tw+6ToUeFZ+OPiq3vwZDA+3fPKQbuHA96IO+hY+MWBZB5FVEDcwkYQT8QVyyH0VFVnqOrN8DxXuq9PRLY=">www.hillwoodmuseum.org</a><br>
<br>
Special Exhibition<br>
<a href="https://www.hillwoodmuseum.org/exhibitions" originalsrc="https://www.hillwoodmuseum.org/exhibitions" shash="M0c/B4R+kVRvAXmgC7t6zqvrZGK/v3qoCsyMxulGP78cbEYsp6C9ALCKsrp7Z5LmWjCBt+reZaCc5EcnzczUXp0UNRfso1bo27MiLIkAFT68UAw6Ho0Ouu2HQTJSwmc/sT75/XPYIz/DCDMksYPpVltzHwCHLkdE/K2D8gcCBxY="><img alt="Special Exhibitions" src="https://hillwoodmuseum.org/sites/default/files/2023-06/Glassmail.png"></a><br>
Through January 14, 2024<br>
<br>
Follow us on <a href="https://www.facebook.com/HillwoodMuseum" originalsrc="https://www.facebook.com/HillwoodMuseum" shash="cLDo+5A90AclC4RE3O4m0wtVmQ20JWiVAkJdf1P+HnizhbMzNeA34uzdz16I4ZpGzjsGsJhFUTpH6xYP0fJ1ADXaRlCvq64gaoKuf6Cigc7jQyQW9Oybk9AUsjj2c5DHy329Ilf8F6NNqWOiObjv2LQCLE0QP5wcMlgog+FbjUM=">
Facebook</a> and <a href="https://www.facebook.com/HillwoodMuseum" originalsrc="https://www.facebook.com/HillwoodMuseum" shash="cLDo+5A90AclC4RE3O4m0wtVmQ20JWiVAkJdf1P+HnizhbMzNeA34uzdz16I4ZpGzjsGsJhFUTpH6xYP0fJ1ADXaRlCvq64gaoKuf6Cigc7jQyQW9Oybk9AUsjj2c5DHy329Ilf8F6NNqWOiObjv2LQCLE0QP5wcMlgog+FbjUM=">
Instagram</a></span><br>
</div>
</div>
</div>
<div id="x_appendonsend"></div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of Bowers, Kate
A. <kate_bowers@harvard.edu><br>
<b>Sent:</b> Wednesday, July 12, 2023 11:24 AM<br>
<b>To:</b> Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject:</b> [External Message] Re: [Archivesspace_Users_Group] Digital Objects as children of Archival Objects</font>
<div> </div>
</div>
<style>
<!--
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
p.x_x_MsoNormal, li.x_x_MsoNormal, div.x_x_MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif}
a:link, span.x_x_MsoHyperlink
{color:blue;
text-decoration:underline}
span.x_x_EmailStyle20
{font-family:"Calibri",sans-serif;
color:windowtext}
.x_x_MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
-->
</style>
<div lang="EN-US" style="word-wrap:break-word">
<div class="x_x_WordSection1">
<p class="x_x_MsoNormal">If we digitize in part, we describe the digitized part as a child. Even if the description is minimal.</p>
<p class="x_x_MsoNormal"> </p>
<p class="x_x_MsoNormal">Imagine the researcher! The user interface is going to tell them the archival object has a digital presence. They will go through the digital object thinking they have the whole thing, in ignorance that they have seen only part. Or,
they will realize it is a partial digitization, and be disappointed.</p>
<p class="x_x_MsoNormal"> </p>
<p class="x_x_MsoNormal">Yes, there is a cost to doing this. There is also a cost to NOT doing this. In the future, how will you find things only digitized in part, if you don’t describe the digitized part? How will you manage digital content, if you don’t
know what it is?</p>
<p class="x_x_MsoNormal"> </p>
<p class="x_x_MsoNormal">There had to be a selection made to digitize the part, so someone had to tell someone else what parts were to be digitized. Is there any way that you can turn the recording of that selection into a description task? Even if it is only
to make a child that duplicates parent and add “[digitized portion]” at the end of the title.</p>
<p class="x_x_MsoNormal"> </p>
<p class="x_x_MsoNormal">Kate</p>
<p class="x_x_MsoNormal"> </p>
<div>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="x_x_MsoNormal"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org>
<b>On Behalf Of </b>Kendall Aughenbaugh<br>
<b>Sent:</b> Wednesday, July 12, 2023 10:55 AM<br>
<b>To:</b> Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org><br>
<b>Subject:</b> [Archivesspace_Users_Group] Digital Objects as children of Archival Objects</p>
</div>
</div>
<p class="x_x_MsoNormal"> </p>
<div>
<p class="x_x_MsoNormal"><span style="font-size:12.0pt; color:black">Hi all, </span></p>
</div>
<div>
<p class="x_x_MsoNormal"><span style="font-size:12.0pt; color:black"> </span></p>
</div>
<div>
<p class="x_x_MsoNormal"><span style="font-size:12.0pt; color:black">Is it possible to attach digital objects as children of archival objects? I'm building out how I want to incorporate digital objects, and I can't get this part figured out. </span></p>
</div>
<div>
<p class="x_x_MsoNormal"><span style="font-size:12.0pt; color:black"> </span></p>
</div>
<div>
<p class="x_x_MsoNormal"><span style="font-size:12.0pt; color:black">We typically created finding aids at the folder level -- and I'd prefer to keep it that way -- but we tend to digitize at the item level. I'd like to link individual digital objects as children
of their parent folder <i>without</i> having to create an individual item level archival object for each digital one. It feels redundant and unnecessary since the digital object is capable of capturing the same exact information. </span></p>
</div>
<div>
<p class="x_x_MsoNormal"><span style="font-size:12.0pt; color:black"> </span></p>
</div>
<div>
<p class="x_x_MsoNormal"><span style="font-size:12.0pt; color:black">My attempt to do this yesterday resulted in 5 digital objects being attached to the folder level archival object, which is OK for now but not ideal. Any ideas? </span></p>
</div>
<div>
<p class="x_x_MsoNormal"><span style="font-size:12.0pt; color:black"> </span></p>
</div>
<div>
<p class="x_x_MsoNormal"><span style="font-size:12.0pt; color:black">-K</span></p>
</div>
<div>
<div>
<p class="x_x_MsoNormal"><span style="font-size:12.0pt; color:black"> </span></p>
</div>
<div id="x_x_Signature">
<div>
<p class="x_x_MsoNormal"><br>
<strong><span style="font-family:"Calibri",sans-serif">Kendall Aughenbaugh</span></strong>
<br>
Digital Services Archivist<br>
202.243.3912<br>
<a href="mailto:kaughenbaugh@hillwoodmuseum.org">kaughenbaugh@hillwoodmuseum.org</a><br>
<br>
Hillwood Estate, Museum & Gardens<br>
4155 Linnean Ave NW<br>
Washington, DC 20008<br>
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.hillwoodmuseum.org_&d=DwMFAw&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=rFxtpPupsQU4Y3Zb4JMEGdzhnA3iU-uauteHu7h3BPztakMirDMJ0w9ILgPPPwZs&s=dfv1C1gl_ue0vNWgY7Mon1RZ_i2sKE_ZzQ4zbY48UI0&e=" originalsrc="https://urldefense.proofpoint.com/v2/url?u=http-3A__www.hillwoodmuseum.org_&d=DwMFAw&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=rFxtpPupsQU4Y3Zb4JMEGdzhnA3iU-uauteHu7h3BPztakMirDMJ0w9ILgPPPwZs&s=dfv1C1gl_ue0vNWgY7Mon1RZ_i2sKE_ZzQ4zbY48UI0&e=" shash="GjBJESoAYZMxau1KwWsTXzh1QLGKi8ma37rnlqHkFVsyZ8JNCBH9nTWSfobciBCJ0yyGbVxdA0cdWFxTCSN7A0DP6cMyd3p+NbxJKOIm24B+AtuQrGR7UvTgYTjM+plL1DB2ryHQcenn30eopVcc+ZVMZqfqQwIYGor+XtcbUhM=">www.hillwoodmuseum.org</a><br>
<br>
Special Exhibition<br>
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.hillwoodmuseum.org_exhibitions&d=DwMFAw&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=rFxtpPupsQU4Y3Zb4JMEGdzhnA3iU-uauteHu7h3BPztakMirDMJ0w9ILgPPPwZs&s=WMPuwQ0P_HTlyoFuFZZrLwz6ElyLJA2imMyeigyGWH4&e=" originalsrc="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.hillwoodmuseum.org_exhibitions&d=DwMFAw&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=rFxtpPupsQU4Y3Zb4JMEGdzhnA3iU-uauteHu7h3BPztakMirDMJ0w9ILgPPPwZs&s=WMPuwQ0P_HTlyoFuFZZrLwz6ElyLJA2imMyeigyGWH4&e=" shash="jYX2Xc1erbA24awrUdwLj6Drl9W8tuENCTfTMd2M39eK9AeOCdxfjUWqiXqsKekk13joyKNfQXsyQK1tEOQsPbNzXKiVzTd1+7C4+HNH7xno7HURT9XXxNVUP+XvflfQ/keUdeyG4YzDIBvI07u1rSAtvPiJcLKRZijFoKJ1bX8="><span style="text-decoration:none"><img border="0" width="500" height="188" id="x_x__x0000_i1025" alt="Special Exhibitions" style="width:5.2083in; height:1.9583in" src="https://hillwoodmuseum.org/sites/default/files/2023-06/Glassmail.png"></span></a><br>
Through January 14, 2024<br>
<br>
Follow us on <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_HillwoodMuseum&d=DwMFAw&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=rFxtpPupsQU4Y3Zb4JMEGdzhnA3iU-uauteHu7h3BPztakMirDMJ0w9ILgPPPwZs&s=aQsCjvQClfN4iXSk95yMnKeH06uYPlMfbe1X97Cqhak&e=" originalsrc="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_HillwoodMuseum&d=DwMFAw&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=rFxtpPupsQU4Y3Zb4JMEGdzhnA3iU-uauteHu7h3BPztakMirDMJ0w9ILgPPPwZs&s=aQsCjvQClfN4iXSk95yMnKeH06uYPlMfbe1X97Cqhak&e=" shash="zHfnjNDMptKSVG/b/8Gs297CkOzgOR1Kem5uecPmB9f3CceES6pHkZELYgZfAYhJ/vDrXE9RnGuEyds36TLVrB1ONF4tOPNZxqGI/xMutctpS08nODkQtzqfZafKrC+BWxFlr3wpD9Cqgtk1FRZoWRODXyiohvRINXQUxNamHoo=">
Facebook</a> and <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_HillwoodMuseum&d=DwMFAw&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=rFxtpPupsQU4Y3Zb4JMEGdzhnA3iU-uauteHu7h3BPztakMirDMJ0w9ILgPPPwZs&s=aQsCjvQClfN4iXSk95yMnKeH06uYPlMfbe1X97Cqhak&e=" originalsrc="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_HillwoodMuseum&d=DwMFAw&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=rFxtpPupsQU4Y3Zb4JMEGdzhnA3iU-uauteHu7h3BPztakMirDMJ0w9ILgPPPwZs&s=aQsCjvQClfN4iXSk95yMnKeH06uYPlMfbe1X97Cqhak&e=" shash="AuxPECEZJb2JxnCyOJ2SinEJ5CeGivpdMvaGa+NQlMe6jl4+Dy9Llww4VNJE+jUR6jCSk9BGPgmg1ApblPI9kmoL2vY9z+WNiwLZ5FNpRc7zRHeoJnBELMDbHQjlhqDb2oR2P0UC4egnjsMQBU2cyQ/Ts/BWrl03B/2fskmqiko=">
Instagram</a></p>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>