thx scott for the good work on the rim stuff. I modified all the PAS-Otrunk steps to use the new persistence mechanism. This required changes to assessment classes.
the questions remain: when we create a new step in the authoring tool its responsible for generating the id? converter too? -Tony On Apr 27, 2008, at 5:33 AM, Scott Cytacki wrote: > > Anthony Perritano wrote: >> So i have been looking and stepping through the helloworld example >> that uses rims for Pas-Otrunk based steps trying to figure out how to >> apply that to Notes and QTI based steps. >> >> >> All we need to do then is replicate the >> property responseDeclarationsToRims on to the OTAssessmentController >> right? which will save the map of responseDeclarationToRims to OTML. >> once read in the LoadReadObject method that property will be set on >> the real notebean. the above code should be able to be used. the >> agentService should be available and able to look up the sock. > > I don't think you need save the the map "responseDeclarationsToRims" > to > otml. It can be created on the fly each time OTAssessmentController > sets up the Assessment object. > Looking at the code you sent you basically replace: > Rim rim = responseDeclarationsToRims.get(rd); > with > Rim rim = new OTrunkRim(rd.getIdentifier(), String.class, > otAssessment); > > Without the map an authoring tool just has to update the QTI; it > wouldn't need to update the QTI and the map. And likewise a > reporting > tool would parse the QTI figure out the responseDeclarations and look > for the corresponding rims. Additionally it means there is no > "rims" > mentioned in the otml file, so if we plug in a different learner data > saving mechanism the otml format for OTAssement shouldn't need to > change. > > Scott > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
