ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
301
|
Tue Apr 22 20:06:51 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | | Re: Converting logs | > `elconv' is just a simple tool to convert pre 2.0 log files to the current
> format. (Well, after all these confusions, dropping it from the future
> releases won't be surprising -at least for me- ;) You might try some
> well-known text-processing tools ie. preferably awk or perl to make the
> required conversions. But I think using comma or tab as the delimiter is
not
> suitable due to the content of logs. If all you want is importing them to
> excel/word, you should play with the delimiter options of mentioned
programs
> before trying a solution.
Hi Recai. I have several requests of this kind. "Want to import/export to
comma separated text" or "XML". So one option is to extend elconv to handle
all kind of conversions 1.x -> 2.x, 2.x -> CSV, 2.x -> XML. An alternative
would be to write some awk/perl scripts as you noted. The disadvantage of
this solution would be that they rely on the installation of awk/perl which
is not given on windows systems. But nevertheless, if anyone volunteers to
write a conversion tool, I would be happy to include it in the distribution.
If not, I can put it into elconv.c, but that could take until June, given my
current work load. |
65711
|
Thu Jan 24 16:50:16 2008 |
| Fergus Lynch | flynch@alternativenetworks.com | Question | Windows | V2.7.1-200 | Re: Converting dates from an Excel import into ELOG |
Fergus Lynch wrote: |
Hi,
I'm importing an Excel spreadsheet into ELOG through CSV format. All working fine apart from dates.
Dates are exporting from Excel in the format "day/month/year" so 1st January 2008 is exported as 01/01/2008 in the CSV.
However all dates are displayed in ELOG as "01/01/1970" regardless of the field content, and looking at the raw ELOG data file dates are displayed as numeric's - so for example 01/01/2008 is "1199188800"
Can you tell me how dates are computed/stored in ELOG so that I can do the necessary conversion.
Many Thanks
Fergus
|
S'ok - looked up the documentation and have converted Excel dates to ELOG 'seconds since 01/01/1970' and all has come over fine!
Thanks
Fergus |
66108
|
Fri Dec 12 07:45:14 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Windows | 2.7.5-2140 | Re: Conflict between Select-Edit and attribute types |
Richard Stamper wrote: |
When doing a Select->Edit operation, if an attribute has a type of "numeric" and the records selected already have (some) values for that attribute, then the "- keep original values -" message that is inserted to indicate that the values should be preserved causes the type check to fail.
Would it be possible to modify the Javascript that carries out the type check to treat the "- keep original values -" message as an exception?
|
Thanks for reporting this. It has been fixed in SVN revision 2155. The fix will be contained in the next release. |
67753
|
Fri Jan 16 14:29:58 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | - | Re: Configure default time range in 'Find' | Have you tried in the "Find" page to set a start date, or select "Show last: Month". This shoudl speed up searching quit a bit.
Eoin Butler wrote: |
Hello,
We have a very large elog database, and executing a 'Find' on the whole range takes several minutes, locking other users out of the elog for that time. It would be very nice if there could be an option to set the default value of the 'search last ...' option on the find page. Thanks in advance!
|
|
67754
|
Mon Jan 19 11:09:31 2015 |
| Eoin Butler | eoin.butler@cern.ch | Request | All | - | Re: Configure default time range in 'Find' | Yes, this works, but users inevitably forget to select "last week" or whatever, and just leave it blank, which means their search unintentionally takes a long time. It would be much better if one could configure it to default to something "fast".
Stefan Ritt wrote: |
Have you tried in the "Find" page to set a start date, or select "Show last: Month". This shoudl speed up searching quit a bit.
|
|
67755
|
Mon Jan 19 17:17:32 2015 |
| David Pilgram | David.Pilgram@epost.org.uk | Request | All | - | Re: Configure default time range in 'Find' | Hi there, In the "Find" page, I changed the default of the "Show last" drop down box in the Entry Date section from the (unstated) "All time" to "Day", and added back in an "All Time" option at the very bottom. This gives a default of searching the last day, and one has to think and select the period of time to search back on.
I did this on my 2.9.2-2475 version, recompiled and it works. Two lines of code changed and even my cr*ppy coding was up to the task. I don't know if Stefan would want to put this into the Master copy (I'll forward the changes if you want Stefan, but it's pretty easy if I can do it), but if you can edit and recompile (Eoin) I can tell you which to lines for immediate functionality. Back up everything first, though!
Eoin Butler wrote: |
Yes, this works, but users inevitably forget to select "last week" or whatever, and just leave it blank, which means their search unintentionally takes a long time. It would be much better if one could configure it to default to something "fast".
Stefan Ritt wrote: |
Have you tried in the "Find" page to set a start date, or select "Show last: Month". This shoudl speed up searching quit a bit.
|
|
|
67756
|
Tue Jan 20 00:58:58 2015 |
| David Pilgram | David.Pilgram@epost.org.uk | Request | All | - | Re: Configure default time range in 'Find' | It has just occurred to me that you may also have to check the non-English files, (./resorces/eloglang_xxxx) as this change introduces a new term "All time" that would need translation into the other lexicons.
By the way, in further testing, the "Show last" selection over-rides whatever two dates are selected, so if you ask for any entry in Dec 2014, but the "Show last" selects "week", nothing is found - very quickly. I trust that is what you're after, Eoin. I'll keep my change to the coding, but that's personal choice.
David.
David Pilgram wrote: |
Hi there, In the "Find" page, I changed the default of the "Show last" drop down box in the Entry Date section from the (unstated) "All time" to "Day", and added back in an "All Time" option at the very bottom. This gives a default of searching the last day, and one has to think and select the period of time to search back on.
I did this on my 2.9.2-2475 version, recompiled and it works. Two lines of code changed and even my cr*ppy coding was up to the task. I don't know if Stefan would want to put this into the Master copy (I'll forward the changes if you want Stefan, but it's pretty easy if I can do it), but if you can edit and recompile (Eoin) I can tell you which to lines for immediate functionality. Back up everything first, though!
Eoin Butler wrote: |
Yes, this works, but users inevitably forget to select "last week" or whatever, and just leave it blank, which means their search unintentionally takes a long time. It would be much better if one could configure it to default to something "fast".
Stefan Ritt wrote: |
Have you tried in the "Find" page to set a start date, or select "Show last: Month". This shoudl speed up searching quit a bit.
|
|
|
|
67759
|
Thu Jan 22 16:30:07 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | - | Re: Configure default time range in 'Find' | I added a new optoin "Show last default = <days>", where one can pre-set the "Show last" drop-down box. I think this is a good idea, so now people can configure their elog to a certain default in this parameter. Of course all settings in the Find page are AND'ed together, so if one restricts the search to tha last week, but then looks for a date more in the past, the result will be zero by definition. The change is in the GIT repository. If you cannot recompile the code yourself, you have to wait for the next release.
David Pilgram wrote: |
By the way, in further testing, the "Show last" selection over-rides whatever two dates are selected, so if you ask for any entry in Dec 2014, but the "Show last" selects "week", nothing is found - very quickly. I trust that is what you're after, Eoin. I'll keep my change to the coding, but that's personal choice.
|
|
|