MCS SCORM Documentation v1 0

Document Sample
MCS SCORM Documentation v1 0 Powered By Docstoc
					This document was prepared by Queenie Cheng at Elsevier MC Strategies under the direction of Brajesh Upadhyay. It
includes input from Jeremy Warren and Kevin Finnegan, and was reviewed and edited by April Childers and Brajesh.




Overview
The purpose of this document is to describe how Elsevier MC Strategies implements SCORM on our EPM
(or LMS) so our product owners, PMs, partners and other 3rd parties can rely on it for any SCORM
products in their planning.




Client-based SCORM Content
When a client wishes to upload SCORM content to be launched in the LMS, it must be in SCORM 1.2.


PROCESS FOR PUBLISHING:
    1. Client Delivers Content to MCS/Elsevier and notifies Client Services representative.
    2. Client Services enters a case in SalesForce to have that lesson linked within the client instance.
       The ticket should include the following:
           a. Lesson Name (as it should appear in the LMS)
           b. Folder/Zip file name if it is on Clients FTP site or the actual Files if they were provided by
               the client in an email (zipped).
           c. If no IMSMANIFEST.XML file is provided with the content then the client must instruct
               which file the LMS should point to (index.html/ScoStart.html). IMSMANIFEST.XML is a
               required file, but many times it is not provided.
    3. Technical Services will move complete the ticket with the following process:
           a. Move lesson files to appropriate application server that the client’s LMS resides on.
               SCORM content must run on the same local server. The location of the folder in
               reference to the KDS50a project is as follows:
               KDS50a/Modules/SCORM/Courses/ClientName/LessonFolder/*
           b. Enter the record in the clients LINKEDWBT table
                      i. DESCRIPTION = Lesson Title
                     ii. TYPE = SCO12
                    iii. URL = ClientName/LessonFolder/Launchfile.html
                    iv. GLOBAL = 1
                     v. WIDTH = 800 (or greater if clients requests)
                    vi. HEIGHT = 600 (or greater if clients requests)
           c. Mark SalesForce Case as “Ready for QA”
    4. Client Services notifies client that SCORM content is available for QA. QA should be performed
       by the Client Administrator.

Client-Based content is not supported by MCS/Elsevier. The client if they wish can utilize the following
tools for testing their content before providing it to MCS/Elsevier:

SCORM CLOUD:            https://cloud.scorm.com/sc/guest/SignInForm

RELOAD:                 http://www.reload.ac.uk/scormplayer.html

* If the client utilizes CAPTIVATE the Content should be placed in a subdirectory labeled “CAPTIVATE” –
this is to stop the LMS from “POSTING” to the launch file which causes an error with CAPTIVATE-based
content. LECTORA content should also be placed in the same subdirectory.
Vendor-based SCORM Content
AORN | AACN | MINDLEADERS | HFMA | CODING METRIX | JCR | HIMSS

Vendor-Based content is preferably SCORM 1.2 compliant. In some instances (AACN) MCS has accepted
SCORM 2004. This requires additional development time. Vendor content that is intended to be
redistributed must be imported into the CONTENT INTERFACE application.


PROCESS FOR PUBLISHING:
   1. Uploading Content to MCS|Elsevier:
         a. Vendors without an FTP site - Product Owner/Manager requests an FTP Site to be
             created for Vendor. Technical Services creates the FTP site and emails the FTP
             information to the project manager and content development. Project manager
             communicates FTP information to the vendor.
         b. Vendors with an FTP site - The vendor should create a new subdirectory for each
             individual course. This FTP site points to
             app26.webinservice.com/ContentInterface/Content/vendor/, but connects through
             app5.webinservice.com. App26 is the staging environment for the Content Interface.
   2. Vendor Uploads SCORM Compliant Content to FTP site and notifies Project Manager that
      content is available to import.
   3. Data entry is required for each lesson that is to be re-distributed via the Content Interface.
      Content development or the Product Owner or Johnel should have the information needed that
      Technical Services doesn’t create. The destination for the data is:
      WEBDATA8.KDSCONNECT.LINKEDWBT VALUES:
         a. DESCRIPTION = Lesson Name
         b. COURSENUMBER = auto number
         c. TYPE = unique course code – this allows us to create the scripts for the individual client’s
             LinkedWBT (technical service creates)
         d. URL =
             http://kdsconnect.webinservice.com/ContentInterface/Launcher.aspx?cid=Q3456&bloc
             k=StandardsCourseCode* (technical services creates)
         e. NOTES = StandardsCourseCode*.htm (this is the library card)
         f. FACILITYCODE = unique course code (same as above)
         g. GLOBAL = 1
         h. WIDTH = 800 (not sure if this is hardcoded to override it).
         i. HEIGHT = 600 (not sure if this is hardcoded to override it).
         j. CONTROLS = 0
        k. STANDARDSCOURSECODE = StandardsCourseCode*
        l. CERTPROVIDER = provider(AHIMA, HIMSS, etc) OR MULTI_1 if more than one provider
        m. HOURS = numerical hours amount

   WEBDATA8.CONTENTMASTER.ACCREDITATION VALUES:
       a. BLOCKNAME = StandardsCourseCode*
       b. CREDITSBY = provider
       c. HOURS = numerical hours amount
       d. BEGINDATE = earliest date for credit/hours
       e. ENDDATE = date credit/hours expire
       f. CERTLABEL = what should appear as link (usually provider)
       g. CREDITTYPE = CEU, Hours, Contact Hours,
4. The WEB.CONFIG file for the Content Interface Application on app26 needs to be updated to
   include a record for each new lesson. It is a good idea to create a back up before edits are made
   to Web.Config. If a mistake is made, it will break the entire Content Interface application for ALL
   CONTENT. Each new record that is added will contain UNIQUE StandardsCourseCode*. This is a
   numeric value that identifies each lesson.
   Example:
   <add key="998" value="Content/Periop/Module_43/Index.html" />
           998 = StandardsCourseCode*

            Content/Periop/Module_43/ = LESSON LOCATION

            Index.html = Launch File

5. Content is ready to be moved to Staging database (currently ELS4.Preview2010_Internal).
      a. Copy the data from WEBDATA8.KDSCONNECT.LINKEDWBT into current Staging
          Database:
          SELECT Description, Type, URL, Notes, FacilityCode, Global, Width, Height, Controls,
          StandardsCourseCode, CertProvider, Hours
          FROM         LinkedWBT
          WHERE (Type = 'unique course code')
          ORDER BY StandardsCourseCode

           The unique course code comes from item 3-c and 3-f
6. Data from (5-a) needs to be updated:

            Update LinkedWBT
            Set URL = Replace(URL, 'Q3456', 'DatabaseName'), FacilityCode = '00'
            Where Type = 'unique course code'
            The above query replaces the token/clientid in order for the results to be sent to the
            correct client database.
               Update LinkedWBT
               Set URL = Replace(URL, 'kdsconnect', 'app26'), Type = 'AICC'
               Where Type = 'unique course code'
               The above query points the user to the staging Content Interface (app26) instead of
               production (kdsconnect) and sets the type to AICC which is necessary for the content to
               work on client instance.
7.    The product owner and project manager can now begin QA and testing on the content on the
      staging instance (Currently Preview 2010).
8.    When QA has been completed and has been signed off on by the Product Owner/Project
      Manager, the content can now be moved to the Production server. Copy the entries from step 4
      above into the WEB.CONFIG file on the KDSCONNECT server.
9.    Copy Content from
      APP26/ContentInterface/Content/vendor/
      TO
      KDSCONNECT/ContentInterface/Content/vendor/
10.   Technical Services will create a SQL Script that will populate the appropriate data to be inserted
      into a client database when they purchase the content (PRIDE), and then run that script on
      KDS5CSDEMO and KDS5DEMO.
11.   FINAL QA should take place on the KDS5CSDEMO server to ensure that the data was populated
      correctly in the SQL script. If all lessons launch appropriately and certificates are displayed
      correctly, the content can be considered “Launched” and it is ready to move to client sites.
SCORM Background
What is SCORM?

Sharable Content Object Reference Model (SCORM) is a collection of standards and specifications for
web-based e-learning. It defines communications between client side content and a host system, which
is commonly supported by a learning management system. SCORM standards are governed and
published by the Advanced Distributed Learning Initiative (ADL).

SCORM Content
SCORM content can come in 2 forms. It can come as a package where one lesson is actually made up of
many mini-lessons. In this case the record that is placed in the LinkedWBT or the clients Web-Based-
Training will contain a manifest file that is in XML format (foldername/coursename/imsmanifest.xml).
That file essentially tells the LMS that this course is made up of x amount of lessons and here are the
links for those lessons. The LMS will then input a record into a table in the database with the learners ID
for each of those mini-lessons. When the user completes all of the mini-lessons, only then is the main
lesson marked complete.

SCORM content will return scores, bookmarks, and the status of the lesson (completed, passed,
attempted, and browsed). SCORM will also return the results of interactions, quizzes and exercises
within the lesson, but the LMS will only record that data if it is included in the “suspend data.”


       client designs / creates e-learning content by using tools like Adobe Captivate and Lectora
       content uploaded to SCORM 1.2 conformant ‘Zipped’ file, which contains all the files of the
        lessons of the course
       at the root of the ‘Zipped’ file, there must be a file called ‘IMSMANIFEST.XML’, which is a key file
        read by LMS API (READER)
       The content is uploaded manually. The tools above can only export content as SCROM or AICC.
       SCORM that belongs to clients must reside on the application
       Our API supports the following SCORM Parameters:
            - Student name
            - Lesson location
            - Lesson status
            - Rawscore
            - Suspend data
CASE A– launching a SCO with a direct link
Learner clicks on link in lesson plan [1]. The LMS recognizes that this is SCORM content and manifest is present. A
new window is opened containing the API (Application Program Interface), which will then open the SCO (Shared
Content Object) If the learner has a pop-up blocker on they may need to click the button or link to open the content,
it is provided in the API window. Depending on the user’s actions within the lesson, data will now pass back and
forth from the API to the SCO. This is will continue until the lesson is finished or closed. When the SCO is completed
or closed the SCO will pass the finalized data to the API and force it to pass that data back to the LMS [6]. At this
time both the SCO and the API windows are closed.




SCORM Tools

Adobe Captivate:
Adobe Captivate (formerly RoboDemo) is an electronic learning tool for Microsoft Windows which can
be used to author software demonstrations, software simulations, branched scenarios, and randomized
quizzes in .swf form. You can create anything from a simple slide show, to a complete branching
software simulation or evaluation, all delivered via Flash without learning any code.
PowerPoint slides can be imported into Captivate, making upgrading existing content to e-learning
courses less labor intensive. It is the most straight-forward package.

Lectora:
Lectora is is an Electronic learning (elearning) development tool, also known as authoring software,
developed by Trivantis Corporation. Lectora is used to create online training courses, assessments, and
presentations. It is also used for the conversion of Microsoft PowerPoint presentations into elearning
content.

Content developed with Lectora authoring software can be published to a variety of outputs such as
HTML, Single File Executable, and CD-ROM. Lectora content is compliant with elearning industry
standards, such as SCORM (Sharable Content Object Reference Model) and AICC (Aviation Industry
Computer-Based Training Committee). Content created in Lectora can also meet 508 Compliance
standards. In addition, Lectora is compatible with any standards-based learning management system
(LMS) on the market.



SCORM Certified
We are SCORM 1.2 Compliant. The company would need to pay to be certified.

For content to be SCORM Certified, means we have to send our product to ADL, it has passed the
SCORM 1.2 Edition LMS certification process and ADL has confirmed that we have implemented the
SCORM 1.2 standards correctly.

We currently are not certified because we would need to pay for each certification and also need more
development to dynamically import and process manifest file. Our current process is handled manually
by Jeremy’s team.


                  Open file        Load into SQL          Move content to
                                                          App Servers



MCS will also support Articulate and other popular authoring tools as long as they are fully SCORM 1.2
compliant.

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:8
posted:10/11/2012
language:English
pages:8