ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
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. |
66643
|
Tue Dec 8 18:57:31 2009 |
| John Lemko | jlemko@hotmail.com | Question | Windows | latest | Certificate Error |
Is there any documentation I can go through that explains how to remove the Certificate Error I am getting as shown in the attachment. I have tried creating my own certificate and putting it in the elog ssl folder but that just prevented the elog service from starting. Any help would be greatly appreciated. Thanks. |
66693
|
Sun Jan 24 18:00:11 2010 |
| Kenneth McFarlane | kenneth.mcfarlane@hamptonu.edu | Comment | Windows | 2.7.8 | first install comments |
I am testing Elog for personal and group use. I am starting with a Windows install on a PC. (I came across Elog when doing a shift on ATLAS at CERN.)
It took me some time to discover how to access a local logbook and create a new one. I suggest adding short sections in a prominent place in the guides:
User guide:
"Accessing a logbook: To access a logbook, point your Web browser at the appropriate URL. The default for a local Elog is http://localhost:8080/logbookname. Logbook files are stored in directory logbookname which is a sub-directory of the logbook root directory, defined by the administrator. See the administrator guide on how to create a new logbook."
Admin guide:
"Creating a logbook: A logbook is created in three steps: 1) The logbook root directory is defined as an option of the elogd start command; 2) A sub-directory, of the logbook root directory, named logbookname is created; and 3) The elogd.cfg file is edited to define the logbook's attributes and options. No files are created in the sub-directory; that is done when entries are made."
Regards,
Ken McF |
66704
|
Tue Feb 9 14:41:02 2010 |
| Sara Vanini | sara.vanini@pd.infn.it | Question | Linux | last | defult format in entry window |
Hi,
is there a way to set default preferences for text in entry text window, as regards : font type, font size, line spacing, paragraph, etc...
Thanks
Sara
|
66782
|
Thu Apr 8 18:06:25 2010 |
| Gary Wilcox | Gary.Wilcox@aleris.com | Question | Linux | 2.7.8 | Submit Buton |
When entering data for a new log entry some folks always type in an attribute and then the "Enter" key which automatically
submits the entry. Is there a way to prevent this so the only way a new entry is submitted is with the Submit button. Also
is there a way to setup the main text box as a required attribute?
Thanks
Gary |
66963
|
Wed Dec 1 17:03:01 2010 |
| Mariusz Stakowski | Mariusz.Stakowski@asseco.pl | Comment | Linux | 2.8.0 | Re: New password file problem |
Stefan Ritt wrote: |
Mariusz Stakowski wrote: |
Hello,
I'm new to elog. I've installed it under Slackware 11. Everything worked smoothly until I wanted to establish access control. I followed the steps described under Access control heading in Syntax of elog.cfg chapter. I specified a new password file name and the following steps with no problem. After having created a new user I stopped elogd and added Admin user to config file. And here is my problem - each time I want to login to elog, I get "Invalid user name or password!" message. The meaning of it is obvious. So I have repeated all the steps several times. Of course I paid attention to enter user name and password correctly but I can't get rid of this message. For sure I making something wrong, but what it is ?
|
Can you try the current SVN version?
http://savannah.psi.ch/websvn/filedetails.php?repname=elog&path=/trunk/src/elogd.c&rev=0&sc=0
There has been some issues with the password encoding, maybe this is fixed now.
|
Thank you Stefan, it works now
Best regards
Mariusz Stakowski
|
67036
|
Wed Mar 30 13:46:01 2011 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Info | Linux | Windows | ELOG V2.7 | Re: Attributes for message workflow. |
Ryan wrote: |
[...] I am even open to losing the historical "status" and beeing able to change all entries on the thread on reply. (i.e. Reply #4 changes "Status" to "Approved", and the system changed all entries in the thread to "Approved")
|
One possibility is to use the new 2.9.0 feature "Propagate attributes = OPS Approval, ENG Approval, Director Approval"
A change in any of the three listed attributes would propage to the corresponding fields of all former entires of the same thread.
So if someone creates a reply and changes "OPS Approval" to "Approved", the field "OPS Approval" of the original entry would go as well to "Approved".
I just happen to know about this feature because Stefan implemented it for me :-) |
67081
|
Fri Jun 3 12:06:20 2011 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Info | Linux | 2.9.0-2414 | Re: elogd crashes when running mirror cron with SSL and KRB5 |
> When I run a mirror server and both logbooks using SSL/KRB5 then the cron job causes a segmentation fault.
>
> I haven't tried to check it with a simple configuration yet.
> My set-up: two elogd on same server, one running "german" on port 444, the other "english" on port 445.
> Both are behind an apache webserver configured reverse proxy, to hide the ports for external access.
> I'll try to reproduce the fault with a "minimal configuration" soon and report again.
>
I've tried to test a simpler configuration on my local PC but failed:
all simple set-ups I've tried worked fine.
I found that the mirror cron synchronization works fine in my production set-up when I remove the line:
Mirror user = luedeke
But I can have this line in my simple test set-up and it still works fine.
Anyway: bugs closed for me. |