Show Advanced KnowledgeHide Advanced Knowledge

Automate Item Collection

1 Initial Problem

Fortunately, some enhancements have been introduced in the last ILIAS versions to make configuration of learning progress reports more comfortable.
However, one aspect is still in a sorry state, and that is "Automatically by Collection of Objects".
E.g., if you want to roll out some LP relevant object in a lot of courses, you will have to handle each single item collection.
Therefore, I plead for automating the item collection, so taking an object into consideration for LP is considered the default case and only those LP-capable objects which are explicitly not supposed to be LP-relevant have to be handled.

2 Conceptual Summary

I suggest the following automatism:

• every LP-capable object
• that becomes content of a LP-capable container in what way ever (manually created, copied, linked, moved, imported)
• will automatically be selected for LP determination of the the container
• as soon as the LP mode "Automatically by Collection of Objects" has been saved in the container
• unless the object's LP mode is "Deactivated" or it's anonymized

It should be possible to activate this automatism in "Administration > Statistics and Learning Progress > Completion Status".

3 User Interface Modifications

3.1 List of Affected Views

• trac/settings/lpdef
• crs/learning_progress/trac_settings
• grp/learning_progress/trac_settings
• fold/learning_progress/trac_settings

3.2 User Interface Details

• trac/settings/lpdef:<br>Additional checkbox "Automate Item Collections"
• crs/learning_progress/trac_settings, grp/learning_progress/trac_settings and fold/learning_progress/trac_settings:<br>As soon as "Automatically by Collection of Objects" has been saved, all entries in the list below are selected by default, unless their LP mode is "Deactivated" or they're anonymized.<br>When the view is opened after new objects arose, they're seelected, too.

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 Contact

• Author of the Request: {Please add your name.}
• 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.}

6 Funding

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

• …

7 Discussion

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