Pre-populate Attachments in URL, posted by Erik Iverson on Thu Aug 6 22:29:12 2009
|
| Is there a way to pre-populate the new entry window with one or more attachments? Per the documentation, this is easy to do with attributes, i.e., http://localhost:8070/demo/?cmd=New&pauthor=joe&ptype=Info as a URL or bookmark will do it. I'd like to do the same thing with attachments, for example http://localhost:8070/demo/?cmd=New&pauthor=joe&ptype=Photograph&attfile1=picture1.jpg&attfile2=picture2.jpg might prepopulate two attachments, giving me an edit window all ready to enter the brief description represented by the two pictures. |
Re: Pre-populate Attachments in URL, posted by Stefan Ritt on Fri Aug 7 08:36:19 2009
|
That would be nice, I want this, too! But unfortunately your browser does not allow this for security reasons, and I found no way around. Assume you look to a page on the internet, and it pre-populates a file selector with something like /etc/passwd or any other sensitive file. Then this box gets hidden by some CSS style so you don't see it. So as soon as you click on something on that page, your sensitive files gets submitted, and you don't want that. Therefore it's impossible to pre-populate file selector boxes.
- Stefan |
Logbook Parser, posted by Alan Grant on Tue Aug 11 00:20:11 2009
|
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 |
|
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: 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!! |
|