[Archivesspace_Users_Group] ampersand issue

[Galligan, Patrick]

Christine,

I’d like to circle back to this issue.

I was doing some testing with the merged pull request, and while it no longer just deletes the escaped character, it actually adds “&” to the display of the title.

I’ve also noticed that while it corrects the unittitle on the highest level, it doesn’t seem to work with series levels later.

Attached is a screenshot and the EAD that I imported into AS. Has anyone else run into this issue? Has anyone found a viable solution so far?

Patrick Galligan
Rockefeller Archive Center
Assistant Digital Archivist
914-366-6386

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella
Sent: Thursday, December 03, 2015 10:10 AM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] FW: ampersand issue

Forwarded for Matt Francis.

(I believe there has been some work on this issue very recently by the University of Michigan folks. See this thread on Github - https://github.com/archivesspace/archivesspace/issues/332 - and the associated merged pull request. – Christine)

From: MATTHEW R FRANCIS [mailto:mrf22 at psu.edu]
Sent: Wednesday, December 2, 2015 3:20 PM
To: archivesspace users group-bounces <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>>
Subject: ampersand issue

All,

We are currently in ASpace v1.4.1 and recently observed an issue for when we try to import EAD files that contain ampersands in the XML, and are now curious if others have experienced this and/or if anyone knows a fix for the issue.

Currently when import files with an ampersand coded as "&" as seen in:

[cid:image001.png at 01D131B7.F229FFF0]


The "&" does not appear to be rendered in ASpace in any form, as seen in:


[cid:image002.png at 01D131B7.F229FFF0]

In looking through JIRA it does not appear that this specific issue/behavior has been reported, but before reporting it as a bug we were hoping to determine if this was a universal issue, or perhaps just local.

Thanks for the help and feedback.

-Matt

Matt Francis
Archivist for Collection Management
Special Collections Library
Penn State University
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20151208/f9b13c46/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 3882 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20151208/f9b13c46/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 15035 bytes
Desc: image002.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20151208/f9b13c46/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Ampersand.JPG
Type: image/jpeg
Size: 172633 bytes
Desc: Ampersand.JPG
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20151208/f9b13c46/attachment.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Ampersand_test.xml
Type: application/xml
Size: 1535 bytes
Desc: Ampersand_test.xml
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20151208/f9b13c46/attachment.xml>