Annotation of loncom/html/adm/help/tex/Domain_Coordination_Overview.tex, revision 1.2
1.2 ! raeburn 1: \label{Domain_Coordination_Overview}
1.1 raeburn 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 boththese 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 authntication 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 (localauth.pm and
33: localenroll.pm) which need to be customized to provide the integration
34: with institutional systems. Although customization and testing will
35: involve a systems administrator, and programmer(s) at an institution,
36: a Domain Coordinator is likely to be involved in the design and testing
37: phases of the integration, if not in the actual implementation. Set-up
38: of a standalone LON-CAPA instance on a separate server is advised
39: for the purposes of implementing and testing institutional integration,
40: before enabling the new functionality on the production system.
41:
42: Besides the integration described above, at present customization
43: of localenroll.pm is also needed to define user populations used at
44: an institution (e.g., Faculty, Staff, Students), and also to define
45: official course categories (e.g., Year, Semester, Department, Number)
46: which can be used as filters when searching the Course Catalog.
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>