This page is to document what tasks and schedule related to integrating OTrunk into SAIL-Core.
Concrete Steps
- Tony working with Scott to port a Pas Step Type to work as a OTObject and OTView.
- At the Sail 07 Retreat give a demonstration of some basic Pas on top of OTrunk code.
More general Plan
- initial version doesn't need changes to sail-core, it can use the same sail-otrunk project that is used by UDL, DIY, and OTrunkExample systems.
- This uses a single POD to represent the curnit
- This single POD contains a root OT Object
- The user data is saved into a single Rim within that POD
- This first version will not work with the existing reporting functionality. So it will require abstracting that functionality so it can work both with both Rims/Socks/SockEntries, and with OTrunk learner data files.
- So the reporting mechanisms in the sds, and portal report tool need to be updated to handle it.
- With this first version it should be easier to create an authoring tool.
- The authoring tool can manipulate to the OTObject representing the project, activity, and steps and when activity is saved those changes will be persisted.
- After the initial version, we can start to look at loosely-integrating OTrunk into sail-core
- If we see that SAIL-core is tightly-coupled to the POD (ie assembly of curnit), we will also need to abstract that part away so other data management entity (like OTrunk) can easily be used also.