18 March 2004 Colin Milligan funded by

© RELOAD 2003, funded by Workshop Structure Session I Introduction: Interoperability and Reload Session II Content Packages Session III Metadata Session IV SCORM

© RELOAD 2003, funded by Interoperability orig. src: Charles Duncan, Intrallect

© RELOAD 2003, funded by Why we need standards Standards Promote: Persistence –Remember laser disc based materials, Discovery –Beyond your local community Sharing between different systems –For efficiency. Flexibility –Internationalization and Accessibility.

© RELOAD 2003, funded by Who makes standards. IMS Working Groups specificationimplementationstandard User Needs New Technology Research review and feedback IEEE CEN/ISSS ISO ADL SCORM (conformance) (certification)

© RELOAD 2003, funded by What do they cover? Metadata Content Packaging Simple Sequencing Learning Design Question and Test Interoperability Digital Repositories Enterprise Accessibility Learner Information Profile Competency (and Portfolios) (Interactive Content)

© RELOAD 2003, funded by Specification Documents Each Spec. has 3 components: –Information Binding XML Binding – how to describe. –Information Model What to describe: definitions, rules and constraints –Best Practice Guide Guidelines for using and implementing. Available from IMS web site for free

© RELOAD 2003, funded by Example: Content Package imsmanifest.xml Metadata Resources

<manifest xmlns=" xmlns:imsmd=" xmlns:xsi=" identifier="MANIFEST-65A1BA8F-3A73-479E-0F FFDA5B0E1" xsi:schemaLocation=" imscp_v1p1.xsd imsmd_v1p2p2.xsd"> Organization sundialjelsim imsmanifest.xml (how to interpret this package) (how the content is organised) (what resources are needed)

© RELOAD 2003, funded by Why do we need tools? Avoid working directly with XML (files get much more complicated than the one in our example), speed up xml creation. reduce errors, aid conformance (and uptake),

© RELOAD 2003, funded by Where Does RELOAD fit?

© RELOAD 2003, funded by In Practice … CREATE CONTENT PACKAGE & ALTER [RELOAD] STORE [REPOSITORY] DELIVER [MLE]

© RELOAD 2003, funded by RELOAD Tools Reference Implementation –Test, benchmark Visually assemble and manipulate Content Packages –Better than XML View Content Packages –For testing and preview.

(screenshot) details Visual equivalent of imsmanifest.xml files

© RELOAD 2003, funded by Interoperability Demonstration Discover Resources Create CP in RELOAD Upload to LMS

© RELOAD 2003, funded by Future RELOAD stable and feature complete Open Source – others are encouraged to extend, and are doing so Designed to adapt easily if specifications are revised.

© RELOAD 2003, funded by Creating CPs with RELOAD 10 minute demo Hands On Further Tasks Round-up

© RELOAD 2003, funded by Hands On: A First CP Core Tasks (p7: Collect Resources Together -p16) –Collect Content –Create Working Directory –Prepare Placeholders –Import Content –Make Organizations –Preview –Rearrange –Add Metadata –Package and Zip

© RELOAD 2003, funded by Advanced tasks Advanced Tasks (p23-25) –Manifests –Dependencies

© RELOAD 2003, funded by Roundup RELOAD allows us to move from Abstract to Physical –Tests (proves) the specification –Links Content Creation and Content Sharing

© RELOAD 2003, funded by 3. Metadata Describes resources: –General (title and keywords) –Lifecycle (versioning) –Metametadata (who wrote the record) –Technical (assisting implementation) –Educational (level) –Rights (copyright and other restrictions) –Relation (to other content) –Annotation (usage metadata) –Classification (in a system)

© RELOAD 2003, funded by Why metadata is important Discovering Resources –Description, educational MD Using Resources –Version control, technical Enforcing Rights Attributing Ownership/Authorship

© RELOAD 2003, funded by Application Profiles Metadata must be interoperable –~80 elements in LOM –Decide on important elements at a local (organisational) level –Use shared vocabulary/taxonomy Kinetics, motion, physics … –Implement Rules and restrictions

© RELOAD 2003, funded by Good Metadata Added by Information Professionals Consistent across a repository Assists Reuse –Usage metadata – recommendation systems like Amazon:

© RELOAD 2003, funded by Hands On Session Take your own content and create content packages. Add Metadata – If you dont have any content of your own, get some here. – Aggregate Packages.

© RELOAD 2003, funded by Roundup You should have been able to : –Make your content reusable –Describe your content –Aggregate your content with others.

© RELOAD 2003, funded by Where next? A repository –JORUM –Merlot, SMETE Federated Search: –Maricopa Learning Exchange –CAREO An LMS –WebCT, BlackBoard, Saba, Teknical

© RELOAD 2003, funded by 4 SCORM SCORM: The Shareable Content Object Reference Model SCORM is real, –Certification (soon), –Now (almost).

© RELOAD 2003, funded by SCORM History US Dept. of Defense, Boeing (AICC) Training Single User Model Drives (pulls) specs forward.

© RELOAD 2003, funded by SCORM Future Close harmonisation with equivalent IMS specs – avoiding divergence. Incorporating Simple Sequencing (1.3 – 2004) Question and Test Interoperability (1.4) Simulations and adaptive learning (v2)

© RELOAD 2003, funded by Hands On Session In addition to CP and MD, SCORM includes support for management of learning (p20 SCORM Elements -22): –Pre-requisites –Max time allowed –Time Limit Action –Data from LMS –Mastery Score

© RELOAD 2003, funded by SCORM Player Allows SCORM functionality preview without using an LMS. –Simple to set up –See what the learner sees –Test functionality. –SingleCourseEx.zip

© RELOAD 2003, funded by The Future RELOAD Editor is stable Others are developing functionality –SCORM 1.3 editor (ADL) –ALOHA Metadata Editor (CanCore) –VDEX Editor (ICBL) Learning Design

© RELOAD 2003, funded by Roundup RELOAD is about enabling –Engage with the standards –Test the standards –Improve the tools.

© RELOAD 2003, funded by Contact Colin Milligan