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

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

> For a large class it might be a bit cumbersome to set it up this way.

What you can do is put most of the configuration options into the [global] section,
such as

[global]
Attributes = ...
Password file = ...
...
Admin user = teacher

[John]
Login user = john
[Joe]
Login user = joe
[Fred]
Login user = fred

In this case, each logbook only requires two lines, while all the other options are
inherited from the [global] section. The "login user" restricts logins only to a
single student, which the teachis has admin rights for all logbooks. The teacher can
reply to individual students by writing into their "personal" logbook, or he can set
up a dedicated teacher logbook which everybody can read (Just omit the 'login user').

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

There was indeed a bug which I fixed. Please obtain the newest snapshot (see
download page). If an admin user is defined in a top group, it does not gain
access to the global if the admin of the global is different, like

[gloabl]
password file = passwd
admin user = joe

Top group g1 = demo1, demo2
Top group g2 = demo3, demo4

[global g1]
admin user = joe

[gloabl g2]
admin user = jack

[demo1]
....

So if user "jack" is logged in to demo3 and therefore g2, he can change the
[global g2] section, but not the [global] section, since only user "joe" is
allowed to so do.

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

This is not directly implemented, but one can configure this kind of "manually",
like

Attributes = ..., Send Email, ...
ROptions Send Email = joe, jack, ...

Email "Send email" joe = joe@some.domain
Email "Send email" jack = jack@other.domain

The option "Email <attribute> <value> = <email address>" gets executed when the
attribute "Send email" has the value "joe" in the first line, so email is sent
to joe@some.domain. It's a bit cumbersome since one cannot use the email
addresses from the password file, but better than nothing. 

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

No, this is not foreseen. One should use email notification for that, which
tells you immediately (not after 15 mins) when a new entry has been submitted.

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

The message id must be unique in a logbook (like in a relational database). If I
would keep the id when moving entries to another logbook, this could cause a
conflict. Assume you have two logbooks both with three entries having ID's
1,2,3. Now you move ID 3 from the first logbook to the second, but ID 3 exists
already in the second logbook, so you would have that ID twice, which breaks the
database structure. What you can do however is user an "numbered" attribute like

Attributes = ..., tag, ...
Preset tag = ID%d

For each new submission, the attribute "tag" gets a new number, like ID1, ID2
etc. These attributes are not modified when moving an entry to another logbook,
but if the target logbook has already an entry with the same tag, you get this
tag twice. I don't know if that is what you want...

An options list that starts with a double-quotes character (") is handled 
incorrectly. 

Try the line: 
Options Student name  = "Doe, John", "Foo, Bar".

The ELOG list will have four entries, namely:
 - Doe
 - John
 - "
 - Foo, Bar

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

> Options Student name  = "Doe, John", "Foo, Bar".

I fixed this bug. Please obtain the newest snapshot (see download page).

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