Changeset 13229 for main/waeup.kofa/trunk/docs/source/userdocs/applicants
- Timestamp:
- 26 Aug 2015, 06:42:31 (9 years ago)
- Location:
- main/waeup.kofa/trunk/docs/source/userdocs/applicants
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
main/waeup.kofa/trunk/docs/source/userdocs/applicants/browser.rst
r13108 r13229 10 10 11 11 In create mode, `firstname`, `middlename`, `lastname`, `email` and 12 `phone` are requested. A new record is being created. 12 `phone` are requested. An unused record is taken, or a new 13 record is being created if no unused record is found (see 14 :ref:`description of application modes <application_mode>`). 13 15 14 16 In update mode, only `reg_number`, `lastname` and `email` have to be … … 19 21 number does not exist or the provided lastname does not match. 20 22 Another ``if`` statement checks whether the password has already 21 been set and used, i.e. the theapplication has already been23 been set and used, i.e. the application has already been 22 24 started. If so, the anonymous user can't register again and is being 23 25 requested to proceed to the login page. … … 36 38 exists. Therefore, we strongly recommend to only send credentials to 37 39 email addresses. 40 41 42 .. _container_maintenance: 43 44 Preparation and Maintenance of Applicants Containers 45 ==================================================== 46 47 As described in the :ref:`interfaces chapter <application_mode>`, 48 applicants containers are aware of their application mode. In update 49 mode, containers must be pre-filled by import with application 50 records from an external board. In create mode, the container can 51 remain empty. Each time an applicant registers, a new record is 52 being created and a corresponding user account set up. This is the 53 method of choice, if the number of expected applicants is not very 54 high (e.g. less than 500). Since each single account creation causes 55 a significant growth of Kofa's database, we strongly recommend to 56 pre-fill applicants containers with empty application records, if 57 the number of expected applicants is higher. Pre-filling is done in 58 a single transaction and does thus save database volume when 59 application is running. 60 61 During application, many records are being initialized but not used. 62 For various reasons, many applicants do create one or more 63 application records with corresponding user accounts but fail to log 64 in. These records remain in state ``initialized`` and are never 65 turned to state ``started``. After a while, these records can be 66 safely removed. When purging an applicants container, also all 67 unused pre-filled application records are being removed. If 68 necessary, the container must be pre-filled with empty records again. 38 69 39 70 -
main/waeup.kofa/trunk/docs/source/userdocs/applicants/interfaces.rst
r13170 r13229 64 64 .. _application_mode: 65 65 66 The application mode is either ``create`` or ``update``. In create 67 mode, no record exists, the applicants container is empty. The records 68 are being created after submission of the first form. Applicants are 69 requested to provide all data needed, including their name details. 70 In update mode, the applicants container must have been prefilled by 71 import, e.g. with records provided by an external board. Applicants 72 can't create new records, they can only open and take possession of 73 existing records. Both methods have pros and cons. This is further 74 discussed below. 66 The application mode is either ``create`` or ``update``. In **create 67 mode** the container can be either left empty or it can be 68 pre-filled with fresh and 'unused' records. In the first case, 69 records are being created after submission of the first form. In the 70 second case, unused record are fetched and filled with the form 71 data. In both 'create mode' cases, applicants are requested to 72 provide all data needed, including their name details. In **update 73 mode**, the applicants container must have been pre-filled by import, 74 e.g. with records provided by an external board. These records are 75 called 'used' since they already contain data. Applicants can't 76 create new records in update mode, they can only open and take 77 possession of existing records. 75 78 76 79 The application category is supplied by the
Note: See TracChangeset for help on using the changeset viewer.