Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019 
<== Date ==> <== Thread ==>

Subject: RE: Electronic Logbooks
From: Emmanuel Mayssat <emayssat@outlook.com>
To: Miroslav Pavleski <miroslav.pavleski@cosylab.com>, "tech-talk@aps.anl.gov" <tech-talk@aps.anl.gov>
Date: Mon, 29 Jul 2013 14:56:56 -0700
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?
--
Emmanuel

> Date: Mon, 29 Jul 2013 16:15:08 +0200
> From: miroslav.pavleski@cosylab.com
> To: tech-talk@aps.anl.gov
> Subject: Electronic Logbooks
>
> Hi
>
> We are currently evaluating Electronic Logbooks solutions for ESS. I
> would be really grateful if you provide references to some existing
> solutions.
>
>
> With Regards,
> Miroslav

References:
Electronic Logbooks Miroslav Pavleski

Navigate by Date:
Prev: Re: catching python exception in pcaspy Xiaoqiang Wang
Next: RE: Electronic Logbooks Emmanuel Mayssat
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019 
Navigate by Thread:
Prev: RE: Electronic Logbooks Emmanuel Mayssat
Next: Re: Electronic Logbooks Ralph Lange
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  <20132014  2015  2016  2017  2018  2019 
ANJ, 20 Apr 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·