source: main/waeup.kofa/trunk/README.txt @ 13177

Last change on this file since 13177 was 13175, checked in by Henrik Bettermann, 9 years ago

Some finetuning.

File size: 2.7 KB
Line 
1What is WAeUP.Kofa ?
2********************
3
4Kofa, which means 'entrance' or 'portal' in Hausa language, is a
5multifunctional, open source, web based student management system to
6provide transparent and comprehensive information about application
7and study progress. Kofa is the flagship of the West African
8eUniversity Project (WAeUP). See http://www.waeup.org to learn more
9about WAeUP. The system controls all kinds of application and
10student registration processes at large schools and universities in
11Nigeria. It is a generic system which can be deployed by, and is
12useful to most universities, colleges or schools wordlwide.
13
14Kofa is really an allrounder. The best way to briefly describe its functionality, is to explain what the software can *not* do for you, rather than trying to describe all its features in just a few words. Kofa is primarily not an e-learning system, although, it has some basic content management features which can be used by lecturers to disseminate course material. Kofa is also not a scheduler which generates lesson plans or timetables for lecturers or students. Although students register their courses with Kofa and can see or print course lists for each academic session, so far, courses do not contain information, when or where they take place. However, due to the modular design of Kofa, a scheduler or room planner could be easily added.
15
16Kofa is divided into sections. Each section has its own folder in
17Kofa's :ref:`object database <object_database>`. When starting Kofa
18in debug mode::
19
20  $ ./bin/kofactl debug
21
22we can use simple Python expression to view the first two levels of
23the database structure::
24
25  >>> list(root.keys())
26  [u'app']
27  >>> list(root['app'].keys())
28  [u'accesscodes', u'applicants', u'configuration', u'datacenter',
29   u'documents', u'faculties', u'hostels', u'mandates', u'reports',
30   u'students', u'users']
31
32
33The section/folder structure can be figured as follows::
34
35  root (Database Root)
36  |
37  +---> app (University)
38        |
39        +---> faculties (Academic Section)
40        |
41        +---> students (Students Section)
42        |
43        +---> applicants (Aplicants Section)
44        |
45        +---> documents (Documents Section)
46        |
47        +---> hostels (Accommodation Section)
48        |
49        +---> accesscodes (Access Codes Section)
50        |
51        +---> configuration (Configuration Section)
52        |
53        +---> users (Officers)
54        |
55        +---> datacenter (Data Center)
56        |
57        +---> mandates (Mandates)
58        |
59        +---> reports (Reports)
60
61The user handbook follows this organizational structure and adds
62further chapters where needed. Also installation instructions and
63basic information about customization can be found there.
Note: See TracBrowser for help on using the repository browser.