I'm looking for config examples of a shift log book where operators have to check a box or select their name from a list to prove they have read the latest entries in the log, can anyone help.

  Thanks for your time.

Ed..

Unfortunately a read confirmation is not foreseen in the Elog system. You would have to define one attribute for each shift worker, like "John has read", "Steve has read" and so on. Then each of the shift workes has to "Edit" each message an check his/her checkmark manually.

Stefan

As a variant of what Stefan has suggested:

Perhaps a simple comment is set up as the pre-loaded reply - perhaps including date and time.  Maybe include the author's name in the comment, but all that is available anyway (see documentation for that).  This bit isn't vital.

Then each user simply has to *reply* to the message concerned, and you then get the list of who has read it, available in threaded view of the comment and replies.

Of course this works best with small numbers of users, and where threads are never very long.  Also, it means that you can lock the original message (prevent it being edited) which may be a particular concern depending on what you are using elog for.

You might also want to define an attribute that a reader can tick to say that they have taken action if it is important that someone has to take further action (as opposed to just reading) - and maybe that changes the colour of the background or the icon in front of the topic.  Then there would be a record as to who has done the necessary, and later readers will know the matter is for information rather than needing attention.   For example,. who kicked the power supply to the ion source on Monday morning to "wake it up" (this is true, but pre-elog, so was a paper record).  John kicked it last Monday, and the power supply respects John, may be a statistic one could find from such information recorded as suggested here.

You may want a second attribute people have to explicity select so as to show they understand what they've read, rather than just reply/submit without having read... e.g. they have to select a digit of the ticket number, or some auto-generated number (or letter, I'm not characterist) that is within the original comment.

We all know people who click on things they've never read, and come on, we've all done it at times...

David.

Appreciate the help..

Thanks

Hi

Can I asign a URL to a Radio Button to bring up another program?

You can do this by adding manyallty some JavaScript to the page.

OK thanks Stefan.

Thats another programming language I'll have to learn then. :-)

The Elog config I am just getting to grips with but Java and Scripts are a bit beyond me.

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

Is there anything I can do about this?

kernel:  2.6.32-279.14.1.el6.x86_64

ldd (GNU libc) 2.12

/lib64/libc.so.6

/usr/lib64/libssl.so.10

rpm -i elog-latest.i386.rpm

error: Failed dependencies:

libc.so.6 is needed by elog-3.1.1-1.i386

libc.so.6(GLIBC_2.0) is needed by elog-3.1.1-1.i386

libc.so.6(GLIBC_2.1) is needed by elog-3.1.1-1.i386

libc.so.6(GLIBC_2.1.3) is needed by elog-3.1.1-1.i386

libc.so.6(GLIBC_2.3) is needed by elog-3.1.1-1.i386

libssl.so.6 is needed by elog-3.1.1-1.i386

I attempted instead to build from the tar ball, and, except for a "fatal" git error, make built elogd, elog, and elconv.  I put the first in /usr/local/sbin, and the latter two in /usr/local/bin, and then restarted elogd, but this didn't work:

Service Temporarily Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

So, I backed these out and restored the previous executables, and access to the elog was restored, and the elogd.cfg accessed is the original one, but all logbooks are empty and requiring authentication.  The logbook directories still contain all the old entries, so I'm not sure what has happened.

Thanks for your advice.

Phil

OK.  I found the source of the logbook problem in an exchange from May 2015, so no need to answer this one.

But I would like to be able to upgrade to 3.x from 2.9, so any help with this will be much appreciated.

Phil

I did the following on CentOS 6.7 (Should work for Fedora and RHEL as well):

This should install all the required dependencies.

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

Hi,

Is it possible to pre-populate a field based on the selection of another field. I like to have the Equipment Description field populated when the use makes a selection on the EQ# field.

Thank you,

Jimmy

Use "conditional attributes" as described in the documentation: https://midas.psi.ch/elog/config.html#conditional

Is there anything I can do about this?

kernel:  2.6.32-279.14.1.el6.x86_64

ldd (GNU libc) 2.12

/lib64/libc.so.6

/usr/lib64/libssl.so.10

rpm -i elog-latest.i386.rpm

error: Failed dependencies:

libc.so.6 is needed by elog-3.1.1-1.i386

libc.so.6(GLIBC_2.0) is needed by elog-3.1.1-1.i386

libc.so.6(GLIBC_2.1) is needed by elog-3.1.1-1.i386

libc.so.6(GLIBC_2.1.3) is needed by elog-3.1.1-1.i386

libc.so.6(GLIBC_2.3) is needed by elog-3.1.1-1.i386

libssl.so.6 is needed by elog-3.1.1-1.i386

I'm running ELOG on a seperate Windows Servers.

When I try to synchronize the logbooks using "elogd -m", I get an "Error sending local entry: Error transmitting message"

If I click on the "Synchronize" link in the logbook, it can correctly send entry to remote ELOG.

Can anyone tell me why I get this error?

==============================

Here is the command & output:

c:\Program Files (x86)\ELOG>elogd -m

Retrieving entries from "http://166.22.64.201/Equipment Log"...
All entries identical

Retrieving entries from "http://166.22.64.201/System Log"...

Error sending local entry: Error transmitting message