Bug #5588

Unencoded ampersand in ISDIAH record (authorized form of name) causes OAI error

Added by Tim Hutchinson over 8 years ago. Updated over 7 years ago.

Status:VerifiedStart date:09/14/2013
Priority:MediumDue date:
Assignee:Dan Gillean% Done:

0%

Category:OAI-PMH
Target version:Release 2.1.0
Google Code Legacy ID: Tested version:
Sponsored:No Requires documentation:

Description

To replicate:
- edit an ISDIAH record for which there are related descriptions, add an unencoded ampersand (& not &)
e.g. authorized form of name: University Archives & Special Collections
- Send an OAI command, e.g. http://atom-server/index.php/;oai?verb=ListRecords&metadataPrefix=oai_dc

Result: XML Parsing error

Hard-coding the ampersand (&) makes the error go away.

This is not an issue with title or scope and content in the descriptive record.


Related issues

Related to Access to Memory (AtoM) - Bug #5984: Parsing error in DC export when institution name contains... Verified 11/16/2013
Related to Access to Memory (AtoM) - Bug #7171: Extent tags in EAD with ampersands in them crash XML export Verified 08/29/2014
Related to Access to Memory (AtoM) - Bug #6949: Ampersand in identifier breaks EAD export Verified 07/08/2014

History

#1 Updated by Tim Hutchinson over 8 years ago

Not surprisingly, the form correctly processed my encoded ampersand - what I meant above is & amp; without the space (workaround, not solution!)

#2 Updated by Dan Gillean over 8 years ago

  • Category set to OAI-PMH
  • Assignee set to Jesús García Crespo
  • Target version set to Release 2.1.0

#3 Updated by Mike Gale over 7 years ago

  • Status changed from New to QA/Review
  • Assignee changed from Jesús García Crespo to Dan Gillean

#4 Updated by Dan Gillean over 7 years ago

  • Status changed from QA/Review to Verified

Also available in: Atom PDF