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