It looks like you've found a bug in ELOG. I've checked my elog.log and see that all NEW entry lines show "#0".

This is nicely explained in the documentation: https://elog.psi.ch/elog/config.html#global

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 :-)

ELOG understands kerberos authentication (See https://elog.psi.ch/elog/config.html#access).

If your SSO works with kerberos, then your SSO user name and password can be used to sign in to ELOG. But I'm not sure if that is what you are asking for...

Cheers, Andreas

Sorting does work fine, if you do it correctly. From your post I cannot even guess what you've tried - let alone tell you what you did wrong.

Please post your config, some example entries and a description of what you've tried, what you expected to happen and what actually happened. Screenshots are often very useful as well.

I am using SSL with ELOG and it works fine with the "elog" executable. I am no expert on SSL, but I can provide my two cent what you could try, maybe it helps:

• SSL desires to run on the port 443 - I have no idea if you can force it to run on an arbitrary port, it might be possible. But does it make sense?
• Certificates are checked against the provider of the certificate. I guess this works fine from your web browser? Or did you just add a security exception?
• Has the installed "elog.exe" been compiled with SSL support on?

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

If you post the [global] part of your configuration, it would help a little bit to understand the problem.

Cheers, Andreas