Questionmark’s Open Assessment Platform

Please direct all feedback to developer@questionmark.com or by raising issues on the GitHub project where these pages are maintained.

Contents:

• Overview
  • Database Structure
  • HTTPS API Endpoints
• OData
  • OData Primer
  • Frequently Asked Questions
• Authoring OData API
  • Introduction
  • Example Applications
  • Entity Type Reference
• Delivery OData API
  • Introduction
  • Example Applications
  • Delivery OData Feeds
  • Entity Type Reference
• Results OData API
• QMWISe
  • Web Service Methods
  • String Parameters
  • Optional Parameters
  • Assessment IDs
  • Extension Types
  • Default Values
  • Basic Types
  • TLS and SoapUI
• Data Model
  • Security Tables
  • Assessment Tables
  • Question Tables
  • Answer Tables
  • Next Generation Tables
  • Scoring Tool Tables
  • Misc Topics
• PIP

Indices and tables

• Index

• Search Page

About this Documentation

This documentation is being developed to update and (eventually) replace the information in the following online guides, some of which may be available only to Questionmark customers:

• Delivery OData API Guide

• Perception 5.7 QMWISe API Guide

• Database Schema Reference Guide

Useful links:

• Configuring OnDemand for use with the Blackboard Connector good exemplar on configuring a suitable role for use with service accounts to use with the APIs.

This documentation is automatically generated using Sphinx from source code marked up with reStructuredText (see also Quick reStructuredText). You can find the full source in our GitHub Repository.

The items documented use a number of custom domains, the source of which is included in the above repository too. The following links have provided invaluable help in creating these custom domains:

• Sphinx Domain API

• Sphinx Source Documentation used in conjunction with the API docs to understand stuff used commonly in custom domain code.

• Sphinx Source on GitHub these domains were very useful in understanding how to implement the required classes directly (as opposed to having them generated automatically as per the GNU Make Domain example referenced in many custom domain projects.

• sphinx-contrib source code for a wide variety of custom domains

• HTTP Custom Domain An interesting project with some more complex layouts, also reviewed as a potential model for documenting OData services

• The Docutils Document Tree useful reading for doing the hard bits such as linking type definitions.

• Documenting a language using a custom Sphinx domain… a useful starting point for showing what is possible though this follows the GNU Make Domain pattern which was not ultimately adopted in the custom domains used.