Bug #8426

Physical description field does not include character escaping

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

Status:VerifiedStart date:05/11/2015
Priority:MediumDue date:
Assignee:Mike Gale% Done:


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


We have been adding this to fields on an ad hoc basis as needed (such as title, scope and content), because unencoded ampersands and other special characters will cause problems in the XML import and export - which in turn affects OAI exposure, roundtripping, finding aid generation and more.

The phsysical description field often includes data where this is an issue - such as describing photos as "b&w" for example.

We should escape these special characters.


#1 Updated by Mike Gale about 7 years ago

  • Status changed from New to QA/Review
  • Assignee changed from Mike Gale to Dan Gillean

#2 Updated by Dan Gillean about 7 years ago

  • Status changed from QA/Review to Verified
  • Assignee changed from Dan Gillean to Mike Gale



Also available in: Atom PDF