Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 730 of 808  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Emaildown Category OS ELOG Version Subject
  66557   Wed Oct 7 16:17:34 2009 Question Steve WilliamsonStephenWilliamson@Barnsley.gov.ukQuestionLinux2.7.5Dynamic attribute values

Hi

I'm doing something wrong but can't work out what! 

I've created a new logbook with some date attributes that need to keep in step, e.g. one date ("receipt date") is set to the date the new record is created and another ("response required") to 7 days later.  The logbook doesn't use threaded messages, just a single page for each log entry with Submin/Preview/Back.  The dates are set with:

Preset Receipt Date = $date

Preset Response Required = $shell(gawk 'BEGIN{ print $Receipt Date + 86400 * 7}')

"receipt date" and "response required"  are set correctly when the log is written but if I change "receipt date" then "response required" is not altered - presumably because Preset only works on "New".  Tho I haven't found a way to make this dynamic with Subst.

When the log is updated later a third date may be entered ("proposal submitted") and this should calculate a fourth date ("proposal expires").  Again, I thought I could do this with some sort of "Subst" but can't work out how.  If I use Subst then the value of "proposal expires" isn't changed at all and if I use Subst On Edit then the value isn't changed until I go in to edit the log when the correct "proposal expires" date gets calculated and displayed, e.g.:

Subst On Edit Proposal Expires = $shell(gawk 'BEGIN{ if ($Proposal Sumbitted > 0) {print $Proposal Submitted + 86400 * 30}}')

Am I trying to do the impossible, and is there a document that will help me to understand when different updates (Preset, Subst, Subst On..., Change etc) happen and comparing their use?

A great piece of software - though I sometimes find it hard to get my head round all that it can be bent to do!

regards

Steve

 

  66599   Fri Nov 13 14:25:52 2009 Question Steve WilliamsonStephenWilliamson@Barnsley.gov.ukRequestLinux2.7.7-2264List View: Attachments icon

It is occasionally convenient to be able to put the Edit button at the beginning of the line in list view, e.g. when pages are wider than the screen it saves having to scroll across to find it.  Would it be possible to do something similar with the Attachments button?

regards

Steve

  66600   Fri Nov 13 14:28:25 2009 Reply Steve WilliamsonStephenWilliamson@Barnsley.gov.ukQuestionLinux2.7.5Re: Dynamic attribute values

Stefan Ritt wrote:

Steve Williamson wrote:

Hi

I'm doing something wrong but can't work out what! 

I've created a new logbook with some date attributes that need to keep in step, e.g. one date ("receipt date") is set to the date the new record is created and another ("response required") to 7 days later.  The logbook doesn't use threaded messages, just a single page for each log entry with Submin/Preview/Back.  The dates are set with:

Preset Receipt Date = $date

Preset Response Required = $shell(gawk 'BEGIN{ print $Receipt Date + 86400 * 7}')

"receipt date" and "response required"  are set correctly when the log is written but if I change "receipt date" then "response required" is not altered - presumably because Preset only works on "New".  Tho I haven't found a way to make this dynamic with Subst.

When the log is updated later a third date may be entered ("proposal submitted") and this should calculate a fourth date ("proposal expires").  Again, I thought I could do this with some sort of "Subst" but can't work out how.  If I use Subst then the value of "proposal expires" isn't changed at all and if I use Subst On Edit then the value isn't changed until I go in to edit the log when the correct "proposal expires" date gets calculated and displayed, e.g.:

Subst On Edit Proposal Expires = $shell(gawk 'BEGIN{ if ($Proposal Sumbitted > 0) {print $Proposal Submitted + 86400 * 30}}')

Am I trying to do the impossible, and is there a document that will help me to understand when different updates (Preset, Subst, Subst On..., Change etc) happen and comparing their use?

Just try with the current version, where I reworked the "Subst" commands. See elog:66592. "Subst" work now only on "New", and "Subst on Edit" only works when editing an entry.

 Thanks for that - it works perfectly.  Another success for elog!

  66617   Tue Nov 17 12:29:24 2009 Reply Steve WilliamsonStephenWilliamson@Barnsley.gov.ukRequestLinux2.7.7-2264Re: Re: List View: Attachments icon
Thanks for all of the contributions - all I meant in my original suggestion was that I'd like to be able to define which column(s) should hold the Attachments paperclip in the Full and Summary List Views, which I use all the time, to reduce the need to scroll horizontally on every page. This would be similar to being able to specify where the Edit control appears by specifying the Edit attribute in the "List Display" list.
... and I really didn't want to ruin another of Stefan's weekends or confuse anybody!
  165   Sat Nov 23 09:20:57 2002 Question egliStephan.Egli@psi.chQuestion  Input text gets lost
Typing in a text for a new entry results in an error message, whenever
one forgets to fill in mandatory attributes (as it should happen !). However
after using the back button in this case (Using netscape 4.79) I made the
experience, that the text typed in gets lost. Other browsers like Mozilla
or IE do not have this problem. Any idea how this problem can be
avoided for netscape as well ?
  167   Mon Nov 25 18:10:04 2002 Question Stephan EgliStephan.Egli@psi.chRequest  Show all common attributes
In the "find" command, when searching over all logbooks, it
would be nice to see ALL attributes, which are common for all
logbooks (e.g. typically the author name), not just
logbook name, date and text.
  169   Tue Nov 26 18:04:43 2002 Question Stephan EgliStephan.Egli@psi.chQuestion  Re: Show all common attributes
> > In the "find" command, when searching over all logbooks, it
> > would be nice to see ALL attributes, which are common for all
> > logbooks (e.g. typically the author name), not just
> > logbook name, date and text.
> 
> That depends on how you specify what gets displayed in a search (with 
> the "Display search" option for example). If you try the following link:
> 
> http://midas.psi.ch/elogdemo/Forum/?mode=summary&all=1
> 
> you see that all attributes are displayed from the three logbooks in this 
> installation.

How does the corresponding elogd.cfg entry look like for the
display search command ? - I can't reproduce this behaviour...
  Draft   Thu Sep 24 00:13:31 2015 Warning Stefano colafranceschiStefano.Colafranceschi@gmail.com Linux3.1.0Elog command not working properly
ELOG V3.1.5-3fb85fa6