[Archivesspace_Users_Group] Collections Browse Error in Public Interface, v2.2.1

[Christine Di Bella]

Hi Neal,

Do you by chance have a collection that has the circumstance described in this JIRA ticket: https://archivesspace.atlassian.net/browse/AR-1938 (A diacritic wrapped in a tag.) Most likely it would be in the scope and contents note or abstract field if the error is happening from the collection browse.

If so, and that record appears on the first page of your all collection browse, that may be what's causing the issue. You would also get a "We're sorry something went wrong" when trying to view that particular record or on a search that includes that particular record. If you have multiple repositories, that would also explain why a collection browse that's scoped to another repository would not yield that issue.

This is a reported issue for all 2.1 and 2.2 versions. The workaround for now would be to remove either the tagging or the diacritic, but we hope to fix this issue for a future release.

If you don't have that circumstance, we'll need to delve into this more deeply.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Harmeyer, Neal A
Sent: Thursday, December 7, 2017 5:45 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Collections Browse Error in Public Interface, v2.2.1

Hello all,

I wonder if anyone else has experienced this issue?

When selecting the Collections browse (/repositories/resources) from the header in the public interface, version 2.2.1, the system throws an error message that reads 'Your request could not be completed due to an unexpected error'. This only occurs for Collections browse; all other areas continue to load without issue-so our systems administrator isn't sure this could be cause by any web server configurations. I've been able to cause the failure on our dev site by repeatedly selecting the Collections browse over a short period of time.

We didn't experience this in any past versions. A restart of the server removes the issue for a period of time but then it re-appears; there is nothing in our logs to point to a cause of the problem.

Any suggestions would be helpful!

Thank you,
Neal

--
Neal Harmeyer
Digital Archivist
Purdue Univesity Archives and Special Collections
Purdue University Libraries
harmeyna at purdue.edu<mailto:harmeyna at purdue.edu>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171208/59daca35/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 6608 bytes
Desc: image003.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171208/59daca35/attachment.jpg>