Hello,

When using restrict edit time together with autosave, there is the following problem: The counter for restrict edit time seems to start after the autosave. If the time is up, it is no longer possible to submit the report.
It is also not possble to edit old drafts if restrict edit has elapsed since the creation of the save.
Autosave is definitively a nice new feature. However, I think it would be better if the counter for restrict edit time only started after the "submit" of the report and allowed edits to drafts no matter how old they are. As it is one needs to either set a really high value for restrict edit time or turn off autosave.
The issue seems to be related to: https://midas.psi.ch/elogs/Forum/68103

Regards

Kester

Hello,

Somehow when replying to a log entry, a log entry was created that was referring to itself. How this happened, I have no idea. The effect was that each time this enty was loaded, the elogd started to hang, going to 100% load and not responding to any http requests anymore. This problem can be reproduced by manually creating such a self-referencing log entry (see attachment). The problem entry that leads to the crash can be made by editing any elog entry and adding a line "Reply to: X" and a line "In reply to: X" where X is the MID of this entry.

1) Maybe it is possible to add a check when writing files that ensure, that is a log entry does not reference itself.
2) Maybe when loading files are preparing the thread view, elogd can detect cycles and abort.

Hallo and thanks for a great program.

At my work we have previously been using another program (Rednotebook) for our lab journals, but now we wish to migrate to elog because it is more configurable and because it runs in a browser.

We would off course like to move all of our old log entries with us. Luckily Rednotebook uses a standard module (YAML) for data storage, so I can easily access the data (e.g. with python) and I have already done do, and I have exchanged the native markup with html.

Now I would prefer it if I can make the elog data files directly, in stead of using the elog command, because that makes it possible and easy to revert the change, and also to not have to handle escaping html string before feeding them to elog on the commandline. I have actually already written the program that produces the elog data files, but now I have a few questions:

1) Is there an overall way of validating the datafiles, to make sure elog doesn't choke on them at some point in the future when I try to open one of the old entries. Along the same lines, does elog parse all the files when the demon is started, so if it starts then I'm ok?

2) What exactly are the requirements for the HTML content

2a) Will any valid html do, or are there some speciel requirements (e.g. like   at blank lines)

2b) Does it require a particular version of html, because then I could at least validate it against that doctype beforehand

3) Is there a log from elog where I can see if it encounters something it doesn't like?

I hope the you can answer some of my questions.

Regards Kenneth

I am testing Elog for personal and group use. I am starting with a Windows install on a PC. (I came across Elog when doing a shift on ATLAS at CERN.)

It took me some time to discover how to access a local logbook and create a new one. I suggest adding short sections in a prominent place in the guides:

User guide:

"Accessing a logbook: To access a logbook, point your Web browser at the appropriate URL. The default for a local Elog is http://localhost:8080/logbookname. Logbook files are stored in directory logbookname which is a sub-directory of the logbook root directory, defined by the administrator. See the administrator guide on how to create a new logbook."

Admin guide:

"Creating a logbook: A logbook is created in three steps: 1) The logbook root directory is defined as an option of the elogd start command; 2) A sub-directory, of the logbook root directory, named logbookname is created; and 3) The elogd.cfg file is edited to define the logbook's attributes and options. No files are created in the sub-directory; that is done when entries are made."

Regards,

Ken McF