[Archivesspace_Users_Group] error saving an Archival Object

[mang.sun at rice.edu]

This issue is now also happening to our v2.7.1 aspace.  Similar error
message.  But the way using the directive of
#AppConfig[:resequence_on_startup]
= True seemingly doesn't work. Is the directive still a valid one with
v2.7.1?
[image: image.png]

Thank you.

Mang Sun
Rice U.

On Thu, Feb 2, 2017 at 3:37 PM Noah Huffman <noah.huffman at duke.edu> wrote:

> Robin,
>
>
>
> Here’s an unresolved JIRA issue describing this problem:
> https://archivesspace.atlassian.net/browse/AR-1326
>
>
>
> It tends to happen when you try to edit an archival object record that has
> been transferred from another resource record.
>
>
>
> As far as I know, there are a couple of fixes for this:
>
> 1.       Resequence your entire ASpace database.  To do this, shut down
> ASpace, modify config.rb (#AppConfig[:resequence_on_startup] = True), and
> restart.  Beware that resequencing a large database will take a long time,
> but this should prevent the same error from occurring in other records.
>
> 2.       Install this plugin that allows you to resequence only the
> resource record where the error occurs:
> https://github.com/archivesspace/resync
>
>
>
> -Noah
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Wendler,
> Robin King
> *Sent:* Thursday, February 02, 2017 3:46 PM
> *To:* archivesspace_users_group at lyralists.lyrasis.org
> *Subject:* [Archivesspace_Users_Group] error saving an Archival Object
>
>
>
> Hello, ASpacers,
>
>          When saving the archival object below, changed only by adding a
> single space preceding “Tours” in the title, we get the following error
> message:
>
>
>
> [image: cid:image001.png at 01D27D70.E6CB7BB0]
>
>
>
> The same error usually occurs if we try to change other archival object
> records attached to this resource record, but not always. One I was able to
> change, but received the error when I tried to change it back. Another I
> could change and change back without encountering the error. The resource
> record itself can be changed.  Any ideas about why this is happening and
> what we can do to clear it up?
>
>
>
> Thanks for your thoughts,
>
> Robin
>
>
>
> Robin Wendler
>
> Library Technology Services
>
> Harvard University
>
> 90 Mt. Auburn St.
>
> Cambridge, MA 02138
>
> 617-495-3724
>
> r_wendler at harvard.edu
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20220525/e8dac320/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 116837 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20220525/e8dac320/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 18137 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20220525/e8dac320/attachment-0001.png>