Extending ASQ: Taxonomy Assignment for Questions

1 Initial Problem

The current implementation and dataset of the ASQ (not yet incorporate in the core of ILIAS) does not offer to process taxonomy assignments to a question. The legacy test question pool object offers this functionality.

2 Conceptual Summary

The data model of the question service will be extended in such a way, as to:

• save an array of taxonomy assignments for a question (one questions can be assigned to multiple taxonomy nodes)
  • in the current implementation of the question pool, taxonomies are bound to and managed by the respective question pool
  • thus, currently, moving a question out of its evironment leads to it losing ots taxonomy assignments - with central service managing the question, this behaviour might be changed in the future, if taxonomies for questions were to be handled "globally"
• each taxonomy assignment comprises a set / an array of taxonomy nodes (node IDs)
• the ASQ offers API functions to read this from / save this for a question

In the user interface, a new section witha  (de-)selector will be implemented  in order to select nodes from a taxonomy (which itself needs to be managed by an external object like a question pool).

3 User Interface Modifications

3.1 List of Affected Views

• [Edit Question]

3.2 User Interface Details

{ For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour. }

3.3 New User Interface Concepts

{ If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this. }

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 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: Glaubitz, Marko [mglaubitz] and Falkenstein, Rob [rob]
• Maintainer: Studer, Martin [mstuder]
• Implementation of the feature is done by:

8 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• Project bwILIAS

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}.