JDTA Item and Learning Object Versioning –Proposed Approach
1 / 17

4 April 2012 - PowerPoint PPT Presentation

  • Uploaded on

JDTA Item and Learning Object Versioning –Proposed Approach Jamie Stewart, Steve Wicinski, Jim Ferrall AIM Team. 4 April 2012. Overview. Status of versioning efforts JDTA Item Versioning Contract with the Fleet Creating and Approving Versioning Approved Items Learning Object Versioning

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about ' 4 April 2012' - ginger

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
JDTA Item and Learning Object Versioning –Proposed ApproachJamie Stewart, Steve Wicinski, Jim FerrallAIM Team

4 April 2012

Overview Approach

  • Status of versioning efforts

  • JDTA Item Versioning

    • Contract with the Fleet

    • Creating and Approving

    • Versioning Approved Items

  • Learning Object Versioning

    • Principles

    • Scenarios

    • Early Feedback

Jdta item versioning status of versioning effort
JDTA Item Versioning ApproachStatus of Versioning Effort

  • White papers describing versioning for JDTA items and Learning Objects

    • Drafted

    • Available for review

      • Already had initial review by MTC PPC

      • Additional MTC input (Mike & Chris)

      • At NETC N74 for review

      • Available for FRB review

  • Looking for comments by 20 APR

Jdta item versioning contract with the fleet
JDTA Item Versioning ApproachContract with the Fleet

  • Once a Skills Hierarchy report has been approved by the sponsor it represents a contract between the training organization and the Fleet

  • Approving the JDTA items in CPM tells the system that they represent that contract and should not be changed unless there is a compelling reason to do so – also makes them selectable as the Skills Basis for a learning object in CPM Project tab

Jdta item versioning creating approving
JDTA Item Versioning ApproachCreating/Approving

  • Submit, Review, Approval operates similarly to current approach with improvements:

    • Reviewer and Approver email takes them directly to item needing attention

    • A Submitted/Accepted visual indicator on skill

    • Approver can approve a submitted skill (doesn’t have to be reviewed first)

  • Existing Interventions can be added after approval and will flag linked content

Jdta item versioning versioning of approved items
JDTA Item Versioning ApproachVersioning of Approved Items

  • NETC business rules must be followed – sponsor notification/concurrence?

  • Occurs when text or attribute for an Approved item needs to change:

    • Adding an additional Condition or Standard to an approved task

    • Correcting a typo in an approved task

    • Procedure

    • New version is initially marked as New and goes through the same Submit, Review and Approve process

    • Once approved, items associated with previous version will be flagged

Jdta item versioning versioning of approved items contd
JDTA Item Versioning ApproachVersioning of Approved Items(contd)

  • Most recent version of item will be shown with a pull-down option to view earlier versions

  • View History button will show who changed the item

  • On approval, flags will be generated on:

    • All usages within the JDTA of earlier versions of the Skill

    • All Modules/Lessons/Sections that cite any earlier version of the Skill

    • Flags will be generated on items regardless of their status (thus, Approved Modules/Lessons/Sections will get flagged)

Jdta item versioning versioning of approved items contd1
JDTA Item Versioning ApproachVersioning of Approved Items(contd)

  • System flags (those that indicate related material changes) will differ in color from Maintenance flags (those that indicate a change has been made on an item)

  • That is, a user will be able to tell the difference between a Lesson that was flagged because it was modified vice a Skill was modified. The color scheme of the System and Maintenance flags will be the same as for traditional AIM I (i.e., blue for System and red for Maintenance).

Jdta item versioning reuse
JDTA Item Versioning ApproachReuse

  • Note: Reuse or linking of Skills functionality will be released in future version of the software when authorized for use by NETC

  • Reusing Skills – An Approved JDTA item can be reused within or external to the Center who built it

  • It will appear as New in the new location

  • It needs to go through the same Approval process as a new Skill, since it is being used under a different occupational structure and its inclusion in the new structure needs to be validated by authorized personnel

Learning object versioning principles
Learning Object Versioning ApproachPrinciples

  • Why version learning object content?

    • Content owners need to ensure that the trainees are receiving the correct authorized content.

    • Training managers need to be able to tell which version of content any individual received.

  • Why not version learning objects the way we have versioned traditional courses?

    • The fact that learning objects are intended to be reused in various lessons, modules, and courses requires that they be independently versioned, as opposed to versioning an entire Course. Also, by versioning only the various modules, lessons, and sections that need to be updated, reviewers can feel assured that content that doesn’t require modifications has not been changed (as it would still be marked as approved).

Learning object versioning principles1
Learning Object Versioning ApproachPrinciples

Principle #1: Each course, module, lesson, and section will have a unique version number assigned and controlled by CPM. A new version may be requested from either CPM or the LO Module; however, new versions are approved only in CPM by the Project Owner or other user with appropriate privileges.

Learning object versioning principles2
Learning Object Versioning ApproachPrinciples

Principle #2: School administrators must be able to tell which students completed which training courses.

Therefore, each unique aggregation of learning objects which make up a course must be versioned. Lessons are versioned when the content (Introduction, Summary, etc.) or the aggregation of sections (a new version of a section or re-sequencing of the existing versions) requires a change. The same approach holds for versioning Modules and Courses.

Learning object versioning scenarios
Learning Object Versioning ApproachScenarios

  • Initial Approval

  • Learning Object Reuse

  • Versioning from the LO Module

  • Versioning from CPM

  • Versioning Due to JDTA Changes

  • Versioning Caused by Aggregation Changes

  • Scenarios include a hypothetical situation, questions and a process description of what happens in CPM/LO Module from a user functionality view.

Feedback to date
Feedback to Date Approach

  • Lots of help from SWS PPC (CFS) to get the draft white papers ready

    • Wendy Pester, Jamie Swaim, & Nicole Williams

  • Great feedback from MTC folks to support final draft

    • Mike Lueken (LMMS) & Chris Roughley (GD-AIS)

    • Mike proposes another principle: “recommend that another Principle be added that states ‘The LO Module will retain a complete copy of all approved Courses, so that the users can access them at any time for printing”

Next steps
Next Steps Approach

  • Ongoing Review by NETC

  • Ongoing Review by MT Continuum community

  • FRB Review Period

    • Papers Posted on Web Site in FRB Area

    • Please provide comments to Jamie Stewart, copy to Ron Zinnato NLT 20 April 2012

Questions? Approach

Backup Slides Approach