> Is it possible to preset an attribute with the current weeknumber?

No. All you can do is 

Date format = %W

which displays the week number in the "Entry date" field. This number goes 
from 00 to 53. Some systems support "%V", which runs from 01 to 53.

> Short of manually editing the logbook files, is there a way I can change the
> date of an entry?  I want to transfer my "Linux Journal", which I have been
> writing as a regular document for several months, into elog so I can take
> advantage of the threading, sorting, find, etc.

You cannot change the entry date, since this is kind of system stamp which 
should not be modified. But you can add an attribute like "Issue" for your 
Linux Journal, where you can add manually the month and year of release or so. 
Then you can preset this attribute with the current date, which you can change 
for older issues, like

Attributes = ...., Issue
Preset Issue = $date
Date format = %B %Y

Hope this helps.

- Stefan

> > Short of manually editing the logbook files, is there a way I can change the
> > date of an entry?  I want to transfer my "Linux Journal", which I have been
> > writing as a regular document for several months, into elog so I can take
> > advantage of the threading, sorting, find, etc.
> 
> You cannot change the entry date, since this is kind of system stamp which 
> should not be modified. But you can add an attribute like "Issue" for your 
> Linux Journal, where you can add manually the month and year of release or so. 
> Then you can preset this attribute with the current date, which you can change 
> for older issues, like
> 
> Attributes = ...., Issue
> Preset Issue = $date
> Date format = %B %Y
> 
> Hope this helps.
> 
> - Stefan


Yes! Thank you.  But now another question.  How can I hide the entry date
attribute on the summary screens and automatically sort by Issue?  No point in
showing both dates.

> > > Short of manually editing the logbook files, is there a way I can change the
> > > date of an entry?  I want to transfer my "Linux Journal", which I have been
> > > writing as a regular document for several months, into elog so I can take
> > > advantage of the threading, sorting, find, etc.
> > 
> > You cannot change the entry date, since this is kind of system stamp which 
> > should not be modified. But you can add an attribute like "Issue" for your 
> > Linux Journal, where you can add manually the month and year of release or so. 
> > Then you can preset this attribute with the current date, which you can change 
> > for older issues, like
> > 
> > Attributes = ...., Issue
> > Preset Issue = $date
> > Date format = %B %Y
> > 
> > Hope this helps.
> > 
> > - Stefan
> 
> 
> Yes! Thank you.  But now another question.  How can I hide the entry date
> attribute on the summary screens and automatically sort by Issue?  No point in
> showing both dates.


I figured out how to hide columns, using the "Display search" parameter.  (BTW,
suggest you modify the Administrator manual to mention that "Display search" applies
  to the initial display as well as any "Find"s.  I had seen this, but assumed it
only applied to actual search results.)  Still have not figured out how to change
the default sort attribute however.

> I figured out how to hide columns, using the "Display search" parameter.  (BTW,
> suggest you modify the Administrator manual to mention that "Display search" applies
>   to the initial display as well as any "Find"s.  I had seen this, but assumed it
> only applied to actual search results.) 

Fully agree. The name comes from historical reasons. I renamed "Display search" 
to "List Display". Will come in the next version.

> Still have not figured out how to change
> the default sort attribute however.

There is a little trick to do that:

Start page = ?rsort=Issue

Since sorting is done only lexically, you need a special date format like

Date format = %Y %m %d

in order to sort correctly.

> Can you give a syntax example of the Logging Level option ?

Please refer to the documentation (http://midas.psi.ch/elog/config.html), I just 
updated it. "Logging Level = 3" is the maximum level which includes writes and 
reads.

Cheers

It appears Im having problems getting this to work, my config is as follows, yet 
its not updating the log file since i installed the new RPM 2.3.9, is there a 
problem or am I doing something wrong ?

Thanks in advance.

[global]
port = 81
Logbook dir = /data
Logbook Tabs = 1
Main Tab = Home
Page title = LogBook System
SMTP host = support.localnet
Logfile = /var/log/elogd.log
Logging level = 3
Resource dir = /usr/local/elog
Welcome title = <img src="logo.gif"><p><font size=4 color=white>Customer Relational 
Management System</font>
Page title = Customer Relational Management System
Bottom text = bottom.html
URL = http://172.16.24.108:81/

> > Can you give a syntax example of the Logging Level option ?
> 
> Please refer to the documentation (http://midas.psi.ch/elog/config.html), I just 
> updated it. "Logging Level = 3" is the maximum level which includes writes and 
> reads.

> > I figured out how to hide columns, using the "Display search" parameter.  (BTW,
> > suggest you modify the Administrator manual to mention that "Display search" applies
> >   to the initial display as well as any "Find"s.  I had seen this, but assumed it
> > only applied to actual search results.) 
> 
> Fully agree. The name comes from historical reasons. I renamed "Display search" 
> to "List Display". Will come in the next version.
> 
> > Still have not figured out how to change
> > the default sort attribute however.
> 
> There is a little trick to do that:
> 
> Start page = ?rsort=Issue
> 
> Since sorting is done only lexically, you need a special date format like
> 
> Date format = %Y %m %d
> 
> in order to sort correctly.

Thanks again!  That did the trick.  One little hassle is that I had to go back and edit
all the Issue fields in my existing records so they would have the correct date format.

Rock on OSS!