[Archivesspace_Users_Group] Trouble transferring resource

[Brian Harrington]

Hi Don,

We saw this error recently with a resource that shared a top container with another resource.  Since top containers are scoped to repositories, when you transfer a resource ASpace moves its top containers to the new repository.  But if a top container is linked to another resource in the old repo, ASpace can’t move it.  I suspect you would get this same message with any repo-scoped item that is linked to multiple resources.

Could this be your issue?

Brian

— 
Brian Harrington
Migration Specialist
LYRASIS
brian.harrington at lyrasis.org

> On Jan 7, 2020, at 2:09 PM, Donald Mennerich <don.mennerich at nyu.edu> wrote:
> 
> Laney, et al.
> 
> Has there been anything done with this situation? A user here was attempting to transfer resource from repo 2 to repo 8, but we're getting an assertion failed error in the log.
> 
> {
>   
> "error": "ASSERTION FAILED: {SNIP} has a repo_id of 8 but the active repository is 2"
> 
> }
> 
> This transfer is working on some resources, but not others, it does not seem to be related to the size of the resources. We are getting the same error in the log if this is done either through the frontend or via the api. Could this be the same problem that Trevor reported in this thread in 2017. We are on v2.7.0.
> 
> Thanks, 
> 
> Don
> 
> Donald R. Mennerich, digital archivist
> New York University Libraries
> don.mennerich at nyu.edu (212) 992-6264
> 
> 
> 
> On Mon, Jun 26, 2017 at 9:23 AM Laney McGlohon <laney.mcglohon at lyrasis.org> wrote:
> Hey Trevor,
> 
>  
> 
> We need to change and use sessions instead of cookies for transferring large resources.
> 
> I have added comment from StackOverflow (my favorite source) to the JIRA ticket,
> 
>  
> 
> Here it is again:
> 
>  
> 
> Rails cookies are limited to 4KB. Note that the sessions is also stored in the cookie in the default configuration. See: http://guides.rubyonrails.org/security.html#session-storage
> 
> The only thing you can do about that: Do not store big objects in the cookie. Store them in the database and then only store the object's id in the cookie.
> 
> This answer might also be interesting to you: https://stackoverflow.com/a/4604212/2483313
> 
>  
> 
> Laney
> 
>  
> 
>  
> 
> Laney McGlohon
> 
> ArchivesSpace Tech Lead
> 
> laney.mcglohon at lyrasis.org
> 
> 800.999.8558 x2927
> 
> laneymcglohon Skype
> 
>  
> 
>  
> 
>  
> 
> From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Trevor Thornton <trthorn2 at ncsu.edu>
> Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
> Date: Friday, June 23, 2017 at 10:21 AM
> To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
> Subject: [Archivesspace_Users_Group] Trouble transferring resource
> 
>  
> 
> Hi-
> 
>  
> 
> We're trying to transfer a relatively large resource to a different repository and the transfer keeps failing with a CookieOverflow exception (the most delicious exception of all).
> 
>  
> 
> The exception response HTML is attached. We're on v. 1.5.1.
> 
>  
> 
> Anybody every experience this? Is there a cure?
> 
>  
> 
> Thanks,
> 
> Trevor Thornton
> 
>  
> 
> --
> 
> Trevor Thornton
> 
> Applications Developer, Digital Library Initiatives
> 
> North Carolina State University Libraries
> 
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group