Using Reply option, posted by Jason S on Tue Jul 12 16:18:46 2016
|
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
|
Re: Using Reply option, posted by Andreas Luedeke on Tue Jul 12 19:39:04 2016
|
Preset on reply Author = $long_name
Cheers, Andreas
Jason S wrote: |
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
|
|
Re: Using Reply option, posted by Jason S on Tue Jul 12 20:53:03 2016
|
Works Great. Thanks Andreas
Andreas Luedeke wrote: |
Preset on reply Author = $long_name
Cheers, Andreas
Jason S wrote: |
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
|
|
|
Multiple outcomes to a conditional attribute, posted by Sofian Jafar on Tue Jul 12 08:06:36 2016
|
Hi,
First of all, thanks for all the great work, we all thank you here at SESAME synchrotron 
I am trying to set a conditional attribute where selecting one option in that attribute should trigger multiple outcomes as shown below:
Options Type = Fault{1_1&1_2}, Test{2_1&2_2}, Report{2_1&2_2}
{1_1} Options Fault Status = Open{a}, Fixed{b}
{2_1} Preset Fault Status = NA
{1_2} Preset Icon = attn.png
{2_2} Preset Icon = icon1.gif
I tries adding "&" as shown but that didn't work, my goal is to have 1_1 and 1_2 triggered whenever I select "Fault" as type, how can I do that?
Thanks in advance.
Cheers,
Sofian.
|
Re: Multiple outcomes to a conditional attribute, posted by Andreas Luedeke on Tue Jul 12 08:31:37 2016
|
Hi Sofian,
it should work like this:
Options Type = Fault{1}, Test{2}, Report{3}
{1} Options Fault Status = Open{a}, Fixed{b}
{2,3} Preset Fault Status = NA
{1} Preset Icon = attn.png
{2,3} Preset Icon = icon1.gif
It is described under "Multiple conditions" in the documentation (https://midas.psi.ch/elog/config.html#conditional).
Cheers and good luck!
Andreas
Sofian Jafar wrote: |
Hi,
First of all, thanks for all the great work, we all thank you here at SESAME synchrotron 
I am trying to set a conditional attribute where selecting one option in that attribute should trigger multiple outcomes as shown below:
Options Type = Fault{1_1&1_2}, Test{2_1&2_2}, Report{2_1&2_2}
{1_1} Options Fault Status = Open{a}, Fixed{b}
{2_1} Preset Fault Status = NA
{1_2} Preset Icon = attn.png
{2_2} Preset Icon = icon1.gif
I tries adding "&" as shown but that didn't work, my goal is to have 1_1 and 1_2 triggered whenever I select "Fault" as type, how can I do that?
Thanks in advance.
Cheers,
Sofian.
|
|
Re: Multiple outcomes to a conditional attribute, posted by Sofian Jafar on Tue Jul 12 09:15:35 2016
|
Thanks Andreas,
Works great.
I tried reading the documentation on this but I was not able to deduce this solution.
Thanks a lot again.
Andreas Luedeke wrote: |
Hi Sofian,
it should work like this:
Options Type = Fault{1}, Test{2}, Report{3}
{1} Options Fault Status = Open{a}, Fixed{b}
{2,3} Preset Fault Status = NA
{1} Preset Icon = attn.png
{2,3} Preset Icon = icon1.gif
It is described under "Multiple conditions" in the documentation (https://midas.psi.ch/elog/config.html#conditional).
Cheers and good luck!
Andreas
Sofian Jafar wrote: |
Hi,
First of all, thanks for all the great work, we all thank you here at SESAME synchrotron 
I am trying to set a conditional attribute where selecting one option in that attribute should trigger multiple outcomes as shown below:
Options Type = Fault{1_1&1_2}, Test{2_1&2_2}, Report{2_1&2_2}
{1_1} Options Fault Status = Open{a}, Fixed{b}
{2_1} Preset Fault Status = NA
{1_2} Preset Icon = attn.png
{2_2} Preset Icon = icon1.gif
I tries adding "&" as shown but that didn't work, my goal is to have 1_1 and 1_2 triggered whenever I select "Fault" as type, how can I do that?
Thanks in advance.
Cheers,
Sofian.
|
|
|
Re: Multiple outcomes to a conditional attribute, posted by Stefan Ritt on Tue Jul 12 08:37:42 2016
|
What about this:
Options Type = Fault{1}, Test{2}, Report{3}
{1} Options Fault Status = Open{a}, Fixed{b}
{2,3} Preset Fault Status = NA
{1} Preset Icon = attn.png
{2,3} Preset Icon = icon1.gif
-Stefan
Sofian Jafar wrote: |
Hi,
First of all, thanks for all the great work, we all thank you here at SESAME synchrotron 
I am trying to set a conditional attribute where selecting one option in that attribute should trigger multiple outcomes as shown below:
Options Type = Fault{1_1&1_2}, Test{2_1&2_2}, Report{2_1&2_2}
{1_1} Options Fault Status = Open{a}, Fixed{b}
{2_1} Preset Fault Status = NA
{1_2} Preset Icon = attn.png
{2_2} Preset Icon = icon1.gif
I tries adding "&" as shown but that didn't work, my goal is to have 1_1 and 1_2 triggered whenever I select "Fault" as type, how can I do that?
Thanks in advance.
Cheers,
Sofian.
|
|
More than 100 attributes , posted by JD on Wed Jun 29 16:07:32 2016
|
I am modifying the elogd.cfg automatically with a script. The Script fetches a list of systems from a LDAP database and writes them into an "Options" line in the elog.cfg.
Everything worked fine, until we hit the critical number of 100 attributes. I saw this is also stated in the manual.
Is there any workaround? I downloaded the source code and hat a quit look, but couldn't find the section which is responsible for this behavior.
Is there a reason for this limit?
Thanks
Jonathan |
Re: More than 100 attributes , posted by Stefan Ritt on Wed Jun 29 16:58:15 2016
|
The limit is in the variable
#define MAX_N_ATTR 100
in elogd.c. If you increase it and recompile, it could work, but at some time you will get a stack overflow since arrays with that size are dynamically allocated on the stack, and depending on your compiler settings the stack size is only finite.
Stefan
JD wrote: |
I am modifying the elogd.cfg automatically with a script. The Script fetches a list of systems from a LDAP database and writes them into an "Options" line in the elog.cfg.
Everything worked fine, until we hit the critical number of 100 attributes. I saw this is also stated in the manual.
Is there any workaround? I downloaded the source code and hat a quit look, but couldn't find the section which is responsible for this behavior.
Is there a reason for this limit?
Thanks
Jonathan
|
|
Re: More than 100 attributes , posted by JD on Thu Jun 30 14:00:43 2016
|
Thank you Stefan, I think then I will leave it at the default value. I need a stable Systen
Stefan Ritt wrote: |
The limit is in the variable
#define MAX_N_ATTR 100
in elogd.c. If you increase it and recompile, it could work, but at some time you will get a stack overflow since arrays with that size are dynamically allocated on the stack, and depending on your compiler settings the stack size is only finite.
Stefan
JD wrote: |
I am modifying the elogd.cfg automatically with a script. The Script fetches a list of systems from a LDAP database and writes them into an "Options" line in the elog.cfg.
Everything worked fine, until we hit the critical number of 100 attributes. I saw this is also stated in the manual.
Is there any workaround? I downloaded the source code and hat a quit look, but couldn't find the section which is responsible for this behavior.
Is there a reason for this limit?
Thanks
Jonathan
|
|
|
Unable to set a custom logbook dir on Debian 8 from the repository package, posted by S. Caiazza on Tue May 31 20:03:53 2016
|
Dear all
I installed elog from the current stable repository on Debian 8 (jessie)
The installation went on smoothly, I modified the configuration files of the Apache server as described in the manual to use the elog in parallel with an existing webserver and then I tested. The demo logbook loads fine and I see that elog created a folder for the logbook in /var/lib/elog/logbooks, which is the directory specified by default in the /etc/init.d/elog file.
Then I modified the /etc/elog.conf file, added the following lines in the global section (custompath is a local path)
Resource dir = /<custompath>/elog/res
Logbook dir = /<custompath>/elog/logbooks
And I created a new logbook.
After restarting the elog service the second database is correctly created but both of them are still stored in /var/lib/elog/logbooks so it seems the global configurations in the config file are overwritten.
How can I specify the custom folder so that the new logbooks are written there? |
Re: Unable to set a custom logbook dir on Debian 8 from the repository package, posted by Stefan Ritt on Mon Jun 27 16:06:55 2016
|
The debian version of elog is pretty old with quite a number of bugs fixed in meantime. Unfortunatlely the debig packase has not bee updated by the maintainers. So better download the current version from bitbucket and compile elogd yourself.
S. Caiazza wrote: |
Dear all
I installed elog from the current stable repository on Debian 8 (jessie)
The installation went on smoothly, I modified the configuration files of the Apache server as described in the manual to use the elog in parallel with an existing webserver and then I tested. The demo logbook loads fine and I see that elog created a folder for the logbook in /var/lib/elog/logbooks, which is the directory specified by default in the /etc/init.d/elog file.
Then I modified the /etc/elog.conf file, added the following lines in the global section (custompath is a local path)
Resource dir = /<custompath>/elog/res
Logbook dir = /<custompath>/elog/logbooks
And I created a new logbook.
After restarting the elog service the second database is correctly created but both of them are still stored in /var/lib/elog/logbooks so it seems the global configurations in the config file are overwritten.
How can I specify the custom folder so that the new logbooks are written there?
|
|
Hide blank fields when displaying logbook entry, posted by Rudy Taraschi on Thu Jun 23 15:57:34 2016
|
Hi, I have a logbook with attributes Tool1, Tool2, and Tool3. When viewing a completed entry, what I want to do is see Tool2 or Tool3 only if they are non-zero, and don't want to see them if blank. Basically, a "Hide if blank" option. I couldn't find it - if it doesn't exist, are there any tricks to simulate it? |
pdf thumbnails in latest Imagemagick, posted by John Haggerty on Mon Jun 6 05:51:44 2016
|
I think with the latest Imagemagick from brew (6.9.4-7) that pdf thumnails no longer get made; the attachment is there but the message "Cannot create thumbnail, please check ImageMagick installation" apears instead of the thumbnails. I couldn't make out from elogd -v 3 why they failed, but I couldn't make out the exact convert command that was failing. This is on MacOS 10.11.5 and I think the updated version ofImagemagick was the last thing that changed before it failed. |
Re: pdf thumbnails in latest Imagemagick, posted by Stefan Ritt on Tue Jun 21 16:33:56 2016
|
Hi John,
I use ImageMagick 6.9.3-10 on my Mac OSX 10.11.5 and it works fine. So apparently the parameters of the ImageMagick program have been changed. If you set the logging level to 2 or higher, you should see the "convert" and "identify" commands in the logging file. If you try these commands manually from the command line, you will see if they succeed or give an error. Please post this error here so I can have a look.
Cheers,
Stefan
John Haggerty wrote: |
I think with the latest Imagemagick from brew (6.9.4-7) that pdf thumnails no longer get made; the attachment is there but the message "Cannot create thumbnail, please check ImageMagick installation" apears instead of the thumbnails. I couldn't make out from elogd -v 3 why they failed, but I couldn't make out the exact convert command that was failing. This is on MacOS 10.11.5 and I think the updated version ofImagemagick was the last thing that changed before it failed.
|
|
Re: pdf thumbnails in latest Imagemagick, posted by John Haggerty on Tue Jun 21 16:44:05 2016
|
Stefan Ritt wrote: |
Hi John,
I use ImageMagick 6.9.3-10 on my Mac OSX 10.11.5 and it works fine. So apparently the parameters of the ImageMagick program have been changed. If you set the logging level to 2 or higher, you should see the "convert" and "identify" commands in the logging file. If you try these commands manually from the command line, you will see if they succeed or give an error. Please post this error here so I can have a look.
Cheers,
Stefan
John Haggerty wrote: |
I think with the latest Imagemagick from brew (6.9.4-7) that pdf thumnails no longer get made; the attachment is there but the message "Cannot create thumbnail, please check ImageMagick installation" apears instead of the thumbnails. I couldn't make out from elogd -v 3 why they failed, but I couldn't make out the exact convert command that was failing. This is on MacOS 10.11.5 and I think the updated version ofImagemagick was the last thing that changed before it failed.
|
|
Since I posted that, there have been multiple versions of Imagemagick released through brew for the Mac in the last few weeks, and I'm now using 6.9.4-9, which seems to work fine with thumbnails again, indeed, I noticed that as soon as 6.9.4-8 was released, I was back to normal, but thanks for the debugging pointer. |
cannot use "use email heading", posted by utomoadji wisnubroto on Tue Jun 14 07:51:37 2016
|
Hello,
i have config file elogd.cfg like below:
[Tom Yaht]
Theme = default
;Comment and Tittle
Comment = LogBook
Page title = Tom LogBook
List page title = Tom LogBook
;admin and user settings
admin user = tom
login user = tom, soc
login expiration = 2
Restrict edit time = 8
Attributes = Controllers, Event Date/Time, Site, Engineers, Type, Category, Subsystems, Subject, Distribution-Mail, EMail to
Moptions Distribution-Mail = Controllers, Engineers, Consultant Team, Manager
;Email settings
Email Distribution-Mail "Controllers" = ble@xxx.com, cor@xxx.com, nor@xxx.com
Email Distribution-Mail "Engineers" = blo@xxx.com, sur@xxx.com, ars@xxx.com
Email Distribution-Mail "Consultant Team" = bli@xxx.com, zam@xxx.com
Email Distribution-Mail "Manager" = bos@xxx.com
Email all = $EMail to
Use Email Subject = Tom Logbook - $Subject
Use Email Heading = New Tom Logbook entry
Use Email Heading edit = Tom Logbook has been updated
The Subject successfully displayed as i expected , but the email heading still use default heading "A new ELOG entry has been submitted" , while i want to changeit to be "New Tom Logbook entry" as i mention in Use Email Heading above.
Could anybody help me.
Thank you |
Re: cannot use "use email heading", posted by Stefan Ritt on Tue Jun 14 14:33:40 2016
|
The setting
Use Email Heading
is only used for plain text encoding of email messages. The default is HTML encoding, which has its own heading which cannot be changed. If you want the different heading, use
Email encoding = 1
and you get it.
/Stefan
utomoadji wisnubroto wrote: |
Hello,
i have config file elogd.cfg like below:
[Tom Yaht]
Theme = default
;Comment and Tittle
Comment = LogBook
Page title = Tom LogBook
List page title = Tom LogBook
;admin and user settings
admin user = tom
login user = tom, soc
login expiration = 2
Restrict edit time = 8
Attributes = Controllers, Event Date/Time, Site, Engineers, Type, Category, Subsystems, Subject, Distribution-Mail, EMail to
Moptions Distribution-Mail = Controllers, Engineers, Consultant Team, Manager
;Email settings
Email Distribution-Mail "Controllers" = ble@xxx.com, cor@xxx.com, nor@xxx.com
Email Distribution-Mail "Engineers" = blo@xxx.com, sur@xxx.com, ars@xxx.com
Email Distribution-Mail "Consultant Team" = bli@xxx.com, zam@xxx.com
Email Distribution-Mail "Manager" = bos@xxx.com
Email all = $EMail to
Use Email Subject = Tom Logbook - $Subject
Use Email Heading = New Tom Logbook entry
Use Email Heading edit = Tom Logbook has been updated
The Subject successfully displayed as i expected , but the email heading still use default heading "A new ELOG entry has been submitted" , while i want to changeit to be "New Tom Logbook entry" as i mention in Use Email Heading above.
Could anybody help me.
Thank you
|
|
Re: cannot use "use email heading", posted by utomoadji wisnubroto on Wed Jun 15 02:42:53 2016
|
Hi Stefan,
Thanks for your reply, i got it now.
Thank you
Stefan Ritt wrote: |
The setting
Use Email Heading
is only used for plain text encoding of email messages. The default is HTML encoding, which has its own heading which cannot be changed. If you want the different heading, use
Email encoding = 1
and you get it.
/Stefan
utomoadji wisnubroto wrote: |
Hello,
i have config file elogd.cfg like below:
[Tom Yaht]
Theme = default
;Comment and Tittle
Comment = LogBook
Page title = Tom LogBook
List page title = Tom LogBook
;admin and user settings
admin user = tom
login user = tom, soc
login expiration = 2
Restrict edit time = 8
Attributes = Controllers, Event Date/Time, Site, Engineers, Type, Category, Subsystems, Subject, Distribution-Mail, EMail to
Moptions Distribution-Mail = Controllers, Engineers, Consultant Team, Manager
;Email settings
Email Distribution-Mail "Controllers" = ble@xxx.com, cor@xxx.com, nor@xxx.com
Email Distribution-Mail "Engineers" = blo@xxx.com, sur@xxx.com, ars@xxx.com
Email Distribution-Mail "Consultant Team" = bli@xxx.com, zam@xxx.com
Email Distribution-Mail "Manager" = bos@xxx.com
Email all = $EMail to
Use Email Subject = Tom Logbook - $Subject
Use Email Heading = New Tom Logbook entry
Use Email Heading edit = Tom Logbook has been updated
The Subject successfully displayed as i expected , but the email heading still use default heading "A new ELOG entry has been submitted" , while i want to changeit to be "New Tom Logbook entry" as i mention in Use Email Heading above.
Could anybody help me.
Thank you
|
|
|
Guest menu commands not working as advertisted, posted by Greg Christian on Tue Jun 14 16:50:41 2016
|
Hello,
I am trying to set up my elog to have read-only guest access and require registration/password for users to be able to post to the elog. I've tried following the instructions here: https://midas.psi.ch/elog/faq.html#6, i.e. putting the following lines under the [global] section of my elogd.cfg file:
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config, Logout, Help
Guest menu commands = List, Find, Login, Help
When I do this, I do get guest acccess, however the menu items are
New | Find | Select | Import | Config | Logout | Last day | Help
rather than the List, Find, Login, Help I would expect. Also, if I click on Logout, it simply does nothing, which means there's now no way to log in as a registered user.
Any thoughts on what might be wrong?
Thanks,
Greg |
Re: Guest menu commands not working as advertisted, posted by Stefan Ritt on Tue Jun 14 17:01:04 2016
|
There are two menus, one for the list display, and one for the individual entry display. To change the first, you need
List menu commands = ...
Guest list menu commands = ...
Greg Christian wrote: |
Hello,
I am trying to set up my elog to have read-only guest access and require registration/password for users to be able to post to the elog. I've tried following the instructions here: https://midas.psi.ch/elog/faq.html#6, i.e. putting the following lines under the [global] section of my elogd.cfg file:
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config, Logout, Help
Guest menu commands = List, Find, Login, Help
When I do this, I do get guest acccess, however the menu items are
New | Find | Select | Import | Config | Logout | Last day | Help
rather than the List, Find, Login, Help I would expect. Also, if I click on Logout, it simply does nothing, which means there's now no way to log in as a registered user.
Any thoughts on what might be wrong?
Thanks,
Greg
|
|
Re: Guest menu commands not working as advertisted, posted by Greg Christian on Tue Jun 14 18:32:03 2016
|
Got it. Thanks!
Stefan Ritt wrote: |
There are two menus, one for the list display, and one for the individual entry display. To change the first, you need
List menu commands = ...
Guest list menu commands = ...
Greg Christian wrote: |
Hello,
I am trying to set up my elog to have read-only guest access and require registration/password for users to be able to post to the elog. I've tried following the instructions here: https://midas.psi.ch/elog/faq.html#6, i.e. putting the following lines under the [global] section of my elogd.cfg file:
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config, Logout, Help
Guest menu commands = List, Find, Login, Help
When I do this, I do get guest acccess, however the menu items are
New | Find | Select | Import | Config | Logout | Last day | Help
rather than the List, Find, Login, Help I would expect. Also, if I click on Logout, it simply does nothing, which means there's now no way to log in as a registered user.
Any thoughts on what might be wrong?
Thanks,
Greg
|
|
|
|