Index: openacs-4/packages/imsld/www/doc/ch04s01.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/imsld/www/doc/ch04s01.html,v diff -u -r1.4 -r1.5 --- openacs-4/packages/imsld/www/doc/ch04s01.html 30 Jun 2005 10:43:20 -0000 1.4 +++ openacs-4/packages/imsld/www/doc/ch04s01.html 5 Jul 2005 16:13:45 -0000 1.5 @@ -5,114 +5,103 @@ if(pos=="center"){LeftPosition=(screen.width)?(screen.width-w)/2:100;TopPosition=(screen.height)?(screen.height-h)/2:100;} settings='width='+w+',height='+h+',top='+TopPosition+',left='+LeftPosition+',scrollbars='+scroll+',location=no,directories=no,status=no,menubar=no,toolbar=no,resizable=no'; win=window.open(mypage,myname,settings);} -

Level A

+ references to files, etc.

  • imsld_time_limits

    • time_limit_id

    • time_limit - amount of time in a specific format

    • property_id ** - references imsld_properties

  • imsld_parameters

    • parameter_id

    • parameter_value

  • imsld_imsld_objects_map. This is a very importan table in this + data model, because it is used to map almost every imsld_* to every + imsld_*. For instance, the activities that are part of a component + are mapped by this table, and the acts to complete play are also + mapped using this table. This is just a representation of the + acs_rels table, because at the implementation phase, acs_rels will + be used with different rel_types

    • imsld_object_one_id - references imsld_* + (acs_objects)

    • imsld_object_one_type - wich can be: learning_object, + imsld_item, imsld_role, support_activity, etc

    • imsld_object_two_id - references imsld_* + (acs_objects)

    • imsld_object_two_type - same as + imsld_object_one_type

  • IMPORTANT NOTES:

    1. The last table will use acs_rels. The rel_types will be + completely defined in the implementation phase. By now we can think + of: parent_item_rel, role_parts_activites_rel, component_service_rels, + service_roles_rel, learning_object_item_rel, + plays_to_complete_method_rel and role_parts_to_complete_act.

    2. There are some important IMS-LD tags (learning objectives, for + instance) that does not have a table for themselves, but this is + because such tags consist only of a reference to a itemmodel or + another table, so there is no need to create a table just for + that.

    3. This data model can (and it is 99% sure) change in the + implementation phase, but we will base the development on this data + model.

    4. There are some tables in this data model that will be related to + some others of other .LRN packages. For instance, the table + imsld_conferences will be used to store the synchronous type (forums) + and asynchronous type (chats) of conferences. Also, we will use + acs_objects for the imslds, activities, services, learning_objects, + components, and for every case we find it useful. We can make use of + the cr_items too. But that is something that we will know better in + the implementation phase.