[Archivesspace_Users_Group] ampersand issue

Novakovic, Julia jNovakovic at museumofplay.org
Tue Dec 8 15:50:25 EST 2015

Similarly, we have found that special characters like ø or quotation marks in the title field do not appear correctly, while they appear fine in other notes fields throughout imported collections. I have had to go through manually and change the characters to something that closely resembles the actual characters we want. [For example, Brøderbund to Broderbund ... Gerald A. ("Jerry") Lawson papers to Gerald A. ('Jerry') Lawson papers.] I would also appreciate clarification like Brian has outlined below.


Julia Novakovic
Associate Editor, American Journal of Play
The Strong
One Manhattan Square
Rochester, NY 14607 U.S.A.
Tel 585-410-6307
Fax 585-423-1886
jnovakovic at museumofplay.org<mailto:jnovakovic at museumofplay.org>

The Strong is home to:
International Center for the History of Electronic Games | National Toy Hall of Fame | World Video Game Hall of Fame
Brian Sutton-Smith Library and Archives of Play | Woodbury School | American Journal of Play

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Brian Hoffman
Sent: Tuesday, December 08, 2015 3:23 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] ampersand issue

Currently unittitle gets imported as-is to the title field of resources and components. So when you import the example you get two records whose title field is "AmpTest & A"

We could change this so that you get "AmpTest & A" instead, but what happens when a user imports a unittitle like: "AmpTest & <emph>A<emph>"? We can't unescape the & entity without leaving the XML zone, so what happens to the <emph> tag and content?

To me this is part of a larger still unresolved question of what exactly the data type of ASpace text field is supposed to be. Is it XML? If so, I think we should be assuming that archivists are managing XML data here, and it should be '&'. If it isn't, and yet we still want to support inline styling, we need to come up with a set of rules for what kind of inline pseudo-markup is allowed and for how it maps to EAD on export.


On Dec 8, 2015, at 1:50 PM, Chris Fitzpatrick <Chris.Fitzpatrick at lyrasis.org<mailto:Chris.Fitzpatrick at lyrasis.org>> wrote:

I think I understand..
So, the title is in the imported XML is
<unittitle>AmpTest & A</unittitle>
but you want the EAD converter to switch this to be "AmpTest & A"?
If that's the case, it seems like a pretty easy thing to add to the converter...


Chris Fitzpatrick | Developer, ArchivesSpace
Skype: chrisfitzpat  | Phone: 918.236.6048

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org><archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Galligan, Patrick <PGalligan at rockarch.org<mailto:PGalligan at rockarch.org>>
Sent: Tuesday, December 8, 2015 6:58 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] ampersand issue


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

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 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)

EAD Import - Problem with Escaped Characters · Issue #332 · archivesspace/archivesspace
It looks like there is an issue with certain escaped characters (& and <) getting dropped in at least and tags. What we suspect is happening is that escaped characters are b...
Read more...<https://github.com/archivesspace/archivesspace/issues/332>

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


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:


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


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 Francis
Archivist for Collection Management
Special Collections Library
Penn State University
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20151208/9e775421/attachment.html>

More information about the Archivesspace_Users_Group mailing list