Index: openacs-4/packages/assessment/www/doc/page_flow.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/assessment/www/doc/page_flow.html,v
diff -u -r1.1 -r1.2
--- openacs-4/packages/assessment/www/doc/page_flow.html 13 Jun 2004 23:20:44 -0000 1.1
+++ openacs-4/packages/assessment/www/doc/page_flow.html 29 Jul 2004 09:35:11 -0000 1.2
@@ -14,15 +14,12 @@
package will use these OpenACS standards:
- - "trail of breadcrumb" navigational links
-
+ - "trail of breadcrumb" navigational links
- context-aware (via user identity => permissions) menu
options (whether those "menus" are literally menus or some other
-interface widget like toolbars)
-
+interface widget like toolbars)
- in-place, within-form user feedback (eg error messages about a
-form field directly next to that field, not in an "error page")
-
+form field directly next to that field, not in an "error page")
Furthermore, the set of necessary pages for Assessment are not all
that dissimilar to the set required by any other OpenACS package. We
@@ -46,44 +43,59 @@
- the "Home" area (for lack of a better term). These are the main
-index pages for the user and admin sections
-
- - Assessment Authoring: all the pages involved in creating,
+index pages for the user and admin sections
+ - Assessment
+Authoring: all the pages involved in creating,
editing, and deleting the Assessments themselves; these are all admin
-pages
-
+pages
- Assessment Delivery: all the pages involved in
deploying a given Assessment to users for completion, processing those
-results, etc; these are user pages
-
+results, etc; these are user pages
- 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
data displays for general users as well (eg for anonymous surveys etc).
Also, this is where mechanisms that return information to "client"
-packages that embed an Assessment would run.
-
+packages that embed an Assessment would run.
- Session Management: pages that set up the timing and
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.
-
+mechanisms reside.
- 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.
-
+CTM system would. But we include this in our diagram as a placeholder.
-
-So this is how we currently anticipate this would all interrelate:
+In addition to the page flow we have two types of portlets for .LRN:
+
+ - Portlet for the respondee with all assessments that have to be
+answered and their deadlines.
+ - Portlet for staff with all assessments that have to be reviewed
+with review deadline and number of responses still to look at.
+
+More Ideas:
+
+
+ - Possibility to browse assessments and
+sections by category.
+
+
+
+
+
+
+
+
+So this is how we currently anticipate this would all
+interrelate:
-
+ style="width: 950px; height: 1058px;">