ELOG Forum

You can define the building number as an attribute and use it in a quick filter. The startview will however not stay on one bilding. An alternative would be to define one logbook per building.

OK!

Thanks for the answer.
I thought that this was the way to go. The problem is that we have several hundreds of buildings.

/UlfO

67530

Tue Jun 4 16:52:18 2013

Re: Filter and sorting

UlfO wrote:

Hi,

We have a fire preventive team at our company doing periodic inspections of our various corporate buildings.

If they find a deviation they want to register this somewhere.

So I thought E-log would be nice to use in this case.

The way the fire preventive team inspection works is building by building.

All the buildings has numbers.

So they want to be able to select a buildingnumber in E-log and filter on open,ongoing and closed records when they do their inspections.

And they also wants the filtering to stay on that choosen buildingnumber despite if they delete or add new entries.

I know that you can have a default startview in E-log but this view is static.

Is it possible to do this in E-log?

You can define the building number as an attribute and use it in a quick filter. The startview will however not stay on one bilding. An alternative would be to define one logbook per building.

67529

Tue Jun 4 16:17:22 2013

Re: Export entries to XLS or CSV?

Stefan Ritt wrote:

Andreas Luedeke wrote:

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?

⇄

Detect language » English

⇄

Detect language » English

Hi Jim, can you confirm that this works for you? If so, I'm willing to incorporate the patch into the distribution.

I do not have the ability to compile a Windows executable, if someone does I'd be happy to test it out and report my results.

Thank you in advance!

67528

Tue Jun 4 15:00:23 2013

David Pilgram

David.Pilgram@epost.org.uk

Question

Linux

2.9.2-2475

Re: Sorting by numeric attribute (not entry ID).

> > By default, elog enties are sorted by their ID number.  When viewing a logbook in Full or Summary, they are
> > shown in strict order of ID.  In Threaded, entries are shown in strict order of ID for the latest entry of each
> > thread, and then previous entries (in reply to) back from the latest one.  
> > 
> > In collapsed mode, it is only the starting entry of each thread is shown (or the latest one if "collapse to
> > last" chosen, but that's a detail).
> > 
> > I have a couple of logbooks where I'd like the default sorting to be by another numeric attribute that I enter. 
> > 
> > Now this works fine in Full or Summary mode.  In threaded mode (e.g. default for this forum, where every entry
> > is shown but are grouped by thread), it works in as much as all the entres are there and in order, but it
> > doesn't quite look the same as when sorting by ID - the replies are not each offset further right beneath the
> > entry it is in reply to, but all just slightly offset to the first entry.  
> > 
> > If you try to [completely] collapse the threaded mode to just one line per threaded topic - it doesn't.  Looks
> > (almost) the same as threaded.
> > 
> > I was hoping to get the list of entries collapsed to one line per thread, in order of the numeric attribute, but
> > I cannot seem to get this to happen.   Have I missed something here?  Or is it possible at all?
> 
> This is not possible at the moment, but I will add it to the wish list.

OK, Thanks Stefan.

67527

Tue Jun 4 13:26:02 2013

Martin Rongen

martin.rongen@rwth-aachen.de

Question

Linux

2.9.2

Re: Daemonizing vs. shell execution

Stefan Ritt wrote:

Martin Rongen wrote:

Hi all

I have setup an logbook that executes a number of shell scripts to preset attributes and append standart information, which works great. Now I am trying to daemonise the whole thing. I have tried the -D option as well as daemontools. In both cases the logbook itself is functional but the bash scripts do not get executed.

Any ideas how I can resolve this problem?

Martin

Usually the problem comes from the fact that a daemon runs from the root directory ('/') by definition. I might not find your scripts if they are not in the path. Try to call them explicitly with the ful path like "/usr/local/elog/script.sh".

/Stefan

I didn't know that. Thanks for the quick response. I have it working now :)

67526

Tue Jun 4 12:38:01 2013