I'm (mis)using elog as a database. I like the fact that I can have presets for fields, but I also like the fact 
that I can make a duplicate of an entry. Now when I make a duplicate, all the fields get overwritten with the 
preset-value. Is there a way to get the preset-values only on entering a NEW reord and NOT on a duplicate ?

I could take away the presets, most of them are "***" (literally) to be able to search for entries that do not 
have a value, but I don't know how to search for empty fields.


PS: They wanted to do a CMDB in BMC-Magic (really expensive $$$-ware), but after about 1 afternoon (and about 6 
prototypes) they went with elog since it was fast, cheap and already implemented (and filled with 200 entries 
through a script using some old CSV list we had lying around) :-) 

 

> I'm (mis)using elog as a database. I like the fact that I can have presets for fields, but I also like the fact 
> that I can make a duplicate of an entry. Now when I make a duplicate, all the fields get overwritten with the 
> preset-value. Is there a way to get the preset-values only on entering a NEW reord and NOT on a duplicate ?

I fixed that in the SVN revision 1583. The fix will be contained in the upcoming version 2.6.1.

Hello there,

After several years of great ELOG usage I decided to upgrade our ELOG server.  I am using it to keep 
a logbook of my students.

ELOG runs as a windows service but since I cannot access or change windows services (only have access to the
ELOG directory) I upgraded by installing the executable to my laptop then copying the new ELOG version over the server installation.  

Tried this first on my laptop going from V2.9.2-2475  to the last version 3.1.1 and this worked without a problem.

When I tried to reproduce this on the server  all the data is there but ELOG displays it as if no theme was installed. (using the default
by the way)  No colors, no formatting
... at first I thougt this was because the copy was not complete but a second try reproduced the same result???

Tried going back to the old version but then ALL data was gone (structure and all logbooks still there, but data in logbooks gone) ....
Used -v switch to debug and the logging displayed an MD5 hash mismatch, so the logbooks could not be opened.  A restore fixed this ....
I guess upgrading means changing the logbook structure?

Anyway does anyone have any idea why the upgrade loses formatting ??  Tips are welcome

Dear all,

I just wanted to share a small script which I wrote to integrate our ELOG in Slack. This allows us to be notified immediately if there is a new logbook entry directly within the appropriate Slack channels. We're using ELOG V2.9.2-245 but if the log-file format has "Subject, Author, Type" in the header, it should work with any other version. I'm using Pyinotify for the file watch which relies on a Linux Kernel feature (merged in kernel 2.6.13) called inotify, so the script only works on Linux.

Here is the code: https://github.com/tamasgal/elog-slack

Cheers and thanks for ELOG!

Tom

I use a elog which has a text field to show log entries:  https://classis01.roma1.infn.it/elog/calib/     In the "Summary" view there are only 3 lines of about 40 characters shown, so often the entry is cut off even though there is plenty of space in the text box for longer lines.   To see the full entry you must click on the ID number.   Is there any way to configure the Text box to show longer lines?   Thank you.

Did you try the options

• Summary lines = x
• Summary line length = x

as documented in https://midas.psi.ch/elog/config.html#flags ?

It works nicely with plain text entries; it has some difficulties with HTML, since it has to remove the formatting and that disturbs the line count.

Cheers Andreas

I'm trying to set up a python rss parser to read the output from my collaboration's elog, however the elog is password protected and I cannot figure out how to have a python scrip get past the login screen.  Is there something obvious I'm missing that will allow a parser to submit a username and password? If that's too python-specific of a question for this audience, then what is the exact security method elog uses, so I can get information on that?  I've read through the documentation and either I don't know what I'm reading (likely) or I'm not looking in the right spot.