2004-10-20
-----------

== Possible Reload improvements ==
 * Rather than adding loads of extra complication to the WCKER to translate user input to the correct formats for the specifications, we should add new widgets that do the job, e.g. VCARD ([http://www.imsglobal.org/metadata/imsmdv1p2p1/imsmd_bindv1p2p1.html#1187732 IMS ref], [http://www.imsglobal.org/metadata/imsmdv1p2p1/imsmd_bindv1p2p1.html#1184094 IMS ref]), ISO 8601 (date, time, [http://www.w3.org/TR/xmlschema-2/#duration duration]), others? This is a good approach as the new widgets can be reused wherever their datatypes are used in the existing Reload.

== Questions to be answered ==

 * How do we see the TALL Short Course Wizard fit into productions processes? 
   * Do we use Reload at the moment?
   * Were does the TALL Short Course Wizard fit into our [wiki:TallCourseProductionProcess process]
   * How do we think other people will use our/other wizards created with the WCKER?
 * Do we want to give the option to add metadata or do we leave it on the reload level?

== Information to ask for in TALL Short Course Wizard ==
{{{
#!html
<dl>
 <dt>
Content Packaging
 </dt>
 <dd>all the information to create the manifest content packaging will come from the created tree of folder and files.</dd>
<dt>Metadata</dt>
<dd> 
<ul>
<li>contributors</li>
<li>target audience</li>
<li>course aim</li>
<li>course objectives</li>
<li>level</li>
<li>length of course</li>
<li>learning outcomes</li>
</dd>
</dl>
}}}

== How to handle changes in structure ==
Changes in structure made outside of the WCKER, whilst authoring should be accomodated.

=== Strategies ===
 * Ask the user if they've added/(re)moved anything (risky, not very helpful)
 * List any files that are unexpected (after reload HTML resource finding) , and ask what to do with them