Index: openacs-4/packages/assessment/www/doc/index.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/index.html,v
diff -u -r1.2 -r1.3
--- openacs-4/packages/assessment/www/doc/index.html	3 Jul 2004 22:38:06 -0000	1.2
+++ openacs-4/packages/assessment/www/doc/index.html	29 Jul 2004 09:35:11 -0000	1.3
@@ -68,8 +68,7 @@
 packages. In particular, incorporating Workflow and a new data
 collection package would be key to creation of new vertical-application
 tools like dotWRK. Such integration would also be immensely useful for
-a clinical trials management toolkit.
-    </p>
+a clinical trials management toolkit. </p>
   </li>
   <p></p>
 </ul>
@@ -112,28 +111,20 @@
 Surveys included several important enhancements to the data model:
     <ul>
       <li> Conditional branching within a survey (though how well
-worked out this is remains unclear)
-      </li>
-      <li> "Folder" based repositories of questions and sections
-      </li>
+worked out this is remains unclear) </li>
+      <li> "Folder" based repositories of questions and sections </li>
     </ul>
-    <p>
-However, Surveys has some important limitations:
-    </p>
+    <p>However, Surveys has some important limitations: </p>
     <ul>
       <li> Surveys are "published" as static HTML files which are
-served out to users when they complete the survey
-      </li>
-      <li> The package doesn't use a templating system
-      </li>
-      <li> Oracle-only
-      </li>
+served out to users when they complete the survey </li>
+      <li> The package doesn't use a templating system </li>
+      <li> Oracle-only </li>
     </ul>
     <p>Still, this package adopts some naming conventions consistent
 with
 the IMS spec and definitely represents the closest effort to a "complex
-survey" done to date.
-    </p>
+survey" done to date. </p>
     <p></p>
   </li>
   <li> "Complex Survey". This is the descendant of
@@ -144,8 +135,7 @@
 incorporates a number of the features of Surveys. We discuss it in
 greater detail <a
  href="http://openacs.org/projects/openacs/packages/assessment/specs/survey-review">here</a>.
-    <p>
-    </p>
+    <p> </p>
   </li>
   <li> Questionnaire. This is a 3.2.5 module developed at <a
  href="http://www.epimetrics.com/">The Epimetrics Group</a> in order to
@@ -192,19 +182,29 @@
 <h2>Data modell</h2>
 The data modell is described in detail in the <a
  href="data-modell.html">design descriptions</a>. <br>
-<h2>User Interface</h2>
+<h2><a href="user_interface/index.html">User Interface</a></h2>
 The UI for Assessment divides into a number of primary functional
-areas, as diagrammed below. These include:
+areas, with the entry page located <a href="user_interface/index.html">here</a>.
+It is split up into multiple sections:<br>
 <ul>
-  <li> the "Home" area (for lack of a better term). These are the main
-index pages for the user and admin sections </li>
-  <li> Assessment Authoring: all the pages involved in creating,
-editing, and deleting the Assessments themselves; these are all admin
-pages </li>
-  <li> Assessment Delivery: all the pages involved in
+  <li><a href="user_interface/assessment_creation.html"> Assessment
+Authoring</a>: all the pages involved in creating,
+editing, and deleting the Assessments themselves</li>
+  <li><a href="user_interface/section_creation.html">Section Authoring</a>:
+all the pages involved in creating,
+editing, and deleting the Sections themselves. Includes the page to
+browse for items to include in sections</li>
+  <li><a href="user_interface/item_creation.html">Item Authoring and
+Catalogue</a>: all the pages involing the item creation and the item
+catalogue.</li>
+  <li><a href="user_interface/user_experience.html"> Assessment Delivery</a>:
+all the pages involved in
 deploying a given Assessment to users for completion, processing those
 results, etc; these are user pages </li>
-  <li> Assessment Review: all the pages involved in select
+  <li><a href="user_interface/tests.html">Section on Tests</a>:
+Currently still split away, some notes on additional user interface for
+test. Shall be integrated with the rest of the pages.</li>
+  <li>Assessment Review: all the pages involved in select
 data extracts and displaying them in whatever formats indicated; this
 includes "grading" of an Assessment -- a special case of data review;
 these are admin pages, though there also needs to be some access to
@@ -215,15 +215,13 @@
 other "policies" of an Assessment. This area needs to interact with the
 next one in some fashion, though exactly how this occurs needs to be
 further thought through, depending on where the Site Management
-mechanisms reside. </li>
-  <li> Site Management: pages involved in setting up who
-does Assessments. These are admin pages and actually fall outside the
-Assessment package per se. How dotLRN wants to interact with Assessment
-is probably going to be different from how a Clinical Trials Management
-CTM system would. But we include this in our diagram as a placeholder.</li>
+mechanisms reside.</li>
 </ul>
-More information can be found at the <a href="page_flow.html">Page Flow</a>
-page.<br>
+<br>
+The&nbsp; <a href="page_flow.html">Page Flow</a>
+page is diagrammed below and should give a very rough and outdated
+overview, but still good for getting an impression.<br>
+<br>
 <h2>Authors</h2>
 The specifications for the assessment system have been written by Stan
 Kaufman and Malte Sussdorff with help from numerous people within and