The 508 field in OPAC and staff detail pages appears without a separator between the 508 entries.
Hi Winona - should there be a patch attached? I am resetting the status to NEW until there is a patch.
Sorry, Using git bz, and something is going wrong. Troubleshooting. Will have something up by the end of the day. -Winona
Thx! If it won't work at all: 'git format-patch' will create a file you can attach.
Created attachment 46256 [details] [review] Corrects repeated 508 formatting This patch adds a separator for multiple 508 fields to the XSLT display in the staff and OPAC detail view. Separator is wrapped in span with class=‘separator’ for easy manipulation via css. To test: * Search the OPAC * Click the title with multiple 508 fields * Make sure the fields display properly * Repeat for a few more titles * Repeat in the Staff Client
Created attachment 46302 [details] [review] Bug 15444 - MARC21: Repeated 508 not correctly formatted (missing separator) This patch adds a separator for multiple 508 fields to the XSLT display in the staff and OPAC detail view. Separator is wrapped in span with class=‘separator’ for easy manipulation via css. To test: * Search the OPAC * Click the title with multiple 508 fields * Make sure the fields display properly * Repeat for a few more titles * Repeat in the Staff Client Signed-off-by: Mark Tompsett <mtompset@hotmail.com>
Created attachment 46363 [details] [review] [PASSED QA] Bug 15444 - MARC21: Repeated 508 not correctly formatted (missing separator) This patch adds a separator for multiple 508 fields to the XSLT display in the staff and OPAC detail view. Separator is wrapped in span with class=‘separator’ for easy manipulation via css. To test: * Search the OPAC * Click the title with multiple 508 fields * Make sure the fields display properly * Repeat for a few more titles * Repeat in the Staff Client Signed-off-by: Mark Tompsett <mtompset@hotmail.com> Signed-off-by: Katrin Fischer <katrin.fischer.83@web.de>
Pushed to Master - Should be in the May 2016 Release - Thanks!
Patch pushed to 3.22.x, will be in 3.22.3
This patch has been pushed to 3.20.x, will be in 3.20.9.