Review of DLCC Developers Meeting 26/27 July 2007 Angela Lindsey Project Manager, Distance Learning Division

Participants JFSC JKDDC Joint Special Operations University Naval Postgraduate School Marine Corps University U.S. Army Command and General Staff College Air War College Concurrent Technologies Corporation, Cande Filip Institute for Defense Analyses, G.A. Redding Knowledge Media Inc., Bill Redeen ADL Co-Lab, Avron Barr & Eric Roberts

Agenda Items DLCC Business Rules Review DODI Requirements ADL Registry Process Resources, Tools, and Techniques Overview of SCORM 2004 Metadata Requirements Development Processes Discussion Lifecycle Content Maintenance Best Practices for Sharing Within DLCC

Meeting Goals introduce the technical body and curriculum development team that serves the DLCC community of practice (COP) learn about ADL initiatives and discuss each of the DLCC schools’ involvement discuss and determine DLCC best practices to register content provide input for the version control/change alert functionality prototype promote sharing amongst the JPME community

DLCC Business Rules Review register content objects deemed “eminently sharable” tag based on potential for reuse, i.e. tags are primarily at lesson level down to “outstanding assets” share Service capability lesson development & tools minimize use of labels (command crests, etc.) restrict public access to content but provide searchers a way to request content & provide it upon authentication establish reuse metrics & techniques for maintaining visibility of changes to content (see Leveraging SCORM across a COP)

DODI Requirements G.A. Redding, Sr. Policy Advisor for ADL –requirements review –ADL-R application process –Review of related handbooks (MIL-HDBK series)

ADL-Registry (ADL-R) Process Bill Redeen, CKO for KMI ADL-R status update Repository registration Operational & practice registry Planned upgrades (ex/ search enhancements, alerts, RIM) Steps to register content 1.Create a Registry Transaction (REG-T). 2.Submit the REG-T to the ADL Registry Portal. 3.Use the returned Transaction Identifier to check the Transaction Status (REG-TS). Slides

Recommended Resources JKDDC Knowledge Management Content Design and Development Guidelines ADL-R DL Portal documentation SCORM rd Edition documentation, conformance test suite, content examples and sample run-time environment Other papers on best practices, business rules, content development handbooks (ex/Navy ILE, Army Courseware Compliance, etc.) ADL websites ( Supporting conferences (ex/JADL Implementation Fest, eLearning Summit 2007) Other training (ex/Academic Co-Lab’s SCOurse, SCORM School, etc.) Templates & style sheets (ex/LSAL SN templates, Dreamweaver templates, CSS, etc.)

Recommended Software Tools JFSC: Reload Editor (create manifests & package SCORM content) NPS: SoftChalk LessonBuilder (create interactive web pages & package SCORM) JKDDC: Wimba Course Genie (rapid SCORM development from Word) NPS & JKDDC: Articulate (synchronize audio & PPT)

Customized Web Applications AJPME Course Configuration Diagnostic Program ( JFSC Repository Request Form ( AJPME Change Request Form & Maintenance System ( Metadata Editor (currently undergoing development)

Overview of SCORM 2004 Cande Filips, Senior ISD for CTC 5 major front-end decisions to determine prior to development: 1.Which LMS are you using? What’s your conformance? 2.What size is a SCO? 3.Who’s reusing it? 4.What learner data should be tracked by the LMS? 5.What metadata should be used & how should you collect it? Crosswalk of SCORM vs. Registry metadata elements Data model element chart

Metadata Requirements REG-T metadata meets ADL requirement Include POC info & decide how to link location Include version, change & relationship data

Development Processes Schools provided overview of processes in developing & maintaining online content The long road ahead - DLCC schools still have to register content, set up repositories, etc. Blackboard primary LMS within DLCC Leverage JKDCC resources & expertise

Lifecycle Content Maintenance Challenge of maintaining change visibility & version history Version change notification prototypes –FY05 ADL-Registry Client (ADL-RC) –FY07 ADL-R Version Control System (ADL-R VCS) Best Practices guide coming –registering updates, metadata changes, etc.

COP Best Practices for Sharing Standardize what metadata to register –Use Joint terminology –Add keywords to be all-inclusive –Add the audience/type of user (joint planner, etc.) –Use standard keywords to describe the type of course, school, & POI (ex/JFSC, AJPME, DLCC) Publish & share style guides Establish a Joint taxonomy Publish shared resources

Other Considerations Adding community-level metadata to REG-T Visibility of what’s available to be shared (DLCC website, Bb class, ADLCommunity.net) Ways to transfer content/source files (ex/Bb CS “passes”, CD/DVD, FTP, DKO)