[Archivesspace_Users_Group] database integrity constraint conflict

[Galligan, Patrick]

Maureen,

We essentially found out that there were only two ways to fix the record save error caused by transferring components in 1.1.2:


*         Export the EAD finding aid and re-import (not ideal because you'd have to recreate some links/connections)

*         Stop the AS instance and then restart it with the resequence on startup option enabled

The first option wasn't viable to us, so anytime someone transfers components, we have to resequence over the weekend. It's a big hassle and not a long-term solution.

We haven't run into this problem with our updated versions that we're running on the dev though.

Patrick Galligan
Rockefeller Archive Center
Assistant Digital Archivist
914-366-6386

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Callahan, Maureen
Sent: Friday, July 17, 2015 4:46 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] database integrity constraint conflict

Hi Chris and Patrick,

We're on a special branched version of 1.1.2 that HM modified for us while we wait for the container management plug-in to be integrated into the core code. The record was transferred two days ago.

Patrick, what do you mean when you say that you resequence every time you transfer components?

Thank you both for your insights!

Maureen

Maureen Callahan
Archivist, Metadata Specialist
Manuscripts & Archives
Yale University Library
maureen.callahan at yale.edu<mailto:maureen.callahan at yale.edu>
203.432.3627

Webpage: web.library.yale.edu/mssa
Collections: drs.library.yale.edu

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Chris Fitzpatrick
Sent: Friday, July 17, 2015 4:23 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] database integrity constraint conflict


Hi Maureen,



Which version are you all using? Was this record transferred recently?



b,chris.


Chris Fitzpatrick | Developer, ArchivesSpace
Skype: chrisfitzpat  | Phone: 918.236.6048
http://archivesspace.org/

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Galligan, Patrick <PGalligan at rockarch.org<mailto:PGalligan at rockarch.org>>
Sent: Friday, July 17, 2015 9:33 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] database integrity constraint conflict


Maureen,



I'm just chiming in to say this has also been happening at the RAC. The only fix we've found is to resequence each time we transfer components, which is obviously not ideal.



We are not on the newest version of AS though.



Patrick Galligan

Rockefeller Archive Center

Assistant Digital Archivist

914-366-6386



From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Callahan, Maureen
Sent: Friday, July 17, 2015 1:45 PM
To: 'archivesspace_users_group at lyralists.lyrasis.org'
Cc: Connolly, Christine; Caldera, Mary
Subject: [Archivesspace_Users_Group] database integrity constraint conflict



Hey folks,



I'm getting this error:

en.validation_errors.database_integrity_constraint_conflict__java__commysqljdbcexceptionsjdbc4__mysqlintegrityconstraintviolationexception__duplicate_entry__2101963 at archival_object-4__for_key__uniq_ao_pos_<mailto:en.validation_errors.database_integrity_constraint_conflict__java__commysqljdbcexceptionsjdbc4__mysqlintegrityconstraintviolationexception__duplicate_entry__2101963 at archival_object-4__for_key__uniq_ao_pos_>



when I try to save archival objects that had been transferred from another resource record. For instance, this archival object is number 2102081 but it looks like it's telling me that it conflicts with archival object 2101963. I'm happy to do something to change one of the sets of records, but it would be helpful to know what that change needs to look like and how I can avoid this constraint in the future.



Thanks,

Maureen



Maureen Callahan

Archivist, Metadata Specialist

Manuscripts & Archives

Yale University Library

maureen.callahan at yale.edu<mailto:maureen.callahan at yale.edu>

203.432.3627



Webpage: web.library.yale.edu/mssa

Collections: drs.library.yale.edu


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