Feature Wiki

Information about planned and released features

Tabs

JourFixe-2013-01-21

Page Overview

[Hide]

The Jour Fixe took place at Monday, January 21 from 09h15 to 13h30 at ILIAS office in Cologne. Participants were:

  • Michael Jansen, Alexander Killing, Matthias Kunkel (Minutes), Jörg Lützenkirchen, Stefan Meyer, Fabian Wolf

1 Appointments

2013-02-18: ILIASuisse, PH Zürich
2013-02-05 (Tuesday!): Jour Fixe in Würselen
2013-02-06: Workshop on Org Units, Qualitus, Köln
2013-02-15: ILIASuisse, PH Zürich
2013-02-20: ILIAS-NRW, Uni Münster
2013-03-21: 19th DevConf, PH Zürich
2013-03-31: Feature Freeze for 4.4
2013-08-28: 20th DevConf, Munich
2013-08-29 to 30: 12th ILIAS Conference Munich

2 Bugfixing for maintained versions 4.1, 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.9 published at 29 March 2012
Next releases:
  • 4.3.2 is scheduled for March 2013
  • 4.2.8 is scheduled for March 2013
  • 4.1.10 is scheduled for 24 January 2012
We went through Mantis and had a overlook about all open issues. All issues were screened and assigned to the responsible developers.

  1. Mantis 10224: We discussed the implementation of the SOAP method getInstallationInfo()
    • In 4.3.1 it returns
      • a list of all clients
      • their NIC ID
      • their Client ID
      • their default language
      • whether soap is activated or not
    • We decided that:
      • The list must not return any clients with deactivated SOAP.
      • An information text (please use a new lang var) should be used to the administration checkbox that activates SOAP. The text should state that the client will be listed in this function that lists all clients without authentication. 
  2. Mantis 10458: Basically we agree with the example. But still we would prefer to leave this in the decision of the author. The solution phrase could be far longer and this could make sense. Another problem is that backwards compatibility should be given, if possible and we do not want to change existing values here.
  3. Responsive Design: We postpone this issue to the next Jour Fixe when our CSS maintainer can join the Jour Fixe.

3 Feature Requests for ILIAS 4.4

3.1 Funded Features

  1. ILIAS Cloud Folder / Cloud Interface: We like and support the idea and schedule it as a plugin slot for 4.4. But we must clarify some technical details:
    • We are not sure if the suggestion to make drop box a core feature and other cloud services plugin-ins. We think all implementations should be plug-ins, since we do not want to create dependencies from other projects. But they all could be based on a common implementation (like suggested) which could be derived from the classes of the repository plugin slot. The cloud plugin slot extends the repository plugin slot and provides common features.
    • We should setup rules how the credentials of the services are used. E.g. passwords should be stored using (m)crypt() in the database. A key/salt could be stored in a separate file. This would make the external accounts safer (e.g. an SQL injection would not be enough). This handling could be also a part of the base implementation.
  2. Terms of Services: We appreciate the idea and schedule it for 4.4. Please use the overlay also for the last screen. Please show the date of the last reset beside the reset button. If easy possible, think of storing the agreements not multiple times but identify them by a md5 string.
  3. Interpretation of http URLs: We re-schedule the feature for 4.4.
  4. Extending Span Formatting: We appreciate the feature except the nbsp idea and schedule it for 4.4. nbsps are ofter used for workarounds that could be solved in better ways.
  5. File Search by Extension: We appreciate the idea and schedule it for 4.4. The file type selection could be represented a s a second checkbox column in the type overlay. We realised that the combination of file type selection and repository type selection makes sense for moste of the repository types (except e.g. course, groups).
  6. Prefilled Textarea in Forms: For the general case there is no need to do any implementation since it is possible to use predefined values from the lang file in forms. We need to discuss concrete cases were this should be introduced. Not scheduled.

3.2 Funding Required / Unclear

  1. Disable placeholders: The maintainer can inform you on technical alternatives. If an implementation should be added to the core a revision of the place-holder-handling would be necessary. Please re-schedule the topic again, if it should be part of the core.
  2. [[[Project] LTI Support in ILIAS]] (e.g. for integrating OpenCast Matterhorn): We strongly support the whole idea. We definitively would like to have a first fixed use case. E.g. the implementation of an LTI repository object with the goal to represent a matterhorn recording as a repository item to the learner. We must clearly define how the behaviour of different LTI consumer implementations as repository objects would be, e.g. their presentations in the "Add New Item" drop down, their presentation in container objects, their permissions, ... So beside the use case a next step would be to have a technical concept.
  3. E-Mail notification only once after the end of the survey: We appreciate the idea and schedule it for 4.4. The implementation of the "tutor" notifications in surveys and exercises should be streamlined:
    • a multi-input field for account names should be used (using autocomplete)
    • only users with write access can add and be added (write access must also be checked if the mails are sent)
    • the settings are put into a separate form section
    • the feature "zusätzliche Teilnehmerdaten" of the survey is abandonded.
    • multiple possible notiication events (user finishes survey, survey ended, all users have finised a survey) are listed separtely (checkboxes). these settings affect all recipients in the same way.
    • if a notification depends on a cron-job (e.g. survey ended event), this should be stated in an information text

3.3 Postponed to 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. Pluginslot in Cronjob
  5. Assign global role to locale role
  6. RSS-Feed - select what kind of data will be collected from the groups, categories etc.
  7. Select users will always be notified when a new appointment was created
  8. Different test parts for randomized tests
  9. Selecting recipients for group and course mails
  10. Taxonomies for Test Questions
  11. Item preview from question pool plus feedback
  12. Auto-fill for Course waiting list
  13. Repository Object Selection Input GUI
  14. Advanced Event Raising
  15. Explorer/Locator Guideline
  16. Client Side Editing of Image Maps
  17. Style Sheet Editor CSS3
  18. Role-based Activation of Portfolio
  19. Export and Import of Portfolios
  20. Usability Improvements of Assignments and Grading Screens in Exercises
  21. Showing Calendar in Portfolio
  22. Add action button in root of repository to provide webdav access
  23. Enhanced Permission Handling For DC Contributors

4 Miscellaneous

Next Jour Fixe takes place at Tuesday, 05 February 2013, 09h00 at Databay office in Würselen.

Last edited: 18. Oct 2024, 15:50, Kunkel, Matthias [mkunkel]