I can't speak to doing this specifically on Drupal, but in terms of
measuring clicks I would simplify. We use google analytics and at each
place I've been I've just set up some custom events analytics code to
record specific types of clicks. Here at the TMC Library we're now
recording database clicks with that mechanism. In terms of a database list,
I've gone a few routes. When I was at the University of New Mexico, where I
had no access to backend databases for most of my tenure, I built an A-Z
list in XML that plugged into our junky CMS (Cascade Server). It worked
quite well. However, I'm more interested in extracting things like that
from a central data node, like serial solutions or intota. Here at TMC
we're using intota, and I've built a php script to extract the contents of
one of the reports and populate into a MySQL database for capturing that
information. At my last library we used serial solutions, and, while I
didn't plug that into the website, I did have to build a script that could
parse a serial solutions csv file into a google books xml format so that Ex
Libris' rather unfortunate Primo tool could make sense of it for discovery
purposes. That file, of course, covered individual publications as well as
other linked objects. It's available on my github site.
*Jason Bengtson, MLIS, MA*
*Houston Academy of MedicineThe Texas Medical Center Library*
1133 John Freeman Blvd
Houston, TX 77030
On Wed, May 27, 2015 at 8:01 AM, Ken Irwin <[log in to unmask]> wrote:
> Hi folks,
> Thanks to all who responded a few weeks ago to my inquiry about updating
> the code on my library's website. Many folks suggested moving to a CMS, and
> I'm starting to look into that possibility, and particularly Drupal.
> In doing so, I'm hoping not to re-invent the wheel, and I'm hoping that
> maybe someone has already designed a basic infrastructure to replace the
> backbone of our current website, namely.
> Under our current arrangement we have an interlocking set of databases
> that performs some basic library functions:
> There's a database table that lists all of the databases we subscribe to.
> That database feeds a user interface that:
> * lists databases
> * counts click-thrus
> * routes traffic to our proxy server when appropriate
> * can list databases by subject area (defined in a table of
> subject associations)
> There's also a back-end UI to create subject/database associations,
> display click-thru stats, generate EZproxy config files based on the table
> of library databases.
> Does anyone know of a freely-available set of modules/pages/etc that's
> already designed to do this sort of thing? In my imagination, lots of
> libraries would want to basically this same thing, customized to their own
> particularly needs and maybe we wouldn't each have to start from scratch.
> Any advice?