Dear all,

First, many thanks for creating and sharing this great tool which is ELOG! Our users are very happy with it!

I have few questions about inserting images into the entries.

From time to time our users insert them directly in the editor what leads to encoding the whole image in the HTML log file and the images does not appear in the attachments list. Saving and further editing of such entries slows down the whole ELOG server which uses 100% of CPU.

I'm not sure how they do it Ctrl+C & Ctrl+V, drag & drop, etc.. What I know is that if they add it using the "Insert image" action in the editor there are no problems and the images are properly listed in the attachments.

I read in the docs:

uploading or downloading an attachement file is a single request, and causes the entire file to be loaded in server memory while the request is being processed.
This is not normally a problem for the sort of short, text-mode entries ELOG is designed to support. However, if a user starts to upload or download a large attachment file (or image) over a slow link, all other users on that ELOG server will have to wait for that transfert to finish before they can access any logbook on that server. This is why there is a low limit on the size of attachments, and why ELOG should not be used to distribute large files under intensive multi-user conditions.

but I think this is not our case. Here I talk about wrongly inserting a single image of 700KiB.

So, I'm asking:

1. Is the behavior that we observe something already detected? If yes, which are exactly the wrong ways of inserting the images?
2. Is it fixed in newer ELOG versions?
3. Is it possible to disable the wrong ways of inserting the images in order to avoid such problems?

Many thanks in advance for your help!

Hi All,

Can I view who is connected to ELOG (I'm the Admin) ?

thank you.

Hey,

I'm trying to integrate the Elog into our SlowControl System (Phoebus/EPICS). As a first step I translated the python library to Java. So writing new Entries and viewing them works.
But for Phoebus, you need a list of the possible values for the attributes. Currently this is done via the config file from Phoebus.

Is there a way to get the values also via a query directly from the Elog?

Cheers,
Florian

Our Unix server died, so we decided to move our old eLog to the new server, running Mac OSX. Elog version is earlier then 2013, I can not say

I read that on OSX  eLog must be intalled through "make" command

if I need to install eLog first, how to add all old information later?

Thanks for your suggestion. Right now, my log is configured as follows:

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

If I select "Pentax", I would like the other two options to be unavailable. Instead, all three options are shown. Can I mask the other unused options?

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?

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.