Return to Domain_Coordination_Overview.tex CVS log

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

Annotation of loncom/html/adm/help/tex/Domain_Coordination_Overview.tex, revision 1.9

1.2       raeburn     1: \label{Domain_Coordination_Overview}
1.1       raeburn     2: The Domain Coordination Manual includes both a description of tasks
1.4       raeburn     3: which require standard LON-CAPA interaction via a web browser, with
1.1       raeburn     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
1.5       raeburn     6: one individual may complete both these types of task, whereas in others
1.1       raeburn     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
1.8       raeburn    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.
1.1       raeburn    22: 
                     23: LON-CAPA provides hooks to permit integration with institutional information
                     24: systems to support the following procedures:
                     25: 
                     26: \begin{itemize}
1.5       raeburn    27: \item Authentication via an institutional authentication service (e.g., LDAP)
1.1       raeburn    28: \item Automatic updates of classlists
                     29: \item Automatic updates of user information
1.8       raeburn    30: \item Automatic processing of validated course requests for ``official'' courses. 
1.1       raeburn    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}
1.8       raeburn    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,
1.3       raeburn    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.
1.1       raeburn    47: 
                     48: Besides the integration described above, at present customization
1.6       raeburn    49: of \emph{localenroll.pm} is also needed to define user population terms/titles
1.3       raeburn    50: used at an institution (e.g., Faculty, Staff, Students), and also
                     51: to define official course categories (e.g., Year, Semester, Department,
1.7       bisitz     52: Number) which can be used as filters when searching the Course/Community Catalog.
1.8       raeburn    53: 
                     54: LON-CAPA installation and/or update will provide unmodifed copies of the three 
1.9     ! raeburn    55: customizable files in \emph{/home/httpd/lib/perl}, each with -std appended, i.e., 
1.8       raeburn    56: \emph{localauth-std.pm}, \emph{localenroll-std.pm}, and 
                     57: \emph{localstudentphoto-std.pm}.  These files receive updates when ./UPDATE is 
                     58: run to update a LON-CAPA installation to a newer version, while their 
                     59: customized equivalents will be left untouched.
                     60: 
                     61: If you have previously customized localenroll.pm it is recommended that
                     62: you compare the contents of localenroll.pm and localenroll-std.pm after
                     63: an update to see if there are new subroutines (which exist as stubs in
                     64: localenroll-std.pm) which can be copied to your custom localenroll.pm
                     65: and later customized, should you wish to use that functionality.