Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 582 of 808  Not logged in ELOG logo
    icon2.gif   Re: Create entry from command line - override Date?, posted by Stefan Ritt on Tue Oct 27 16:49:53 2020 
"Date" must be on the first line on each entry and it must be named "Date".

Stefan




David
    icon2.gif   Re: Create entry from command line - override Date?, posted by Andreas Luedeke on Tue Oct 27 17:07:00 2020 
You could transform your entries into the ELOG file format (either XML or CSV) and then use the import function. That would upload the correct dates
from your entries.

If you use the "Orig Date" trick you've proposed, you'll see that datetime fields are stored as seconds of the epoch (since
    icon2.gif   Re: Create entry from command line - override Date?, posted by David Wallis on Tue Oct 27 17:45:29 2020 
Hi Andreas,

Thanks for your input! After a little testing, it appears that if I make "Orig Date" the first field, it will fall under the Date field
in the logbook file. I can then do a global delete of Date:, and replace Orig Date: with Date:, leaving it as the first field in the entry. Then I can
    icon2.gif   Re: Create entry from command line - override Date?, posted by Andreas Luedeke on Tue Oct 27 21:59:03 2020 
Hi David,
correct. And in addition you will need to convert "Orig Date" from seconds-of-the-epoch into a properly formated date string (see example
below from Stefan) ...
    icon2.gif   Re: Create entry from command line - override Date?, posted by David Wallis on Tue Oct 27 22:24:18 2020 
Hi Andreas,

It was actually easier than that. The time stamps in the old system were in epoch format, so when I created the new record, (my conversion program
was written in Python), I simply formatted that value in the format Stefan pointed out below, and defined the Orig Date field as text. Then I was able
    icon2.gif   Re: Crashes when editing entries, posted by T. Ribbrock on Wed Jul 22 12:15:56 2009 


    
        
            T. Ribbrock wrote:
        
        
            
            For some odd reasons, we are experiencing frequent crashes of elogd over the past few days. It has been
    icon2.gif   Re: Crashes when editing entries, posted by Stefan Ritt on Wed Jul 22 12:46:36 2009 


    
        
            T. Ribbrock wrote:
        
        
            
            For some odd reasons, we are experiencing frequent crashes of elogd over the past few days. It has been
    icon2.gif   Re: Crashes when editing entries, posted by T. Ribbrock on Wed Jul 22 15:35:57 2009 


    
        
            Stefan Ritt wrote:
        
        
            
            well, I need to reproduce your problem in order to fix it. The failed assertation you get is due to some internal
ELOG V3.1.5-3fb85fa6