Transcript RELOAD Editor Update

RELOAD
Reusable E-Learning Object Authoring and Delivery
Phil Beauvoir
Colin Milligan
funded by
Workshop Structure
Session I
Introduction: Interoperability and Reload
Session II
Content Packages
Session III
Metadata
Session IV
SCORM
© RELOAD 2003, funded by
JISC & CETIS
JISC: Joint Information Systems
Committee
Funds Learning Technology projects in
Higher and Further Education
CETIS: Centre for Educational Technology
and Interoperability Standards
Provides Standards Information for the
Community
© RELOAD 2003, funded by
Who we are
Colin Milligan
Learning Technologist: Virtual Learning
Environments, Simulations, Assessment,
Standards.
Phil Beauvoir
Programmer: Colloquia Learning
Environment and RELOAD tools.
© 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 and efficiency.
• Flexibility
– Internationalization and Accessibility.
© RELOAD 2003, funded by
Who makes standards.
review and feedback
User Needs
New Technology
Research
IMS
Working
Groups
ADL SCORM
IEEE
(conformance)
(certification)
CEN/ISSS
specification
implementation
standard
ISO
© RELOAD 2003, funded by
What do they cover?
• Metadata
• Enterprise
• Content Packaging
• Accessibility
• Simple Sequencing
• Learning Design
• Learner Information
Profile
• Question and Test
Interoperability
• Competency (and
Portfolios)
• Digital Repositories
• (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 form IMS web site for free
© RELOAD 2003, funded by
Example: Content Package
imsmanifest.xml
Metadata
Resources
© RELOAD 2003, funded by
imsmanifest.xml
(how to interpret this package)
<manifest xmlns="http://www.imsglobal.org/xsd/imscp_v1p1“
xmlns:imsmd="http://www.imsglobal.org/xsd/imsmd_v1p2"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" identifier="MANIFEST-65A1BA8F-3A73-479E-0F63163FFDA5B0E1"
xsi:schemaLocation="http://www.imsglobal.org/xsd/imscp_v1p1 imscp_v1p1.xsd
http://www.imsglobal.org/xsd/imsmd_v1p2 imsmd_v1p2p2.xsd">
<metadata />
<organizations default="ORG-9CD8FA62-FF8C-B998-55CA-C1599862AEA6">
<organization identifier="ORG-9CD8FA62-FF8C-B998-55CA-C1599862AEA6" structure="hierarchical">
<title>Organization</title>
<item identifier="ITEM-CD55CF07-609F-A592-E0B9-8EC68A32942F" isvisible="true" identifierref="RES5669B8B0-85B5-01D8-0A33-3284AE5A6218">
<title>sundialjelsim</title>
</item>
</organization>
</organizations>
<resources>
<resource identifier="RES-5669B8B0-85B5-01D8-0A33-3284AE5A6218" type="webcontent"
href="sundialjelsim.html">
<file href="images/jspowered.gif" />
<file href="images/solarGeom/sun.gif" />
<file href="jscore.jar" />
<file href="progress.jar" />
<file href="SolarGeom.jar" />
<file href="sundialjelsim.jsm" />
<file href="sundialjelsim.html" />
</resource>
</resources>
</manifest>
(how the content is organised)
(what resources are needed)
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 …
i

R
i


CREATE
CONTENT
PACKAGE
& ALTER
[RELOAD]

i

i

i

i

R
STORE
[REPOSITORY]
DELIVER
[MLE]
i
© 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.
© RELOAD 2003, funded by
(screenshot)
Visual equivalent
of imsmanifest.xml
files
details
Interoperability Demonstration
i

R
Discover
Resources
i
R
Create CP
in RELOAD
R
Upload to
LMS
© RELOAD 2003, funded by
Future
• RELOAD 1.1.1+ 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
Session II
The Reload Editor
© RELOAD 2003, funded by
Summary
•
•
•
•
10 minute demo
Hands On
Further Tasks
Round-up
© RELOAD 2003, funded by
Hands On: A First CP
• Core Tasks (p7-16)
–
–
–
–
–
–
–
–
–
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
Session III
Metadata
© RELOAD 2003, funded by
What is 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
– http://www.cetis.ac.uk/profiles/uklomcore
• If you don’t have any content of your
own, use bizstartup.
– http://homepages.strath.ac.uk/~ess03134/
demo/ecsig8demo.zip
• 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 
• An LMS
– WebCT, BlackBoard, Saba, Teknical
© RELOAD 2003, funded by
Session IV
SCORM: The Shareable Content
Object Reference Model
© RELOAD 2003, funded by
The Importance of SCORM
• 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)
• 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-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.
© RELOAD 2003, funded by
The Future
• RELOAD Editor is stable
• Others are developing functionality
– SCORM 1.3 editor (ADL)
– 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
Phil Beauvoir
[email protected]
Colin Milligan
[email protected]
http://www.reload.ac.uk/
© RELOAD 2003, funded by