Re: Logbook Parser, posted by Stefan Ritt on Tue Aug 11 08:29:23 2009
|
| 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. |
|
Re: List Option, posted by Stefan Ritt on Tue Aug 11 08:33:32 2009
|
| Alan Grant wrote: |
|
Currently this is defined as a maximum of 100 literals in the cfg file. I would like to see the option to reference an external text file as input for this.
|
I will put this on the wish list.
| Alan Grant wrote: |
|
As a side question, I would also like to increase the max to a greater value, for example, even 5000. I assume I can change the source (I recall var was something like "List_Option_Max") and see if that would still work, but would you know offhand if that would cause a problem anywhere else?
|
I limited this to 100 entries because it will be hard to handle it. Imagine a drop-down list box with 5000 entries. It would fill your complete screen and you still won't see all 5000 entries. In that case it might be better to use a free text field and enter the attribute value as free text.
You can increase MAX_N_LIST in elogd.c, but at some point you will get a stack overflow and elogd will just crash.
- Stefan
|
Re: Logbook Parser, posted by Steve Williamson on Tue Aug 11 13:02:22 2009
|
| 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
|
|
Re: Logbook Parser, posted by Stefan Ritt on Tue Aug 11 13:25:48 2009
|
| 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. |
Re: Logbook Parser, posted by Alan Grant on Tue Aug 11 16:25:28 2009
|
| 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. |
|
Re: Logbook Parser, posted by Steve Williamson on Wed Aug 12 14:40:52 2009
|
| 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!! |
fckeditor update, posted by Arno Teunisse on Tue Aug 25 21:08:51 2009
|
Hello
Just a few fckeditor related questions. How do elog versions and fckeditor versions relate. ?
Can I just drop another version of the fckeditor over an other version? What things should I consider when doing so ?
thanks for you're time.
|
|
Re: fckeditor update, posted by Stefan Ritt on Mon Aug 31 11:22:20 2009
|
| Arno Teunisse wrote: |
|
Hello
Just a few fckeditor related questions. How do elog versions and fckeditor versions relate. ?
Can I just drop another version of the fckeditor over an other version? What things should I consider when doing so ?
thanks for you're time.
|
The relation is not very "stong". In the past I updated between major version of fckeditor without chaning any elog code, so just give it a try. |