Re: Create entry from command line - override Date?, posted by Stefan Ritt on Tue Oct 27 16:15:26 2020
|
You have to manually manipulate the logbook files YYMMDDa.log where you find the date at the top like:
MID@$: 1
Date: Wed, 02 Sep 2020 15:38:09 +0300 <==== change here !!!! |
Re: Create entry from command line - override Date?, posted by David Wallis on Tue Oct 27 16:37:07 2020
|
Hi Stefan, thanks! Does the Date field need to be the first field in each entry? I can see adding a "termpory" field called "Orig Date",
upload the old entries, then edit the file(s), delete the Date field, and rename Orig Date to Date. Will that work?
Stefan |
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 |
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 |
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 |
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) ... |
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 |
Style <attribute> and Cell Style <attribute> on the same row, posted by David Dunne on Tue Nov 17 12:10:07 2020
|
Query
(FYI, OS = FreeBSD, Elog Version as showing on logon box = V3.1.4-)
Is it possible to use both Style <attribute> and Cell Style <attribute> on the same row? |