One way would be to create a seperate logbook for each student including the
teacher. It should then be fairly simple to set up the permissions however you
would like. For a large class it might be a bit cumbersome to set it up this way.
 
Ralph Kuehn

> Hi,
> 
> Is it possible to restrict the display of logbook entries to the entries 
> created by the currently logged-in user?
> 
> I'm thinking of using the ELOG system in a school laboratory environment: 
> students must write entries in the logbook about their excersises, but I 
> would like that students can not "see" what other students have written. To 
> make it even more complicated, I would like that students can see their own 
> entries and the teacher entries.....
> 
> Is something like this possible?
> 
> Thanks in advance
> Bartjan Wattel
> the Netherlands

Is there a way to disable editing of the textarea, but still allow editing 
of other fields in the entry? (e.g. Fixed Attributes Edit = Text)
Also, is the data entered in that field accessible through a variable like 
$author? I tried $text, but that doesn't seem to work.

Thanks,
-Todd

By the way... Nice work on this. It has a lot of good features.

HI 
I have setup top group in my elog . I will want to restrict the different 
admin user on the global and the global on top groups .
But however i am not able to use the configuration on "admin user" on the 
global portion to strict admin of top group to access the main global 
config .
Did i configure it wrongly or is there a way?

And for email notification , is there a way which i can select who to email 
it to ? like check box etc.

And is there a way which i can setup the summary page to refresh every 
15mins , so that new entry can be shown ?

And can i make the message id unique , when i move the messages from one 
log book to another log book , the messages id change accorddingly based on 
the number or messages . Anyway for me to make it fixed even i moved to 
another log book , i need the running number still .

Sorry for the many questions
Thanks for your help

Hello to all,

I'm trying to get ELOG to run several separate logbooks which will
eventually have their own password/user files and other little things.
The problem I have is I want to have a main selection type page so when a
user enters ELOG they see this page with links on it to main logbook groups.

So, for my example I'd have a main page INDEX1.HTML which has links to:
  /Server_Logbooks
  /Other_Logbooks

but I want those top groups to just show standard ELOG generated logbook
list once you select a link on index1.html page.
Unfortunately "Selection page = index1.html" if defined in [global] just
gets used everywhere, so once I click on a link to go to
http://elog.blah.internal/Server_Logbooks it just shows the same index1.html
selection page. So I never get to the actual logbook list...
I could make separate selection pages for each top logbook group,
but that means that I have to alter those HTML files every time I add or
remove a logbook. I'd ruther have ELOG generate those pages on the fly.

Is there any way to do this?
Could I tell ELOG not to use a selection page at all for a particular group
of logbooks, and just show the logbook list.

Thank you very much.

GL.

//ELOG on FreeBSD 5.2//

Is it possible to add one more "text entry" field ?

Hi,

I want to create a series of logbooks, say logbook A, and logbooks B up to 
including S. I want the logbooks B,C,D,E,...S to have the same options and 
layout, the only difference is: the name of the logbook, and an options or 
extendable options list. All other settings of logbooks B-S are the same, 
while logbook A is a completely different logbook. 

I know I can simply copy the settings for logbook B and repeat the settings 
for all logbooks C-S. But is there a better way to accomplish this?

Thanks, 
Bartjan Wattel

> I know I can simply copy the settings for logbook B and repeat the settings 
> for all logbooks C-S. But is there a better way to accomplish this?

Yes. Put all common settings into the [global] section, only differences into
the individual logbook sections. Like

[global]
Attributes = ....
Options ....

[A]
; Logbook A is different
Attributes = ....
Options = ...

[B]
Option X = ...

[C]
Option X = ...

[D]
Option X = ...

This way all logbooks "inherit" the settings from the [global] section, only the
differents are superseeded in the individual sections. Still you need two lines
for each logbook, but all recurring configuration can be omitted.

> > I know I can simply copy the settings for logbook B and repeat the settings 
> > for all logbooks C-S. But is there a better way to accomplish this?
> 
> Yes. Put all common settings into the [global] section, only differences into
> the individual logbook sections. Like
> 
> [global]
> Attributes = ....
> Options ....
> 
> [A]
> ; Logbook A is different
> Attributes = ....
> Options = ...
> 
> [B]
> Option X = ...
> 
> [C]
> Option X = ...
> 
> [D]
> Option X = ...
> 
> This way all logbooks "inherit" the settings from the [global] section, only the
> differents are superseeded in the individual sections. Still you need two lines
> for each logbook, but all recurring configuration can be omitted.

Thanks for you quick and correct answer. I have one question left ;-)

Suppose I want to have different password files for all the logbooks, but I want to 
have a single (admin) user that can log in to all logbooks... Do I need to specify 
the admin data in all the different password files, or can I use one global 
password file containing the login name and password for the administrator?