Hey,

if you define a Tooltip at the moment it is only displayed on the attribute. I would like it very much if it would also be displayed on the values (on the right column in the detailed view and on the whole column in the list view), since we are using the tooltips to define the units of the attribute and it would be nice to pop up when you hover a value.

As for the comment it would be nice to have a flag to also show the comment on the detailed view while looking at an entry. At the moment it is only showed when creating a new entry. Again we use this field to define the units.

This is an example of how we use these options:

attributes = Fill Number, Beam Current, Beam Energy, Beam Lifetime, RF Voltage S2, RF Voltage S4, RF Frequency, Synchrotron Frequency

Comment Beam Current = in mA
Comment Beam Energy = in GeV
Comment Beam Lifetime = in hh:mm
Comment RF Voltage S2 = in kV
Comment RF Voltage S4 = in kV
Comment RF Frequency = in MHz
Comment Synchrotron Frequency = in kHz

Tooltip Beam Current = in mA
Tooltip Beam Energy = in GeV
Tooltip Beam Lifetime = in hh:mm
Tooltip RF Voltage S2 = in kV
Tooltip RF Voltage S4 = in kV
Tooltip RF Frequency = in MHz
Tooltip Synchrotron Frequency = in kHz

Cheers

eddy

Hey,

if you define a Tooltip at the moment it is only displayed on the attribute. I would like it very much if it would also be displayed on the values (on the right column in the detailed view and on the whole column in the list view), since we are using the tooltips to define the units of the attribute and it would be nice to pop up when you hover a value.

As for the comment it would be nice to have a flag to also show the comment on the detailed view while looking at an entry. At the moment it is only showed when creating a new entry. Again we use this field to define the units.

This is an example of how we use these options:

attributes = Fill Number, Beam Current, Beam Energy, Beam Lifetime, RF Voltage S2, RF Voltage S4, RF Frequency, Synchrotron Frequency

Comment Beam Current = in mA
Comment Beam Energy = in GeV
Comment Beam Lifetime = in hh:mm
Comment RF Voltage S2 = in kV
Comment RF Voltage S4 = in kV
Comment RF Frequency = in MHz
Comment Synchrotron Frequency = in kHz

Tooltip Beam Current = in mA
Tooltip Beam Energy = in GeV
Tooltip Beam Lifetime = in hh:mm
Tooltip RF Voltage S2 = in kV
Tooltip RF Voltage S4 = in kV
Tooltip RF Frequency = in MHz
Tooltip Synchrotron Frequency = in kHz

Cheers

eddy

Hey,

You can use the elog command line tool and submit the same attributes to the 5 different logbooks by iterating over the logbook names executing something like this:

elog -l logbook1 -a "attr1=value1" -a "attr2=value2"

elog -l logbook2 -a "attr1=value1" -a "attr2=value2"

elog -l logbook3 -a "attr1=value1" -a "attr2=value2"

elog -l logbook4 -a "attr1=value1" -a "attr2=value2"

elog -l logbook5 -a "attr1=value1" -a "attr2=value2"

Another option would be having an additional common logbook, removing the commonly shared attributes from the other logbooks and add an attribute which links to this entry (using the "elog:logbook/ID" syntax as a value).

Cheers, eddy

> <p>Hi,</p>
> 
> <p>I have a problem running elog command from php script. Basically in the php I call system(&quot;elog -h etc etc.. And from the php command line works but not in the browser apparently without errors (php apache 
logfile no problem), any suggestions?</p>

Hey,
this sounds more like a PHP issue.
Which PHP version are you using? 
Which webserver? 
Which php function are you using: shell_exec() or exec()? Try looking at the return of exec()
Is the elog file set to the correct file permissions to be executed by the webserver?
Is the elog file in the PHP path or do you take care of defining the correct path?


eddy

Hey,

the edit/replace feature is already capable of just replacing individual attributes. I already make heavy use of this feature:

1. One entry is created with some measurement parameters

2. A different script is running processing the measurement data making a plot and a fit

3. Two fit parameters and the attachment are added to the original elog entry (all other attributes and values still exist afterwards)

But the problem here is, that although it does work for normal attrbutes, the attachments will always be replaced (=> removed) if you use this command. Since I only add the attachment on the edit it does work for me. 

Btw the documentation on the homepage is also misleading about the -w command, since in the actual version it does nothing with any password but just reads back the whole elog entry (which I use to manually append the main message)

[-e <id>]                Edit existing message

Right now a Draft shows a red error indication, that the entry is currently a draft. For the CSS styling it uses the HTML class="errormsg". The same class is also used if an entry does not exist.

Would it be possible for the draft version to use a different HTML class (for example class="draftmsg")? It can also use the same visual style (or making it yellow would probably also work)

The reason is that the py_elog Interface uses the class="errormsg" to determine if an entry does not exist ( https://github.com/paulscherrerinstitute/py_elog/blob/master/elog/logbook.py#L394 ) and refuses to return the content for this entry. One could possibly fix that also on the py_elog part, but it would probably at least require parsing of actual text (which might make problems for translated pages). Alternativley one could also look for the edit button, but maybe a small change on the elog server side is the simplest solution to this problem?

It was now moved to the Draft space (which I did not even now existed so far): https://en.wikipedia.org/wiki/Draft:ELOG

If I understand it correctly I think it has to be submitted for review with the blue button on that page, just not sure if that should come from your side or someone else