Unless Elog is a turnkey solution, you may want to have a look at the couchdb/couchapp/sofa.
couchdb is a nosql document-based database (1 document = 1 post or 1 attachment)
It is by default in chronological order (think timeline of facebook/twitter)
It has a JSON interface (so your program can post in the log book)
Everything is dumped together, but you can easily filter the data (i.e. want only info from operators? no problems. From a specific program/operator? no problem either ! )
It can be standalone (couchdb is built by the apache fundation and can be standalone (couchdb + webserver is called a couchapp))
You have command line interface, python/C/C++/... interface, web interfaces (1 admin interface aka futon, 1 user with MVC framework)
Search engine: apache Lucene
If you go that road have a look at the sofa couchapp, you will have to customize the frontpage (by default your entries are submitted through a simple textarea and as a twitter feel).
But with FCKEditor (or other) and twitter bootstrap, you can easily customize it.
In my case, I wanted ALL my desktop applications to access directly the logbook (i.e. when the conditioning of the magnet is initiated, an entry appears in the logs with the used configuration. when it is completed another entry in the log appears). Due to the numbers of required hooks, that's a work in progress.
It turns out, the problem I am facing is not to put the logbook in place.
Rather the issue is for everyone (operators/programs) to populate it!
What are your requirements?
> Date: Mon, 29 Jul 2013 16:15:08 +0200
> From: firstname.lastname@example.org
> To: email@example.com
> Subject: Electronic Logbooks
> We are currently evaluating Electronic Logbooks solutions for ESS. I
> would be really grateful if you provide references to some existing
> With Regards,