ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66328
|
Fri Apr 24 09:03:05 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.6 | Re: Is there a way to import old log messages |
Joseph Le wrote: |
I update my elog from version 2.7.5 to 2.7.6 and mistakenly replace configuration file. so i have to reconfigure everything from ground up. when my elog back online, old log messages are not show up. is there a way to import old log messages from old log book to new one.
thanks
|
You don't have to import old log book messages, they should be shown automatically (as long as you don't overwrite your configuration file mistakenly). If you had a different logbook name (not "demo") your files will still be there under c:\Program Files\ELOG\logbooks\<logbook name>. Just add the proper name in elogd.cfg, restart elogd and you will see your old messages. |
68441
|
Mon Oct 3 10:18:19 2016 |
| Alex Kühnel | alexander.kuehnel@gmail.com | Question | Linux | 3.1.2 | Re: Is there a way to export logs |
shame on me, there is a way!
I can search with find and then export as csv file
/alex
Alex Kühnel wrote: |
hello
Is there a way to export logs from elog (for example after I have selected a filter) to txt or csv...
I found the "Download" attribute but this works for only one elog entry...
regards
|
|
68719
|
Tue Jan 16 09:46:04 2018 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.2 | Re: Is there a python3 api to generate logbook entries from python? |
There are two options
- Wrap the "elog" command line tool
- Use "curl". Ther is a PycURL library http://pycurl.io/docs/latest/ which can be used, so you don't have to call any command line tool. The usage of curl is described in elog:68597
Stefan
markus wrote: |
Dear elog community,
I wonder whether there is a python3 api or lib to generate and append entries (and attachments) to the logbook using scripts.
However, so far I did not find anything...
At the moment I am thinking about wrapping the "elog" command line tool.
Is there something usable already out there?
Thanks and regards
Markus
|
|
68720
|
Tue Jan 16 10:13:00 2018 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 3.1.2 | Re: Is there a python3 api to generate logbook entries from python? |
Have a look here: https://github.com/paulscherrerinstitute/py_elog
I haven't tried it myself, but it should allow you to add, reply, edit, delete elog entries from python (>= 3.5) via the http elog interface. It's an anaconda package.
markus wrote: |
Dear elog community,
I wonder whether there is a python3 api or lib to generate and append entries (and attachments) to the logbook using scripts.
However, so far I did not find anything...
At the moment I am thinking about wrapping the "elog" command line tool.
Is there something usable already out there?
Thanks and regards
Markus
|
|
68723
|
Wed Jan 24 07:54:47 2018 |
| markus | markus.ries@helmholtz-berlin.de | Question | Linux | 3.1.2 | Re: Is there a python3 api to generate logbook entries from python? |
Thanks Andreas!
This is more or less exactly what I was looking for...
Regards
Markus
Andreas Luedeke wrote: |
Have a look here: https://github.com/paulscherrerinstitute/py_elog
I haven't tried it myself, but it should allow you to add, reply, edit, delete elog entries from python (>= 3.5) via the http elog interface. It's an anaconda package.
markus wrote: |
Dear elog community,
I wonder whether there is a python3 api or lib to generate and append entries (and attachments) to the logbook using scripts.
However, so far I did not find anything...
At the moment I am thinking about wrapping the "elog" command line tool.
Is there something usable already out there?
Thanks and regards
Markus
|
|
|
2221
|
Fri Apr 27 08:38:58 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.6.3-1764 | Re: Is there (planned) support for <A NAME> and <HR /> in ELCODE? |
Kevin McCarty wrote: | I am wondering if there is any support (or if not, if it is planned) for inserting HTML <a name> and <hr /> tags via ELCODE. |
Very good idea. The horizontal line is already implemented via [LINE] and the anchor tag will soon follow. |
2222
|
Fri Apr 27 08:56:10 2007 |
| Kevin McCarty | kmccarty@princeton.edu | Request | Linux | 2.6.3-1764 | Re: Is there (planned) support for <A NAME> and <HR /> in ELCODE? |
Stefan Ritt wrote: |
Kevin McCarty wrote: | I am wondering if there is any support (or if not, if it is planned) for inserting HTML <a name> and <hr /> tags via ELCODE. |
Very good idea. The horizontal line is already implemented via [LINE] and the anchor tag will soon follow. |
Wonderful, thanks!
-- Kevin McCarty |
2223
|
Fri Apr 27 13:06:59 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.6.3-1764 | Re: Is there (planned) support for <A NAME> and <HR /> in ELCODE? |
Kevin McCarty wrote: | I am wondering if there is any support (or if not, if it is planned) for inserting HTML <a name> and <hr /> tags via ELCODE. This would be useful for long log messages in order to provide a table of contents and divide them into clear sections. If this support already exists, I'm afraid it is not obvious to me how to access it in ELCODE. If it does not yet exist, would you consider a patch for it?
As a related issue, to support <a name> usefully, it will also be necessary for ELCODE to support things like [url=#tag], which it currently converts to <a href = "http:///#tag"> instead the expected result of <a href = "#tag">. |
I implemented anchor tags. You can write something like
[ANCHOR]top[/ANCHOR]
and you can then reference it either by directly entering
http://midas.psi.ch/elogs/Forum/2223#top
or by entering simply
elog:2223#top
To make your table of contents, you can put a complete URL tag like
[URL=http://midas.psi.ch/elogs/Forum/2223#top]Goto top[/URL]
or inside the same entry simply
[URL=#top]Goto top[/URL]
which will be shown as
Goto top
I have added these link again at the bottom of this entry so you can try it with this entry directly.
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
elog:2223#top |