Multiple URI's will show when using opac.located_uri.act_as_copy flag

Bug #1582720 reported by Steve Callender on 2016-05-17
This bug affects 6 people
Affects Status Importance Assigned to Milestone

Bug Description

When enabling the global flag opac.located_uri.act_as_copy (When enabled, Located URIs will provide visiblity behavior identical to copies.)

It will list out the URI's per branch in the TPAC.

For example, having a single 856 tag with indicator 1 = "4" and indicator 2 = "0", a single u subfield (URL), a single y subfield (Label) and multiple 9 subfields (for each branch) will cause the TPAC to display the same exact link and label for however many 9 tags there are.

The args are setup for the URI's in Open-ILS/src/templates/opac/parts/misc_util.tt2 and the screen is Open-ILS/src/templates/opac/parts/record/summary.tt2

I believe it would be a cleaner display to display the URI links only once if they are identical then displaying the same exact url and label multiple times in a row.


Kathy Lussier (klussier) wrote :

I don't know what the original intended behavior was, but I agree that if there is just one label associated with the Located URI, then the URL should only display once per record.

Changed in evergreen:
status: New → Confirmed
importance: Undecided → Medium
Rogan Hamby (rogan-hamby) wrote :

I was looking at this one today during the Hack-A-Way some. We can certainly go over the name value pairs and prevent duplicates from going in when they're processed in misc_util but I'm increasingly of the thought we shouldn't. There's a question about to the extent that code should compensate for bad data and if the label, note and href are all duplicates I think that's bad data and something that catalogers should be alerted to to clean out, not cleaned up by the system.

Kathy Lussier (klussier) wrote :

I don't know that we're talking about the same thing here. As I understood Steve's original report, he is talking about one 856 field with one URL, one label, and one note. The 856 just happens to have multiple subfield 9s, which is something that the documentation says we should be able to do.
For example:

856 4 0 ‡u ‡yLinks to web site ‡9BR1 ‡9BR2 ‡9BR3

Rogan, it sounds like you're talking about multiple 856 fields with duplicate URLS, labels, etc.

Elaine Hardy (ehardy) on 2019-03-07
tags: added: cataloging displayfields tpac
tags: added: opac
removed: tpac
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers