Personal tools
Namespaces
Variants
Actions

Ook Nog

From DevXS 2011
Jump to: navigation, search

Contents

Team

  • Andrew Collins, University of Liverpool
  • Thomas Gorry, University of Liverpool
  • Jude-Thaddeus Ojiaku, University of Liverpool
  • Arnoud Pastink, University of Liverpool / University of Utrecht

Description

Ook Nog is an interface for the data provided by openurl allowing you to search all of the data for any term and find search terms within their archive. By selecting any prior search term, you can then browse all search terms that were also performed by that user(s) within a small time period.

All publications/searches are nodes. A node shares an edge with another node if a user has searched both nodes. We try to increase the chance of relevance by only showing neighbours of a node that were formed +- 90 days (a semester!).

Despite no further tests of relevancy, the searches/publications found can be surprisingly similar (or amusing).

Competitions

  • Competitions entering: Library activity data, DevCSI, Public Platforms,OKFN, Variation on “ 6 degrees of separation
  • Initial Idea: Graph representation of library data, 6 degrees of seperation.

Demo

http://www.csc.liv.ac.uk/~tgorry/OokNog/

We did not blatantly plagarise any search engine's theme in anyway shape or form.

Instructions

Enter a search term (E.g. "chess"), follow any of the articles and a list of all similar articles will be listed. You can continue following further related articles of those related articles.

Warning: There appears to be a high chance you will eventually find articles related to breasts and sex. Apparently all in the good name of science*. (*Alright, searching for "muff" may be the exception...)

Source Code

Database schema:

C# tool to parse the big ugly dataset from openURL and produces a 700 MB of SQL insert statements.

<Here we would have that 700MB file but we suspect if we did directly link to it our departments technicians may shout at us (again). So sadly you will have to generate it yourself>

Simply takes the output of the C# parser and dumps it into the database.

The main search page:

The search terms/ related links

The config file:

The fancy CSS and images:


We also make the assumption you use ADOdb, if you don't... why not? Go grab the library here: http://sourceforge.net/projects/adodb/files/

TO DO

  • Pagination could be useful...
  • Cleaning the data with a fine toothed comb. We spent several hours and we would like to say we were successful, just like the NHS IT project. :(

Apologies

Sorry the code structure is bizarre. We developed this across 3 user accounts to do some parts in parallel.

Also sorry for the mix of languages. Though it could be worse, we nearly used R.