Bug 18599

Summary: "Record URL" link href is broken for multiple 856$u links in MARC record
Product: Koha Reporter: Eric Phetteplace <ephetteplace>
Component: Course reservesAssignee: Bugs List <koha-bugs>
Status: RESOLVED DUPLICATE QA Contact: Testopia <testopia>
Severity: normal    
Priority: P5 - low CC: amber, csq, jonathan.druart, mustaqeemabd
Version: Main   
Hardware: All   
OS: All   
Change sponsored?: --- Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:

Description Eric Phetteplace 2017-05-12 21:46:30 UTC
If you place a course reserve on a bib where the MARC record contains multiple 856 $u URLs, the resulting "Record URL" link in the Link column on both the staff and public catalogs (i.e. /cgi-bin/koha/course_reserves/course-details.pl?course_id=XXX  and /cgi-bin/koha/opac-course-details.pl?course_id=XXX) is broken. It looks as if the URL is constructed by concatenating both 856 URLs and separating them with a vertical bar character surrounded by spaces, " | ".

Testing Plan:

- create a bib record with at least two MARC 856 fields with valid URLs in their $u subfields
- add an item to the bib record
- enable course reserves (UseCourseReserves)
- create a course
- add an item from the aforementioned record on course reserve
- visit its course details page
- note that the "Record URL" link in the Link column is broken

I'm not sure if the problem lies within Course Reserves itself; I investigated briefly and I see "cr.item.url" is the field utilized by the template. I don't need a "url" field in course_reserves or related database tables, I'm guessing it's a field on the connected item record.

I'm seeing this on 16.11 but I haven't tested master.
Comment 1 mustaqeem 2017-09-07 16:53:14 UTC
Also getting this error for Koha 17.05..work perfectly fine if there is only one 856 field, but error for multiple 856..
Comment 2 Charles Quain 2019-10-23 13:23:11 UTC
Is also in 18.11.06
Comment 3 Katrin Fischer 2023-09-15 20:54:24 UTC

*** This bug has been marked as a duplicate of bug 20502 ***