The New ADL Registry

Eric Sakmar, ADL Technical Team

Jason Haag, Joint ADL Co-Lab

Larry Lannom, CNRI

August 18-19, 2009

ADL Registry Web Portal Changes

Report Documentation Page Form ApprovedOMB No. 0704-0188

Public reporting burden for the collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering andmaintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information,including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, ArlingtonVA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to a penalty for failing to comply with a collection of information if itdoes not display a currently valid OMB control number.

1. REPORT DATE AUG 2009 2. REPORT TYPE

3. DATES COVERED 00-00-2009 to 00-00-2009

4. TITLE AND SUBTITLE The New ADL Registry. ADL Registry Web Portal Changes

5a. CONTRACT NUMBER

5b. GRANT NUMBER

5c. PROGRAM ELEMENT NUMBER

6. AUTHOR(S) 5d. PROJECT NUMBER

5e. TASK NUMBER

5f. WORK UNIT NUMBER

7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) Advanced Decision Learning (ADL),Joint ADL Co-Lab,13501 IngenuityDrive Suite 248,Orlando,FL,32826

8. PERFORMING ORGANIZATIONREPORT NUMBER

9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10. SPONSOR/MONITOR’S ACRONYM(S)

11. SPONSOR/MONITOR’S REPORT NUMBER(S)

12. DISTRIBUTION/AVAILABILITY STATEMENT Approved for public release; distribution unlimited

13. SUPPLEMENTARY NOTES ImplementationFest2009, 18-20 Aug 2009

14. ABSTRACT

15. SUBJECT TERMS

16. SECURITY CLASSIFICATION OF: 17. LIMITATION OF ABSTRACT Same as

Report (SAR)

18. NUMBEROF PAGES

38

19a. NAME OFRESPONSIBLE PERSON

a. REPORT unclassified

b. ABSTRACT unclassified

c. THIS PAGE unclassified

Standard Form 298 (Rev. 8-98) Prescribed by ANSI Std Z39-18

ADL Registry Web Portal

ChangesEric Sakmar

3

ADL Registry Informational Site

http://www.adlnet.gov/Technologies/adlr/

News and Announcements

Frequently Asked Questions (FAQ)

Documentation

Events and Event Registration

4

ADL Registry Functional Site

http://adlregistry.adlnet.gov

Search

Contribute

Register Repositories and Contributors

Practice Registry

Help and Contact Information

ADL Registry Changes

6

ADL Registry Changes

Identifiers

Registry Transaction Envelope

LOM Overview

Search Results

7

Registry Transaction Envelope

Multiple, Typed URLs

Types of URLs object - Direct link to the object itself, no authentication

required

advertisement - link to information about the object (preview, screenshot, etc.)

runtime - link to the object in a runtime environment

contact – link to information about a contact through which the object may be requested

extended metadata – link to additional metadata

repository – link to the object in a repository, authentication may be required

8

Search Results

ADL Registry 1.7

Metadata Changes

10

LOM Changes Overview

„conformance‟ was replaced with „compliance‟

„content object‟ was replaced with „object‟

Additional support for Educational Objectives and

Competencies

Represented in <classification> elements

Additional values for „complies with‟ classification

Additional values for „object type‟ classification

11

Metadata Changes

„conformance‟ to „compliance‟

LOM Classifications

„conforms to‟ >> „complies with‟

„ADL/DOD Conformance Taxonomy‟ >> „ADL/DOD Compliance

Taxonomy‟

12

Metadata Changes

„content object‟ to „object‟

XML Elements contentObjectDescriptor >> objectDescriptor

cordraContentObject >> cordraObject

contentObjectIdentifier >> objectIdentifier

contentObjectLocation >> objectLocation

communityContentObject >> communityObject

LOM Classifications „content type‟ >> „object type‟

„ADL/DOD Content Type Taxonomy‟ >> „ADL/DOD Object Type Taxonomy‟

„ADL/DOD Content Category Taxonomy‟ >>

„ADL/DOD Object Category Taxonomy‟

13

Metadata Changes

Additional support for Educational Objectives

and Competencies Create a lom:classification element

Set value to lom:classification/lom:purpose/lom:value

„educational objective‟ or „competency‟

Set values for

lom:classification/lom:taxonPath/source

lom:classification/lom:taxonPath/lom:taxon/lom:id

lom:classification/lom:taxonPath/lom:taxon/lom:entry

14

Metadata Changes

Additional values for „complies with‟ classification SCORM 2004 3rd Edition

SCORM 2004 4th Edition

SCORM Version 1.2

S1000D V2.0

S1000D V2.1

S1000D V2.2

S1000D V2.3

S1000D V3.0

S1000D V4.0

IEEE 1484.20.1-2007 RCD

other

15

Metadata Changes

Additional values for „object type‟ classification

sco

aggregation

other

ADL Registry Use Cases

Jason Haag

Introduction

Overview

Success Stories (Navy & JKDDC)

Similar Challenges

Technical Approaches

18

19

Primary ADL Registry Contributors

Contributor Records Entry Date

Navy eLearning (US Navy) 2,086 08/05/2008

Joint Knowledge Development and

Distribution Capability (JKDDC)

127 4/01/2007

Defense Ammunition Center 76 09/08/2008

20

Use Case: U.S. Navy

Currently deploys more than 4,000 custom catalog

items (content packages) to multiple environments

and platforms

2008

21

U.S. Navy Organizational Challenges

Lack of consistent metadata for learning content

Most content was created prior to the establishment of

Navy content development policy, guidelines, and

DoD Instruction 1322.26

Many learning programs in “legacy state” of

maintenance

Lack of funding and/or resources to move to a more

mature state of life-cycle management

22

U.S. Navy Technical Challenges

Metadata was available for all of the learning

content, but it was not always included in the

SCORM content package

Hosting process required manual input into the LMS but

only course-level (aggregate)

CMAD Repository was no longer operational

R&D project unable to transition to enterprise data center

Provided capability to populate ADL-R using RIM-LITE

Lack of tools for new content development efforts

All new metadata would have to be updated/modified by

the technical implementer to support the ADL-R

23

U.S. Navy Situation

All metadata wasn‟t always included in the

content package

The Navy‟s LMS contained this metadata for

each catalog item (course aggregation)

Title

Description

Keywords

Instructional Hours (Duration)

SCORM Version

U.S. Navy Approach

Populate the ADL

Registry with a single

insert transaction file

generated by the

custom utility

Develop utility to

extract metadata

from the LMS

24

U.S. Navy Approach

<lom:identifier>

<lom:catalog>NeL</lom:catalog>

<lom:entry>R-500-0140/02PG</lom:entry>

</lom:identifier>

<lom:title>

<lom:string language="en-US">NROWS Orders Administration Course</lom:string>

</lom:title>

<lom:keyword>

<lom:string language="en-US">NROWS</lom:string>

</lom:keyword>

<lom:keyword>

<lom:string language="en-US">Orders</lom:string>

</lom:keyword>

<lom:keyword>

<lom:string language="en-US">Administration</lom:string>

</lom:keyword>

<lom:keyword>

<lom:string language="en-US">Course</lom:string>

</lom:keyword>

<lom:description>

<lom:string language="en-US">The NROWS Orders Administration course is designed primarily for Unit Reviewers and Unit Approvers but contains an overview of the order submission and approval process from which all Members will benefit. This course provides an introduction to AT/ADT/IDTT Orders Policy; NROWS Roles and Responsibilities; Maintaining NROWS; Unit Reviewer and Unit Approver Menus and Procedures; Order Writing Authority (OWA) and Orders Specialist (OS) Menus; Orders Verification Submission and Approval; Email Notifications; and NROWS Reports.</lom:string>

</lom:description>

<lom:source>ADL-Rv1.0</lom:source>

<lom:value>conforms to</lom:value>

</lom:purpose>

<lom:taxonPath>

<lom:source>

<lom:string>ADL/DOD Conformance Taxonomy</lom:string>

</lom:source>

<lom:taxon>

<lom:entry>

<lom:string>SCORM Version 1.2</lom:string>

</lom:entry>

</lom:taxon>

</lom:taxonPath>

<lom:educational>

<lom:typicalLearningTime>

<lom:duration>PT8H0M0S</lom:duration>

</lom:typicalLearningTime>

</lom:educational>

Populate the ADL Registry with a single insert

transaction file generated by the custom utility

26

U.S. Navy Approach

Use Case: JKDDC

28

JKDDC Technical Challenges

Lack of metadata for learning content

Majority of the content was created prior to the

establishment of DoD Instruction 1322.26

Metadata was not always included in the SCORM

content package

Would have to manually create metadata using source

materials

29

JKDDC Approach

Reviewed each piece of content

Used instructional lesson plans, storyboards, etc. to

locate relevant metadata

Manually created new metadata and entered it into a

database that supported

Title

Description

Keywords

Duration

Created wrapper utility to generate XML for the

ADL Registry

Each insert file contained 20 content aggregation records

U.S. Navy & JKDDC

Current Status

31

Current Status – U.S. Navy

NeL in-house content deployment tracking

application doesn‟t currently support ADL Registry

Navy lacks funding and additional resources to update

this application

Manual ADL Registry population could be automated if

an interface for RIM-LITE were added

NeL TestTrack Metadata Editor supports new content

development efforts to include all LOM elements and

ADL Registry-specific metadata

32

U.S. Navy Metadata Editor

Support for ADL Registry

33

Current Status - JKDDC

Uses a Rapid Online Content Creation Engine

(ROCCE) to create metadata as part of the Atlas

Pro Engine

Atlas Pro LMS supports RIM-LITE

ADL Registry is currently a public registry

JKDDC will resume ADL Registry updates when a miliraty

domain (.mil) network is available.

3434

GOTS Learning

Management

System

(JKO LMS)

ROCCEGOTS Authoring Tool

ADL Registry

(GOTS)

Automatic

distribution of

SCO metadata

Automated

Loading / Testing

ATRRS

(GOTS)

Military

Services

Tracks

Users

All components are DoDI 1322.26 compliant

All GOTS / FASTCOURSE tools provided at no cost to JKO Stakeholders

ATRRS -- Army Training Requirements and Resources System

SCOs -- Shareable Content Objects

JKO NIPR

JKO SIPR

Internet Public

JKO Joint Content Management

Architecture

Summary

Don‟t let technical challenges stand in your way

Locate metadata outside of the content package

Instructional Plans

LMS DB

LCMS

etc.

Contact ADL for support

35

36

Resources

ADL Initiative

http://www.adlnet.gov/

ADL Registry

http://adlregistry.adlnet.gov/

Navy eLearning Content Team

https://www.netc.navy.mil/ile

Joint Knowledge Online

http://jko.jfcom.mil/

37

References

The ADL Registry and CORDRA, Volume 2: ADL Registry

Overview and User Guide

http://adlregistry.adlnet.gov/

DoD Instruction 1322.26, Development, Management, and

Delivery of Distributed Learning, June 2006

http://www.dtic.mil/whs/directives/corres/html/132226.htm

Questions or Comments?

Jason Haag

Learning Technology Analyst

jason.haag.ctr@adlnet.gov

+1.850.471.1300