The D2LLO Project: A Successful Collaborative Project Using Learning Objects Lorna Wong UWWhitewater

1
The D2LLO Project A Successful Collaborative
Project Using Learning ObjectsLorna Wong
UW-WhitewaterPat Fellows UW- CollegesCid
Freitag UW-Madison

• New Media Conference, June 19, 2004

2
Who we are ..University of Wisconsin System
3
Is made up of

• 26 Institutions
• 13 Four Years Campuses
• 13 Freshman-Sophomore campuses
• and UW Extension
• Common systems
• Enterprise SIS
• Enterprise Library
• Enterprise HR
• Enterprise CMS Desire2Learn (D2L)
• LTDC Learning Technology Development Council
• Instructional Technologists from each campus

4
Adopting D2L as our CMS

• UWS adopted Desire2Learn as a system wide Course
  Management System
• There is an immediate need to create training
  material for both faculty students
• This offers an excellent opportunity to
  collaborate and share resources among campuses

5
JELLO?
no, D2LLO

• D2LLO stands for D2L Learning Objects
• A project inspired by
• The need for generating commonly used training
  material quickly
• The importance for shareable training material
  with flexible formats
• The enthusiasm of a group of dedicated LTDC folks
  to do a real application in learning objects

6
Forming the D2LLO group

• 12 instructional technologists from the campuses
  participated
• The ADL-Colab SCO Days conference in Madison on
  June 2003 provided an opportunity to hone
  technical skills, brainstorm and do group
  planning
• UWS sponsored the group to attend the conference
  and supported the ongoing work

7
D2LLO Project Goals

• Create learning objects that cover all major
  areas of D2L for faculty Training
• Keep these learning objects small, granular, and
  standards conformant
• Ensure the LOs can easily be incorporated into
  training material of various formats
• Open these learning objects to all D2L trainers
  at UWS or beyond

8
D2LLO Process

• Divide the group into 5 teams, each with a lead
  person
• Each responsible for a functional area faculty
  uses
• Each team maps the tasks needed to
  comprehensively understand the function
• Decide on the granularity of each LO to match a
  task
• Communication during the project
• Email
• Conference calls
• F2F work sessions ( 3 times total)
• Spreadsheet for tracking LO mapping and progress

9
Collaborative Design Prototype

• A prototype of a learning object was designed
  created as a group effort
• During our SCO Days face-to-face meeting
• A detailed 32 pages step-by-step documentation on
  creating a LO was developed
• key to consistency in the construction of the
  LOs
• A common D2L course is used for creation
• Key to ensure common look and feel

10
D2LLO Repositories Dissemination

• Use D2L as a central repository for LOs
  documentation
• Created a D2L course site at UWS as a testing
  ground
• A website was designed to organize the LOs for
  easy access and distribution

11
Project Timeline

• June 2003 - SCO Days
• F2F team meeting to develop prototype
• June-August 2003 refine prototype and
  documentation
• F2F meeting to work through LO development
  process
• August January LOs created and deposited
  into D2L course site and external website
• January 2004 Retreat to finish production
• March June 2004 - Edit and final polish
• Proofreading and editing to flush out
  inconsistency
• Modification and cleanup

12
Using the D2LLO Learning Objects

• Incorporated into various training material
• Directly linked to the D2LLO repository website
• Presented as an organized training resource
  inside D2L
• Embedded into the HELP tool in D2L

13
Anatomy of a Learning Object
14
Anatomy of a Learning Object - behind the scenes

• Detailed specification sheet
• File naming conventions
• Typeface, sizes, use of styles
• Use of colors, logo
• Consistent wording and level of detail in
  captions
• SCORM conformant

15
Tools for Creation

• RoboDemo - (now Macromedia)
• Screen captures, animation export, text/image
  export
• Word - (Microsoft Office)
• Editing text/image document
• Dreamweaver (Macromedia)
• Index file, SCORM runtime wrapper, imsmanifest
• WinZip (or OS provided)
• Packaging for import into D2L

16
Using RoboDemo

• Screen capture software
• Screenshots
• Mouse movements and clicks
• Captions
• Flash (.swf) output
• Text/image output

17
RoboDemo - Properties
18
RoboDemo - Captioning
19
RoboDemo - Animation
20
RoboDemo Word Export
21
Word minor editing
Edited for layout, image size
RoboDemo output
22
Using Dreamweaver MX
Index page
23
SCORM Runtime Wrapper(extension)
24
IMS Manifest Maker(extension)
25
IMS Manifest MakerProject Specs
26
IMS Manifest
Edit XML file directly in Dreamweaver
Project documentation guidelines
27
Packaging, Importing

• Compressed to Zip format
• Import into D2L, unpackaged as a content topic
  with title
• Use D2L files area as repository

28
D2LLO - Editing Phase

• Single editor (multiple authors)
• Check for consistency
• Styles
• Caption wording

29
Tool/File Integration
30
Why this Format?

• Flexibility
• Suit multiple learning styles
• Greater accessibility of formats to audience

31
Our Challenges

• The steps involved in the creation of each LO are
  rather complex
• Each participant faces an overload of duties,
  including conversion of previous CMS to D2L on
  each campus
• D2L released new version and major patches during
  the year
• Participants need to relearn the platform
• LOs need to be modified

32
Accomplishments

• Created 150 LOs on 5 major functional areas for
  faculty training
• Learnt new skills on the tools and understanding
  of LO and SCOs
• The LOs was a welcome training supplement within
  the UW campuses and other institutions
• This LO concept is adopted by the vendor as a
  model for building its own learning community
  resources

33
Lessons Learnt

• The project was too labor intensive for the
  already overloaded instructional technologists
• started with 12 participants, only 6 active
  members left
• Incentive can keep interest
• Stipend help to sustain the group
• Keeping consistency and organization of an
  end-product created by a diverse group of authors
  is not trivial

34
Next Steps

• Phase 2 learning objects for student tasks
• Updates as new versions are released

35
New Challenges

• How do we keep up with version changes?
• How do we deal with the next phase?
• Hire students
• Collaborate with other institutions
• Continue with the SWAT team approach
• How do we evaluate and assess the usage of these
  LOs ?

36
The Active People in D2LLO

• Cheryl Diermyer Whitewater
• Pat Fellows UW-Colleges (co-ordinator)
• Cid Freitag Madison
• Molly Immendorf Extension
• Kathy Konicek Madison
• Sherry Post Stout (documentation)
• Nicholle Stone Stout (technical testing)
• Simone Vuong UW-Colleges (editor)
• Lorna Wong Whitewater (coordinator, website
  manager)
• A Collaborative LTDC group at UW System campuses

37
More Examples

• How to add a link in the NavBar
• How to Add a Discussion Topic
• Adding Feedback to students in the Dropbox
• Setting up Quiz Layout questions

38
Questions?
39
Contact us

• Lorna Wong wongl_at_uww.edu
• Cid Freitag - cfreitag_at_doit.wisc.edu
• Pat Fellows pfellows_at_uwc.edu
• D2LLO website- http//www.uww.edu/d2l/
• This presentation will be available at
• http//ltc.uww.edu/nmc/d2llo.ppt

40
(No Transcript)
41
(No Transcript)
42
(No Transcript)