Bug #5984

Parsing error in DC export when institution name contains an unencoded ampersand

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

Status:VerifiedStart date:11/16/2013
Priority:MediumDue date:
Assignee:Dan Gillean% Done:

0%

Category:Import/ExportEstimated time:0.25 hour
Target version:Release 2.1.0
Google Code Legacy ID: Tested version:2.0.0, 2.0.1
Sponsored:No Requires documentation:

Description

To reproduce:
- edit an ISDIAH record for which there are related descriptions, add an ampersand to the institution name
e.g. authorized form of name: University Archives & Special Collections
- follow the link for DC XML export
Result: XML Parsing Error: not well-formed

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

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

An equivalent issue with title was fixed in #3809; and #5588 re OAI is likely related.


Related issues

Related to Access to Memory (AtoM) - Bug #3809: Parsing error in MODS and DC when title contains an amper... Verified
Related to Access to Memory (AtoM) - Bug #5588: Unencoded ampersand in ISDIAH record (authorized form of ... Verified 09/14/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 Dan Gillean over 8 years ago

  • Category set to Import/Export
  • Assignee set to Jesús García Crespo
  • Target version set to Release 2.1.0

Reproduced in 2.x

#2 Updated by Tim Hutchinson over 8 years ago

This seems to be a more general issue. I haven't tested further, but I got the same parsing error for an EAD record where the note element has an ampersand.

#3 Updated by Dan Gillean over 8 years ago

Thanks Tim. It seems like the best solution would be to add some logic to the export scripts that replaces any unacceptable characters with the hard-code/ASCII code prior to generating the export.

#4 Updated by Tim Hutchinson over 8 years ago

It looks like something must be in place for certain fields already - e.g. as I noted above, it's not happening for title or scope and content.

#5 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
  • Estimated time set to 0.25

#6 Updated by Dan Gillean over 7 years ago

  • Status changed from QA/Review to Verified
  • Tested version 2.0.0, 2.0.1 added

Also available in: Atom PDF