ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 706 of 806

Not logged in

Find | Login | Help

Full | Summary | Threaded | Show attachments

6445 Entries

Goto page Previous 1, 2, 3 ... 705, 706, 707 ... 804, 805, 806 Next

Mon Jan 7 16:43:27 2013

Re: How to put "Quote text" _below_ new message?

If you use HTML encoding, you can do that with

Prepend on reply = <br />

to achieve the same thing (as I did just here in this reply).

Stefan

David Pilgram wrote:

Valentin wrote:

Hi there,

It seems that by default in a message created as "reply" of another message, the "quoted text" of the original entry is put at the _TOP_ of the new entry and not movable (Firefox 17, elog 2.92). I would strongly like to have it opposite, i.e. that one is able to create a new text first and only then has the "quoted text" since people are interested to see a new information and only then the previous messages as sort of "reminder". It was like this in older (2.6?) version but now I did not find how to change this default behavior. Did I miss something?

Cheers

Valentin

I use plain encoding, cannot answer for the others but it should do the trick as it's in the documentation. I'm using Firefox some large number and 2.9.2.-2475

I do what I believe you want, and get it by having the following line in my config file for that logbook (which is part of elog.cfg):

Prepend on reply = \n

This gives a blank line at the "top" of the entries when you start a reply, and all the previous entries gain another "> " unless you've also altered that default behaviou (as in fact I have). The result then looks like:

Latest line of text

> Previous entry

> > Previous entry to that

67518

Fri May 31 11:41:48 2013

Andreas Luedeke

andreas.luedeke@psi.ch

Bug fix

All

2.9.2-2481

Re: Export entries to XLS or CSV?

Jim Tinlin wrote:

Andreas Luedeke wrote:

scogordo wrote:

I've been asked to export one of our logbooks to xls or csv. Doable?

Thanks,

Scott

Hi Scott,

yes, every user can export entries using the "find" command.

Just select the export format in the first line

Export to: CSV ("," separated) CSV (";" separated) XML Raw

I often use the XML Format, but CSV is fine if you just want to import the entries to some spreadsheet program.

I was shocked to find out that this feature has not yet made it into the documentation?!? But it is that simple to use that there is not much to document.

There is even an "Import" command, to reimport entries from a file. But this is tricky to use: if you have fields of type date or datetime, then you have to convert those fields in the proper format.

I tried EXPORTING logbooks as .csv but have not been fully successful. Elog seems to only export the data entered for various fields with the exception of the text field.

Here is an example export from my logbook (used to track simulator problems), I would like to also export the TEXT field so it can be used by my managers in excel...but as you can see there is no entry for "TEXT" fields...

Thanks in advance!

"Message ID","Date","Author","Type","Status","Priority"

107,Thu 30 May 2013 11:28:57 -0700,"Jim Tinlin","Graphic Display","Evaluated","Low"

106,Thu 30 May 2013 10:02:24 -0700,"Jim Tinlin","Graphic Display","Identified","Low"

105,Thu 30 May 2013 08:07:27 -0700,"Jim Tinlin","Problem ID","Identified","Medium"

104,Thu 30 May 2013 08:04:30 -0700,"Jim Tinlin","Problem ID","Identified","Medium"

103,Wed 29 May 2013 09:36:11 -0700,"Jim Tinlin","Problem ID","Evaluated","High"

102,Wed 29 May 2013 08:58:02 -0700,"Jim Tinlin","Problem ID","Evaluated","High"

Yes, you're right: the text field is only exported in XML and Raw mode.

It is questionable how EXCEL should cope with HTML or ELCode output from the text fields.

But I admit that this would be a useful feature for logbooks that only use plain text entries. And it is simple to implement.

I've attached a patch to elogd.c from elog-2.9.2-2081 that adds a third CVS mode 'CSV (";" separated) + Text'.

(This string has not yet been added to the localization.)

As far as I've tested it works fine to import the text to OpenOffice and EXCEL, even with multiple text lines and HTML code in the text.

Of course the spreadsheet programs just display the HTML source.

Stefan, do you think this should be added to the official branch?

67526

Tue Jun 4 12:38:01 2013