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

If you start over, you can just copy the xxyyzza.log files into the new logbook directory and it should be fine. You can also change the config file in your current logbook without starting over. 

Best is if you edit elgod.cfg or the user configuration from inside the web browser (Click on 'config' on the elog page), then you don't have to restart elogd. If you do have to restart it, go to My Computer/Manage/Services, select elogd, then stop and start the service.

- Stefan

 Fantastic! That worked great. Thanks so much for the help guys!!

Terry

 Sorry, about this dumb question but with  "Copy to = <logbook list> " what is the format of  <logbook list>?

Is it just the "logbook Name" or is it the actual path name   "http://something/somethingelse"?

 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.

I would be too lucky if I just could fix this as I fix some ELOG problems! I guess hundreds of physicists right now are pondering about what could have gone wrong in data taking, because nobody really believes that this is a real effect. 

We have about 10 logbooks running on the same Elog that all get fair use. Many people have turned off new entry emails because they were filling up inboxes, but are still interested in what's new. I saw the option to add "?last=1" to the start page, although I'm afraid using it might cause confusion over how to get to the older posts.

I was trying to figure out a way of creating a "digest" of sorts, a list of entry subjects posted in the past day or week, something similar to what's generated by "?last=1?mode=threaded", but for every logbook (similar layout to the selection page with nested logbooks). This could either be a page, or a regular email.

Is there way to generate such a cross-logbook page? What about a scheduled email formatted based on a given filter?

PS: The elog has been invaluable to us, a big thanks to all involved!