Wikisoba project: Difference between revisions
Jump to navigation
Jump to search
m (→Active pages: +) |
(→Mark II development plan: objectives) |
||
| Line 23: | Line 23: | ||
*The underlying layer of syntax should be JSON, and closely compatible with XML exported from Moodle. | *The underlying layer of syntax should be JSON, and closely compatible with XML exported from Moodle. | ||
*The working title for the underlying repository is "WikiQuiz". | *The working title for the underlying repository is "WikiQuiz". | ||
===Current objectives=== | |||
What are we trying to do? | |||
*Define a “lingua franca” in JSON that covers most standard question types as data structure, and that is also compatible with the format used in XML export from Moodle files. | |||
*Define a working format (MF, i.e. middle format) for data representation that is closely related, but more compatible with the operational side of the system. | |||
*Define a system architecture, in three parts (WA, QA and UA), for handling quizzes, which will be adequate to the needs of “students” (those using the quizzes), and “teachers” (those authoring quizzes), assuming a repository of quiz material in JSON. Here WA is the web app; QA would handle tasks such as marking and generating hints, that depend directly on processing the input from questions considered as a type of online form; and UA would handle aspects that most directly concern the user, such as tracking sessions, feedback, badges, and any notifications (for example to those developing questions). | |||
*Define a development path, via scenarios that introduce the ambitions for rendering, collaboration and security. | |||
==Active pages== | ==Active pages== | ||
Revision as of 09:56, 11 September 2014
The Wikisoba project is a spin-off of the WMUK Virtual Learning Enviroment, a software development initiative concerned with developing lightweight course management tools.
Mark I tool
The Wikisoba tool authored by Magnus Manske in Javascript is hosted on Wikimedia Labs. It pulls in sections of any fixed MediaWiki site, displaying them in a plain skin; and interleaves them with questions written in GIFT format.
Mark II development plan
For the next step, some new principles are being taken into account.
Aspirations:
- The quiz component should move beyond online forms as the only type of input, to include drag-and-drop and clicks on images.
- The design should be engaging, intuitive, colourful, and suited to the tablet era.
- The range of questions should be much extended.
- The tool should be versatile as far as the question setter is concerned, and should offer varied question types, though complex instances will probably have to be limited to form input.
- Navigation through a quiz will be flexible, and done section by section, rather than being linear and start-to-finish
- The back office parts of the system will be able to handle scoring of quizzes, responses (i.e. feedback to answers), hints, progress tracking, badges, and notifications to authors.
Technical:
- The Mark II tool is conceived of as a Web app, supported by server-side code: see diagram for a proposed architecture.
- GIFT format, and possibly other markup quiz formats, will be offered as human-readable layers for authors, but will not be the underlying language of the system.
- The underlying layer of syntax should be JSON, and closely compatible with XML exported from Moodle.
- The working title for the underlying repository is "WikiQuiz".
Current objectives
What are we trying to do?
- Define a “lingua franca” in JSON that covers most standard question types as data structure, and that is also compatible with the format used in XML export from Moodle files.
*Define a working format (MF, i.e. middle format) for data representation that is closely related, but more compatible with the operational side of the system. *Define a system architecture, in three parts (WA, QA and UA), for handling quizzes, which will be adequate to the needs of “students” (those using the quizzes), and “teachers” (those authoring quizzes), assuming a repository of quiz material in JSON. Here WA is the web app; QA would handle tasks such as marking and generating hints, that depend directly on processing the input from questions considered as a type of online form; and UA would handle aspects that most directly concern the user, such as tracking sessions, feedback, badges, and any notifications (for example to those developing questions).
- Define a development path, via scenarios that introduce the ambitions for rendering, collaboration and security.