JourFixe-2013-03-04

The Jour Fixe has taken place at Monday, March 04 from 09h00 - 13h45 at ILIAS office in Cologne with the following participants:

• Björn Heyser, Alexander Killing, Matthias Kunkel (Minutes), Jörg Lützenkirchen, Stefan Meyer, Florian Suittenpointner, Fabian Wolf

1 Appointments

2013-03-18: Jour Fixe
2013-03-21: 19th DevConf, PH Zürich
2013-03-31: Feature Freeze for 4.4
2013-04-15: Jour Fixe
2013-05-07: ILIAS-Nord in Bad Segeberg
2013-08-28: 20th DevConf, Munich
2013-08-29 to 30: 12th ILIAS Conference Munich

2 Bugfixing for maintained versions 4.2 and 4.3

Last releases:

• ILIAS 4.3.1 published at 14 January 2013
• ILIAS 4.2.7 published at 03 January 2013
• ILIAS 4.1.10 published at 03 February 2013 (maintenance ended)

• 4.3.2 is scheduled for 04 March 2013
• 4.2.8 is scheduled for end of March 2013

Bug Fixing Statistics (Status: 03 March 2013)

• Open bugs in Mantis: 1678
• Balance open-resolved:
  • last 7 days: -20
  • last 30 days: +20
  • last 90 days: +81
• Open for longer than three month (submitted before 03 Dec 2012): 1464
• Open for longer than one year: 916
• Open for longer than two years: 460

We went through Mantis and had a overlook about all open issues reported or modified since the last Jour Fixe. All issues were screened and assigned to the responsible developers. We discussed in detail:

1. Mantis 10488 - Sessions, Material in Sessions, and Edit Timings: Materials can be downloaded: A final solution would require a change of the ilAccess object in the central permission system. We should schedule this for 4.4.
2. Mantis 10594 - blog comments: We currently do not consider this as a bug. The edit views of other tools (e.g. wikis) also do not show the comments that are supposed to be displayed for all users with read access (read permission) on the edit screens. The SCORM editor uses comments for authors *only* on the editing pages (write access). If this behaviour should be changed, please add a change request to the feature wiki.
3. Mantis 10652 - survey - codependent form fields: We prefer the solution to move the min/max options as suboptions to the subtype setting.
4. Mantis 10680 - Selected objects for linking are untoggled when expanding another node: We hope to get a jsTree based implementation for 4.4 that is able to load subtrees per ajax and keep the rest of the HTML (including the selections) as it is.
5. Mantis 10265 - A started test is shown as failed in Learning Progress (see comments in report): The current behaviour is the desired behaviour, we do not consider this as a bug. We agree that the behaviour could be changed and/or improved, but this should be done with a change request in the feature wiki for a major release. A discussion with the eAssessment SIG would be desirable.
6. Mantis 9930: Highscore : access to feature: We postpone the discussion for now and move it to the Revision of info page discussion.

3 Feature Requests for ILIAS 4.4

3.1 Funded Features

1. Item preview from question pool plus feedback: We support the idea and schedule it for 4.4.
2. Categorize Add New Item list: We highly appreciate the idea and schedule it for 4.4. We agree that ILIAS should support two options: (1) Categorized by ILIAS OS, (2) Adapted categories (with the possibility for ILIAS-Admins to create an own arranged system). We keep the discussion open for the first "default" ordering.
3. Numerical evaluation in tracking of learning progress: We agree that this could be an interesting extension of the learning progress feature. However there are some details that need to be clarified in the concept. E.g. how points for tests are calculated that have a percentage > 0 but have been failed. In general we prefer any technical solution that does not depend on changes in the components (test, exercise, ...) but only extends the current learning progress code. Please also note that, if the code is provided by a person that is currently not a maintainer of the code, integration costs must be funded and the code may be rejected by the maintainer if it does not comply with general conventions or quality, see the list of maintainers and the rules for developers.
4. Multilingual content support: We still appreciate the feature and schedule it for 4.4.
5. Extended Category Settings: We highly appreciate this feature and schedule it for 4.4.
6. Learning Progress for LM Chapters: Today we discussed the presentation of the Learning Progress icons. If a chapter determines the overall status, its chapter icon should be replaced by the lp status icon in the table of contents views (left handed and main toc).

3.2 Funding Required / Unclear

1. Separating Submission and Navigation: We appreciate the improvement. We would not like to have too many options here to configure the behaviour. We currently see the following alternatives:
   • Questions are shown in a non-editable "navigation" view per default. In this view answer cannot be submitted. Previous/Next buttons are dispayed and if activated the buttons "Postpone"/"Suspend" or the list of questions would be offered in the navigation mode as well (and only here). A "Edit Answer" button would lead to an editing view that allows the editing and includes a "Submit Answer" and a "Cancel" button, but hides the Previous/Next buttons and all other navigation elements.
   • We do not introduce a non-editable view but a "Submit Answer" button would be added. The Previous/Next buttons are renamed to show explicitly what they do, e.g. "Do not submit answer and move to next question".
   • We do not introduce a non-editable view but a "Submit Answer" button would be added and always leads to the next question. If the user hits "Previous/Next" a confirmation message is shown ("You did not submit the answer, do you want to continue?"). The effort for this implementation could be quite high, if the messages should only be shown if any change has been made to an answer.
   • We currently prefer the first solution and hope to get feedback on this from the eAssessment SIG and other users. We schedule the implementation but asks the developers not to start with an implementation before mid April 2013.
2. Right and Wrong Instead of Points: We agree that this could be improved but there are two main issues that need to be solved:
   • How are points for partly correct answers defined?
   • How are existing questions migrated, if this new (simpler) editing should completely replace the existing implementation?

3.3 Postponed to Next Jour Fixe

There was not enough time to discuss the following suggestions. They are now on the agenda of the next Jour Fixe.

1. E-Mail notification to the participant of a survey
2. List of participants in an anonymous survey
3. Metric rows in matrix questions
4. Assign global role to locale role
5. RSS-Feed - select what kind of data will be collected from the groups, categories etc.
6. Select users will always be notified when a new appointment was created
7. Auto-fill for Course waiting list
8. Repository Object Selection Input GUI
9. Advanced Event Raising
10. Client Side Editing of Image Maps
11. Style Sheet Editor CSS3
12. Mobile Support Style Sheet Editor
13. Role-based Activation of Portfolio
14. Export and Import of Portfolios
15. Usability Improvements of Assignments and Grading Screens in Exercises
16. Add action button in root of repository to provide webdav access
17. Enhanced Permission Handling For DC Contributors
18. Default object settings
19. Improvements of Tooltip Creation in Online Help
20. Online Help: Search
21. Enhance evaluation of ordering questions
22. Setting Templates Course
23. Mail via role assignment over the personal dektop
24. PDF-Printing a Portfolio
25. Temporary Role Memberships
26. Object Terminator
27. Default Sorting of Objects in Repo
28. Assign Permissions of New Objects to Existing Roles
29. Revision News Presentation
30. Design for the Maintenance Page

4 Miscellaneous

Next Jour Fixe:

• Monday, 18 March 2013, 09 a.m. at the ILIAS open source e-Learning office in Cologne. This is the last Jour Fixe before Feature Freeze.