> Is there any way to configure elog so that attribute fields can be edited 
> on more than line like the 'text' field? 
> 
> (This would be useful so that attributes could contain larger portions of 
> text including line breaks)

No, but this request is already on the wishlist
(http://midas.psi.ch/elog/wishlist.html) since some time. I added your vote.

> > However I'd like to import data from the CSV file, directly to the 'text' 
> > field, rather than just to one an attribute fields. Is it possible to do 
> > this?
> 
> Not yet, but I can implement it. Do you always have a column "text" in your
> CSV data or would you like to be able to select which column goes into the
> "text" field? Can you apend some sample CSV data so that I can have a look at it?

I've been trying an alternative approach which is basically to :

1. Import the data (not including the text field) into elog from a CSV file
2. Stop the elog server
3. Use a perl script to add each text entry to the appropriate record within the 
logbook file. 
(I.e. between the =============================== of the appropriate entry
and the next  '

Is there any way to configure elog so that attribute fields can be edited 
on more than line like the 'text' field? 

(This would be useful so that attributes could contain larger portions of 
text including line breaks)

thanks

Paul

> However I'd like to import data from the CSV file, directly to the 'text' 
> field, rather than just to one an attribute fields. Is it possible to do 
> this?

Not yet, but I can implement it. Do you always have a column "text" in your
CSV data or would you like to be able to select which column goes into the
"text" field? Can you apend some sample CSV data so that I can have a look at it?

I have been importing data from a CSV file into elog which has worked.

However I'd like to import data from the CSV file, directly to the 'text' 
field, rather than just to one an attribute fields. Is it possible to do 
this?

Paul

> > Yes, that is what I want.
> 
> I implemented a switch "protect selection page" in revision 1.318, which can be
> obtained at http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.318. If this
> switch is not set to "1", the selection page can be seen without having to log in.

Stefan,
thank you for the fast implementation of this feature. I compiled the new revision and
it worked as expected.

Kind regards,
Bertram

> Yes, that is what I want.

I implemented a switch "protect selection page" in revision 1.318, which can be
obtained at http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.318. If this
switch is not set to "1", the selection page can be seen without having to log in.

> > Hello,
> > 
> > is it possible to have an guest account together with a global password file?
> > 
> > I tried to put the password file statement into the global section of
> > elogd.cfg. But in this case every user must login and it is not possible to
> > have a read only guest account. 
> > But if I put the password file statemnet into the logbook sections, it is
> > possible to access the logbooks in read-only mode without logging in. The
> > drawback of this solution is, that you have to login into every logbook
> > seperately.
> > 
> > Bertram
> 
> Right, guest access is not possible with a global password file. This comes from
> the fact that people wish to protect their logbook selection page. What I can do
> is add another flag "protect selection page = 0 | 1". If "0", the logbook
> selection page can be seen without logging in. Is that what yo want?
> 
> - Stefan
Yes, that is what I want.
Bertram