The As_Item and Section catalogues
+ The As_Item and Section catalogues
are central parts of the assessment system. These repositories
support reuse of Assessment components by storing of the various
as_items (or questions if you like) and groups of as_items (e.g.
Sections) that can be used in an assessment. You are able to
add/edit/delete an as_item of a certain type to a certain scope.
Furthermore it allows you to search and browse for questions for
inclusion in your assesment as well as import and export multiple
-questions using various formats. In this description here we will only
+questions using various formats. In this description here we will only
discuss the design implications for as_items. Green colored tables
-have to be internationlized. Each as_item consists of a specific
+have to be internationlized. Each as_item consists of a specific
as_item Type like "Multiple Choice Question" or "Free Text". Each
-as_item Type adds additional
+as_item Type adds additional
Attributes to the as_item, thereby making it pretty flexible.
-Additionally each as_item has a related display type storing information on how to
+Additionally each as_item has a related display type storing information on how to
display this as_item. This way we can create an adp-snippet which
we can include to display a certain as_item (the snippet is stored
de-normalized in the as_items table and update on every change to
the as_item or the as_item_type). How is this achieved concretely? Each
+ How is this achieved concretely? Each
as_item Type has it's own table with attributes useful for this
as_item type. All tables (as_items, as_item_type_*,
as_item_display_*) are controlled by the content repository. Each
as_item is linked using acs-relationships to the specific items of
the as_item_type_* and as_item_display_* tables. Each as_item
can only be linked to one as_item_type instance and one
as_item_display instance. Categorization and internationalization
+ Categorization and internationalization
will make it into OpenACS 5.2, therefore we are not dealing with it
in Assessment seperately but use the (to be) built in functionality
-of OpenACS 5.2 Additionally we have support functionality
+of OpenACS 5.2 Additionally we have support functionality
for an as_item. This includes the help functionality. To give
Assessment authors flexibility in adapting as_item defaults, help
messages, etc for use in different Assessments, we abstract out a
number of attributes from as_items into mapping tables where
"override" values for these attributes can optionally be set by
authors. If they choose not to set overrides, then the values
-originally created in the as_item supercede. Seperately we will deal with Checks on
+originally created in the as_item supercede. Seperately we will deal with Checks on
as_items. These will allow us to make checks on the input (is the
value given by the user actually a valid value??), branches (if we
display this as_item, which responses have to have been given) and
post-input checks (how many points does this answer
-give). Here is the graphical schema for the
+give). Here is the graphical schema for the
as_item-related subsystems, including the as_item Display subsystem
-described here.Overview
+
-
-
-Core Function: as_items
-
+
Each item_display_type has a couple of -attributes in common.
Each item_display_type has a couple of +attributes in common.
+Depending on the presentation_types
+
+ Depending on the presentation_types
additonal attributes (presentation_type
attributes) come into play (are added as attributes to the
CR item type) (mark: this is not feature complete. It really is up
@@ -254,7 +276,8 @@
mentioning all HTML possibilities associated with each type (e.g. a
textarea has width and heigth..) as these can be parsed in via the
html_display_options.
-
+
Relationship attributes:
Relationship attributes:
+
+
+
Messages (as_messages) abstracts
out help messages (and other types of messages) for use in this
-package. Attributes include:
+package. Attributes include: