If you have multiple 260 fields in a record, they are all run together in the search results, so that there is no space between the 260$c in the first field and the 260$a in the second field. They display properly in the details display, with spacing and a semicolon between them.
Created attachment 9044 [details] [review] Bug 7845: Multiple 260s don't display properly in search results Corrects display for multiple 260 fields in intranet and OPAC. In intranet the order of fields was wrong on the detail page. In OPAC and intranet punctuation for multiple 260 fields in the result list was not displaying properly. Example after correction: Publisher: Jena : Elsevier, 1907 ; Stuttgart : Franckh, 1907-1992 ; Jena : Urban & Fischer, 1993-2003
Created attachment 9133 [details] [review] Bug 7845: Multiple 260s don't display properly in search results Corrects display for multiple 260 fields in intranet and OPAC. In intranet the order of fields was wrong on the detail page. In OPAC and intranet punctuation for multiple 260 fields in the result list was not displaying properly. Example after correction: Publisher: Jena : Elsevier, 1907 ; Stuttgart : Franckh, 1907-1992 ; Jena : Urban & Fischer, 1993-2003 Signed-off-by: Chris Cormack <chrisc@catalyst.net.nz>
XSLT only change to 260 processing. Looks to separate out subfields a and b from multiple subfield processing. Effects MARC21 only. Marking as Passed QA.
I haven't tested this patch myself, but: * looks OK * reliable author & signoff so => patch pushed
This will be in 3.6.5.