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

Custer, Mark mark.custer at yale.edu
Mon Dec 11 10:58:06 EST 2017


Leilani,


Could you attach an example EAD file?  I'm curious what happens when Unicode characters are used in place of the character entities.  I'm wondering if the issue might simply be that the font used doesn't include italic characters for the character entities that are tagged as italic (as an aside, what fonts do you use outside of ArchivesSpace?).  Either way, it would be nice to add these examples to some test scripts for ArchivesSpace.


Mark


________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Leilani Dawson <ltdawson at hawaii.edu>
Sent: Friday, December 8, 2017 3:45 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Collections Browse Error in Public Interface, v2.2.1

Yes, all of our accessibility-wrapped diacritics are in html tags.

(Occasionally we have notes where words labeled with alternate text are nested within EAD elements such as <title> or <persname> or the like, but those EAD elements are not as critical for us as the <span> with aria-label attribute.)

I'll ask our IT folks to put together a 2.2 test instance so I can upload a finding aid with diacritics and see whether the new PUI handles it in a screen-reader-friendly manner.

Thanks,
-Leilani

On Fri, Dec 8, 2017 at 9:12 AM, Christine Di Bella <christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>> wrote:

Hi Leilani,



Thanks for making me dig into this a bit more and for explaining one of the reasons tagging around a diacritic may be especially necessary. For your use case, is your tagging always like your example? If so, there’s sanitizer for HTML in the PUI that allows this kind of tagging to sail through just fine. It is XML tags like <emph> that we’re seeing this bug on.



There was some accessibility work that went into the development of the new PUI, but it would be good to know that what makes this kind of tagging work in the PUI doesn’t also cause the same issue for screen readers that is the reason for you wrapping the text originally. Can you test this out locally or upload a finding aid to http://test.archivesspace.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__test.archivesspace.org&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=3hrk0xcC4ZChzrpcCh0CQ_Gvang7BVjr4txYuvjxyM8&s=ojcyFCMoM3zS9hpwYf4E7AnqB96za3sLtX6PZ20VkFM&e=> and try it out?



Christine



Christine Di Bella

ArchivesSpace Program Manager

christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>

800.999.8558 x2905<tel:(800)%20999-8558>

678-235-2905<tel:(678)%20235-2905>

cdibella13 (Skype)



[ASpaceOrgHomeMedium]







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<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>] On Behalf Of Leilani Dawson
Sent: Friday, December 8, 2017 1:13 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Collections Browse Error in Public Interface, v2.2.1



Hi Christine,

I see this is listed in JIRA as a minor issue, but is there any guess for when it might be addressed?

Certain Hawaiian-language diacritics "break" screen readers, so in order to satisfy both accessibility requirements and UH's mandate to be a Hawaiian place of learning, the Library has started wrapping these diacritics in <span> tags with aria-label attributes.   (E.g.: <span aria-label="Hawaii">Hawaiʻi</span>)   ArchivesSpace 2.1 and 2.2 not being able to handle wrapped diacritics might preclude us from going forward with using the public user interface and/or upgrading to 2.x. until the fix is in.

-Leilani.

- -

Leilani Dawson

Manuscript Collections Archivist

University Archives & Manuscripts Department

University of Hawaii at Manoa Library

2550 McCarthy Mall, Honolulu, HI 96822

ltdawson at hawaii.edu<mailto:ltdawson at hawaii.edu>



On Fri, Dec 8, 2017 at 3:28 AM, Christine Di Bella <christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>> wrote:

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<https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_AR-2D1938&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=3hrk0xcC4ZChzrpcCh0CQ_Gvang7BVjr4txYuvjxyM8&s=VMpZ3HzcFod2VlOa_Q5TAqIkbX5K9NFmJ-9RGxTgJRI&e=> (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<tel:(800)%20999-8558>

678-235-2905<tel:(678)%20235-2905>

cdibella13 (Skype)



[ASpaceOrgHomeMedium]







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<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<mailto: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>



_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=3hrk0xcC4ZChzrpcCh0CQ_Gvang7BVjr4txYuvjxyM8&s=mcku_27mMAV6rVbPS8IwL0Tx_W-qI7NJvab5eSZgQuU&e=>



_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=3hrk0xcC4ZChzrpcCh0CQ_Gvang7BVjr4txYuvjxyM8&s=mcku_27mMAV6rVbPS8IwL0Tx_W-qI7NJvab5eSZgQuU&e=>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171211/375fb341/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.jpg
Type: image/jpeg
Size: 6608 bytes
Desc: image005.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171211/375fb341/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 6608 bytes
Desc: image006.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171211/375fb341/attachment-0001.jpg>


More information about the Archivesspace_Users_Group mailing list