Help with How to wiki (new window)

Business Practices for Applying SCORM

Ken Pisel and his Community of Practice is looking to find other sets of business rules or for comments on the working outline below. Please choose the Edit tab above and add your suggestions within the document.

The outline below is a working document and the items are listed in no particular order other than when they came up in brainstorming.

The following is a partial list of issues that need consensus for application of business practices within a community of practice:

  • Labeling content
    • Do we give credit to originating organization?
    • If so, how?
      • Is there a label on slides?
      • Will it require individual memoranda or agreement? 
  • Book marking
    • Can students return to specific locations within content?
  • Tagging
    • At what level?  Asset? SCO? Aggregation?
    • Do we want redundant tagging?
      • Tag all SCOs
      • Tag aggregations as well to show interrelations 
  • Naming Schema
    • What do we collectively call things?
      • Lessons/TLO/LO/ELO/etc….
    • How do these names correlate to assets, SCOs, etc…?
      • How do we name these elements within SCORM?
  • Assets
    • What do we tag at this level, if anything?
    • Video capture of guest speakers is primary target
      • Will require universal release policy/form throughout the community 
  • Packaging content
    • How do we do it?
  • Sequencing
    • How do we address remediation?
    • What about pretests and posttests?
    • Testing out of some sections?
      • What is the minimum score to enable the learner to validate a section? 
  • GUI
    • Discuss a common user interface standard
      • Skins
      • Navigation 
  • Business processes
    • Are there issues beyond the mechanics of SCORM and ADL-R that we need to resolve to facilitate sharing?
  • Plug-ins
    • We will need a common standard across the community
    • Will we need to create a common system test for students to verify that they have the plug-ins loaded to support all potential pieces of content?
  • Style guide
    • Some level of commonality will be required for optimal sharing
  • Accessible repositories
    • Define accessible
    • What are the implications of multiple LMSs/LCMSs?
  • Other content
    • Are there other items that would be of value to register?
      • RFPs/Story boards/etc. . . ?
  • Registering content
    • Do we want to pursue a common registry number for the community?
  • Intellectual property
    • Copyright v. GOTS
    • How do we address copyrighted/licensed content within a piece of content?
  • Reuse metrics 
    • At the end of the day, can we justify what we are doing?
    • How do we measure success?
    • How do we capture it and what are the metrics?
  • Versioning
    • How do we label and track differing versions?
  • Points of contact (POCs)
    • How are POCs listed?
    • What happens when a POC changes? 


Referring links:
Main adlCommunity Wiki