Changeset 248
- Timestamp:
- 4 Jun 2006, 19:43:34 (19 years ago)
- Location:
- waeup_doc
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
waeup_doc/MainProcesses.html
r247 r248 472 472 <div class="section"> 473 473 <h1><a id="v-portal-setup" name="v-portal-setup">V Portal Setup</a></h1> 474 <p>The portal will be delivered with infrastructure data. Faculties, Departments, Course Lists, Study Programmes and Hostel data are already imported. Specific roles can be hierarchically assigned to edit or add infrastructure data (see VII Portal Roles).</p> 475 </div> 476 <div class="section"> 477 <h1><a id="vi-access-card-management" name="vi-access-card-management">VI Access Card Management</a></h1> 478 <p>The Access Card (Scratch Card) data are kept outside of the main portal and managed by the Access Card Manager. Each Access Code starts with a prefix depending on the Access Card's function. The prefix defines the value of the Access Card.</p> 474 <p>The portal will be delivered with infrastructure data. Faculties, Departments, Course Lists, Study Programmes and Hostel data are already imported. Specific roles can be hierarchically assigned to edit or add infrastructure data (see also VIII Portal Roles).</p> 475 <p>The portal content types are (not yet all attributes defined):</p> 476 <pre class="literal-block"> 477 Student: see Clearance 478 Faculty: Description 479 Department: Description 480 Course: Decription, Course Number 481 Study Programme: List of Courses 482 Hall: Hall Name 483 Block: Block or Section Name 484 Room: Room Number 485 Bed: Room Letter 486 </pre> 487 </div> 488 <div class="section"> 489 <h1><a id="vi-gown-hiring" name="vi-gown-hiring">VI Gown Hiring</a></h1> 490 <p>(forthcoming)</p> 491 </div> 492 <div class="section"> 493 <h1><a id="vii-access-card-management" name="vii-access-card-management">VII Access Card Management</a></h1> 494 <p>The Access Card (Scratch Card) data are kept outside of the main portal and managed only by the Access Card Manager.</p> 495 <p>The data fields of Access Card records are:</p> 496 <pre class="literal-block"> 497 Series Batch Code 498 Access Code 499 Matric or Registration Number 500 Cost 501 Generated By 502 Date Activated 503 Sold by 504 </pre> 505 <p>Each Access Code starts with a prefix depending on the Access Card's function, i.e. what it is used for. The prefix also defines the value of the Access Card.</p> 479 506 <p>Administrative PINs: ????</p> 480 507 <pre class="literal-block"> 481 Application XXX 482 Clearance XXX 483 Hostal Application XXX 484 Hostal Maintanance XXX 508 Application ??? 509 Clearance ??? 510 Hostal Application HOS 511 Hostal Maintanance ??? 512 Gown Hiring GWN 485 513 </pre> 486 514 <p>School Fee PINs:</p> … … 512 540 Diploma in Comp. Eng DCE 513 541 </pre> 514 <p>New Students' School Fee PINs the prefix <tt class="docutils literal"><span class="pre">NEW</span></tt> is added at the beginning. For example, a new student in the Education Faculty will need to buy a Scratch Card which starts with: <tt class="docutils literal"><span class="pre">NEWEDU</span></tt>.</p>515 </div> 516 <div class="section"> 517 <h1><a id="vii -portal-roles" name="vii-portal-roles">VII Portal Roles</a></h1>542 <p>New Students' School Fee PINs additionally start with the prefix <tt class="docutils literal"><span class="pre">NEW</span></tt>. For example, a new student in the Education Faculty will need to buy a Scratch Card with Prefix: <tt class="docutils literal"><span class="pre">NEWEDU</span></tt>.</p> 543 </div> 544 <div class="section"> 545 <h1><a id="viii-portal-roles" name="viii-portal-roles">VIII Portal Roles</a></h1> 518 546 <div class="section"> 519 547 <h2><a id="portal-manager-pm" name="portal-manager-pm">Portal Manager (PM)</a></h2> … … 526 554 <div class="section"> 527 555 <h2><a id="matric-number-manager-mm" name="matric-number-manager-mm">Matric Number Manager (MM)</a></h2> 528 <p>Only th is role allowsto edit Matriculation Numbers and to access and configure the Matric Number Generation tool.</p>556 <p>Only the Matric Number Manager is allowed to edit Matriculation Numbers and to access and configure the Matric Number Generation tool.</p> 529 557 </div> 530 558 <div class="section"> 531 559 <h2><a id="access-card-manager-am" name="access-card-manager-am">Access Card Manager (AM)</a></h2> 532 <p>The only function of the Access Card Manager will be to generate and administer the Access Codes (PINs). This could be done by a person which completely outside and not assigned to any other role of the portal.</p>560 <p>The only function of the Access Card Manager will be to generate and administer the Access Codes (PINs).</p> 533 561 </div> 534 562 <div class="section"> 535 563 <h2><a id="faculty-manager-fm" name="faculty-manager-fm">Faculty Manager (FM)</a></h2> 536 <p>The Faculty Manager sets up the infrastructure of his/her department and provides content specific to thefaculty. He/She can add or change departments and can assign local roles within all departments.</p>564 <p>The Faculty Manager sets up the infrastructure of his/her faculty and provides content specific to his/her faculty. He/She can add or change departments and can assign local roles within all departments.</p> 537 565 </div> 538 566 <div class="section"> … … 543 571 <div class="section"> 544 572 <h2><a id="course-adviser-ca" name="course-adviser-ca">Course Adviser (CA)</a></h2> 545 <p>The Course Adviser is responsible for the study programmes of each department. He/She selects the courses (from the entire university course list) for each programme and he/she validates the registered courses of each student who studying a programme the CA is responsible for. The CA role is a sub-role of the Department Manager.</p>573 <p>The Course Adviser is responsible for the study programmes of the department. He/She selects the courses (from the entire university course list) for each study programme and validates the registered courses of each student who is studying in the department. The CA role is a sub-role of the Department Manager.</p> 546 574 </div> 547 575 <div class="section"> … … 555 583 </div> 556 584 <div class="section"> 557 <h1><a id="viii-portal-versioning" name="viii-portal-versioning">VIII Portal Versioning</a></h1> 585 <h1><a id="ix-portal-versioning-and-archiving" name="ix-portal-versioning-and-archiving">IX Portal Versioning and Archiving</a></h1> 586 <p>Course specific data (including list of participants) are under version control. Each session new course objects are created on the basis of the data of the previous session.</p> 558 587 </div> 559 588 </div> -
waeup_doc/MainProcesses.rst
r247 r248 213 213 -------------- 214 214 215 The portal will be delivered with infrastructure data. Faculties, Departments, Course Lists, Study Programmes and Hostel data are already imported. Specific roles can be hierarchically assigned to edit or add infrastructure data (see VII Portal Roles). 216 217 218 VI Access Card Management 219 ------------------------- 220 221 The Access Card (Scratch Card) data are kept outside of the main portal and managed by the Access Card Manager. Each Access Code starts with a prefix depending on the Access Card's function. The prefix defines the value of the Access Card. 215 The portal will be delivered with infrastructure data. Faculties, Departments, Course Lists, Study Programmes and Hostel data are already imported. Specific roles can be hierarchically assigned to edit or add infrastructure data (see also VIII Portal Roles). 216 217 The portal content types are (not yet all attributes defined): 218 219 :: 220 221 Student: see Clearance 222 Faculty: Description 223 Department: Description 224 Course: Decription, Course Number 225 Study Programme: List of Courses 226 Hall: Hall Name 227 Block: Block or Section Name 228 Room: Room Number 229 Bed: Room Letter 230 231 232 VI Gown Hiring 233 -------------- 234 235 (forthcoming) 236 237 238 VII Access Card Management 239 -------------------------- 240 241 The Access Card (Scratch Card) data are kept outside of the main portal and managed only by the Access Card Manager. 242 243 The data fields of Access Card records are: 244 245 :: 246 247 Series Batch Code 248 Access Code 249 Matric or Registration Number 250 Cost 251 Generated By 252 Date Activated 253 Sold by 254 255 256 Each Access Code starts with a prefix depending on the Access Card's function, i.e. what it is used for. The prefix also defines the value of the Access Card. 222 257 223 258 Administrative PINs: ???? … … 225 260 :: 226 261 227 Application XXX 228 Clearance XXX 229 Hostal Application XXX 230 Hostal Maintanance XXX 262 Application ??? 263 Clearance ??? 264 Hostal Application HOS 265 Hostal Maintanance ??? 266 Gown Hiring GWN 231 267 232 268 … … 262 298 263 299 264 New Students' School Fee PINs the prefix ``NEW`` is added at the beginning. For example, a new student in the Education Faculty will need to buy a Scratch Card which starts with: ``NEWEDU``. 265 266 267 268 VII Portal Roles 269 ---------------- 300 New Students' School Fee PINs additionally start with the prefix ``NEW``. For example, a new student in the Education Faculty will need to buy a Scratch Card with Prefix: ``NEWEDU``. 301 302 303 VIII Portal Roles 304 ----------------- 270 305 271 306 Portal Manager (PM) … … 282 317 ++++++++++++++++++++++++++ 283 318 284 Only th is role allowsto edit Matriculation Numbers and to access and configure the Matric Number Generation tool.319 Only the Matric Number Manager is allowed to edit Matriculation Numbers and to access and configure the Matric Number Generation tool. 285 320 286 321 Access Card Manager (AM) 287 322 ++++++++++++++++++++++++ 288 323 289 The only function of the Access Card Manager will be to generate and administer the Access Codes (PINs). This could be done by a person which completely outside and not assigned to any other role of the portal.324 The only function of the Access Card Manager will be to generate and administer the Access Codes (PINs). 290 325 291 326 Faculty Manager (FM) 292 327 ++++++++++++++++++++ 293 328 294 The Faculty Manager sets up the infrastructure of his/her department and provides content specific to thefaculty. He/She can add or change departments and can assign local roles within all departments.329 The Faculty Manager sets up the infrastructure of his/her faculty and provides content specific to his/her faculty. He/She can add or change departments and can assign local roles within all departments. 295 330 296 331 Department Manager (DM) … … 303 338 +++++++++++++++++++ 304 339 305 The Course Adviser is responsible for the study programmes of each department. He/She selects the courses (from the entire university course list) for each programme and he/she validates the registered courses of each student who studying a programme the CA is responsible for. The CA role is a sub-role of the Department Manager.340 The Course Adviser is responsible for the study programmes of the department. He/She selects the courses (from the entire university course list) for each study programme and validates the registered courses of each student who is studying in the department. The CA role is a sub-role of the Department Manager. 306 341 307 342 Lecturer (L) … … 317 352 318 353 319 VIII Portal Versioning 320 ---------------------- 321 322 323 354 IX Portal Versioning and Archiving 355 ---------------------------------- 356 357 Course specific data (including list of participants) are under version control. Each session new course objects are created on the basis of the data of the previous session. 358 359 360
Note: See TracChangeset for help on using the changeset viewer.