Feature Wiki
Tabs
Migration path for question types to ASQ
Page Overview
[Hide]1 Initial Problem
With the Introducing Assessment Question Service a new and independent service for the component Test & Assessment should be implemented. To make existing questions usable with the new service a migration path for every single question type must be created.
2 Conceptual Summary
We want to introduce a migration path (“migrate to asq”), so that questions created and used in the Test & Assessment can be migrated to the new Assessment Question Service. There need to be code for every single question type to make the migration possible. After this, question pools can be migrated to a new Test Question Pool as Independent Object, that uses ASQ.
After migration the “old” versions of pools are still usable in all existing components of T&A, the “new” versions with the components like ASQ, question pools, test players.
The challenging parts in this development are:
- Creating a possibility to migrate further information around questions (like content and context surrounding questions, e.g. taxonomies, page editor information, competences)
- All questions and their contents need to work with ASQ
- Quality assurance & testing (internal QS: we will ask for existing db-dumps to test; external QS: we need testers from the community)
3 User Interface Modifications
Migration process needs to be placed in the T&A question pools, after creating migration paths for all question types, see also:
- Multiple Choice Question (Single Answer)
- Multiple Choice Question (Multiple Answer)
- Multiple Choice Question (Kprim Answer)
- Error Text
- Hot Spot / Image Map Question
- Cloze Question (also supporting Long Menu Question)
- Numeric Question
- Formula Question
- Test Subset Question
- Ordering Question (vertical & horizontal)
- Matching Question
- Essay Question
- File Upload Question
- Text Order Question
4 Technical Information
{ The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }
5 Privacy
{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }
6 Security
{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }
7 Contact
- Author of the Request:
- Maintainer: Studer, Martin [mstuder]
- Implementation of the feature is done by: & Studer, Martin [mstuder]
8 Funding
If you are interest in funding this feature, please add your name and institution to this list.
- …
9 Discussion
10 Implementation
{ The maintainer has to give a description of the final implementation and add screenshots if possible. }
Test Cases
Test cases completed at {date} by {user}
- {Test case number linked to Testrail} : {test case title}
Approval
Approved at {date} by {user}.
Last edited: 29. Apr 2021, 15:23, Undisclosed