| 1 | What is WAeUP.Ikoba ? |
|---|
| 2 | ********************* |
|---|
| 3 | |
|---|
| 4 | Ikoba, which means 'bucket' in Bini language, is a multifunctional Application and Registration Web Portal to provide transparent and comprehensive information about application and registration processes. |
|---|
| 5 | |
|---|
| 6 | Ikoba is the second flagships of the West African eUniversity Project (WAeUP) Group. See http://www.waeup.org to learn more about WAeUP. |
|---|
| 7 | |
|---|
| 8 | Installation instructions can be found in the User Documentation (docs folder in the file system). |
|---|
| 9 | |
|---|
| 10 | |
|---|
| 11 | Ikoba and Kofa - Similarities and differences |
|---|
| 12 | --------------------------------------------- |
|---|
| 13 | |
|---|
| 14 | Ikoba could be described as a customer registration, document verification and contract conclusion portal. Customers are being registered (customer registration workflow), documents are being verified (document verification workflow) and contracts are being applied for and concluded (contract workflow). |
|---|
| 15 | |
|---|
| 16 | Ikoba's user interface and its usability is very similar to WAeUP's Student Management System Kofa. This comprises: |
|---|
| 17 | |
|---|
| 18 | - Responsive webdesign (by Bootstrap) |
|---|
| 19 | - User management |
|---|
| 20 | - Permissions and roles |
|---|
| 21 | - Authentication |
|---|
| 22 | - Portal configuration |
|---|
| 23 | - Data import (batch processing) |
|---|
| 24 | - Data export |
|---|
| 25 | - Logging |
|---|
| 26 | - Reporting |
|---|
| 27 | - Localization |
|---|
| 28 | - Mandates |
|---|
| 29 | - Notification and mailing |
|---|
| 30 | - Data tables |
|---|
| 31 | - etc. |
|---|
| 32 | |
|---|
| 33 | But in Ikoba there are completely new content components (models), views (including pdf slips) and controlling components. |
|---|
| 34 | |
|---|
| 35 | |
|---|
| 36 | Company |
|---|
| 37 | ------- |
|---|
| 38 | |
|---|
| 39 | The main web application and container class is called 'Company' which corresponds to the University container in Kofa. |
|---|
| 40 | |
|---|
| 41 | Products |
|---|
| 42 | -------- |
|---|
| 43 | |
|---|
| 44 | Among others, a company includes a 'products' container which contains the products offered by the company. A product could be a license, a visa or any purchasable merchandise/article. In the base package a product has eight attributes: |
|---|
| 45 | |
|---|
| 46 | - unique product id, |
|---|
| 47 | - title |
|---|
| 48 | - contract title |
|---|
| 49 | - contract_category |
|---|
| 50 | - options (set of product options) |
|---|
| 51 | - valid from |
|---|
| 52 | - valid to |
|---|
| 53 | - terms and conditions |
|---|
| 54 | |
|---|
| 55 | Products don't have a workflow. |
|---|
| 56 | |
|---|
| 57 | Public Documents |
|---|
| 58 | ---------------- |
|---|
| 59 | |
|---|
| 60 | Public documents, which are likewise put up in a 'documents' container, are meant for publishing content on the portal. There are three types of public documents: |
|---|
| 61 | |
|---|
| 62 | - PDF documents |
|---|
| 63 | - HTML documents |
|---|
| 64 | - REST documents |
|---|
| 65 | |
|---|
| 66 | The first can be used to provide pdf files for download. The second and third can be used to create multilingual static html pages on the portal. HTML documents expect html coded text as input, REST documents expect reRtructuredText which is transformed into html. Public documents have a publication workflow with two states: created and published. Only published documents can be seen by anonymous users. |
|---|
| 67 | |
|---|
| 68 | Customers |
|---|
| 69 | --------- |
|---|
| 70 | |
|---|
| 71 | The company container also contains a 'customers' container which again contains all customers of the company. A customer object itself is also a container, containing all the documents and contracts owned by the customer. Beyond that, a customer is also an authenticated user of the system with a user account adapted to each customer object. |
|---|
| 72 | |
|---|
| 73 | The attributes of a customer in the base package are: customer id, firstname, middlename, lastname, sex, email, phone and a unique registration number which can be set by the company. |
|---|
| 74 | |
|---|
| 75 | Customers have a registration workflow with four states: created, started, requested and approved. |
|---|
| 76 | |
|---|
| 77 | Customer accounts can be temporarily suspended. Although suspension is not part of the workflow it does appear in the customer's workflow history. |
|---|
| 78 | |
|---|
| 79 | Only approved customers can conclude contracts (see below). |
|---|
| 80 | |
|---|
| 81 | Customer Documents |
|---|
| 82 | ------------------ |
|---|
| 83 | |
|---|
| 84 | Customers are requested to upload scanned documents and images required e.g. for the conclusion of contracts. Each uploaded file is connected with a document object which carries the metadata of the scanned document. In the base package a customer document has only a title, a unique document id and an md5 attribute. The latter contains the md5 checksum of the connected (binary) file after verification. |
|---|
| 85 | |
|---|
| 86 | Documents have a verification workflow with five states: created, submitted, verified, rejected and expired. |
|---|
| 87 | |
|---|
| 88 | Various document classes can be implemented and selected by the customer to make customization as flexible as possible. |
|---|
| 89 | |
|---|
| 90 | Verified documents cannot be edited or manipulated. The md5 checksum proves the genuineness of the uploaded file. |
|---|
| 91 | |
|---|
| 92 | A pdf document slip can be downloaded. The slip is composed of a covering page and the scanned document badged by a watermark. |
|---|
| 93 | |
|---|
| 94 | Contracts |
|---|
| 95 | --------- |
|---|
| 96 | |
|---|
| 97 | Contracts are being concluded between the company and the customer. The customer applies for a contract by |
|---|
| 98 | |
|---|
| 99 | 1. selecting a proper form (= contract class), |
|---|
| 100 | 2. selecting one of the products which belong to the contract class, |
|---|
| 101 | 3. filling the contract form, |
|---|
| 102 | 4. uploading required documents, |
|---|
| 103 | 5. submitting the documents for verification, |
|---|
| 104 | 6. linking the submitted documents on the contract form, |
|---|
| 105 | 7. submitting the contract form for approval. |
|---|
| 106 | |
|---|
| 107 | Company officers verify the documents and finally approve the contract which means that the contract is concluded. The contract can also be rejected or expire. |
|---|
| 108 | |
|---|
| 109 | Each contract class belongs to a contract category. The contract category defines the subset of products which can be selected when configuring the contract (see Products section above). |
|---|
| 110 | |
|---|
| 111 | A contract in the base package has a title, a unique contract id, one document reference, one product reference and list of product options. A customized contract can have several document references, but it can only refer to a single product offered by the company. The product options determine the fees to be paid before a contract can be concluded. |
|---|
| 112 | |
|---|
| 113 | A contract can only be submitted if all documents attached to the contract have been at least submitted for verification. |
|---|
| 114 | |
|---|
| 115 | The contract workflow has the following states: created, submitted, approved, rejected and expired. |
|---|
| 116 | |
|---|
| 117 | A pdf contract slip can be downloaded. |
|---|
