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

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

Stefan

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?

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
 

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?

It was done using the "groups" feature:

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

Stefan

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

Instead of using three different options you could use the same:

Options Eyepiece = Pentax{a}, TeleVue{b}, Meade{c}

{a} Options Form = 5mm, 20mm, 30mm
{b} Options Form = 7mm Nagler, 10mm Radian, 24mm Panoptic
{c} Options Form = 8.8mm UWA, 14mm UWA, 26mm QX

It makes more sense.
But it is as well possible to supress attributed in the edit from. See

• Show Attributes = <list>
  Attributes present in this list are shown in the single entry page. Omitting attributes can make sense for attributes which are automatically derived from other attributes via the Change <attribute> command.
• Show Attributes Edit = <list>
  The same as Show Attributes, but for the entry form.

You just have a different <list> for each conditional case {a} {b} {c}.