Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 75 of 806  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6444 Entries 
Goto page Previous  1, 2, 3 ... 74, 75, 76 ... 804, 805, 806   Next  
IDdown Date Icon Author Author Email Category OS ELOG Version Subject
  69257   Tue Oct 27 21:59:03 2020 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinuxV3.1.4-ba84827Re: Create entry from command line - override Date?

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) ...

Andreas

David Wallis wrote:

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 delete the Orig Date field.

Andreas Luedeke wrote:

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 1.1.1970). Not so easy to copy and paste them, but you can convert them with a script.

Cheers, Andreas

David Wallis wrote:

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 Ritt wrote:

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 !!!!
Author: Stefan
Type: General
Category: 
Subject: CURL test
Attachment: 
Encoding: plain
========================================
Text body
 

 

 

 

 

  69256   Tue Oct 27 17:45:29 2020 Reply David Walliswallis@aps.anl.govQuestionLinuxV3.1.4-ba84827Re: Create entry from command line - override Date?

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 delete the Orig Date field.

Andreas Luedeke wrote:

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 1.1.1970). Not so easy to copy and paste them, but you can convert them with a script.

Cheers, Andreas

David Wallis wrote:

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 Ritt wrote:

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 !!!!
Author: Stefan
Type: General
Category: 
Subject: CURL test
Attachment: 
Encoding: plain
========================================
Text body
 

 

 

 

  69255   Tue Oct 27 17:07:00 2020 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinuxV3.1.4-ba84827Re: Create entry from command line - override Date?

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 1.1.1970). Not so easy to copy and paste them, but you can convert them with a script.

Cheers, Andreas

David Wallis wrote:

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 Ritt wrote:

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 !!!!
Author: Stefan
Type: General
Category: 
Subject: CURL test
Attachment: 
Encoding: plain
========================================
Text body
 

 

 

  69254   Tue Oct 27 16:49:53 2020 Reply Stefan Rittstefan.ritt@psi.chQuestionLinuxV3.1.4-ba84827Re: Create entry from command line - override Date?

"Date" must be on the first line on each entry and it must be named "Date".

Stefan

David Wallis wrote:

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 Ritt wrote:

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 !!!!
Author: Stefan
Type: General
Category: 
Subject: CURL test
Attachment: 
Encoding: plain
========================================
Text body
 

 

 

  69253   Tue Oct 27 16:37:07 2020 Reply David Walliswallis@aps.anl.govQuestionLinuxV3.1.4-ba84827Re: Create entry from command line - override Date?

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 Ritt wrote:

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 !!!!
Author: Stefan
Type: General
Category: 
Subject: CURL test
Attachment: 
Encoding: plain
========================================
Text body
 

 

  69252   Tue Oct 27 16:15:26 2020 Reply Stefan Rittstefan.ritt@psi.chQuestionLinuxV3.1.4-ba84827Re: Create entry from command line - override Date?

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 !!!!
Author: Stefan
Type: General
Category: 
Subject: CURL test
Attachment: 
Encoding: plain
========================================
Text body
 

  69251   Tue Oct 27 16:00:03 2020 Question David Walliswallis@aps.anl.govQuestionLinuxV3.1.4-ba84827Create entry from command line - override Date?

I'm converting our on-call logbook, with 25 years of history, to elog. Is there a way to override the current date/time for the Date field with the creation date/time of the original logbook entry?

  69250   Mon Oct 26 11:42:53 2020 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux | Windows | Mac OSX | All | Other3.1.4Re: MEG style elog configuration

It was done using the "groups" feature:

https://elog.psi.ch/elog/config.html#groups

Stefan

Daniel Kohl wrote:

Hello,

 

I'm new to elog software and I could not find a solution to my configuration issue. I would like to setup a configuration file similar to MEG experiment's elog.

https://elog.psi.ch/elogs/meg/

I'm interested in creating similar to the structure: "General", "Collaboratoin", "Sub-groups (with sub-sub groups "Software", "Hardware" etc). I cannot tell if this was created by using Top Group feature.

Can someone explain how this design structure can be achieved?

 

Thanks,

Daniel

 

Goto page Previous  1, 2, 3 ... 74, 75, 76 ... 804, 805, 806   Next  
ELOG V3.1.5-3fb85fa6