From ClaroDevel

Claroline have no specifications but a roadbook. (found it on www.claroline.net)

We make choice and we try to follow them.

Find here a list of choices.

Table of contents

1 Users 2 User Info 3 Courses 4 Groups 5 Course description 6 Course_home 7 Course_info 8 Create_course 9 Admin 10 Todo 11 Auth 12 Student_view 13 Statistique / tracking 14 Forum 15 Chat / Discussion 16 Calendar 17 Document 18 Exercice 19 Work 20 Garbage

Users

1. A user have always a username, a password, a name and a firstname.
2. A user can subscribe it'self (can be dislabed ;-( in config )
3. A user can give an email, a phone number, an officialCode (be unique or empty)
4. Claroline accept email, phone number, and officialCode as optionnal
5. For the system, 2 accounts are 2 differents persons.
6. Name, Firstname are public
7. Username and password are only readable by owner.
8. Email is reserved to platform users (perhaps not true acutally)
9. Phone are reserved to courses manager (and owner + admin)
10. Status, expiration, creatorId are sysadmin reserved
11. Only admin of course can edit user properties
12. Admin of course can add account other than is own, but still the propritary until first login of a user with this account login-pass
13. Users added by other need an email. The user receipt an login-pass generated by system and pruposed as key to keep account but would be changed on ifrst identification.

User Info

(bloc = section, including a title ,write by course admin and a content fill by user.

1. . The manager of the course define blocs
2. . Defined blocs are required (show also title for not filled blocs)
3. . A user can edit only it's own info
4. . Empty blocs do not necessary existing in DB.
5. . Empty blocs are show
6. . Some contents can exist for undefined blocs.
7. . Some contents can exist for unknow users.
8. . A bloc can't be hide for one user.

Courses

1. Course have many users
2. Course can have many course admin
3. Course have 1 categorie
4. Course are used of one session
5. Course must have as less One User adminOfCourse
6. Course can work without groups
7. Course can work without student
8. All admin of a course have sames right

Groups

see in Groups

Course description

1. Course_description is a list of blocs text
2. Each bloc contain a title and a body
3. Some titles can't be change (only translate during change of lang)
4. There is 1 calandar by course

Course_home

1. Only admin of course can switch tools for student between visible and hide
2. Only admin of platform can switch tools for admin of course between visible and hide

Course_info

1. Only the admin of a course can edit course settings

Create_course

1. A user need creator status to use this script
2. a notification is send to course administrator, and platform admin on each course creation

Admin

• admin is reserved to user present in .htaccess
• table admin content id of user who can admin all courses.

Todo

Auth

Student_view

Statistique / tracking

voir CLANN

Forum

Chat / Discussion

Calendar

• Documentation
• Table
• Options

1. Only admin of course can add, edit and delete entries in calandar
2. There is 1 calandar by course
3. event can be empty
4. entry are order by date (asc or desc)

Document

table

Exercice

tables

Work

Garbage