> > I wondered if there had been some flag for the config file whereby the original file for attachment was
> > processed by ImageMagick, but not stored, only the .png file(s) stored - or rather, some other way that achieved
> > the same end. as there is no such flag at present.
> > 
> > For now, anyway, I can attach the documents/pics I want, then go in and delete the 'originals' as saved in the
> > logbook, leaving just the .png files. But maybe something for the wishlist?
> 
> At least I now understood your problem :-)
> 
> You can have a script in your hidden logbook, that processes your attachments with "execute new", create thumbnails
> of them (using ImageMagicks "convert") and submit those thumbnails as one additional entry to your public logbook.
> 
> But then you would get thumbnails of all attachments of the hidden logbook in the public one, maybe you don't want
> that either? If you want them all, this method is more automated. If you just want some, do it as you suggested it.
> 
> In my opinion this is a rather exotic feature request :-)
> I wonder if there is a second person in the world who could use it?

Hi Andreas,

True, as a feature explained here, it may not be the most frequently used ;-)

And you are right, I would not want *all* attachements in the hidden directory to appear in the public.  But I've got
quite used to playing around in the logbook subdirectories now.

In my case, the ever-expanding use I make of ELOG - and the fact that I use it with the logbook directory stored on a
memory stick (to move from location to location and use local computers, and that's partly to ensure the hidden
directory stays hidden!) - does mean I sometimes run into issues that some hyper-networked system with ZB of storage
don't even notice. 

 In order to copy (or move) files from one logbook to another, you first need to ensure that  the
appropriate commands are in the section of elogd.cfg of the logbook the files move *from* (called 'current')

 - made up elogd.cfg to show this, and obviously only the pertinant lines

[Global]

Group = current, Y2011, Y2010, Y2009...

...

 [current]
...
Menu commands = New, ... Copy to, ...
...
Copy to = Y2011, Y2010, Y2009 ...
...
 - end of made up example.
 
So to solve your problem, the <logbook list> is simply the list of logbooks in
this part of elogd.cfg after the 'Copy to =' line in the elogd.cfg file (Y2011, Y2010, Y2009...)  

You also need to ensure that the directory to which the entries are to be copied to exists!

('Move to' would be faster if you are going to delete the entries in 'current' afterwards, but as always, it depends on

your perception of risk.)

For the user, the logbook list is the set of logbooks that appear in the
drop-down menu by the side of "Copy to" in the menu bar, and it allows you to
move that entry (or thread of entries if more than one) to the selected destination.

---

My reason for answering this is because I have actually done this operation 'in
anger' some time ago and regularly since, and would have answered before if Stafan had not beaten me
to it.  I used what was Stefan's second method, which, for those who are
reasonably confident with file manipulation, is far faster, and, dare I say,
less prone to 'unexpected' issues - some here will know what I'm
getting at.

So I say, "Back up your files and take the plunge", I would have put something
else but this is a family friendly forum.

But you must bear in mind my views are those seen through the filter of a
regular Elog ab-user, which may be why Stefan worked so hard to answer before
me ;-)

Anyway, Stefan <i>et al</i> have got CERN's faster-than-light particle problem to deal with this morning.

 Well done Mike!

One result is that I've also learnt things, realised that there are some known unknowns and perhaps some unknown unknowns in my

understanding of Elog.

 Does this occur if you are adding an attachment?  As I am blessed with forever using ancient systems, I've seen fields and indeed text  being cleared  because they were entered between clicking on 'Upload' for an attachment and the .png files being generated and displayed.  Answer here is patience - I use all too much of mine up in this exercise, sadly.

 Hi there,

I'm not sure where it appears in the documentation, but question 9 of the FAQs shows that 'Bottom text' has to be in html - and so does 'top text'

The get-it-done-now way to do it would be

Top Text = <img src=Logo.png>

(and ensure Logo.png is in the same directory as the config file - otherwise you'd best put the path of where it is in).

Of course you can do all sorts of things with this, such as centering, have it so that if you click on the logo you get taken to some other home page, but for

all that sort of thing check up with a guide to html.

Hi,

I hope I'm not missing the blindingly obvious here, but I have an issue with time and date formats

Extract from my elog.cfg file:


Time format = %a %d %b %y
Date format = %d %b
Thread display = $Ticket: $System, $entry time. ($message id). $status
Preset text = [$date]
Prepend on reply = [$date] \n

I can point to places in the syntax doc where each of these lines are given.

As for the results, the thread display is (for example):

T00001: Computer, Wed 29 Aug 12. (1). Problem

However, what I get at the top of the text box in starting a new entry or replying to a previous one is

[Wed 29 Aug 12]

whereas I expected to get

[29 Aug]

Putting $date instead of $entry time in the Thread display line makes (the by now expected) no difference

I cannot see where I'm going wrong.  

TIA 

David.

OK, I see that $date can work in a different way; if the Thread display uses $date,
then the present timestamp is substituted into the thread display line, rather than the 
date that the entry is entered.  So, for example, in a whole list of entry and replies, the present
date shows on each entry of the thread.  However, the format is still that as defined by
'Time format' rather than 'Date format'.

If nothing else, I cannot really see the point of the 'Date format =' in the way that this all works.

> Hi,
> 
> I hope I'm not missing the blindingly obvious here, but I have an issue with time and date formats
> 
> Extract from my elog.cfg file:
> 
> 
> Time format = %a %d %b %y
> Date format = %d %b
> Thread display = $Ticket: $System, $entry time. ($message id). $status
> Preset text = [$date]
> Prepend on reply = [$date] \n
> 
> I can point to places in the syntax doc where each of these lines are given.
> 
> As for the results, the thread display is (for example):
> 
> T00001: Computer, Wed 29 Aug 12. (1). Problem
> 
> However, what I get at the top of the text box in starting a new entry or replying to a previous one is
> 
> [Wed 29 Aug 12]
> 
> whereas I expected to get
> 
> [29 Aug]
> 
> Putting $date instead of $entry time in the Thread display line makes (the by now expected) no difference
> 
> I cannot see where I'm going wrong.  
> 
> TIA 
> 
> David.

 Hi Garret,

Why cannot you just use $entry time ?  It uses the date that the entry was made which appears as the first line of every elog entry -

[Sorry for mis-post, just discovered cannot put the 'dollar at' control set in an entry]

MID: 12458
Date: Fri, 07 Sep 2012 17:22:06 +0100
In reply to: 12453
 

You can use 'Time format = ' to get the date to display in the format you like.  You will see I have posted an issue about 'Date format = '.  I mention this because in trying to understand what was happening, I too had a case where all the dates were showing as the same in a thread.  I suspect your 12/31/1969 was due to the entries as being read were non-existant or blank.

Of course I may have mis-understood your requirements.