Bug #7587

Unescaped ampersand in creator name causes description export errors

Added by Dan Gillean over 7 years ago. Updated about 7 years ago.

Status:VerifiedStart date:11/18/2014
Priority:MediumDue date:
Assignee:David Juhasz% Done:


Target version:Release 2.2.0
Google Code Legacy ID: Tested version:2.1, 2.2
Sponsored:No Requires documentation:No


To reproduce

  • Create a new description, or find an existing one
  • Modify the creator name (or any other associated actor) to include an ampersand
  • Attempt to export or expose record via OAI-PMH
Resulting error
  • EAD export results in whitescreen
  • DC export and OAI query returns an XML Parsing error (not well formed), and chokes on the ampersand

Expected result
Ampersands are consistently escaped throughout. The exports perform normally regardless of ampersands entered during data creation.

NOTE: We have been resolving this in a spotty way, on a case by case basis - see for example #5588, #3809, #6949, #7171, etc. It would be great if we could find a solution that would consistently escape the whole record 1x before export, instead of on a field by field basis as we encounter problems.


#1 Updated by Dan Gillean about 7 years ago

  • Status changed from New to Verified
  • Tested version 2.2 added

This has been resolved thanks to the escaping introduced in 2.2 via #7647. Tested in AtoM 2.2 qa branch March 19, 2015.

Also available in: Atom PDF