[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [k12L-A] Pre-Alpha Release of k12admin-server packages




On Thu, 6 May 1999, Bruno Vernier wrote:

> Basically, all students in linux managed schools would have an entry 
> in a centrally-distributed EDUML (XML) database.
> 
> Changes made in k12admin package database would also trigger an update to the 
> central EDUML database (via email, http, uucp, ftp, or whatever)
> 
> Every night, or after every change, the central database distributes itself 
> to the local area network servers
> 
> Then k12admin database gets updated (cvs style) ... AND so do any other 
> educational management applications (like gradebooks) that need contact 
> information  or authentication info (like quizzers)


This is what I had in mind.  I log all changes made to the database, and
it would be trivial to have a script scan through this log and update the
EDUML database.  It might be tricker if changes are also being made
directly to the EDUML database at the same time.  Which one is
authoritative?  I gather that it should also be possible to have changes
made to the EDUML database trigger an immediate update to the k12admin
database?

Is there going to be any kind of access control in the EDUML database
specs?  Who gets to modify what in the database?  In k12admin, if a user
is a member of the "Account Administrators" group in a particular school,
they can modify any accounts within that school.  This is not particularly
fine grained access control, but it has worked okay so far.  I've been
giving some thought to have access control on a per group basis as well as
a per school basis.

Steve.