I have just updated the website with a detailed example of a Nabu
extractor. You can find it at: =20
Reading this simple (but still useful) example should help everyone
grasp the goal of this project. You will see how intimately tied to
docutils it is. In the example, I'm extracting book references from
field lists of the following format:
:title: National Geographic Photography Field Guide 2nd Edition:
Secrets to Making Great Pictures
:author: Peter Burian, Bob Caputo
Excellent diversified advice from top photographers. The book
manages to pack lots of relevant content in a small format. It
contains a nice section on composition, which is what originally
attracted me to it. As per usual, I found the digital
photography section useless, but for the most part, the
information available in this book is of great value. This is
the best general book about photography that I've read.
Any questions, let me know.
On 7/15/05, Martin Blais <martin.blais@...> wrote:
> On 7/13/05, Felix Wiemann <Felix.Wiemann@...> wrote:
> > Martin Blais wrote:
> > > http://furius.ca/nabu
> > Thanks.
> > I admit I didn't read it in detail and didn't test it either (it seems
> > fairly complicated, and there is no step-by-step tutorial to get it
> > running), but I have two questions:
> you can try this:
> > Nabu stores things in databases (extracted from field lists?). Is it u=
> extracted from field lists or whatever other document structure you
> care to write an extractor (a docutils transform) for.
> > to me what I do with those things in the database then? Or is Nabu
> yes. make your own blog. build your own calendar. make your own
> wiki-like system. your list of book reviews. whatever. we all have
> varying needs for kinds of human-editable information we want to store
> and present. nabu just helps you put the stuff from restructuredtext
> files into database tables.
> > involved with extracting anything except documents? Or did I
> anything you like that can be extracted from a docutils document tree.
> > misunderstand it entirely?
> it's not quite obvious how to use it indeed, because it does not fit
> into any traditional ways of manipulating information. but i think
> that it opens up new possibilities for people who can edit text files
> easily (i.e. all programmers, for example).
> in the worse case, i'll use it for myself to re-implement my travel
> journal website into a kind of generalized blog/travel journal/book
> reviews/shared calendar/tech documents publishing "thing" with
> advanced discrimination for access privileges (for example, in my new
> site, i'll be able to send someone a link that will automatically give
> access to only "some" part of the site, e.g. photographs from the last
> trip, but not the texts, for example; a kind of weak user-level
> access without user/passwords with expiring dates).
> > And can you give me a short description for the link list, please?
> Nabu is a simple framework that extracts chunks of various types of
> information from documents written in simple text files (written with
> reStructuredText conventions) and that stores this information
> (including the document) in a remote database for later retrieval. The
> processing and extraction of the document is handled on a server, and
> there is a small and simple client that is used to push the files to
> the server for processing and storage (think rsync). The client
> requires only Python to work. The presentation layer is left
> unspecified: you can use whichever web application framework you like
> to present the extracted data in the way that you prefer.
> > By the way, the links in style.css (in the distribution tarball) are
> > broken.
> yeah, that's ok. in my projects structure, the source code both feeds
> the website and the projects source. it's no biggie.