Dear ELOG users,

starting with SVN revision 2328, custom input forms are implemented. This allows application specific formats for check lists etc. In our specific case we had to implement a shift check list, which was quite long. Furthermore the check list should be optimized for an iPad, which we take in the field and record various checks and readings (in our case some gas pressure gauges at the PSI particle accelerator). Since the standard ELOG interface was too inflexible, a completely hand-written form was needed. The form can be activated by the new configuration options Custom New Form, Custom Edit Form and Custom Display Form, one for a new entry, an entry to edit and and entry to display. In our case we used the same form for all three cases. This is how the shift check list looks under the Safari Browser on a PC:

And here is how it looks on the iPad:

Each section can be collapsed and expanded (blue arrows at the left), and various internal checks are made before the check list can be submitted.

Implementing such forms is however more something for the advanced user, since you have to hand-write HTML with CSS and JavaScript code. It can then however be a powerful method for check lists. Please find in the attachments the elogd.cfg configuration for that logbook and the shiftcheck.html source code file. It is a bit complicated since the page is a static page, elogd just serves it from the file. This requires all the dynamic functions to be implemented inside the HTML file with JavaScript. To display an entry for example, the JavaScript loads the raw data with the "?cmd=Download" command and the populates the form fields. The collapsing and expanding is done by using CSS properties. The integrated style sheet was optimized for the rendering on an iPad. Rather large fonts were chosen so that the items can be checked easily with your finger tips. Various parameters are sent between the browser and the elogd program via hidden fields and cookies. So only something for experts! But if you go through the effort and hand-write the form, it can be very handy. Note that you have to upgrade to SVN revision 2328 for the three new options.

Forgive me I'm not incredibly Elog savy yet.

A little backround about this log book -  I have our log set up as individual user names.  The log book is designed for entrys to be made when a process shutdown needs to be bypassed.  The operator will create an entry and submit it.  Then a supervisor will come in after and review/approve it.  I've removed the edit function,  but left the "Reply" option available for the supervisor to go into the same entry and check off the "Reviewed" attribute.  When the reviewed attribute is checked off, even with a different logged in author the next entry ID still shows the original author that put in the entry rather then the author who clicked reviewed.  If there a way to get around this?

[Process Bypass]
Comment = (Not in use right now, currently developing)
Attributes = Author, Date/Time of Bypass, Equipment Name, Device Tag, Supervisor Sign-off,
Moptions Supervisor Sign-off = Reviewed
List Menu commands = New, Find, Logout
Menu Commands = New, Find, Reply, Logout
Required Attributes = Date/Time of ByPass, Equipment Name, Device Tag
 

Dear all, I have a problem with my window elog installation (2.9.2) and I would like to ask your help for solving it.

I'm using elog on my lab computer for a single user installation, so something very simple. It was running smoothly for many months using the automatic window service (i.e. elogd was started automatically at boot). I need to add that the service is started as the local administrator, while my user has no administrative rights. ELOG is installed in the standard location C:\Program Files (x86)\ELOG\ with the logbook folder inside and this is actually accessible only for admins.

On 8/04/2016, elogd crashed while I was saving an edited message. Then instead of restarting the service or rebooting the PC, I was just starting elogd manually (as me not as admin). It worked for many weeks. And now comes the problem: at the next reboot the elogd service came up automatically but all the new records I added in the logbook since I re-started manually are not there. Indeed in the C:\Program Files (x86)\ELOG\logbooks the latest entry is 160408a.txt. But if I stop the service and restart elogd manually (as me not as admin), then I can see in the logbook all the new entries.

My questions is where the ascii files corresponding to the new entries? They must be saved somewhere, maybe in some temporary folder. I want to copy them back and keep them in the backup to avoid unpleasant surprise.

Thanks in advance for your help,

Antonio