How to enforce line breaks in plain text entries?, posted by Andreas Luedeke on Wed Apr 27 14:07:52 2016
|
We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
entries made during the shift and files the printouts. If one entry in the shift was plain text without
appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the width
|
Re: How to enforce line breaks in plain text entries?, posted by Andreas Luedeke on Wed Apr 27 14:15:19 2016
|
> We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
> entries made during the shift and files the printouts. If one entry in the shift was plain text without
> appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the
|
|
Re: How to enforce line breaks in plain text entries?, posted by Andreas Luedeke on Wed Apr 27 14:36:42 2016
|
> > We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
> > entries made during the shift and files the printouts. If one entry in the shift was plain text without
> > appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the
|
|
Re: How to enforce line breaks in plain text entries?, posted by Stefan Ritt on Wed Apr 27 14:39:28 2016
|
> > We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
> > entries made during the shift and files the printouts. If one entry in the shift was plain text without
> > appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the
|
|
How to login and export to CSV using wget?, posted by Alan Grant on Sun Apr 24 02:09:47 2016
|
Is it possible to use wget to log into elog and export all of a logbook's data into a CSV file?
I can accomplish this perfectly when authentication IS NOT required by using: wget --no-check-certificate -O e:\export.csv http://localhost:8080/demo/?mode=CSV1
However, I cannot accomplish it when authentication IS required by using: wget --no-check-certificate -O e:\export.csv "http://localhost:8080/demo/?mode=CSV1&uname=agrant&upassword=skipper" |
|
Re: How to login and export to CSV using wget?, posted by Alan Grant on Sun Apr 24 06:49:33 2016
|
UPDATE:
After days of head banging and trying different syntax combinations, I finally stumbled on my own answer. It involved some syntax adjustments,
and then splitting the task into these two consecutive operations: |
|
Send email based on lookup of an attribute, posted by Rudy Taraschi on Thu Mar 31 16:31:45 2016
|
I'm trying to send an email based on an attribute, in other words, a lookup and not $user_email of the author.
For instance, if I set a an attribute "Assignee" with a valid user full name (i.e. John Smith), I'd like to look up John Smith's
|
|
Re: Send email based on lookup of an attribute, posted by Stefan Ritt on Mon Apr 4 14:09:42 2016
|
> I'm trying to send an email based on an attribute, in other words, a lookup and not $user_email of the author.
>
> For instance, if I set a an attribute "Assignee" with a valid user full name (i.e. John Smith), I'd like to look up John Smith's
|
|
Preloading Options or Moptions from a text file or CSV, posted by Francois Cloutier on Wed May 6 21:25:34 2015
|
Title says all :)
Is it possible to preload Options or Moptions from a text file or CSV instead of being load from the elogd.conf ?
|
|
Re: Preloading Options or Moptions from a text file or CSV, posted by Stefan Ritt on Wed May 6 21:30:13 2015
|
> Title says all :)
>
> Is it possible to preload Options or Moptions from a text file or CSV instead of being load from the elogd.conf ?
|
|
Re: Preloading Options or Moptions from a text file or CSV, posted by Francois Cloutier on Thu May 7 02:25:16 2015
|
> > Title says all :)
> >
> > Is it possible to preload Options or Moptions from a text file or CSV instead of being load from the elogd.conf ?
|
|
Re: Preloading Options or Moptions from a text file or CSV, posted by Stefan Ritt on Thu May 7 09:48:32 2015
|
Forget scripting under Windows, this is painful and not really working. Wrong OS for that.
But have you considered conditional attributes? With this you can load different option lists straight from the elogd.cf file. Use something like this:
|
|
Re: Preloading Options or Moptions from a text file or CSV, posted by Francois Cloutier on Thu May 7 14:37:39 2015
|
Not really...
The thing is I have to let some users the capacity of changing the content of that option list.. I was hoping there could be a different way for
them then to edit the cfg file...
|
|
Re: Preloading Options or Moptions from a text file or CSV, posted by Andreas Luedeke on Mon May 11 22:42:44 2015
|
> > > Title says all :)
> > >
> > > Is it possible to preload Options or Moptions from a text file or CSV instead of being load from the elogd.conf ?
|
|
Re: Preloading Options or Moptions from a text file or CSV, posted by Jimmy Bria on Fri Apr 1 18:45:01 2016
|
> Title says all :)
>
> Is it possible to preload Options or Moptions from a text file or CSV instead of being load from the elogd.conf ?
|
|
Re: Preloading Options or Moptions from a text file or CSV, posted by Stefan Ritt on Mon Apr 4 13:59:42 2016
|
> Did you ever get an answer or figure out how to preload Options from a CSV?
|
|
Read Validation, posted by Ed Strohak on Sat Apr 2 12:43:17 2016
|
I'm looking for config examples of a shift log book where operators have to check a box or select their name from a list to prove they
have read the latest entries in the log, can anyone help.
|
|
Re: Read Validation, posted by Stefan Ritt on Sat Apr 2 17:56:04 2016
|
Unfortunately a read confirmation is not foreseen in the Elog system. You would have to define one attribute for each shift worker, like "John has
read", "Steve has read" and so on. Then each of the shift workes has to "Edit" each message an check his/her checkmark manually.
Stefan |
|
Re: Read Validation, posted by David Pilgram on Sat Apr 2 21:21:04 2016
|
As a variant of what Stefan has suggested:
Perhaps a simple comment is set up as the pre-loaded reply - perhaps including date and time. Maybe include the author's name in the
comment, but all that is available anyway (see documentation for that). This bit isn't vital. |
|
Re: Read Validation, posted by Ed Strohak on Mon Apr 4 13:05:55 2016
|
Appreciate the help..
Thanks
David |
|
URL, posted by Neal Grafton on Tue Mar 15 09:26:40 2016
|
Hi
Can I asign a URL to a Radio Button to bring up another program? |
|
Re: URL, posted by Stefan Ritt on Tue Mar 22 12:47:50 2016
|
You can do this by adding manyallty some JavaScript to the page.
Neal
Grafton wrote:
Hi |
Re: URL, posted by Neal Grafton on Wed Mar 23 16:01:46 2016
|
OK thanks Stefan.
Thats another programming language I'll have to learn then. :-)
The Elog config I am just getting to grips with but Java and Scripts are a bit beyond me. |
|
Width of text field, posted by Edward Diehl on Tue Mar 22 18:28:03 2016
|
I use a elog which has a text field to show log entries: https://classis01.roma1.infn.it/elog/calib/ In the "Summary"
view there are only 3 lines of about 40 characters shown, so often the entry is cut off even though there is plenty of space in the text box for longer
lines. To see the full entry you must click on the ID number. Is there any way to configure the Text box to show longer lines? |
|
Re: Width of text field, posted by Andreas Luedeke on Wed Mar 23 11:40:52 2016
|
Did you try the options
Summary lines = x
Summary line length = x
as
documented in https://midas.psi.ch/elog/config.html#flags ? |
|
Installation: Failed Dependencies, posted by Phil Rubin on Fri Mar 11 17:29:47 2016
|
Is there anything I can do about this?
kernel: 2.6.32-279.14.1.el6.x86_64
ldd (GNU libc) 2.12 |
|
Re: Installation: Failed Dependencies, posted by Phil Rubin on Fri Mar 11 18:59:30 2016
|
I attempted instead to build from the tar ball, and, except for a "fatal" git error, make built elogd, elog, and elconv. I put
the first in /usr/local/sbin, and the latter two in /usr/local/bin, and then restarted elogd, but this didn't work:
Service Temporarily Unavailable |
|
Re: Installation: Failed Dependencies, posted by Phil Rubin on Fri Mar 11 19:24:11 2016
|
OK. I found the source of the logbook problem in an exchange from May 2015, so no need to answer this one.
But I would like to be able to upgrade to 3.x from 2.9, so any help with this will be much appreciated.
Phil |
|
Re: Installation: Failed Dependencies, posted by Darren Hollinrake on Sat Mar 19 15:24:29 2016
|
I did the following on CentOS 6.7 (Should work for Fedora and RHEL as well):
yum install -y wget
wget http://midas.psi.ch/elog/download/RPMS/elog-latest.i386.rpm |