[LON-CAPA-cvs] cvs: loncom /html/adm/help/tex Domain_Coordination_Overview.tex

[raeburn]

raeburn		Mon Jul 28 19:23:16 2008 EDT

  Modified files:              
    /loncom/html/adm/help/tex	Domain_Coordination_Overview.tex 
  Log:
  - Provide location of localauth.pm and localenroll.pm
  
  
Index: loncom/html/adm/help/tex/Domain_Coordination_Overview.tex
diff -u loncom/html/adm/help/tex/Domain_Coordination_Overview.tex:1.2 loncom/html/adm/help/tex/Domain_Coordination_Overview.tex:1.3
--- loncom/html/adm/help/tex/Domain_Coordination_Overview.tex:1.2	Mon Jul 28 10:00:00 2008
+++ loncom/html/adm/help/tex/Domain_Coordination_Overview.tex	Mon Jul 28 19:23:16 2008
@@ -29,18 +29,19 @@
 \item Searches for users at the institution
 \item Automatic import of student photos from an institutional repository
 \end{itemize}
-There are two perl modules included in LON-CAPA (localauth.pm and
-localenroll.pm) which need to be customized to provide the integration
-with institutional systems. Although customization and testing will
-involve a systems administrator, and programmer(s) at an institution,
-a Domain Coordinator is likely to be involved in the design and testing
-phases of the integration, if not in the actual implementation. Set-up
-of a standalone LON-CAPA instance on a separate server is advised
-for the purposes of implementing and testing institutional integration,
-before enabling the new functionality on the production system.
+There are two perl modules included in LON-CAPA (\emph{localauth.pm}
+and \emph{localenroll.pm}, both located in \emph{/home/httpd/lib/perl})
+which need to be customized to provide the integration with institutional
+systems. Although customization and testing will involve a systems
+administrator, and programmer(s) at an institution, a Domain Coordinator
+is likely to be involved in the design and testing phases of the integration,
+if not in the actual implementation. Set-up of a standalone LON-CAPA
+instance on a separate server is advised for the purposes of implementing
+and testing institutional integration, before enabling the new functionality
+on the production system.
 
 Besides the integration described above, at present customization
-of localenroll.pm is also needed to define user populations used at
-an institution (e.g., Faculty, Staff, Students), and also to define
-official course categories (e.g., Year, Semester, Department, Number)
-which can be used as filters when searching the Course Catalog.
+of \emph{localenroll.pm} is also needed to define user populations
+used at an institution (e.g., Faculty, Staff, Students), and also
+to define official course categories (e.g., Year, Semester, Department,
+Number) which can be used as filters when searching the Course Catalog.