Return to Domain_Coordination_Overview.tex CVS log

Up to [LON-CAPA] / loncom / html / adm / help / tex

- Institutional status types now defined using Domain Coordinator's web
  interface for setting domain configuration.

    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, approval of course requests, and assignment of 
   14: author roles. Courses can be created interactively by completing a web 
   15: form or can be created in batch mode by uploading a file containing course
   16: specifications for one or more courses.  The right to submit course requests
   17: via a web form may also be granted to groups of users, and requests can 
   18: be set to be processed automatically, or require Domain Coordinator approval.
   19: Addition of users/roles can similarly be carried out interactively,
   20: or by uploading a text file of users. The Domain Coordinator may also
   21: periodically need to modify domain settings via the Domain Configuration menu.
   22: 
   23: LON-CAPA provides hooks to permit integration with institutional information
   24: systems to support the following procedures:
   25: 
   26: \begin{itemize}
   27: \item Authentication via an institutional authentication service (e.g., LDAP)
   28: \item Automatic updates of classlists
   29: \item Automatic updates of user information
   30: \item Automatic processing of validated course requests for ``official'' courses. 
   31: \item Retrieval of institutional user information for individual users
   32: \item Searches for users at the institution
   33: \item Automatic import of student photos from an institutional repository
   34: \end{itemize}
   35: There are three perl modules included in LON-CAPA (\emph{localauth.pm} 
   36: \emph{localenroll.pm}, and \emph{localstudentphoto.pm} all located in 
   37: \emph{/home/httpd/lib/perl}) which need to be customized to provide 
   38: integration with institutional systems.
   39: 
   40: Although customization and testing will involve a systems administrator,
   41: and programmer(s) at an institution, a Domain Coordinator is likely 
   42: to be involved in the design and testing phases of the integration,
   43: if not in the actual implementation. Set-up of a standalone LON-CAPA
   44: instance on a separate server is advised for the purposes of implementing
   45: and testing institutional integration, before enabling the new functionality
   46: on the production system.
   47: 
   48: Besides the integration described above, customization
   49: of \emph{localenroll.pm} is also needed (at present) to define the
   50: titles used for official course categories (e.g., Year, Semester, Department, Number)
   51: which can be used as filters when searching the Course/Community Catalog.
   52: 
   53: LON-CAPA installation and/or update will provide unmodifed copies of the three 
   54: customizable files in \emph{/home/httpd/lib/perl}, each with -std appended, i.e., 
   55: \emph{localauth-std.pm}, \emph{localenroll-std.pm}, and 
   56: \emph{localstudentphoto-std.pm}.  These files receive updates when ./UPDATE is 
   57: run to update a LON-CAPA installation to a newer version, while their 
   58: customized equivalents will be left untouched.
   59: 
   60: If you have previously customized localenroll.pm it is recommended that
   61: you compare the contents of localenroll.pm and localenroll-std.pm after
   62: an update to see if there are new subroutines (which exist as stubs in
   63: localenroll-std.pm) which can be copied to your custom localenroll.pm
   64: and later customized, should you wish to use that functionality.