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

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

I have two identical servers (IBM X337) setup on the same LAN with Ubuntu Linux 10.04 LTS with ELOGD running (Compiled from tarbell) with the same exact package install base. (Only difference between the two servers is the hostname, and the ELOGD.CFG global section)

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!

What we do is use the RSS feed of elog. This gives you nice summaries without going through your email inbox. Most browsers have RSS readers, there are also tons of stand-alone programs for that. Attached is a screenshot from the Google Reader subscribed to this logbook and to the "contributions' logbook. You see nice one-line summaries, you can expand them, and you can go directly to the logbook if you click on the arrow. The second image is from the Firefox using what they call "live bookmarks", but it's basically a RSS reader.

To make this work, I installed the RSS extension of Google Chrome (Firefox has this under "Bookmarks"/"Subscribe to this page"), then go to the elog page, then click on the RSS icon, then clicked on "Subscribe to this" via Google Reader. Just a few clicks.

Hope this is what you want.

- Stefan

 Perfect! I didn't not know there was RSS support. I will probably use something like rss2email, but this is exactly what I needed. Thanks!

Hello,

I'm not able to authenticate to a logbook using my text based browser links, so I've started investigating with wget hoping solving the problem one will lead to a solution for the other.  I've seen some examples on how to use wget to parse logbook entries in this forum, but my attempts keep returning the login page.  Any advice would be helpful and appreciated.  Here are a couple of the command line arguments I've tried:

wget --save-cookies cookie.txt --keep-session-cookies -d "http://hostname/LOGBOOK?unamee=YYY&upassword=XXX" -O elog.txt

wget --save-cookies cookie.txt --keep-session-cookies -d --post-data="redit=&uname=YYY&upassword=XXX&remember=1" -e robots=off "http://hostname/LOGBOOK" -O elog.txt

After these executions, my cookies.txt file remains empty.  Running subsequent command with "--load-cookies=cookies.txt" still points me to the login page.

Many Thanks,

Chris 

I've just checked that 'wget --no-check-certificate --save-cookies cookie.txt --keep-session-cookies -d "https://elog-gfa.psi.ch/SLS?uname=uuu&upassword=ppp" -O elog.txt'

created a file cookie.txt. The file contains three lines of data if uname and upassword are a valid login, and it is empty (beside of three comment lines) if they are not a valid login (wrong user or wrong password).

Could it be related to the set-up of your particular logbook?