[Archivesspace_Users_Group] database integrity constraint conflict
PGalligan at rockarch.org
Fri Jul 17 15:33:56 EDT 2015
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.
Rockefeller Archive Center
Assistant Digital Archivist
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 1:45 PM
To: 'archivesspace_users_group at lyralists.lyrasis.org'
Cc: Connolly, Christine; Caldera, Mary
Subject: [Archivesspace_Users_Group] database integrity constraint conflict
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.
Archivist, Metadata Specialist
Manuscripts & Archives
Yale University Library
maureen.callahan at yale.edu<mailto:maureen.callahan at yale.edu>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Archivesspace_Users_Group