[okfn-help] Xapian in Milton

Rufus Pollock rufus.pollock at okfn.org
Sat Jul 19 19:12:32 BST 2008


On 17/07/08 20:41, Iain Emsley wrote:
> Dear all,
> 
> I've finally uploaded the scripts that I've been working on for Xapian.
> 
> I have included a textindex.py which does a basic index job (paths will 
> need to be altered - can I make a suggestion that the shksprdata file is 

Looks great. I've started work on integrating this into shakespeare 
refactoring to make it is as general as possible as I go.

http://knowledgeforge.net/shakespeare/trac/changeset/169

> renamed data which allows for extensibility with other authors?). 

I think the way to go here is have a common core (what is currently the 
shakespeare package) with relevent data + author specific stuff in a 
named data directory e.g.:

shksprdata
miltondata

> Textsearch is a CLI file which should search the index and the 
> controller/search.py file is a form base version for folks who want to 
> do either form of search. One change that does need making is that the 
> document returns the document id not name. (Its on my to do list).

I'm already on to it -- though results may not be seen for a week or so 
as I won't be able to code next week and my efforts so far are only 50% 
complete.

> I've also inserted  templates/search.html and searchword.html which 
> return the form results.

Great stuff again. I'm also in the process of migrating this over to the 
shakespeare side of things. It is definitely clear that we need a common 
core which can be reused per author so we don't have to duplicate all 
this stuff.

~rufus

PS: you might want to avoid adding *.pyc files to svn :) One easy way is 
to set the svn:ignores stuff in your main subversion configuration



More information about the okfn-help mailing list