Evergreen

Ampersand in Call Number causes not well-formed error

Bug #1021427 reported by Jason Stephenson
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Evergreen
Confirmed
Undecided
Unassigned

Bug Description

Evergreen version: master/2.2 from 2012-04-08
OpenSRF version: maser/2.something from 2012-04-08 (maybe more recent)
PG version 9.1
Server OS: Ubuntu 12.04

When moving a volume from 1 bib record to another, our cataloger gets a not well-formed error from server/util/fancy_prompt.xul if the call number contains an ampersand (&). This would appear to point to the call number not being entityized or escaped when passed to the xml in the client.

Jason Stephenson (jstephenson)
Changed in evergreen:
status: New → Triaged
Michele Morgan (mmorgan)
Changed in evergreen:
status: Triaged → Confirmed
Revision history for this message
Michele Morgan (mmorgan) wrote :

I just ran into this issue in 2.9, so it's still a problem in current releases. I was unable to test to see if it is still an issue in the web client.

Revision history for this message
Rogan Hamby (rogan-hamby) wrote :

I wasn't able to duplicate this in the web client in 3.2.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.