I can put it on the wish list.

Just my two cent - I would have many very good applications for that feature:

• Keep option lists identical over different logbooks.
• Keep option lists identical over different applications.
• Create option lists from a database - that allows to use the options in many applications and in the database; e.g. a list of systems with a failure database, but failure reports in the regular ELOG.
• Export extendable option lists to other applications:
  • Inform administrator about options that have been newly added to a logbook for a review.
  • Provide option lists as menu buttons in these applications.
  • Prevent other applications to submit elog entries with illegal option choices.
• Import extendable option lists from other applications (at least after next elogd restart, if no "update option list" URL/command is provided for elogd).

We recently went through the process of renaming a "system list" in several logbooks, to make it consistent over several facilities. If the "on-call service" is called "radio frequency", but the "system" is called "RF", then searching the logbook can become difficult. It was painful: half a dozen applications had to be adapted at the same time the lists were updated, because they had features to create a failure report to ELOG - assuming specific "system" names.

So I'm in favour of putting that high up in the wishlist :-)

May I slip my vote in for this, especially if it would allow more than 100 attributes (the default, and I do know how to increase it).

I even considered cutting that into two groups,. the first being words like "New", "Re-" and the second being actions.  Clunkey and binned.

Yes, I agree that cleaning up old Draft entries and correcting/deleting old entries is a job for the administrator. Currently I do what you've said: commenting out "restrict edit time", changing the entry, commenting in "restrict edit time".

There are already some commands specifically for the admin:

• Admin textarea = <cols>,<rows>
• Admin user = <user list>

It would make sense to add more of them, for this specific case:

• Admin restrict edit time = <hours>

If that is set to "-1", then the Admin can edit old entries regardless of their age. Actually there is no option to "unset" restrict edit time inherited from a global config: a negative time would make sense as "disabling" restrict edit time.

Another item for the endless wishlist ;-)

Cheers, Andreas

Hello, Is there any way to organize logbooks in some kind of tree with sublogbooks or just have a subdirectories in a logbook directory on the filesystem (treat it as a sublogbook if its name is different from 4 digits of year and pin above all the entries in a list) to structure entires a bit?

Just use groups as written in the manual: https://elog.psi.ch/elog/config.html#groups

Stefan

Greetings!

We've been successfully running nearly a dozen separate logbooks on independent laptops -- all of them are running elogd as a Windows service. This works well, since I've also set up auto recovery options in the event that the service inadvertently stops.

Now, I have a need to place the value of an attribute of the latest log entry into a basic text file.  Of course, this works just fine if I have launched elogd -x as a normal executable, using Execute new = echo $Status > Last_status.log in my CFG file.  However, I would like to be able to do this using the Windows service which is running in the background. 

Is there another way to write the value of an attribute into a separate file?  If not, do I have to have a special build of ELOG in order to be able to enable the Windows service to execute shell commands?  For the record, these logbooks are running on secure laptops that are isolated onto their own network, and the user is unable to edit the CFG file.

In case you're wondering about the reason for the separate text file -- I've written a separate program which illuminates one of 4 different color signal lamps (mounted on a test station), based on the latest "Status" of the test station. (Running, Idle, Broken, Other).

I appreciate any guidance here -- this is a "big deal" here, as one glance over the floor gives us an idea of what's running (or not).

Thanks!
Frank

Sorry -- I somehow selected the wrong OS in my original message. Asleep at the wheel again.