Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 340 of 807  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Categorydown OS ELOG Version Subject
  67524   Mon Jun 3 20:02:38 2013 Question David PilgramDavid.Pilgram@epost.org.ukQuestionLinux2.9.2-2475Sorting 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?
  67525   Tue Jun 4 12:03:18 2013 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.9.2-2475Re: 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.
  67527   Tue Jun 4 13:26:02 2013 Reply Martin Rongenmartin.rongen@rwth-aachen.deQuestionLinux2.9.2Re: 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 :)

  67528   Tue Jun 4 15:00:23 2013 Reply David PilgramDavid.Pilgram@epost.org.ukQuestionLinux2.9.2-2475Re: 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.
  67530   Tue Jun 4 16:52:18 2013 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.9.2-2455Re: 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. 

  67531   Tue Jun 4 17:02:32 2013 Reply UlfOulf.olsson@dynamate.seQuestionWindows2.9.2-2455Re: Filter and sorting

Stefan Ritt wrote:

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. 

 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

 

 

 

  67532   Tue Jun 4 17:07:04 2013 Question UlfOulf.olsson@dynamate.seQuestionWindows2.9.2.2455Latest windows version vs 2.9.2.2455

 

What is the differences between E-log windows version 2.9.2-2455 like we run and E-log windows version 2.9.2.-2475 ?

I cant find a changelog for this.

Best regards
/UlfO

 

  67533   Tue Jun 4 17:07:13 2013 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.9.2-2455Re: Filter and sorting

UlfO wrote:

Stefan Ritt wrote:

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. 

 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 

Ouch! In principle the filtering could be stored in some cookie, but I would have to develop this, and I have currently no time for that. 

ELOG V3.1.5-3fb85fa6