File:  [LON-CAPA] / loncom / html / adm / help / tex / Domain_Coordination_Overview.tex
Revision 1.6: download - view: text, annotated - select for diffs
Tue Jul 29 21:02:36 2008 UTC (16 years ago) by raeburn
Branches: MAIN
CVS tags: version_2_9_X, version_2_9_1, version_2_9_0, version_2_8_X, version_2_8_99_1, version_2_8_99_0, version_2_8_2, version_2_8_1, version_2_8_0, version_2_7_X, version_2_7_99_1, version_2_7_99_0, version_2_7_1, version_2_7_0, version_2_6_99_1, bz5969, bz2851, HEAD, GCI_2, GCI_1, BZ5971-printing-apage, BZ5434-fox
- Clarification.

    1: \label{Domain_Coordination_Overview}
    2: The Domain Coordination Manual includes both a description of tasks
    3: which require standard LON-CAPA interaction via a web browser, with
    4: the Domain Coordinator role active, but also tasks which require command
    5: line access to the primary library server in a domain. In some cases
    6: one individual may complete both these types of task, whereas in others
    7: a separate Systems Administrator may need to be called upon for tasks
    8: completed from the command line.
    9: 
   10: With the Domain Coordinator role active, the Main Menu provides a
   11: Domain Coordinator with access to the functionality needed to complete
   12: the routine tasks which a Domain Coordinator carries out, including
   13: creation of courses and assignment of course coordinator and author
   14: roles. Courses can be created interactively by completing a web form,
   15: or can be created in batch mode by uploading a file containing course
   16: specifications for one or more courses. Addition of users/roles can
   17: similarly be carried out interactively, or by uploading a text file
   18: of users. The Domain Coordinator may also periodically need to modify
   19: domain settings via the Domain Configuration menu. 
   20: 
   21: LON-CAPA provides hooks to permit integration with institutional information
   22: systems to support the following procedures:
   23: 
   24: \begin{itemize}
   25: \item Authentication via an institutional authentication service (e.g., LDAP)
   26: \item Automatic updates of classlists
   27: \item Automatic updates of user information
   28: \item Retrieval of institutional user information for individual users
   29: \item Searches for users at the institution
   30: \item Automatic import of student photos from an institutional repository
   31: \end{itemize}
   32: There are two perl modules included in LON-CAPA (\emph{localauth.pm}
   33: and \emph{localenroll.pm}, both located in \emph{/home/httpd/lib/perl})
   34: which need to be customized to provide the integration with institutional
   35: systems. Although customization and testing will involve a systems
   36: administrator, and programmer(s) at an institution, a Domain Coordinator
   37: is likely to be involved in the design and testing phases of the integration,
   38: if not in the actual implementation. Set-up of a standalone LON-CAPA
   39: instance on a separate server is advised for the purposes of implementing
   40: and testing institutional integration, before enabling the new functionality
   41: on the production system.
   42: 
   43: Besides the integration described above, at present customization
   44: of \emph{localenroll.pm} is also needed to define user population terms/titles
   45: used at an institution (e.g., Faculty, Staff, Students), and also
   46: to define official course categories (e.g., Year, Semester, Department,
   47: Number) which can be used as filters when searching the Course Catalog.

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>