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