• ELOG allows you to have different commands for different users. You could allow "New" and "Edit" for normal users, but "Reply" only for administrators.
• You can use "Subst on reply <attribute> = <string>" to set a specifc fields only on reply. 
  • You would hide "status" & "assignee" for new entries or edit (Show Attributes Edit = <list>), and show a "set status" field instead.
  • The line "Subst on reply status = $set status" would take care, that only an administrator can set "status" with a reply to the original entry (+ a "set assignee" field, etc.). While normal users could set "set status", it would not change the "status" field. You could provide a comment or tooltip to explain that.
  • The list view or single entry view should not show the "set status", but only the "status" attribute (List display = <list>, Show Attributes = <list>).
• Use "Propagate attribute = status, assignee" to take care, that the original entry gets their fields set accordingly.

This is how you could do what you want. But bugzilla can do a lot more if you are looking for a bug tracking software.

Cheers, Andreas

Hi all,

I have a use case for ELOG where I need to be able to "prefill" some attributes in the "cmd=new" form, based on the URL.

To illustrate, imagine a link that takes the user directly to the form for creating a new post, with the "Subsystem" attribute already filled out to "Vacuum".

Is this possible already? I've tried naively using URL parameters (e.g. "&Subsystem=Vacuum") but that does not work. If it's not implemented, I think it would be a useful feature to have (and quite important for my particular use case). I could create a new post first using the "elog" tool, with the desired attributes set, but it makes more sense to defer the actual creation of the post to the user, i.e. he/she might change their mind before pressing "submit".

Thanks,

Johan Forsberg, MAX IV Laboratory, Sweden

Hi again!

I've another need that you probably already thought of :)

I'd like to be able to efficiently monitor a logbook for changes (new or edited posts) somehow. The most reasonable way I've found so far is to periodically poll a search that looks for posts after the time of the last poll. But that might note be very efficient, especially if the polling period gets short (or number of clients grows).

Is there some other feature that could be used for this? I was thinking maybe the ETag or Last-Modified HTTP header field could be used to show changes to a logbook by just reading the headers, but it would also require HEAD request support which does not seem to be there.

Cheers,

Johan

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

The elog client binary does not work with webserver authentication.  One fix would be to support both webserver and kerberos authentication (authentication = webserver, kerberos), similar to how you currently support 
"authentication = kerberos, file".

A more general discussion of the elog client binary with webserver authentication can be found at https://midas.psi.ch/elogs/Forum/68318 .

Many thanks,
Devin

The URL encoding of ']' as '%5D' appears to work:

[url=http://example.com?arrays[%5D=v1&arrays[%5D=v2]click here[/url]

Cheers, Andreas

A new version 3.1.2 of elog has been released today and can be retrieved through the normal download section. Since it fixes some vulnerabilities, it is recommended to update to this version.

Stefan