1 / 14

Standardized And Extensible JavaScript-API For Logging Functionality For the MVP Player

Standardized And Extensible JavaScript-API For Logging Functionality For the MVP Player. Heid J, Hess F, Huber S, Haag M, Huwendiek S. ANSI/MEDBIQ VP.10.1-2010. Defines storage of virtual patients (VP) Provided as a SCORM package virtualpatientdata.xml for the data

homer
Download Presentation

Standardized And Extensible JavaScript-API For Logging Functionality For the MVP Player

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Standardized And Extensible JavaScript-API For Logging Functionality For the MVP Player Heid J, Hess F, Huber S, Haag M, Huwendiek S

  2. ANSI/MEDBIQ VP.10.1-2010 • Definesstorage of virtual patients (VP) • Provided as a SCORM package • virtualpatientdata.xml for the data • dataavailabilitymodel.xml for aggregation of the content • activitymodel.xml for walk-through definitions • Used by eViP for 320 VPs

  3. Example: OpenLabyrinth VP in CAMPUS Card-Player

  4. Player Implementations • MVP players use the same data format • MVP VP inside SCORM package for use in learning management systems (LMS) • Idea: Standardized, extensible logging API based on MVP standard

  5. Player Implementations (cont.) MVP player Server firesevents transmitsdata Log-API MVP generates interacts Reports User

  6. Player Implementations (cont.) • Step #1: Include JavaScript-API:<script type=“text/javascript“ src=“mvp-log-api.js“></script> • Step #2: Fire events:logAPI.fireSpecEvent ({ type: logAPI.Type.INTERVIEW_ITEM_SHOWN, id: ‘4711‘ });logAPI.fireEvent ({ ns: ‘http://www.imsglobal.org/xsd/imsqti_v2p1‘, typeID: ‘question-answered‘, id: ‘4711‘, data: … });

  7. Event attributes • namespace: Spec or external (like QTI) • elementID: Reference to the XML-id • userID: Identification of the current user • typeID: The type of the event • date: Timestamp of the event • data: Optional additional data (e.g. for QTI)

  8. Consumers MVP player firesevents Log-API register Consumer #2 Consumer #1 transmitsdata transmitsdata

  9. Consumers (cont.) • Consumers register themselves at the API: medbiq.mvp.log.registerImplementation ({ eventReceived: function (e) { // do something with the event… }, isNamespaceSupported: function (ns) { // Only ActivityModel return ns === medbiq.mvp.log.NS_ACTIVITY_MODEL; } });

  10. Consumers (cont.) • Consumers can analyze the data to show: • Walk-throughs of users • Frequency of pages • Time-consumption • Media usage • Resuts of a formative assessment • … → independent from the MVP system

  11. Consumer-Example #1: Console • Helps developing by showing all events • Just include an extra JavaScript file:<script type=“text/javascript“ src=“mvp-log-console.js“></script> Log-API Console

  12. Consumer-Example #2: Walk-through Visualisation Demo Log-API Consumer

  13. Get involved • Code and examples at:http://code.google.com/p/mvp-log-api/ • Discussion at: http://groups.google.de/group/mvp-log-api • MVP-XSLT-test-suite at:http://code.google.com/p/mvp-evip-xslt-test-suite/

  14. Thanks for your attention. Contact: Centre for Virtual Patients University Hospital Heidelberg http://campus-virtual-patients.com info@campus-virtual-patients.com

More Related