Minutes for Tuesday, July 7, 1998

• Recorder: Raphen
• Start: 12:15
• Stop: 1:30

Admistration

• Lunch meeting today at Edie's Edibles.
• We will meet again tomorrow (Wednesday, July 8) at 2:00 to work on our presentation for the web workshop. We will also meet on Thursday (whtouth Hilary) and again on Monday (July 13). Monday's meeting will be a slightly late (12:30-ish) lunch meeting
• The MathLAN will be closed Wednesday through Friday (July 8, 9 & 10) for painting. Don't forget to log out Tuesday night.
• There will be a games night at the Rebelsky residence this Thursday at 6:30 pm.
• The web workshop is all next week. We will put together our demonstration starting tomorrow.
• Hilary will be gone Thursday and Friday. Almost everybody else will be gone only Friday.

Reports

Sarah

She said that the adding of annotation tags is almost done.

To Do:

• Have the program notice when there are changes to the headers and notify someone by e-mail or just log it to a file.

Kevin

He has done a little coordinating with Hilary. Kevin will call Hil's CGI routines. The first takes the name of the HTML page and returns the modified page. The second routine takes the username and groups as parameters and returns a form. When submit on the form is pressed, the third routine will be called.

Note: Kevin wanted to remind everyone to make sure their variables in Perl are local to the subroutines by using my.

To Do:

• Implement the design changes that we will talk about involving access privaledges for administrators.

• Implement file locking.

Hilary

She has her annotations working and is doing testing and fixing any bugs she finds.

To Do:

• Continue finding and fixing any bugs.
• Making it useable by Kevin.

Raphen

He has found and implemented an acceptable work-around for all of the Java bugs discovered. He is currently working on implementing the hardest of the log file conversions (from user log files to condensed user log files).

To Do:

• Finish up the conversion program soon and get to work on data visualization

Administrative System

We discussed who should have what access priviledges to user and group information. This is what we decided on:

System Administrator

• Can do anything
• View sessions
• Stop sessions
• View all users
• Change for all users
  • username
  • password
  • group membership
  • real name
  • e-mail address
• Create/delete user accounts
• Create/delete groups
• Create/delete Group Administrator accounts

Group Administrator

• Add/remove users from their group
• View users that are members of their group

Users

• Change real name from "anonymous" to whatever
• Change password
• Change e-mail address
• View groups they are members of
• Add/remove/alter groups for their own annotations

Other Issues

• We should have a script to add many users quickly and easily
• Limit accounts to 1 per person
• Annotation system should allow a user to type in who it is from
• Allow completely anonymous annotations - using something like a checkbox with a disclaimer
• Log annotations with usernames except for the anonymous ones