>>> [2] opac-main.pl displays the cloud if cloud file is >>> present. >>> >> This seems like a very odd way to do this, given the way we handle >> similar functions. Why not create a separate page for the tag cloud? >> Since some libraries use the opacmainuserblock preference to define >> the content of opac-main.pl, having the tag cloud here may make it >> unusable for those libraries. >> >> -- Owen > Maybe it could be juste a stand alone either XML or HTML div that would > be send by function and reuse here and there... Whereever user like.
Since it is a static html file, not the result of a dynamic query to the DB, it's just a matter of adding a directive to any template: <!-- TMPL_INCLUDE NAME="../../../cloud.html" --> In my opinion, it works really well on the opac main page in a way that it is an enter point to the catalog as whole. You get an instant picture of catalog content and from that point you enter in the collection. I agree that it may not be the best solution for every library but nothing prevent controlling subjects cloud display on other pages with Syspref. It could be very easily extended to generated other Zebra index clouds: Authors, Site, Libraries, Acquisition date, Specific subjects, etc. And when Zebra will be able to do index scan sorted by term weight, it even will be possible to do it dynamically! -- Frédéric DEMIANS http://www.tamil.fr/u/fdemians.html _______________________________________________ Koha-patches mailing list [email protected] http://lists.koha.org/mailman/listinfo/koha-patches
