<div dir="ltr"><div class="gmail_extra"><div><div class="gmail_signature"><div dir="ltr"><div>Hi Chris, </div><div><br></div><div>Thanks for picking this up. </div><div><br></div><div>Transferring a single resource and a.o. to a new repository does not include any attached d.o. instances. They do not follow and their :id parameters remain scoped to the origin repository. (This includes via the UI or via API calls.) </div><div><br></div><div>I've transferred the d.o. manually (via the API) and they're properly scoped now but have no means to reattach to containing a.o. </div><div><br></div><div>On the other hand, transferring an entire repository to the custody of another repository transfers all d.o. and preserves the relationship with the a.o.</div><div><br></div><div>I can't think of a use case in which you would want to transfer select resources and a.o. from one repo to a new one while abandoning their d.o. in the origin repo. But it's entirely possible I'm missing something.</div><div><br></div><div>JL</div></div></div></div>
<div class="gmail_extra"><br></div><div class="gmail_quote">On Wed, Feb 10, 2016 at 5:30 PM, Chris Fitzpatrick <span dir="ltr"><<a href="mailto:Chris.Fitzpatrick@lyrasis.org" target="_blank">Chris.Fitzpatrick@lyrasis.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div style="font-size:12pt;color:#000000;background-color:#ffffff;font-family:Calibri,Arial,Helvetica,sans-serif">
<p>Hi,</p>
<p><br>
</p>
<p>Yeah....sorry, just got to look at this...</p>
<p><br>
</p>
<p>There is a bit of conceptual thing here...a DO can be tied to multiple resources/AOs. It is also scoped to a repo. When you transfer the resource, does the DO follow? What if it's tied to another resource in the source repo?
<br>
</p>
<p><br>
</p>
<p>Does that make sense? I might be missing something obvious...</p>
<p><br>
</p>
<p>b,chris. <br>
</p>
<p><br>
</p>
<div>
<div name="divtagdefaultwrapper">
<div><font size="2">
<div>Chris Fitzpatrick | <font size="2">Developer, ArchivesSpace</font><br>
Skype: chrisfitzpat | Phone: <a href="tel:918.236.6048" value="+19182366048" target="_blank">918.236.6048</a><br>
<a href="http://archivesspace.org/" target="_blank">http://archivesspace.org/</a><br>
</div>
</font></div>
</div>
</div>
<br>
<br>
<div style="color:rgb(0,0,0)">
<hr disabled style="display:inline-block;width:98%">
<div dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">archivesspace_users_group-bounces@lyralists.lyrasis.org</a> <<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>> on behalf of Jason Loeffler
<<a href="mailto:j@minorscience.com" target="_blank">j@minorscience.com</a>><br>
<b>Sent:</b> Wednesday, February 10, 2016 12:03 AM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> [Archivesspace_Users_Group] Fwd: seeking clarification on transfer of digital objects between repositories</font>
<div> </div>
</div>
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>Pursuant to <a disabled href="https://archivesspace.atlassian.net/browse/AR-1405" target="_blank">
AR-1405</a>, can anyone replicate the issue or otherwise assist in this matter? </div>
</div>
</div>
<div><br>
</div>
<div>In summary, during a resource-to-repository transfer, attached digital object instances are not transferred to new repository. </div>
<div><br>
</div>
<div>Thanks, Jason</div>
<br>
<div class="gmail_quote">---------- Forwarded message ----------<br>
From: <b class="gmail_sendername">Jason Loeffler</b> <span dir="ltr"><<a disabled href="mailto:j@minorscience.com" target="_blank">j@minorscience.com</a>></span><br>
Date: Thu, Feb 4, 2016 at 7:23 PM<br>
Subject: seeking clarification on transfer of digital objects between repositories<br>
To: Archivesspace Users Group <<a disabled href="mailto:archivesspace_users_group@lyralists.lyrasis.org" target="_blank">archivesspace_users_group@lyralists.lyrasis.org</a>><br>
<br>
<br>
<div dir="ltr">
<div>
<div>
<div dir="ltr">
<div>Having a little trouble understanding what's going on with transferring digital objects between repos. </div>
<div><br>
</div>
<div>A repository to repository transfer of archival objects works fine. All linked digital objects are successfully transferred. However, when a resource is transferred, linked digital objects are not transferred.<br>
</div>
<div><br>
</div>
<div>For testing purposes, I've created a simple hierarchy of archival objects and linked a digital object to a child item. Using both the GUI and API, I've initiated a transfer of the top-level resource to a target repository. It appears that the associated
digital objects are not included in the transfer to the target repository and are orphaned at the originating repository. </div>
<div><br>
</div>
<div>I am unable to use the API to transfer the orphaned digital objects to the new repository because the association between the archival object and digital object no longer exists. </div>
<div><br>
</div>
<div>This is described more completely in the attached <a disabled href="https://gist.github.com/minorscience/930fd457f0815b63defd" target="_blank">gist</a>. I posted something related <a disabled href="https://archivesspace.atlassian.net/browse/AR-1405" target="_blank">here</a>.
(Not sure if that's the right place.)</div>
<div><br>
</div>
<div>Can someone confirm whether there is some design principle I am missing?</div>
<div><br>
</div>
<div>Many thanks, Jason</div>
</div>
</div>
</div>
</div>
</div>
<br>
</div>
</div>
</div>
</div>
</div>
<br>_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br>
<br></blockquote></div><br></div></div>