[Archivesspace_Users_Group] Fwd: seeking clarification on transfer of digital objects between repositories

Chris Fitzpatrick Chris.Fitzpatrick at lyrasis.org
Wed Feb 10 17:30:11 EST 2016


Yeah....sorry, just got to look at this...

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?

Does that make sense? I might be missing something obvious...


Chris Fitzpatrick | Developer, ArchivesSpace
Skype: chrisfitzpat  | Phone: 918.236.6048

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Jason Loeffler <j at minorscience.com>
Sent: Wednesday, February 10, 2016 12:03 AM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Fwd: seeking clarification on transfer of digital objects between repositories

Pursuant to AR-1405<https://archivesspace.atlassian.net/browse/AR-1405>, can anyone replicate the issue or otherwise assist in this matter?

In summary, during a resource-to-repository transfer, attached digital object instances are not transferred to new repository.

Thanks, Jason

---------- Forwarded message ----------
From: Jason Loeffler <j at minorscience.com<mailto:j at minorscience.com>>
Date: Thu, Feb 4, 2016 at 7:23 PM
Subject: seeking clarification on transfer of digital objects between repositories
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>

Having a little trouble understanding what's going on with transferring digital objects between repos.

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.

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.

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.

This is described more completely in the attached gist<https://gist.github.com/minorscience/930fd457f0815b63defd>. I posted something related here<https://archivesspace.atlassian.net/browse/AR-1405>. (Not sure if that's the right place.)

Can someone confirm whether there is some design principle I am missing?

Many thanks, Jason

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160210/ea19515e/attachment.html>

More information about the Archivesspace_Users_Group mailing list