Use cover image/blurb URL from field 856

Bug #1133464 reported by Pasi Kallinen
This bug affects 7 people
Affects Status Importance Assigned to Milestone

Bug Description

Wishlist item:

MARC 21 uses field 856 for electronic "links", where you can have URLs for example covers images and/or blurbs.

Most of the libraries in Finland get the cover image and blurb data URLs via and the fields (after conversion from our old system to EG) look like this:

856 4 2. ‡u
856 4 2. ‡u ‡qTEXT ‡zKuvaus

The URL "key" parameter has nothing to do with ISBN or anything else in the MARC.

It should be possible to configure EG so that 856‡u that matches a (configurable) regexp, or if 856‡z matches some text, or if 856‡q is "IMAGE", the URL is used as the cover image.
Or grabbing the blurb from the url, if some other rules are matched.

From the discussion on IRC:
< jeff> paxed: there are two major approaches that come to mind: 1) seek the url in the template tookit bits and populate/use it if found. you will encounter mixed content warnings/errors when logged in unless you proxy the image or it is served by an https url. 2) write an added content handler that extracts the url from the marc. you will need the added content by record id branch as a starter.
[18:41] < jeff> paxed: as i mentioned, i'm interested in this and would probably work on option 2 myself. it has applicability for other bib sources, and benefits from some caching which would skip the need to parse the bib on every cover image display.

Ben Shum (bshum)
Changed in evergreen:
status: New → Triaged
Revision history for this message
Pasi Kallinen (paxed) wrote :

I wonder if this could tie into bug 1065378

Revision history for this message
Pasi Kallinen (paxed) wrote :

I've got branch at user/paxed/ac-image-url-in-marc - it adds a new Added Content handler ImageURLinMARC. Configuration in opensrf.xml allows defining which MARC field it looks for, and a regex the value of the field must match.

Pasi Kallinen (paxed)
tags: added: pullrequest
Revision history for this message
Galen Charlton (gmc) wrote :

I think the general idea is a good one and worth reviving. Rather than relying on fetching and parsing MARC though, I think it might be faster to fetch asset.uri rows related to the record and check patterns against asset.uri.label and asset.uri.use_restriction.

As a side note, looks like records from iVerse Media include cover images.

856 40 ‡zCover Image ‡u

tags: removed: tpac
tags: added: needsreleasenote
Revision history for this message
Terran McCanna (tmccanna) wrote :

Removing pullrequest for the time being since the proposed patch is now 7 years old and there has been an alternate approach suggested. At the very least, it would need to be rebased against current master before testing.

tags: added: needsdiscussion
removed: pullrequest
tags: added: cat-marc
removed: wishlist
tags: added: needsrebase
removed: needsreleasenote
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers