sorry (again!) for the radio silence. Have been very busy coming up
with an optimal JSON output format for the search and document
browsing responses. Here's a sample of a current format:
https://gist.github.com/2693bfc44293873744d7
which has been used in the UI shown in the attached screenshot which
shows a search of Dicken's "Old Curiosity Shop" against a plagiarism
corpus. The interface is using ExtJS and seems to work well for
quickly browsing through each matched document and looking at the
discovered fragments. I'm doing the same for the document browsing
page and hope to have something that you can play with soon.
A lot of the work being done is directly replicable in the Churnalism
browser extension, and in a browser neutral fashion so it should speed
that part of the work up too. It's an open question of how much
processing of the fragments to do on the server or client side. There
are a great deal of interesting things that can be done with the
fragments list and I've been tending to do the work in the client.
The python client could follow the same model... Not sure, any
feedback appreciated!!
Cheers,
Donny.