| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66512
|
Tue Aug 11 13:02:22 2009 |
 | Steve Williamson | StephenWilliamson@Barnsley.gov.uk | Question | Windows | 2.6.5 | Re: Logbook Parser |
| Stefan Ritt wrote: |
|
| Alan Grant wrote: |
|
We are exploring whether it's possible/feasible to import ELog logbooks into a another database for special purposes (plotting/statisical, etc). Target database is TBD (perhaps Access).
Does anyone have or know of a logbook parser program? From cut/pasting into, for example, Excel, it does appear that the data fields are already line-feed delimited so offhand it would seem possible to parse if one really wanted to pursue it.
Regards,
- Alan
|
You can export to CSV (comma-separated-values) if you go to "Find" and then click on "Export: CSV". These fiels you ran read right into Excel or other spreadsheet programs for further analysis.
|
excuse my butting in ... I've found the exports useful in the past - however, is is possible to run the export from a script in order to produce reports? Utilities like wget won't work as the export process doesn't return the data as html.
regards
Steve
|
|
66513
|
Tue Aug 11 13:25:48 2009 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.6.5 | Re: Logbook Parser |
| Steve Williamson wrote: |
|
excuse my butting in ... I've found the exports useful in the past - however, is is possible to run the export from a script in order to produce reports? Utilities like wget won't work as the export process doesn't return the data as html.
|
That's not true. wget does work. Try that one:
wget --no-check-certificate -O export.csv https://midas.psi.ch/elogs/linux+demo/?mode=CSV1
actaully wget doesn't care if the return is HTML or a GIF image or anything else, it just saves it into the output file. |
|
66514
|
Tue Aug 11 16:25:28 2009 |
 | Alan Grant | netman311@mts.net | Question | Windows | 2.6.5 | Re: Logbook Parser |
| Steve Williamson wrote: |
|
| Stefan Ritt wrote: |
|
| Alan Grant wrote: |
|
We are exploring whether it's possible/feasible to import ELog logbooks into a another database for special purposes (plotting/statisical, etc). Target database is TBD (perhaps Access).
Does anyone have or know of a logbook parser program? From cut/pasting into, for example, Excel, it does appear that the data fields are already line-feed delimited so offhand it would seem possible to parse if one really wanted to pursue it.
Regards,
- Alan
|
You can export to CSV (comma-separated-values) if you go to "Find" and then click on "Export: CSV". These fiels you ran read right into Excel or other spreadsheet programs for further analysis.
|
excuse my butting in ... I've found the exports useful in the past - however, is is possible to run the export from a script in order to produce reports? Utilities like wget won't work as the export process doesn't return the data as html.
regards
Steve
|
Steve, just a word of thanks for "butting in" ... my next thought was how could I schedule an export to feed the other database so it wouldn't have to be done manually each day. Your question took care of that for me! :)
Good community. Thanks. |
|
66516
|
Wed Aug 12 14:40:52 2009 |
| Steve Williamson | StephenWilliamson@Barnsley.gov.uk | Question | Windows | 2.6.5 | Re: Logbook Parser |
| Stefan Ritt wrote: |
|
| Steve Williamson wrote: |
|
excuse my butting in ... I've found the exports useful in the past - however, is is possible to run the export from a script in order to produce reports? Utilities like wget won't work as the export process doesn't return the data as html.
|
That's not true. wget does work. Try that one:
wget --no-check-certificate -O export.csv https://midas.psi.ch/elogs/linux+demo/?mode=CSV1
actaully wget doesn't care if the return is HTML or a GIF image or anything else, it just saves it into the output file.
|
you're right, of course, on all counts!
when I was testing wget/elog to try to automate an extract I was getting a lot of stuff like:
/Change_Log/587">Software Only</a></td><td class="92^M^H<88>^\ÿ^Y"ÿ"><a href="../Change_Log/587">23416</a></td><td class="92^M^H<88>^\ÿ^Y"Ã<a href="../Change_Log/587">New</a></td><td class="92^M^H<88>^\ÿ^Y"ÿ"><a href="../Change_Log/587">Awaited</a></td>
but I must have been getting something wrong, using your command line as an example it works perfectly! Thanks again for elog!! |
|
69448
|
Tue Dec 14 21:55:16 2021 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 3.1.4 | Re: Log4j exploit |
ELog does not use the Log4j library so no issue there. If you run a web server like Apache in front of ELog, you however have to check if you use log4j there.
| Alan Grant wrote: |
|
Is there any potential impact/concern with the Log4j exploit in Elog applications?
|
|
|
66722
|
Mon Feb 22 11:15:48 2010 |
| Yoshio Imai | | Question | Linux | latest | Re: Log Thread Close Automatically |
| tom wrote: |
|
If you have a logbook and you create a new entry, is it possible to put a time limit on that new entry so that edits/replies are only valid for certain amount of time. I am looking for a way that would allow me to have a user start a new message, but after 8 hours, that message becomes locked and no one can edit or add to the message. This is for some shift work and we do not want users to go back after their shift and edit the messages.
|
Did you consider using the "Restrict edit time" option? It should provide the necessary functionality, as long as you don't want to lock the entry at a fixed absolute time, but really only x hours after creation (also, as you talked about closing the "thread" automatically, there is no option to prevent replies after a certain amount of time).
See the administrator's guide. |
|
66748
|
Fri Mar 12 09:18:11 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | latest | Re: Log Thread Close Automatically |
| tom wrote: |
|
If you have a logbook and you create a new entry, is it possible to put a time limit on that new entry so that edits/replies are only valid for certain amount of time. I am looking for a way that would allow me to have a user start a new message, but after 8 hours, that message becomes locked and no one can edit or add to the message. This is for some shift work and we do not want users to go back after their shift and edit the messages.
|
What you need is
Restrict edit time = ...
as written in the manual. |
|
574
|
Wed Jul 7 18:13:26 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.5.3 | Re: Locking the Text field |
> Is there a way to disable editing of the textarea, but still allow editing
> of other fields in the entry? (e.g. Fixed Attributes Edit = Text)
I could add that option, but I don't know if it helps you (see below).
> Also, is the data entered in that field accessible through a variable like
> $author? I tried $text, but that doesn't seem to work.
No, that won't work. Attributes are limite to some 500 characters, while the
text body is limited to 250000 characters. If you add $text to an attribute, it
would overflow or you would have to truncate the text, which I guess is not
good in both cases.
If you still want "Fixed attributes edit = text", please explain me you exact
case and I will consider implementing it. |