Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 371 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  2318   Thu Sep 27 15:18:10 2007 Question Bertram MetzBertram.Metz@gefanuc.comQuestionLinux | Windows2.6.5-1844Re: Post appearing twice
I've observed the same behavior with attributes containing a dash. Would it be possible to allow '-' in attributes?

Bertram
  2319   Fri Sep 28 17:52:37 2007 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux | Windows2.6.5-1844Re: Post appearing twice

Bertram Metz wrote:
I've observed the same behavior with attributes containing a dash. Would it be possible to allow '-' in attributes?


Yes. Fixed in Revision 1930.
  66006   Fri Oct 17 18:06:04 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows Re: Possible to submit entries by email to logbook

 

thorsten kamps wrote:

Hi, thanks to everyone involved for giving us the elog.

A question:

Is it possible to submit entries to an elog on a remote machine by email?

 

Thanks, Thorsten

 

 Have a look at Contributions.

  65717   Tue Jan 29 08:02:41 2008 Reply Stefan Rittstefan.ritt@psi.chQuestion 2.7.0Re: Possible to sort attribute chronologically?
> Hi,
> 
> We've defined a "LastEdit" attribute for some of our logs so that we can indicate that an entry has been revised, and when that was done. 
> 
> From our config:
> 
> Attributes =  Last Edit, etc etc
> .
> .
> .
> Preset Last Edit =$date
> Locked Attributes = Last Edit
> Subst on edit Last Edit = $date
> 
> This works fine, but when we sort the LastEdit column, the dates are sorted alphabetically. 
> Is there a way to tell Elog to treat this particular attribute as a date when sorting?

You are missing:

Type Last Edit = datetime

which will tread the "Last Edit" attribute as a date/time combination. Actually it's stored 
internally in seconds since Jan 1st 1970, so sorting will work right. The only caveat is that
when you edit an entry, the "Last Edit" is displayed really in seconds since 1970, but I will
fix this in the next release.
  65718   Tue Jan 29 08:09:50 2008 Reply Stefan Rittstefan.ritt@psi.chQuestion 2.7.0Re: Possible to sort attribute chronologically?
> The only caveat is that
> when you edit an entry, the "Last Edit" is displayed really in seconds since 1970, but I will
> fix this in the next release.

I just fixed this in SVN revision #2010. If you would have filled out which operating system you use
with elog, I could tell you how to upgrade.
  65725   Thu Feb 7 01:33:03 2008 Reply Dennis Seitzdseitz@berkeley.eduQuestion 2.7.0Re: Possible to sort attribute chronologically?
> > The only caveat is that
> > when you edit an entry, the "Last Edit" is displayed really in seconds since 1970, but I will
> > fix this in the next release.
> 
> I just fixed this in SVN revision #2010. If you would have filled out which operating system you use
> with elog, I could tell you how to upgrade.

Thanks for the help and the bug fix. I have a colleague who keeps our installation up to date, so I'll ask him to install it.
  65863   Tue Apr 29 02:00:03 2008 Reply Dennis Seitzdseitz@cosmology.berkeley.eduQuestion 2.7.0Re: Possible to sort attribute chronologically?
> > The only caveat is that
> > when you edit an entry, the "Last Edit" is displayed really in seconds since 1970, but I will
> > fix this in the next release.
> 
> I just fixed this in SVN revision #2010. If you would have filled out which operating system you use
> with elog, I could tell you how to upgrade.

Thank you for pointing out the method to identify Last Edit as a datetime type so that it will sort properly. I now have created Last Edit in several 
preexisting logbooks. 

I want to use 
Start page = ?rsort=Last Edit
to set the default sorting of each logbook to be by Last Edit. 

However, all of the entries made before I added Last Edit have no value for that field, so they are all grouped together at the end of the sort. So I 
decided to go through the older entries and set Last Edit equal to the original entry date, as a starting value.

I tried to use the command
Subst on edit Last Edit = $entry time
but it gives a "-" for the Last Edit value when I edit an entry. 

I think this is because $entry time is not a variable supported by Subst. Can you add that support, or else tell me if you know a better way to go about 
doing what I'm attempting? Is there perhaps a way to globally process a group of entries in a logbook and set one attribute's value to be equal to 
another's?

Thanks
  65891   Mon Jun 2 11:11:27 2008 Reply Stefan Rittstefan.ritt@psi.chQuestion 2.7.0Re: Possible to sort attribute chronologically?
> I tried to use the command
> Subst on edit Last Edit = $entry time
> but it gives a "-" for the Last Edit value when I edit an entry. 
> 
> I think this is because $entry time is not a variable supported by Subst. Can you add that support, or else tell me if you know a better way to go about 
> doing what I'm attempting? Is there perhaps a way to globally process a group of entries in a logbook and set one attribute's value to be equal to 
> another's?

I tried to reproduce what you said and it worked fine for me. I used:

[demo]
Attributes = Author, Type, Last Edit, Subject
Subst on edit Last Edit = $entry time

And got correctly the entry time copied to the "last edit" field when I changed old entries. I used version V.7.3-2104.
ELOG V3.1.5-3fb85fa6