Changeset 15163 for main/waeup.kofa/trunk/docs
- Timestamp:
- 23 Sep 2018, 05:05:04 (6 years ago)
- Location:
- main/waeup.kofa/trunk
- Files:
-
- 5 edited
Legend:
- Unmodified
- Added
- Removed
-
main/waeup.kofa/trunk
- Property svn:mergeinfo changed
/main/waeup.kofa/branches/henrik-transcript-workflow (added) merged: 15127-15128,15133-15134,15140-15143,15145-15150,15152-15155,15157-15160,15162
- Property svn:mergeinfo changed
-
main/waeup.kofa/trunk/docs/source/userdocs/datacenter/export.rst
r15051 r15163 282 282 .. autoattribute:: waeup.kofa.students.export.SessionPaymentsOverviewExporter.fields 283 283 .. autoattribute:: waeup.kofa.students.export.SessionPaymentsOverviewExporter.title 284 .. autoattribute:: waeup.kofa.students.export.SessionPaymentsOverviewExporter.curr_year285 284 .. automethod:: waeup.kofa.students.export.SessionPaymentsOverviewExporter.mangle_value() 286 285 -
main/waeup.kofa/trunk/docs/source/userdocs/datacenter/import_stages.rst
r12998 r15163 8 8 :ref:`Data Center Doctests <datacenter_txt>` 9 9 10 The term 'data import' actually understates the range of func nctions10 The term 'data import' actually understates the range of functions 11 11 importers really have. As already stated, many importers do not only 12 12 restore data once backed up by exporters or, in other words, take -
main/waeup.kofa/trunk/docs/source/userdocs/security.rst
r14948 r15163 241 241 :noindex: 242 242 243 .. autoclass:: waeup.kofa.students.permissions.TranscriptOfficer() 244 :noindex: 245 246 .. autoclass:: waeup.kofa.students.permissions.TranscriptSignee() 247 :noindex: 248 243 249 .. _local_roles: 244 250 … … 306 312 .. autoclass:: waeup.kofa.permissions.CourseAdviser100() 307 313 :noindex: 314 315 .. autoclass:: waeup.kofa.permissions.LocalTranscriptOfficer() 316 :noindex: 317 318 .. autoclass:: waeup.kofa.permissions.LocalTranscriptSignee() 319 :noindex: -
main/waeup.kofa/trunk/docs/source/userdocs/students/workflow.rst
r13610 r15163 28 28 29 29 a 30 created ------- admitted 31 b | 32 +----------------+ 33 | e 34 +------------------------------------------------------+ 35 | c d | 36 clearance started ------- clearance requested ------- cleared 37 | 38 f | 39 +--------+---------------------------------------------+ 40 | | 41 | h school fee paid -------- returning -------------+ 42 | | \ l | | 43 +--------+ g \ _ _ _ m | k | 44 | \ | | 45 courses registered ------ courses validated | 46 | i | | 47 | | n | 48 | j | | 49 | graduated | 50 | | | 51 | | o | 52 | | | 53 | transcript requested | 54 a: admit | | 55 -a: reset1 +---------------------------------+ 56 b: start_clearance 57 -b: reset2 58 c: request_clearance 59 -c: reset3 (= reject request) 60 d: clear 61 -d: N/A 30 created ------- admitted 31 b | 32 +----------------+ 33 | e 34 +------------------------------------------------------+ 35 | c d | 36 clearance started ------- clearance requested ------- cleared 37 | 38 f | 39 +--------+---------------------------------------------+ 40 | | 41 | h school fee paid -------- returning -------------+ 42 | | \ l | | 43 +--------+ g \ _ _ _ m | k | 44 | \ | | 45 courses registered ------ courses validated | 46 | i | | 47 | | n | 48 | j | | 49 | +-- graduated | 50 | | | | 51 | | | o | 52 | | | | 53 | | transcript requested | 54 a: admit | | | | 55 -a: reset1 | r | | p | 56 b: start_clearance | | | | 57 -b: reset2 | | transcript validated | 58 c: request_clearance | | | | 59 -c: reset3 | | | q | 60 (= reject request) | | | | 61 d: clear | +-- transcript released | 62 -d: N/A +---------------------------------+ 62 63 e: N/A 63 64 -e: reset4 (= annul clearance) … … 81 82 -n: N/A 82 83 o: request_transcript 83 -o: process_transcript 84 84 -o: reset10 (= reject request) 85 p: validate_transcript 86 -p: N/A 87 q: release_transcript 88 -q: N/A 89 r: N/A 90 -r: reset11 85 91 86 92 Student registration starts with the first login of the student into … … 131 137 list. 132 138 139 After graduation, former students (alumni) can apply for an official 140 transcript. The transcript processing workflow (**opqr**) is a 141 subset of the registration workflow which starts in state 142 ``graduated``. Many people are involved in transcript processing. 143 Therefore, Kofa provides two additional roles, the Transcript 144 Officer and Transcript Signee roles. Both are available globally and 145 locally (at faculty level). First of all, the graduated student has 146 to request a transcript **(o)** by filling a request form. The 147 Transcript Officer will see the new request and can either reject 148 the request **(-o)** or validate the request **(p)**. Before 149 validation course results can be edited or added. After validation 150 the entire studycourse including its content is locked. Nobody will 151 be able to modify the course lists, neither through the UI nor by 152 import. Transcripts can now be electronically signed by Transcript 153 Signees. Once all signees have done their job, the Transcript 154 Officer can release the transcript **(q)**. A pdf file is created 155 and stored in the file system. The transcript pdf slip contains all 156 signatures. The dynamic transcript generation is disabled. Nothing 157 can be changed now, unless the entire transcript process is reset 158 **(-r)** by a Students Manager. Then comments and signatures will be 159 removed and the pdf file deleted. The student can start afresh. 160 133 161 134 162 .. _registration_workflow_batch_processing:
Note: See TracChangeset for help on using the changeset viewer.