Feature Wiki
Tabs
Test Question Pool as Independent Object
Page Overview
[Hide]- 1 Initial Problem
- 2 Conceptual Summary
- 2.1 Main Purpose
- 2.2 Basic Requirements
- 2.2.1 Integrated Services
- 2.2.2 RBAC
- 2.2.3 TABS
- 3 User Interface Modifications
- 4 Privacy Information
- 5 Security Implications
- 6 Technical Information
- 7 Contact
- 8 Funding
- 9 Discussion
- 10 Implementation
This feature is part of the ongoing project Splitting-up T&A Into New Components
1 Initial Problem
With the introduction of an Assessment Question Service, the test question pool object needs to undock from the component formaly known as Test & Assessment.
With the current implementation of the question pool test object, questions are integrated as they belong to the same component. There is no clear cut between the test question pool related source code and the integration of the questions sub system.
2 Conceptual Summary
The integration of questions within the test question pool object needs to be changed. The Assessment Question Service comes with a defined interface for using an assessment question as service consument. The implementation using questions within the new Test Question Pool component needs to dock to this new interface. The new component Test Question Pool does not reuse the code of the legacy Question Pool Test but is a written from scratch as a repository object.
2.1 Main Purpose
The main purpose of the repository object "Test Question Pool" is to store test questions and make them re-usable in different components (test players and others). The object offers an interface to the new Assessment Question Service to allow creating and editing test questions. Like the legacy "Question Pool Test" it is mainly an object for authors. Learners won't use it.
2.2 Basic Requirements
As repository object, the "Test Question Pool" has to offer the Basic Features of an ILIAS Repository Object and to follow the Guideline Creation of Repository Objects.
2.2.1 Integrated Services
The "Test Question Pool" component reuses amongst others the following ILIAS services:
- Assessment Question Service to create and edit test questions
- Competence Management service to support the assignment of selected competences to questions
- Metadata service to support LOM metadata (incl. Quick Edit) for the pool
- Taxonomy Service to support the assignment of taxonomy nodes to selected questions and to offer question filtering by taxonomies
2.2.2 RBAC
Basic permissions are already defined by the "Basic Features" guideline. As the "Test Question Pool" is a component for authors only, READ permission should allow to see all questions within the pool and to re-use them in another component (e.g. test player). EDIT SETTINGS as WRITE permissions allow to create questions and to edit the settings of the object. At the time being, we do not see the need to offer separated permissions for editing content and editing settings. There is also no need to separate viewing questions and reusing them.
Global roles like USER and GUEST do not need to have any permissions on this object by default. Course and group administrators as well as the role template AUTHOR should get full permissions to use the Test Question Pool for authoring purposes. Roles and role templates should be adapted by DB migration when introducing this component to ILIAS.
2.2.3 TABS
The implementation of this components follows the Tabs Guideline for repository objects. Offered tabs and sub-tabs will be:
- Questions
- List View
- Print View
- Taxonomies
- Settings
- Competences (if activated in Settings)
- Question-Compentence Assignments
- Assignment Statistics
- Metadata
- Export
- Permissions
- Object Permission Settings
- Permissions of User
- Owner
- Log
Unlike the existing pool implementation, no Info page will be offered for this new component as there is currently no need for it.
Tab "Questions » List View"
While the former test question pool only offered one view under the tab "Questions", the new implementation gets two more sub-tabs from other parts of the former pool implementation. This is why a new subtab "List View" is necessary. This view contains:
- Filter to select questions according to title, description, author, lifecycle, question type, taxonomies (if activated), given comments
- Table for all contained questions with columns [1] for
- Title
- Description
- Question Type
- Points
- Statistics
- Author
- Lifecycle
- Comments
- Create Date
- Update Date
- Working Time
- Actions (with related dropdown)
- Actions offered in Actions dropdown are
- Question Page
- Edit Question
- Edit Page
- Move
- Copy
- Delete
- Feedback
- Hints
- Comments
- Actions offered in Multi-Actions are
- Copy
- Move
- Export
- Delete
Tab "Questions » Taxonomies"
- Button "Add Taxonomy"
- Table "Taxonomies" with all existing taxonomies
- Title
- Description
- Actions (Edit, Delete)
Tab "Questions » Print View"
This view was a main tab in the former implementation but should be moved under the "Questions" main tab as sub-tab as it is content-related.
Main purpose of this view is … [ needs to be clarified ]
Tab "Settings"
Only a few settings will be offered for the test question pool. Additional submenues are not needed. Settings are clustered in sections:
- General Settings
- Title (text input)
- Description (text input)
- Availability
- Online (checkbox)
- Presentation
- Tile Image (file upload)
- Additional Features
- Taxonomies (checkbox)
- Taxonomy Filter as Navigation Tree (dropdown)
- Competence Service (checkbox)
- Taxonomies (checkbox)
Tab "Competences"
This tab appears only when competences have been activated in Settings.
- Question/Competence Assignment
- Table with columns for
- Question (all questions of pool are listed)
- Competence (if assigned)
- Evaluation by
- Competence Points
- Competence Assignment (with shy button for "Manage"
- Table with columns for
- Assignment Frequency
- Table with columns for
- Competence
- Number of Questions in Pool adressing this competence
- Total Sum of Points per Competence
- Table with columns for
Tab "Metadata"
Re-uses the known Metadata views and sub-menues. No specific changes for this component.
Tab "Export"
This view offers export files for the following formats:
- [ needs to be clarified ]
Tab "Permissions"
Re-uses the known RBAC views and sub-menues. No specific changes for this component.
3 User Interface Modifications
3.1 List of Affected Views
- Questions
- List View
- Print View
- Taxonomies
- Settings
- Competences
- Question-Compentence Assignments
- Assignment Statistics
- Metadata
- Export
- Permissions
- Object Permission Settings
- Permissions of User
- Owner
- Log
3.2 User Interface Details
to do
3.3 New User Interface Concepts
???
3.4 Accessibility Implications
{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }
4 Privacy Information
{ 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. }
5 Security Implications
{ 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. }
6 Technical Information
This request depends on the request for an Introducing Assessment Question Service.
7 Contact
- Author of the Request: Kunkel, Matthias [mkunkel]
- Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
- Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}
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: 18. Oct 2024, 15:27, Kunkel, Matthias [mkunkel]