Great program!  Thank you.

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.

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

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!

Is there any way to include the text of a log message in the CSV export? 
Anyway to include a pointer to the attachment?

> > Is there any way to include the text of a log message in the CSV export? 
> > Anyway to include a pointer to the attachment?
> 
> The text of a log message is usually several lines long. To my knowledge, CSV
> only allows single line values, that's why I excluded the text field from the
> CSV export. This is different in the XML export, which supports multi-line
> values. If you teach me however how multi-line values can be represented in
> CSV format, I could easily add that.
> 
> As for the attachment, do you just need a name, or a URL back to the logbook?
> Should the pointer be in the form "http://elog.server/logbook/attachment.jpg"
> or in HTML form like <a href="http:/...">attachment</a> ?

I will attempt to use an active x script in a DTS package on SQL Server to parse
the xml and load it into the database. I can see where CSV has it's limitations.

When entering data for a new log entry some folks always type in an attribute and then the "Enter" key which automatically

submits the entry. Is there a way to prevent this so the only way a new entry is submitted is with the Submit button. Also

is there a way to setup the main text box as a required attribute?

Thanks

Gary