[Koha-bugs] [Bug 5738] Display the URI in 856u as an Image

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5738

Doug Dearden <dearden at sarsf.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Attachment #3127|0                           |1
        is obsolete|                            |
   Attachment #3136|0                           |1
        is obsolete|                            |

--- Comment #8 from Doug Dearden <dearden at sarsf.org> 2011-02-15 17:48:05 UTC ---
Created attachment 3158
  --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=3158
Coding work done ready for QA testing

I have this working with  the MARC21 display files for results and details on
the OPAC.  I also have it working for the Unimarc detail file on the OPAC.  I
was unable to get it working for the Unimarc results pages on the OPAC, as
there is another conditional test around the 856u field looking for a ‘0’ in
ind2.  It is also labeling this area ‘Availability’ instead of ‘Online
Resources’.  I’m not sure what is going on there, but didn’t want to mess up
something by changing that around so left well enough alone.  In addition I
have a new preference for the staff client – and renamed the OPAC preference to
distinguish the two.  I revised the pref and sql files accordingly.  Per the
current doc the xslt display file for Results is not working in the staff
client, but I got the respective MARC21 and Unimarc intranet detail files
working.  As far as I can tell this is now ready for QA testing and hopefully
inclusion in a future release.  I will post the file up to the bug entry. 

Still to be done – text to be included in the documentation, and a script that
will populate the 856q field with a MIME extension based on the URI in the 856u
field.

-- 
Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.