[Archivesspace_Users_Group] Unable to edit archival object after transferring

[Peterson, Christie]

Thanks, yeah, that's what I thought might have happened. Was wondering if
anyone else had encountered it and if there was a known fix, since the
transfer was done months ago and rolling back the db is not an option at
this point.

On Tue, Apr 18, 2017 at 9:48 AM, Lora Davis <ljdavis at jhu.edu> wrote:

> Hey Christie,
>
> Given this:
>
> duplicate_entry__297608 at archival_object-0__for_key__uniq_ao_pos_
>
>
> I’m thinking that what is going on is that during the merge you’ve ended
> up with two sets of archival_objects belonging to the same parent that have
> matching “positions" (the ao field that tells ASpace where to place an
> object in the collection’s tree).  If you have a way to look at the JSON
> for the archival objects you could confirm that multiple objects have the
> same position #.
>
> So, for example, archival_objects/2 would be:
>
> {
>   "lock_version": 0,
>   "position": 0,
>   "publish": true,
>   "ref_id": "9759e8ea59d8e8c95237974522c97551",
>   "title": "Research Materials”,
>      <snip>
>   "parent": {
>     "ref": "/repositories/2/archival_objects/1"
>   }
> }
>
> And archival_objects/3 is also:
>
> {
>   "lock_version": 0,
>   "position": 0,
>   "publish": true,
>   "ref_id": "4b2114851f10f24ea86c6506fb1a829f",
>   "title": "Rabelais-Villon",
>      <snip>
>   "parent": {
>     "ref": "/repositories/2/archival_objects/1"
>   }
> }
>
> That said, if this is the culprit, clearly this shouldn’t happen when
> transferring ao’s from one collection to another via the staff interface!
>
> Or, I could be way off base… :)
>
> Lora
>
>
> On Apr 18, 2017, at 8:57 AM, Peterson, Christie <cspeterson at email.gwu.edu>
> wrote:
>
> Hello,
>
> I'm having a problem with some archival objects where any attempt to edit
> them through the user interface results in the following error:
>
> translation missing: en.no key - translation missing:
> en.validation_errors.database_integrity_constraint_conflict__java__
> commysqljdbcexceptionsjdbc4__mysqlintegrityconstraintviolat
> ionexception__duplicate_entry__297608 at archival_object-0__
> for_key__uniq_ao_pos_
>
> The only thing I can think of that might be relevant is that these are
> objects in a series that was transferred from one collection to another via
> the interface.
>
> Has anyone run into this before? Have any suggestions?
>
> Thanks,
>
> Christie
>
> --
> Christie S. Peterson
>
> University Archivist
> George Washington University Libraries
> 704H Gelman Library
> cspeterson at gwu.edu
> 202.994.3925 <(202)%20994-3925>
> _______________________________________________
> 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
>
>


-- 
Christie S. Peterson

University Archivist
George Washington University Libraries
704H Gelman Library
cspeterson at gwu.edu
202.994.3925
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20170418/6a467ea4/attachment.html>