A customer has reported that the automatic linking of series authority records to series fields in the bib record (440 and 830) fails due to the space added before the semicolon when series numbering is present. Prescribed punctuation for series fields requires a space before the semicolon so this space should be ignored. Example: 830 Series Added Entry – Uniform title Alcuin Club collections links to authority record Alcuin club collections ; does not link to authority record Background: ISBD punctuation, which is used in the most recent cataloguing standard (RDA) and in the preceding standard (AACR2), requires a space semicolon at the end of a series statement if it is followed by series numbering (cf. http://www.ifla.org/files/assets/cataloguing/isbd/isbd-cons_2007-en.pdf , RDA 0.3.3 and AACR2 1.6 A1).
ByWater is seeing this happen at a partner site. To add to this description, the Opac search is filing but the Staff search is not. The space and semicolons are in the 490 and 800 fields of three bibliographic records, a trilogy. The Opac series search url comes out as </cgi-bin/koha/opac-search.pl?q=se,phr:"Example%20title%20;"&q=au:"Smith,%20N.%20K."> and the staff series search url comes out as </cgi-bin/koha/catalogue/search.pl?q=se,phr:"Example%20title%20;"&q=au:"Smith,%20N.%20K."> If the space and semicolon is standard, as Lucy points out, this should be a bug, not an enhancement.
Bug 14716 might help with the problem, but haven't tested!
Thanks Katrin! There is also Bug 16804 - Searching can be broken by search terms containing semicolons in XSLT, which may be helped by bug 14716. For what it is worth I don't think this is a duplicate of 16804 exactly.
As was said above, standard cataloging rules call for a space and a semicolon to precede a subfield "v" in an 830 tag. When the 830 tag does not link correctly, links in our OPAC do not work correctly, which equates to poor customer service for our patrons. My library would be delighted to see this bug resolved so we can maintain both good customer service and industry standard cataloging practices, rather than being forced to sacrifice one for the other. Thank you!
I think that this has been fixed: I catalogued a record with: 830 _ 0 ‡aAdvanced language series ;‡v955 The link still contains the ;, but search works correctly. I believe this is due to the correct handling of url-encoding in the XSLT now. I've also used the Advanced editor to link the entry to an authority record which appeared to work well: ‡aAdvanced language series ;‡v333‡9612 Please note: Koha might not display the ; - but there is bug 15436 for that. Please reopen if I missed something!