Bug 5843 - semicolon preceded by space in 490 subfield a (Series statement) causes search to time out
Summary: semicolon preceded by space in 490 subfield a (Series statement) causes searc...
Status: CLOSED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: rel_3_2
Hardware: All All
: P5 - low critical
Assignee: Galen Charlton
QA Contact: Bugs List
URL: http://catalogue.efdss.org
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-08 17:14 UTC by Elaine Bradtke
Modified: 2019-06-27 09:24 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Elaine Bradtke 2011-03-08 17:14:44 UTC
In 3.2.5, 
This seems to be a problem with newly edited records and records already in the system.
If there is a series statement in subfield a, and a volume number in subfield v the correct punctuation for subfield a is to end with a space semicolon space
http://openlib.org/home/krichel/courses/lis512/aacr2/6.html

However, if subfield a is punctuated as above, it causes a fault in the search, in both the OPAC and the staff interface.  The search times out.

To test it out on our catalogue (in the URL field above) search for 'school songs'
You'll get a slew of items that are in the Novello's school songs series.  Clicking on the series in the list on the left side of the page works fine.  But if you go to an item that has both the series and the number (Folksongs from Somerset, Set II for example) and click on the series link there (in the normal view), it doesn't work.
Chrome eventually returns a message that the page is unresponsive.
I have deleted the spaces around the semicolon in a few records (the series County folklore) and the series link in the normal view works fine.
Comment 1 Jared Camins-Esakov 2012-02-19 15:40:34 UTC
This has been fixed in Master.