Ignore:
Timestamp:
18 Jun 2015, 08:18:16 (10 years ago)
Author:
Henrik Bettermann
Message:

More docs.

In the documentation we prefer to speak of applicant records and avoid the term application as best as we can.

Location:
main/waeup.kofa/trunk/docs
Files:
5 edited

Legend:

Unmodified
Added
Removed
  • main/waeup.kofa/trunk/docs/INSTALL.txt

    r12968 r13075  
    2222
    2323The Kofa packages are based on `Grok`_, which is a Python_
    24 framework for agile webapplication development. Grok_ itself is based
     24framework for agile web application development. Grok_ itself is based
    2525on `Zope`_.
    2626
  • main/waeup.kofa/trunk/docs/source/userdocs/applicants.rst

    r12908 r13075  
    1 .. _application_section:
     1.. _applicant_section:
    22
    3 Application Section :sup:`in progress`
    4 **************************************
     3Applicant Section :sup:`in progress`
     4************************************
     5
     6Applicants and Students are different entities. Moreover, the student section is completely independent from the applicant section. Kofa can be configured without its `applicants` module but not without its `students` module.
     7
     8Anonymous users can self-register and automatically become applicants (users) of the portal. The number of applicants is not limited and, theoretically, Kofa can host hundredthousands of applicants in various applicants containers. Usually, only a few of them are beeing accepted for studying at the university. Once the application process has ended, admitted applicants are transformed into student records.  New student records are created and the data are copied from the applicant records. When this 'student creation' process is finished, the applicant records are dispensable. Aim was to provide an easy way to get rid of the huge batches of applicant records by only one click, in order to keep the database clean and tidy. The process is described further below.
     9
     10.. note::
     11
     12  The term 'application' has a double meaning in English. An 'application' in computer sciences is understood as a software or web application. Software developers may get confused by using the term in a different context. To take this into account, we prefer to speak of an 'applicant' in this documentation, instead of an 'application' although, in the linguistic context, it sometimes makes more sense to speak of the latter. However, in the user interface (UI) and also in Python docstrings the term 'application' predominates.
  • main/waeup.kofa/trunk/docs/source/userdocs/datacenter/logging.rst

    r12901 r13075  
    158158
    159159The creation, editing and removal of applicants containers as well
    160 as editing application records (applicants) is being logged. Also
     160as editing applicant records is being logged. Also
    161161the approval of payment tickets and all other payment ticket
    162162transactions are being recorded in ``applicants.log``. Kofa also
    163163logs all workflow transitions into both the applicant's history
    164164attribute and the logfile. Okay, this is somehow redundant, but it
    165 has proved useful to get a complete overview over all application
     165has proved useful to get a complete overview over all applicant
    166166data transactions also in the logfile. In return, Kofa does not
    167167aditionally log actions of browser pages if a workflow transition is
     
    186186An applicants container was added first. The `startdate`, `enddate`
    187187and the `application_fee` attributes were edited and a new
    188 application record (applicant) was added some seconds later. The
     188applicant record was added some seconds later. The
    189189`ApplicantManageFormPage` was opened, `reg_number`, `sex`, `course1`
    190190and `date_of_birth` was edited and the ``start`` transition was
     
    195195applicant subsequently admitted. The form was automatically locked
    196196(see time difference). A student container was created and filled
    197 with the data from the application record. Finally, the entire
     197with the data from the applicant record. Finally, the entire
    198198applicants container including its content was removed in the same
    199199transaction, see time diffence between the last two log entries.
     
    205205The following example shows a typical Nigerian logfile excerpt for a
    206206student from the very beginning (student record creation from
    207 application data) till the first registration of courses at level
     207applicant data) till the first registration of courses at level
    208208100. Such an excerpt can be produced simply by searching for
    209209``B1234567`` on the ``students.log`` search page::
  • main/waeup.kofa/trunk/docs/source/userdocs/index.rst

    r13047 r13075  
    77   install
    88   academics
     9   students
    910   applicants
    10    students
    1111   hostels
    1212   documents
  • main/waeup.kofa/trunk/docs/source/userdocs/security.rst

    r13045 r13075  
    8989   :noindex:
    9090
    91 Application Section Permissions
    92 -------------------------------
     91Applicant Section Permissions
     92-----------------------------
    9393
    9494.. autoclass:: waeup.kofa.applicants.permissions.ViewApplication()
     
    199199   :noindex:
    200200
    201 Global Application Section Roles
    202 --------------------------------
    203 
    204 Global Application Section Roles are assigned portal-wide (globally)
    205 but do actually only allocate permissions in the Application Section.
     201Global Applicant Section Roles
     202------------------------------
     203
     204Global Applicant Section Roles are assigned portal-wide (globally)
     205but do actually only allocate permissions in the applicant section.
    206206
    207207.. autoclass:: waeup.kofa.applicants.permissions.ApplicantRole()
     
    218218
    219219Global Student Section Roles are assigned portal-wide (globally) but
    220 do actually only allocate permissions in the Student Section.
     220do actually only allocate permissions in the student section.
    221221
    222222.. autoclass:: waeup.kofa.students.permissions.StudentRole()
     
    249249strange that some of these 'odd' roles do not give more permissions
    250250than the user already has due to other roles. Their real purpose is to
    251 delegate permissions to the students or application section. If a user
     251delegate permissions to the students or applicant section. If a user
    252252has for example the LocalStudentsManager role described below at
    253253department level, s/he automatically gets the StudentsManager role for
Note: See TracChangeset for help on using the changeset viewer.