[Archivesspace_Users_Group] Archivesspace: Log run Amok
Jason Loeffler
j at minorscience.com
Wed Jan 3 17:35:16 EST 2018
I am able to reproduce this issue on 2.2.2.
I tried a few of the other log levels at config.rb and receive only info
level output.
I've opened a bug report here: https://archivesspace.
atlassian.net/projects/ANW/issues/ANW-293
Jason Loeffler
Technology Consultant | The American Academy in Rome
Minor Science | Application Development & Metadata Strategy
Brooklyn, New York
jason at minorscience.com
(347) 405-0826
minorscience (Skype)
On Wed, Jan 3, 2018 at 4:15 PM, Mark Cyzyk <mcyzyk at jhu.edu> wrote:
>
> All,
>
> Yesterday our archivesspace.out log file ran amok and consumed our disk
> space. (It grew to a whopping 11 GB.) I took a peek at it and am seeing
> that it's logging at the "Info" level when my config says it should only be
> logging at "Fatal":
>
> ## Log level for the backend, values: (everything) debug, info, warn,
>> error, fatal (severe only)
>> AppConfig[:backend_log_level] = "fatal"
>>
>
> This is sounding like a bug to me.
>
> If anyone has ideas on how to force logging to only fatal events, I'd like
> to know. MUCH appreciated.
>
> Mark
>
> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
> Mark Cyzyk, M.A., M.L.S.
> Scholarly Communication Architect
> Library Applications Group
> The Sheridan Libraries
> The Johns Hopkins University
> mcyzyk at jhu.edu
>
> Verba volant, scripta manent.
>
>
> On 1/2/2018 4:52 PM, archivesspace_users_group-requ
> est at lyralists.lyrasis.org wrote:
>
>> Send Archivesspace_Users_Group mailing list submissions to
>> archivesspace_users_group at lyralists.lyrasis.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_
>> users_group
>>
>> or, via email, send a message with subject or body 'help' to
>> archivesspace_users_group-request at lyralists.lyrasis.org
>>
>> You can reach the person managing the list at
>> archivesspace_users_group-owner at lyralists.lyrasis.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Archivesspace_Users_Group digest..."
>>
>>
>> Today's Topics:
>>
>> 1. Re: ArchivesSpace user manual error page (Christine Kim)
>> 2. Re: ArchivesSpace user manual error page (Christine Kim)
>> 3. Re: Collections Browse Error in Public Interface, v2.2.1
>> (Custer, Mark)
>> 4. Re: Collections Browse Error in Public Interface, v2.2.1
>> (Leilani Dawson)
>> 5. truncation in PUI 2.2.1 (Maderik, Rachel A)
>> 6. Re: truncation in PUI 2.2.1 (Christine Di Bella)
>> 7. Merging Controlled Values (Stasiulatis, Suzanne)
>> 8. installing wildcard SSL cert, redirect http to https (Brian
>> Slenk)
>> 9. digital object mapping to EAD in v.2.2.1 (Amanda Focke)
>> 10. Splitting off one repository into a new database
>> (Celia Caust-Ellenbogen)
>> 11. Position statement on multitenancy (Christie Peterson)
>> 12. Re: Merging Controlled Values (Michelson, Daniel)
>> 13. Re: Splitting off one repository into a new database
>> (Majewski, Steven Dennis (sdm7g))
>> 14. Re: Webinar Announcement: Varying Approaches to Testing
>> ASpace Pre-Releases - Dec 14 (Christine Kim)
>> 15. Re: installing wildcard SSL cert, redirect http to https
>> (Jason Loeffler)
>> 16. Ideas for advanced training topics? (Christine Kim)
>> 17. Re: installing wildcard SSL cert, redirect http to https
>> (Cook, Robert)
>> 18. ArchivesSpace 2.2.2 now available (Christine Di Bella)
>> 19. Re: ArchivesSpace 2.2.2 now available (Christie Peterson)
>> 20. Re: ArchivesSpace 2.2.2 now available (Christine Di Bella)
>> 21. ASpace 2.1.2 issue with digital object links (Knox, Ashley M.)
>> 22. Creating staff entities for Assessments module? (Tang, Lydia)
>> 23. Trouble changing localhost:9081 to new URL (Walker, Scott)
>> 24. New version of aspace-import-excel, a plugin to support bulk
>> loading of Archival Objects (Fox, Bobbi)
>> 25. Re: New version of aspace-import-excel, a plugin to support
>> bulk loading of Archival Objects (Majewski, Steven Dennis (sdm7g))
>> 26. reports (Steve Majewski)
>> 27. Re: DAO Notes in EAD (Christine Kim)
>> 28. Re: Creating staff entities for Assessments module?
>> (Pruitt, Adrienne)
>> 29. Re: Creating staff entities for Assessments module? (Tang, Lydia)
>> 30. reports (Majewski, Steven Dennis (sdm7g))
>> 31. release of updated Archivists' Toolkit to ArchivesSpace
>> migration tool (Christine Di Bella)
>> 32. Re: reports (Christie Peterson)
>> 33. Happy Holidays from ArchivesSpace! (Christine Kim)
>> 34. Re: reports (Majewski, Steven Dennis (sdm7g))
>> 35. Update on reports (Laney McGlohon)
>> 36. Re: Update on reports (Jordon Steele)
>> 37. release of updated Archon to ArchivesSpace migration tool
>> (Christine Di Bella)
>> 38. Overriding/Extending the new public interface in 2.2.0
>> (Flanagan, Patrick)
>> 39. Re: Overriding/Extending the new public interface in 2.2.0
>> (Fox, Bobbi)
>> 40. Re: Overriding/Extending the new public interface in 2.2.0
>> (Flanagan, Patrick)
>> 41. Re: Overriding/Extending the new public interface in 2.2.0
>> (Majewski, Steven Dennis (sdm7g))
>> 42. ArchivesSpace Update - December 2017 (Christine Kim)
>> 43. latest version and format for the ArchivesSpace roadmap
>> (Christine Di Bella)
>> 44. Re: Overriding/Extending the new public interface in 2.2.0
>> (Flanagan, Patrick)
>> 45. Error when saving records in 2.2.2 (Trevor Thornton)
>> 46. Re: Error when saving records in 2.2.2 (Custer, Mark)
>> 47. Re: Error when saving records in 2.2.2 (Trevor Thornton)
>> 48. Processing notes (Christie Peterson)
>> 49. Re: Processing notes (Kevin Clair)
>> 50. Re: Processing notes (Christie Peterson)
>> 51. Re: Processing notes (Kevin Clair)
>> 52. Re: Processing notes (Jordon Steele)
>> 53. Related Agents link strangeness (Kevin Clair)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Mon, 11 Dec 2017 15:18:11 +0000
>> From: Christine Kim <Christine.Kim at lyrasis.org>
>> To: Archivesspace Users Group
>> <archivesspace_users_group at lyralists.lyrasis.org>
>> Subject: Re: [Archivesspace_Users_Group] ArchivesSpace user manual
>> error page
>> Message-ID:
>> <MWHPR08MB24959E52E7B20C1D47239E65F5370 at MWHPR08MB2495.namprd
>> 08.prod.outlook.com>
>>
>> Content-Type: text/plain; charset="utf-8"
>>
>> I?m receiving the same. I will submit a support ticket for this. Thanks
>> for reporting!
>>
>> Christine Kim
>> ArchivesSpace Community Engagement Coordinator
>> christine.kim at lyrasis.org<mailto:christine.kim at lyrasis.org>
>> 800.999.8558 x4820
>> 404.592.4820
>> Skype: ckim.lyrasis
>>
>> From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
>> archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of
>> Mayo, Dave
>> Sent: Monday, December 11, 2017 7:15 AM
>> To: Archivesspace Users Group <archivesspace_users_group at lyr
>> alists.lyrasis.org>
>> Subject: Re: [Archivesspace_Users_Group] ArchivesSpace user manual error
>> page
>>
>> I can confirm that I?m getting the same thing.
>>
>> - Dave Mayo
>>
>> From: <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:
>> archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of
>> Jasmine Jones <jjones at smith.edu<mailto:jjones at smith.edu>>
>> Reply-To: Archivesspace Users Group <archivesspace_users_group at lyr
>> alists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org
>> >>
>> Date: Monday, December 11, 2017 at 10:07 AM
>> To: "archivesspace_users_group at lyralists.lyrasis.org<mailto:arch
>> ivesspace_users_group at lyralists.lyrasis.org>" <
>> archivesspace_users_group at lyralists.lyrasis.org<mailto:arch
>> ivesspace_users_group at lyralists.lyrasis.org>>
>> Subject: [Archivesspace_Users_Group] ArchivesSpace user manual error page
>>
>> Hi all:
>>
>> I'm having trouble with the ArchivesSpace user manual this morning and
>> get directed to an error page (http://docs.archivesspace.org/Default.htm<
>> https://urldefense.proofpoint.com/v2/url?u=http
>> -3A__docs.archivesspace.org_Default.htm&d=DwMFaQ&c=WO-RGve
>> fibhHBZq3fL85hQ&r=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYn
>> E&m=Uwkulyf5Wv3_OV4RVr9ZeAak82IKUfn4c2nGpZ6RRy4&s=DmQELUqxVl
>> saOSW0SYFX6TjQFAgffB6bXn_YmXU29m0&e=> and screenshot attached). Has
>> anyone else had issues?
>>
>> Thank you,
>>
>> Jasmine Jones
>>
>> [nline image 1]
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_
>> group/attachments/20171211/37c61133/attachment-0001.html>
>> -------------- next part --------------
>> A non-text attachment was scrubbed...
>> Name: image001.png
>> Type: image/png
>> Size: 278340 bytes
>> Desc: image001.png
>> URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_
>> group/attachments/20171211/37c61133/attachment-0001.png>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Mon, 11 Dec 2017 15:35:33 +0000
>> From: Christine Kim <Christine.Kim at lyrasis.org>
>> To: Archivesspace Users Group
>> <archivesspace_users_group at lyralists.lyrasis.org>
>> Subject: Re: [Archivesspace_Users_Group] ArchivesSpace user manual
>> error page
>> Message-ID:
>> <MWHPR08MB249578F47CA23D152809C1A3F5370 at MWHPR08MB2495.namprd
>> 08.prod.outlook.com>
>>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Hi all,
>>
>> The problem has been resolved.
>>
>> For the info curious ? it seems there was a problem with bad bots or
>> something hitting it this morning.
>>
>> Thanks so much for reporting, and have a great Monday!
>>
>> Best wishes,
>> Kim
>>
>> Christine Kim
>> ArchivesSpace Community Engagement Coordinator
>> christine.kim at lyrasis.org<mailto:christine.kim at lyrasis.org>
>> 800.999.8558 x4820
>> 404.592.4820
>> Skype: ckim.lyrasis
>>
>> From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
>> archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of
>> Christine Kim
>> Sent: Monday, December 11, 2017 7:18 AM
>> To: Archivesspace Users Group <archivesspace_users_group at lyr
>> alists.lyrasis.org>
>> Subject: Re: [Archivesspace_Users_Group] ArchivesSpace user manual error
>> page
>>
>> I?m receiving the same. I will submit a support ticket for this. Thanks
>> for reporting!
>>
>> Christine Kim
>> ArchivesSpace Community Engagement Coordinator
>> christine.kim at lyrasis.org<mailto:christine.kim at lyrasis.org>
>> 800.999.8558 x4820
>> 404.592.4820
>> Skype: ckim.lyrasis
>>
>> 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] On Behalf Of
>> Mayo, Dave
>> Sent: Monday, December 11, 2017 7:15 AM
>> To: Archivesspace Users Group <archivesspace_users_group at lyr
>> alists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org
>> >>
>> Subject: Re: [Archivesspace_Users_Group] ArchivesSpace user manual error
>> page
>>
>> I can confirm that I?m getting the same thing.
>>
>> - Dave Mayo
>>
>> From: <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:
>> archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of
>> Jasmine Jones <jjones at smith.edu<mailto:jjones at smith.edu>>
>> Reply-To: Archivesspace Users Group <archivesspace_users_group at lyr
>> alists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org
>> >>
>> Date: Monday, December 11, 2017 at 10:07 AM
>> To: "archivesspace_users_group at lyralists.lyrasis.org<mailto:arch
>> ivesspace_users_group at lyralists.lyrasis.org>" <
>> archivesspace_users_group at lyralists.lyrasis.org<mailto:arch
>> ivesspace_users_group at lyralists.lyrasis.org>>
>> Subject: [Archivesspace_Users_Group] ArchivesSpace user manual error page
>>
>> Hi all:
>>
>> I'm having trouble with the ArchivesSpace user manual this morning and
>> get directed to an error page (http://docs.archivesspace.org/Default.htm<
>> https://urldefense.proofpoint.com/v2/url?u=http
>> -3A__docs.archivesspace.org_Default.htm&d=DwMFaQ&c=WO-RGve
>> fibhHBZq3fL85hQ&r=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYn
>> E&m=Uwkulyf5Wv3_OV4RVr9ZeAak82IKUfn4c2nGpZ6RRy4&s=DmQELUqxVl
>> saOSW0SYFX6TjQFAgffB6bXn_YmXU29m0&e=> and screenshot attached). Has
>> anyone else had issues?
>>
>> Thank you,
>>
>> Jasmine Jones
>>
>> [nline image 1]
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_
>> group/attachments/20171211/9ccc17bf/attachment-0001.html>
>> -------------- next part --------------
>> A non-text attachment was scrubbed...
>> Name: image001.png
>> Type: image/png
>> Size: 278340 bytes
>> Desc: image001.png
>> URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_
>> group/attachments/20171211/9ccc17bf/attachment-0001.png>
>>
>> ------------------------------
>>
>> Message: 3
>> Date: Mon, 11 Dec 2017 15:58:06 +0000
>> From: "Custer, Mark" <mark.custer at yale.edu>
>> To: Archivesspace Users Group
>> <archivesspace_users_group at lyralists.lyrasis.org>
>> Subject: Re: [Archivesspace_Users_Group] Collections Browse Error in
>> Public Interface, v2.2.1
>> Message-ID:
>> <BN3PR08MB1303914D77E761964B6D5E538C370 at BN3PR08MB1303.namprd
>> 08.prod.outlook.com>
>>
>> Content-Type: text/plain; charset="windows-1252"
>>
>> 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.arc
>> hivesspace.org&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcr
>> mRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=3hrk0xcC4ZChzrpcCh0CQ_G
>> vang7BVjr4txYuvjxyM8&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 lyr
>> alists.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.at
>> lassian.net_browse_AR-2D1938&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-
>> poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=3hrk0xcC
>> 4ZChzrpcCh0CQ_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 lyr
>> alists.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:Archi
>> vesspace_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=3hrk0xcC4ZChzr
>> pcCh0CQ_Gvang7BVjr4txYuvjxyM8&s=mcku_27mMAV6rVbPS8IwL0Tx_W-
>> qI7NJvab5eSZgQuU&e=>
>>
>>
>>
>> _______________________________________________
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archi
>> vesspace_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=3hrk0xcC4ZChzr
>> pcCh0CQ_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-0001.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-0002.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-0003.jpg>
>>
>> ------------------------------
>>
>> Message: 4
>> Date: Mon, 11 Dec 2017 09:02:37 -1000
>> From: Leilani Dawson <ltdawson at hawaii.edu>
>> To: Archivesspace Users Group
>> <archivesspace_users_group at lyralists.lyrasis.org>
>> Subject: Re: [Archivesspace_Users_Group] Collections Browse Error in
>> Public Interface, v2.2.1
>> Message-ID:
>> <CADGuORE3ZJ84itYeHSmf-zduRHE-PPzPo545zj3T2F-3UiajCA at mail.gm
>> ail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Sure, here's an export of a tiny collection showing a couple of wrapped
>> diacritics in the custodial history.
>>
>> We haven't yet done any testing of the PUI--or the staff interface, for
>> that matter--with screen readers; what we know of how the ?okina (the
>> glottal stop marker, ʻ) interacts with them comes mostly from
>> Library-wide testing of WordPress and LibGuides. (And from that testing
>> we know that vowels with macrons don't normally confuse screen readers, so
>> we haven't been coding words containing them, e.g. M?noa, with aria-label
>> attributes.)
>>
>> I'm not sure what fonts we're using in WordPress and LibGuides. I'd
>> assume
>> they're pretty standard, but I'll ask.
>>
>> -Leilani.
>>
>> On Mon, Dec 11, 2017 at 5:58 AM, Custer, Mark <mark.custer at yale.edu>
>> wrote:
>>
>> 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> 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.ar
>>> chivesspace.org&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVc
>>> rmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=3hrk0xcC4ZChzrpcCh0CQ_
>>> Gvang7BVjr4txYuvjxyM8&s=ojcyFCMoM3zS9hpwYf4E7AnqB96za3sLtX6PZ20VkFM&e=>
>>> and try it out?
>>>
>>>
>>>
>>> Christine
>>>
>>>
>>>
>>> Christine Di Bella
>>>
>>> ArchivesSpace Program Manager
>>>
>>> christine.dibella at lyrasis.org
>>>
>>> 800.999.8558 x2905 <(800)%20999-8558>
>>>
>>> 678-235-2905 <(678)%20235-2905>
>>>
>>> cdibella13 (Skype)
>>>
>>>
>>>
>>> [image: ASpaceOrgHomeMedium]
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *From:* 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 lyr
>>> alists.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
>>>
>>>
>>>
>>> On Fri, Dec 8, 2017 at 3:28 AM, Christine Di Bella <
>>> 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__archiv
>>> esspace.atlassian.net_browse_AR-2D1938&d=DwMFaQ&c=cjytLXgP8
>>> ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&
>>> m=3hrk0xcC4ZChzrpcCh0CQ_Gvang7BVjr4txYuvjxyM8&s=VMpZ3H
>>> zcFod2VlOa_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
>>>
>>> 800.999.8558 x2905 <(800)%20999-8558>
>>>
>>> 678-235-2905 <(678)%20235-2905>
>>>
>>> cdibella13 (Skype)
>>>
>>>
>>>
>>> [image: 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 lyr
>>> alists.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
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Archivesspace_Users_Group mailing list
>>> 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__lyralis
>>> ts.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-
>>> 5Fgroup&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1
>>> FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=3hrk0xcC4ZChzrpcCh0CQ_
>>> Gvang7BVjr4txYuvjxyM8&s=mcku_27mMAV6rVbPS8IwL0Tx_W-qI7NJvab5eSZgQuU&e=>
>>>
>>>
>>>
>>> _______________________________________________
>>> Archivesspace_Users_Group mailing list
>>> 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__lyralis
>>> ts.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-
>>> 5Fgroup&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1
>>> FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=3hrk0xcC4ZChzrpcCh0CQ_
>>> Gvang7BVjr4txYuvjxyM8&s=mcku_27mMAV6rVbPS8IwL0Tx_W-qI7NJvab5eSZgQuU&e=>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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/20171211/2418fb0d/attachment-0001.html>
>> -------------- next part --------------
>> A non-text attachment was scrubbed...
>> Name: image005.jpg
>> Type: image/jpeg
>> Size: 6608 bytes
>> Desc: not available
>> URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_
>> group/attachments/20171211/2418fb0d/attachment-0002.jpg>
>> -------------- next part --------------
>> A non-text attachment was scrubbed...
>> Name: image006.jpg
>> Type: image/jpeg
>> Size: 6608 bytes
>> Desc: not available
>> URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_
>> group/attachments/20171211/2418fb0d/attachment-0003.jpg>
>> -------------- next part --------------
>> A non-text attachment was scrubbed...
>> Name: MANUSCRIPT.M00060_20171211_184828_UTC__ead.xml
>> Type: text/xml
>> Size: 3409 bytes
>> Desc: not available
>> URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_
>> group/attachments/20171211/2418fb0d/attachment-0001.xml>
>>
>> ------------------------------
>>
>> Message: 5
>> Date: Mon, 11 Dec 2017 20:02:37 +0000
>> From: "Maderik, Rachel A" <maderikra at vmi.edu>
>> To: "'Archivesspace_Users_Group at lyralists.lyrasis.org'"
>> <Archivesspace_Users_Group at lyralists.lyrasis.org>
>> Subject: [Archivesspace_Users_Group] truncation in PUI 2.2.1
>> Message-ID: <be6834aa52ef42b38fa0691dd7e77eca at vmi.edu>
>> Content-Type: text/plain; charset="us-ascii"
>>
>> Has anyone else had problems with search term truncation not working in
>> the PUI in v2.2.1? I can replicate the problem on the public sandbox: I
>> created a record entitled "Test Record Morrill":
>> http://public.archivesspace.org/repositories/3/resources/105, but
>> searching for "morril*" brings back 0 results (it also inserts a backslash
>> before the truncation character, which may be related to the problem):
>>
>> [cid:image003.jpg at 01D37291.14C1DCB0]
>>
>> Rachel Maderik
>> Systems and Technology Librarian
>> 501D Preston Library
>> Virginia Military Institute
>> Lexington, VA 24450
>> 540-464-7572
>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_
>> group/attachments/20171211/79470ac7/attachment-0001.html>
>> -------------- next part --------------
>> A non-text attachment was scrubbed...
>> Name: image003.jpg
>> Type: image/jpeg
>> Size: 31259 bytes
>> Desc: image003.jpg
>> URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_
>> group/attachments/20171211/79470ac7/attachment-0001.jpg>
>>
>> ------------------------------
>>
>> Message: 6
>> Date: Mon, 11 Dec 2017 20:23:28 +0000
>> From: Christine Di Bella <christine.dibella at lyrasis.org>
>> To: Archivesspace Users Group
>> <archivesspace_users_group at lyralists.lyrasis.org>
>> Subject: Re: [Archivesspace_Users_Group] truncation in PUI 2.2.1
>> Message-ID:
>> <CY1PR08MB119796FBE72BA32B04E2B9ACF1370 at CY1PR08MB1197.namprd
>> 08.prod.outlook.com>
>>
>> Content-Type: text/plain; charset="us-ascii"
>>
>> Dear Rachel,
>>
>> This was a bug inadvertently introduced in 2.2.1 that will be resolved in
>> 2.2.2, which we anticipate putting out before the holiday break. We
>> overcorrected when we put in a fix to allow searching for another character
>> that was previously causing errors.
>>
>> Apologies,
>> 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
>> Maderik, Rachel A
>> Sent: Monday, December 11, 2017 3:03 PM
>> To: 'Archivesspace_Users_Group at lyralists.lyrasis.org' <
>> Archivesspace_Users_Group at lyralists.lyrasis.org>
>> Subject: [Archivesspace_Users_Group] truncation in PUI 2.2.1
>>
>> Has anyone else had problems with search term truncation not working in
>> the PUI in v2.2.1? I can replicate the problem on the public sandbox: I
>> created a record entitled "Test Record Morrill":
>> http://public.archivesspace.org/repositories/3/resources/105, but
>> searching for "morril*" brings back 0 results (it also inserts a backslash
>> before the truncation character, which may be related to the problem):
>>
>> [cid:image002.jpg at 01D37293.FA1F2360]
>>
>> Rachel Maderik
>> Systems and Technology Librarian
>> 501D Preston Library
>> Virginia Military Institute
>> Lexington, VA 24450
>> 540-464-7572
>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_
>> group/attachments/20171211/61d7e45a/attachment-0001.html>
>> -------------- next part --------------
>> A non-text attachment was scrubbed...
>> Name: image001.jpg
>> Type: image/jpeg
>> Size: 6608 bytes
>> Desc: image001.jpg
>> URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_
>> group/attachments/20171211/61d7e45a/attachment-0002.jpg>
>> -------------- next part --------------
>> A non-text attachment was scrubbed...
>> Name: image002.jpg
>> Type: image/jpeg
>> Size: 31259 bytes
>> Desc: image002.jpg
>> URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_
>> group/attachments/20171211/61d7e45a/attachment-0003.jpg>
>>
>> ------------------------------
>>
>> Message: 7
>> Date: Tue, 12 Dec 2017 19:57:42 +0000
>> From: "Stasiulatis, Suzanne" <sustasiula at pa.gov>
>> To: Archivesspace Users Group
>> <archivesspace_users_group at lyralists.lyrasis.org>
>> Subject: [Archivesspace_Users_Group] Merging Controlled Values
>> Message-ID: <103c127cd54443c7b8e301e93f2fbb4c at ENCTCEXCH008.PA.LCL>
>> Content-Type: text/plain; charset="us-ascii"
>>
>> I remember a while back that people were having trouble merging
>> controlled values. Is this a safe feature to use yet? Has anyone used it
>> successfully in 2.2.x?
>>
>> Thanks,
>>
>> Suzanne
>>
>> Suzanne Stasiulatis | Archivist II
>> Pennsylvania Historical and Museum Commission | Pennsylvania State
>> Archives
>> 350 North Street | Harrisburg, PA 17120-0090
>> Phone: 717-787-5953
>> http://www.PAStateArchives.com
>> sustasiula at pa.gov<mailto:sustasiula at pa.gov>
>>
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_
>> group/attachments/20171212/91be7f7a/attachment-0001.html>
>>
>> ------------------------------
>>
>> Message: 8
>> Date: Tue, 12 Dec 2017 15:57:33 -0500
>> From: Brian Slenk <slenkb at hope.edu>
>> To: archivesspace_users_group at lyralists.lyrasis.org
>> Subject: [Archivesspace_Users_Group] installing wildcard SSL cert,
>> redirect http to https
>> Message-ID:
>> <CAAK7xVSGJZF==PkKyY8E_2xkoqHLQYqaBZ0EC0=tERviJ+qs4A at mail.gm
>> ail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Hello,
>>
>> I have a new installation of an archives space server. Is there a way
>> with the Apache Solr web server to add an SSL wildcard certificate, and
>> then redirect http to https for the the public interface ? I am not
>> finding documentation if this is possible.
>>
>> Brian
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_
>> group/attachments/20171212/efeb656c/attachment-0001.html>
>>
>> ------------------------------
>>
>> Message: 9
>> Date: Tue, 12 Dec 2017 15:14:01 -0600
>> From: Amanda Focke <afocke at rice.edu>
>> To: archivesspace_users_group at lyralists.lyrasis.org
>> Subject: [Archivesspace_Users_Group] digital object mapping to EAD in
>> v.2.2.1
>> Message-ID: <5A304699.8030907 at rice.edu>
>> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>>
>> Hello all -
>>
>> We have "nearline" digital objects which do not have a public URL, and
>> we describe them in ArchivesSpace.
>> They have a Title and an Identifier, but we don't use the File Version
>> field for them because there is no File URI.
>>
>> This is an example of what ArchivesSpace exports as EAD for a digital
>> object which has an Identifier of "ms0599aip_001" but has no "File
>> version / file URI".
>> <dao xlink:actuate="onRequest" *xlink:href="ms0599aip_001"*
>> xlink:show="new" xlink:title="Louis Albach Buffalo Bayou research
>> materials" xlink:type="simple">
>>
>> So it is mapping the Identifier to an xlink:href attribute, and
>> therefore makes a dead link in the EAD.
>>
>> Has anyone successfully edited the mapping to make this stop? I would
>> want the Identifier to simply show as "Identifier" and not try to be a
>> link.
>>
>> Thanks,
>> Amanda
>>
>>
> _______________________________________________
> 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/20180103/97076481/attachment.html>
More information about the Archivesspace_Users_Group
mailing list