Syndetics Does Not Return Jacket Image for Item Record with UPC and no ISBN

Bug #1463469 reported by John Yorio
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Evergreen
Undecided
Unassigned

Bug Description

Evergreen 2.7.2

This sounds similar to https://bugs.launchpad.net/evergreen/+bug/1318029

Although an item is cataloged correctly with a UPC in the 024 field(first indicator = 1), and no ISBN in 020 or ISSN in 022, Evergreen passes the UPC as an ISBN to Syndetics to retrieve the jacket image.

The result is that there is no match for the jacket on the item record, although it does appear in the search results.

Manually creating a link to Syndetics and passing the value explicitly as a UPC returns the correct image. [syntax for medium sized jacket image: http://www.syndetics.com/index.aspx?isbn=''/mc.gif/&upc=(UPC CODE)&issn=''&client=(CLIENT_CODE)&type=rw12 ]

Revision history for this message
Ben Shum (bshum) wrote :

I can't confirm this bug on our production system (which is 2.8ish). So far all our tests in retrieving bibs with only UPC 024 and no ISBN 020 or ISSN 022 have yielded no issues.

In my logs, I can see our system passing the UPC code in the correct part of the URL retrieve to Syndetics.

For fun, a terrible SQL I crafted to find bibs that fit the pattern:

SELECT DISTINCT record FROM metabib.real_full_rec WHERE tag = '024' AND ind1 = '1' AND record NOT IN (SELECT DISTINCT record FROM metabib.real_full_rec WHERE tag = '020' OR tag = '022') LIMIT 10;

Marking bug incomplete pending further information or confirmation of issue on other systems. Maybe it's a 2.7 specific bug (though to my knowledge, nothing changed between 2.7 and 2.8 in this area).

Changed in evergreen:
status: New → Incomplete
Revision history for this message
Ben Shum (bshum) wrote :
tags: added: addedcontent syndetics
Revision history for this message
Chris Owens (owensch) wrote :

This is something we have been dealing with since we started on Evergreen a couple of years ago. Records with a UPC in the 024 field did not retrieve images from Syndetics unless we added a zero in front of the UPC. We have the same item from your first sample in our catalog and the image only displays with that added zero. If I take away the zero, no image.

https://blanchester.cool-cat.org/eg/opac/record/947818

Also, once we upgraded to 2.7 last fall, the images began displaying on the results page without the additional zero, but they still do not display on the item record page.

Revision history for this message
Ben Shum (bshum) wrote :

Hmm, when you say that it works in results, but not record view, that makes me question whether there are local template customizations in your TPAC causing problems...

The extra 0 sounds weird too...

Revision history for this message
Ben Shum (bshum) wrote :

Yes, inspecting your catalog Chris, I can see that you're using the original method for the record details page like: <a href="/opac/extras/ac/jacket/large/0024543971757"><img alt="Image of item" id="rdetail_image" src="/opac/extras/ac/jacket/medium/0024543971757"></a>

Which is wrong. During 2.7's development, a new feature was added for Added Content by Record ID (see bug 1065378).

By way of comparison, our Penguins record page html renders like <a href="/opac/extras/ac/jacket/large/r/3177205"><img alt="Image of item" id="rdetail_image" src="/opac/extras/ac/jacket/medium/r/3177205"></a>

Where the r/bib_id instead of the older method.

Based on that, I would say that you have a rogue TPAC template for record details that's still processing the page the old way, which is expecting ISBN only, not UPC. And that it happens that there's an ISBN with the extra 0 padded in front of the UPC?

Either way, if you guys are the primary reporter of this bug, I'm going to consider this is a support issue within your consortium and something to be fixed and not a bug with Evergreen/Syndetics/UPC.

Changed in evergreen:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers