Forum .LRN Q&A: Re: LORSm SCORM issues

Collapse
3: Re: LORSm SCORM issues (response to 1)
Posted by Michele Slocovich on
In order to make a bit of clarity regarding the categories for the problems:

a) LORS problems: these are "course loading" problems and have to do with lors::imscp and (maybe) lors::imsmd calls. These problems consist of treating correctely weird characters, paths, sizing correctely the fields of the datamodel, and doing everything consistentely with the delivery process, which is based on lors::cr::get_item_id and lorsm::delivery, lorsm::get_ims_item_id and maybe others.

b) Delivery problems: javascript to java collaboration and dialogue with servlet. Each course seems to require different behaviour from the client. Some seem to expect the window to close when they issue LMSFinish, others don't even bother sending LMSFinish when they reach their end or get unloaded (so they expect the client to do that on their part ?).

c) tracking problems (regarding both the datamodel for the scorm runtime, its trackability and the rendering/extraction of the data - done in through the "tracking-rte")

Collapse
4: A) course loading problem (response to 3)
Posted by Michele Slocovich on
as an example the lenght of many fields won't be enough.
it depends on every course, but the main problem is that we are using fixed lenght fields for storing an XML structure.
So, as an example, i needed to change this

-- SCORM extensions (based on SCORM 1.2 specs)
prerequisites_t varchar(100),
prerequisites_s varchar(200),
type varchar(1000),
maxtimeallowed varchar(1000),
timelimitaction varchar(1000),
datafromlms varchar(200),
masteryscore varchar(255),
isshared boolean default 'f' not null,
sort_order integer

into

-- SCORM extensions (based on SCORM 1.2 specs)
prerequisites_t varchar(100),
prerequisites_s varchar(2000),
type varchar(1000),
maxtimeallowed varchar(1000),
timelimitaction varchar(1000),
datafromlms varchar(200),
masteryscore varchar(255),
isshared boolean default 'f' not null,
sort_order integer

unfortunately, due to dependent constraints, it's very difficult to do this on a running system. or is there a shortcut ?

(PS i've tried:
ALTER TABLE ims_cp_items ALTER pr_old TYPE character varying(2000);
or the column rename copy drop for postgres 7.4
)