ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66517
|
Wed Aug 19 11:49:37 2009 |
| Johannes Liegl | Johannes.Liegl@gefanuc.com | Request | Linux | Windows | 2.7.2-2012 | multiple keyword search - regular expression | Dear Sirs,
searching for keywords regular expression becomes very long. Are there any other type easy multiple keyword search supported. For example a keyword search like keyword1 & keyword2 results in different output than a keyword search like keyword2 & keyword1. A simple keyword search like "keyword1 & keyword2 and keyword2 &keyword1 should find all documents in a database containing both keywords resulting in the same output.
Thank you very much for you help in advance.
Best Regards
Johannes Liegl
|
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!! |
66515
|
Tue Aug 11 17:46:33 2009 |
| Dennis Seitz | dseitz@berkeley.edu | Comment | Linux | 2.7.7-2251 | Re: Comment on: Alphabetize Quick Option filter | Yes, many thanks, Stefan, from me, too! It's really great that you respond so quickly to requests and suggestions.
And thanks to David for the fine tuning, great suggestion.
Dennis
> Thanks Stefan! Works great.
>
> > Ok, that makes sense, so I changed it to
> >
> > Sort Attribute Options Status = 1
> >
> > as you suggested.
> >
> > > (For some reason I could not add this in Dennis's thread.)
> > >
> > > I like this new feature, BUT
> > >
> > > I happen to have two Options: Options System, and Options Status.
> > >
> > > System are a very few items, whereas Status has a long list, which, like Dennis's example, can be added to.
> > > Keeping the latter in alpha order is great, but it's a shame that the cost is that Options System are also
> > > sorted alphabetically, whereas it has a natural order which it would be preferable to keep - for example (and
> > > this is made up)
> > >
> > > Options System: 3.1, NT, 2000, XP, Vista
> > >
> > > where the natural order here is chronological.
> > >
> > > Perhaps the configuration file option could be more specific, for example
> > >
> > > Sort attribute Options Status = 1
> > >
> > > which would then NOT sort Options System. If both are needed to be sorted, both should be specified, or back to
> > > the original syntax which defaults to sort *all* Options. |
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. |
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. |
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
|
66511
|
Tue Aug 11 10:07:08 2009 |
| David Pilgram | David.Pilgram@epost.org.uk | Comment | Linux | 2.7.7-2251 | Re: Comment on: Alphabetize Quick Option filter | Thanks Stefan! Works great.
> Ok, that makes sense, so I changed it to
>
> Sort Attribute Options Status = 1
>
> as you suggested.
>
> > (For some reason I could not add this in Dennis's thread.)
> >
> > I like this new feature, BUT
> >
> > I happen to have two Options: Options System, and Options Status.
> >
> > System are a very few items, whereas Status has a long list, which, like Dennis's example, can be added to.
> > Keeping the latter in alpha order is great, but it's a shame that the cost is that Options System are also
> > sorted alphabetically, whereas it has a natural order which it would be preferable to keep - for example (and
> > this is made up)
> >
> > Options System: 3.1, NT, 2000, XP, Vista
> >
> > where the natural order here is chronological.
> >
> > Perhaps the configuration file option could be more specific, for example
> >
> > Sort attribute Options Status = 1
> >
> > which would then NOT sort Options System. If both are needed to be sorted, both should be specified, or back to
> > the original syntax which defaults to sort *all* Options. |
66510
|
Tue Aug 11 08:38:56 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Comment | Linux | 2.7.7-2251 | Re: Comment on: Alphabetize Quick Option filter | Ok, that makes sense, so I changed it to
Sort Attribute Options Status = 1
as you suggested.
> (For some reason I could not add this in Dennis's thread.)
>
> I like this new feature, BUT
>
> I happen to have two Options: Options System, and Options Status.
>
> System are a very few items, whereas Status has a long list, which, like Dennis's example, can be added to.
> Keeping the latter in alpha order is great, but it's a shame that the cost is that Options System are also
> sorted alphabetically, whereas it has a natural order which it would be preferable to keep - for example (and
> this is made up)
>
> Options System: 3.1, NT, 2000, XP, Vista
>
> where the natural order here is chronological.
>
> Perhaps the configuration file option could be more specific, for example
>
> Sort attribute Options Status = 1
>
> which would then NOT sort Options System. If both are needed to be sorted, both should be specified, or back to
> the original syntax which defaults to sort *all* Options. |
|