Feature Wiki

Information about planned and released features

Tabs

JourFixe-2015-06-08

Page Overview

[Hide]

Date and place:

  • Monday, June 08, 2015 from 12h30 - 17h00 at ILIAS-Verein office in Köln
Participants:
  • Björn Heyser, Alexander Killing, Colin Kiegel, Matthias Kunkel (via Skype), Jörg Lützenkirchen, Guido Vollbach

1 Appointments

2 Bugfixing for maintained versions 4.3, 4.4 and 5.0

Last releases:

  • ILIAS 5.0.2 published at May 13, 2015
  • ILIAS 4.4.9 published at May 15, 2015
  • ILIAS 4.3.10 published at January 31, 2015
Next releases:
  • 5.0.3 is scheduled for June 24, 2015
  • 4.4.10 is scheduled for July
  • 4.3.11 is scheduled for June 12, 2015 as final release of version 4.3

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. #16035 - cron job deactivation on crash : The cron mangager only deactivates tasks that do no return any result. If any catchable error or exception is thrown during the execution, the task itself should catch it and return an error to the manager, in this case the manager should not deactivate the task.
  2. ILIAS announces Oracle-Support. Currently ILIAS-Releases are not tested on a Oracle-Based-Installation. With a possible removal of ilDB and the replacement with PDO the Oracle-Support could be a problem. How to handle Bugreports which only appear on Oracle-Based-Installations? There is no Dev-Environment for Maintainers. A possible solution is to provide a Test and Dev installation with an Oracle-DB (a Amazon RDS Instance would be several €/month) ore to abandon the Oracle support of ILIAS. Last Bug reported with an oracle-Installation: http://www.ilias.de/mantis/view.php?id=16028. But there where discussions before, sometimes almost emotional: http://www.ilias.de/mantis/view.php?id=13883... Others are without solution: http://www.ilias.de/mantis/view.php?id=13327 or http://www.ilias.de/mantis/view.php?id=7548 : Currently ILIAS supports Oracle, if a maintainer gets a oracle bug report assigned (s)he is responsible to fix it, this means, if necessary the developer has to set up an Oracle installation for himself (this happened in the past).

3 Developing ILIAS 5.1

3.1 Development Issues 5.1

  • Design Revision Part 2 : Ranking of issues and definition of next steps : We ask everyone interest to give feedback until 13 June. Please use the format used by Matthias and Hansjörg. After that Matthias will provide an overall aggregated priorization.
  • Who is online? tool for awareness : Alex has shown a first visual prototype today. Using a scrollable area is ok, also the presentation of the functions for each presented user. The presentation uses bootstrap popupers, drop downs and the media lists, which seems appropriate. We appreciate the feature and schedule it for 5.1. We agree that a separate administration section should be added for the "Awareness Tool" (the configuration should not be part of the Chat section).
  • Learning Progress on visited pages : We re-schedule this feature for 5.1.
  • Introduction of Split Buttons, see http://getbootstrap.com/components/#btn-dropdowns-split : We support the idea to introduce Split Buttons. A first use case should be the actions in forum postings. The "Reply" action should be triggered by the button part, all other actions should be placed in the drop down. Before split buttons are introduced in other places a separate JF discussion is needed.

3.2 Feature Requests for ILIAS 5.1

We discussed and decided upon the following features:

  1. Test: Long Menu Question: We assume that all entries are always sorted alphabetically and a manual ordering is not needed. In this case the fourth mockup by BH could feature a second input text field (under Item List Upload) and an "Add" button instead of "+" icons for every entry in the list. "Manage List Entries" should be listed before "Select/Reset". 
    • Mockup...
      •    Answers     Answer Options: 200 [Edit]
      •               Correct Answers: Item1, Item 2 [Edit]
    • Moving the upload field into the overlay is ok. We appreciate the mockups in general and this implementation would be ok for us, we schedule this for ILIAS 5.1.
    • We also had a look at https://select2.github.io/. We see some advantages
      • uses minimal space
      • similar ui is used on well known websites
      • autocomplete gives flexibility when entries are searched/filtered (however this could be added to the "edit correct answer" screen in Björns solution, too
    • .... and some disadvantages
      • new dependency to third party lib
      • seems to have a bad accessibility (screenreader)
      • if the user does not use type-ahead, but selects from the list, a lot more clicks are needed to select multiple items
    • Please check again on the accessibility of select2 lib. If this issue has been solved, using it would be ok for us.
  2. Mail: HTML Mails with Skin: We appreciate this feature and schedule it for 5.1. Please note that we slightly modified the feature description.
  3. General Services / Multilinguality: Extended Translation Functionality for Container : We appreciate the feature and schedule it for 5.1.
    • For item groups the "description" property can be abandoned, since it is not used.
    • We also would like to revise the editing of properties that provide translations. The properties should stay in their orginal forms. The multilinguality settings screen should only list the supported languages and make a decision on the default language. For properties the values of the default language should always be used for the input fields in the original form. Below the input fields a link "Translations (number of available translations)" should open a bootstrap modal dialog, where the translations (for this field) can be edited.
  4. IPE: Option to Hide Title of Item Groups: We see two options.
    1. Item Groups get an option to "Hide the title in presentation". The presentation for non-editors would be as in the screenshot from MK. Users with editing permission would see the title in the header with the action drop down on the right.
    2. The second option would be: "Real" support of single items in the page editor. But this should include drag/drop for all repository items on the screen (also within item groups). In this case objects "under" the page content should be visible in the editor, too, even if not included yet. We would start with the first implementation and schedule it for 5.1.

3.3 Requests for Removal

  1. Remove Local Administration: We need to discuss again when Stefan joins the Jour Fixe.

3.4 Decision Postponed

The following features requests will be discussed in an upcoming Jour Fixe due to missing time.

Features with (announced) funding:

  1. Forum: Add New Posting
  2. Wiki: Embedding and Scripting on Wiki Pages
  3. ILIAS Learning Module: Improve Multi-Linguality and Translation
  4. LM ILIAS: Improve Usage of Subtitles
  5. Media Pool and Media Object: Migrate videos to mp4
  6. Cron Service: Summary Mail comprising News of Groups and Courses
  7. Test: Cloze Question Improvements
  8. Export: Export HTML source code to Excel
  9. Mail: Placeholder_FIRST_NAME_in_fields_CC_and_BCC
  10. Session: Hide columns in edit participants tab of a session
  11. Portfolio: PDF-Printing a Portfolio
  12. Personal Desktop: Configure detail options for Selected items
  13. Media Pool: Insert question into a content snippet in media pools
  14. Wiki: Extending User Activities for Page Editing, Protecting and Deleting
  15. Wiki: HTML Export Extensions
  16. Course / Groups: News Notification for Courses and Groups
  17. Course: Default for Status "Online" after copying an object
  18. Test: Separating Submission and Navigation
  19. Test: Export HTML source code to Excel
  20. Question Pool & Test: Revision of MCQ: Alternative points specification for multiple choice question
  21. Portfolio: Export and Import of Portfolios
  22. Learning Module: Support Plugin Question Types on Learning Module Pages
  23. Session: Hide columns in edit participants tab of a session
  24. Personal Desktop: Configure detail options for Selected items
  25. Media Pool: Insert question into a content snippet in media pools
  26. Authentication/Login: OAuth1 and OAuth2
  27. Exercise: Criteria for assignment reviews
  28. Exercise: Extension of peer feedback: self-review
  29. Test: Extended Test and Item Statistics
  30. Test / Plugin Slot: Plugin Slot for Test and Item Statistics
  31. Copying Linked Objects
  32. Interactive Videos
  33. Exercise: Show Peer Feedback Deadline in Object Description
  34. Notifications: Scheduled Reminders
  35. Repository et. al.: My courses and groups as alternative source on copy screen
  36. Registration: Multiple LDAP server configurations
  37. SOAP: SOAP method for determination of Learning Progress: getProgressInfo
  38. Repository: Improve Deletion of Objects
  39. Courses: Embedded Folders in Courses
  40. Repository: Tile View in Repository
  41. Repository: Images for Tests
  42. Repository: Images for exercises
  43. Repository: Image for File Objects
  44. Language Handling: Language Detection via Browser
  45. Registration: No automatic log out / Users stay logged in
  46. Interfaces: [[[Project] LTI Support in ILIAS]]
  47. Course: Learning Objectives-Driven Course
 
Features appreciated by maintainer or SIG:
  1. Test: Improve Shuffling of Answer Options during Testpass
  2. My Workspace: Better Integration of Workspace with Repository
Features without funding but with feedback from other users:
  1. Test: Extract Test Results from the Participant tab and make a separate Tab of it
  2. User Interface: Error and No Permission Screen
  3. Certificate: Open Badges
  4. Courses and Groups: Blog-overview in member area of groups and courses
  5. Personal Desktop: Usability Improvements of the Personal Desktop
  6. User Interface: Breadcrumb Navigation Bar
  7. Object Templates: Administrating Settings Templates
  8. Course Management & Object Templates: Setting Templates Course
  9. RBAC, Portfolio & My Workspace: Role-based Activation of Portfolio
  10. Repository: Separate tracking of user access from content changes
  11. Portfolio: Link to view stored portfolio
Suggested features that require funding:
  1. Performance: Lightweight profiling of requests
  2. Test: Style for Tests
  3. Booking Tool: First Come First Serve Solution
  4. Booking Tool: Reminders and Notifications in Booking Pool
  5. Learning Progress determined by Collection of Objects, yet alterable by Tutor
  6. Main Administration: Searchable Labels in Administration
  7. Groups - Import Members or Batch Selection
  8. Setup/Core: Modern Configuration File Format
  9. IPE: Manual Carousel / Slider Content Element for Page Editor
  10. IPE: Tabbed Content Element for Page Editor
  11. Test: Random Test Directly Linked With Pool(s)
  12. Test: Rearrange Elements of Test-Question-Page
  13. Test/Pool: Test-Parts and Question-Groups
  14. Learning Module ILIAS: ePUB Export
  15. IPE: Context-dependent paragraph styles in advanced lists and tables
  16. IPE: Linking in ILIAS Editor
  17. Test: Filter Revision in Manual Scoring
  18. Online Help: ILIAS can handle several help packages
  19. Media Objects and Pools: Filter for inserting media objects from media pool
  20. Repository: Separating Changed Inside and Number of Read Accesses
  21. Media Objects and Pool: Extend Usage of Content Snippets
  22. Organizational Units: OrgUnit behaves in RBAC like a group and category
  23. Learning Module HTML: Abandon Feature - Bibliographical Data in HTML Learning Modules
  24. Course Management: Streamline Membership Assignment Methods
  25. Course Management: Mail from Course Members Gallery
  26. RBAC: Role Template Screen Revision
  27. Core: Streamlining the copy process in general
  28. IPE: Poll as Page Editor Element
  29. Groups: Randomly distribute a set of course / group members  to a set of groups
  30. Media Objects: Link-areas in images: coordinates should be easily changeable + grid desirable
  31. Media Objects: Pop-up container: more variations desirable
  32. Learning Module SCORM: Feedback of questions: change of behavior requested
  33. News: Change Generation of RSS-Feed Link
  34. Learning Module ILIAS & Test: Traceable connection between tests and ILIAS-learning module
  35. Test: Detailed feedback (text and hyperlinks) after test is finished
  36. Files & Learning Module ILIAS: Collaborative Annotation / Social Reading
  37. IPE: Content Snippets in Pages of Container Objects
  38. IPE: Content Snippets in Portfolio Pages
  39. IPE: Content Snippets in Wiki Pages
  40. Test: Multiple pass scoring: change default setting to scoring the best pass
  41. Test: Using Signature-Plugin and Max. Processing Time simultaneously
  42. User Interface: 'Availability' in Action-Menue and 'Settings'-Tab
  43. Course Management: Printable Member List for Members
  44. Course Management: Additional sorting options for My Courses and Groups
  45. Search: Switch off Content Search but still search for Users
  46. Learning Progress: Privacy Improvements of the Learning Progress for Course Members
  47. Course Management: Send Mail when Course Copying is Finished
  48. Learning Module SCORM: Internal Links for SCORM Modules
  49. Booking Tool: Allow booking after timeslot has started
  50. Booking Tool: Filter for free ressources
  51. Booking Tool: Import form Untis or Davinci
  52. My Workspace: Mediacast in My Workspace
  53. Learning Communities: Teams
  54. Learning Modules HTML: timestamp for last changes in HTML Learning Modules
  55. News: Present (manually created) news on course content page
  56. My Workspace: »Last Edited« in Table of Shared Resources
  57. Course / Group: Preset notification of blog posts
  58. Precondition Handling: Separate Preconditions for Registration/Participation in Courses/Groups
  59. Course: Auto-fill for Course waiting list
  60. Course: Course Type: Online vs. On-Site
  61. Course: Course/Group Cancellation Deadlines
  62. Course: Relative Dates in Courses/Groups
  63. Course: Minimum Number of Participants
  64. Learning Module ILIAS: Question Overview in ILIAS LM
  65. IPE: Insert HTML5 Objekt
  66. Media Pools and Media Objects: Client Side Editing of Image Maps
  67. Learning Module SCORM: Improved License Management
  68. Course: Using SCORM modules to validate course objectives
  69. Test: Deactivation of Javascript Usage in Tests
  70. Cloud Object: Cloud Folder in the users workspace
  71. SCORM Editor: question pool support
  72. SCORM Editor: Feedback of questions: change of behavior requested
  73. SCORM Editor: Internal Links for SCORM Modules
  74. SCORM Editor: poster image for videos
  75. Intellectual Property Rights Object
  76. Help: Help Icon in the Page Editor Panel
  77. Learning Progress: Segmented Learning Progress
  78. Course: Course IDs
  79. Course: Credit Points
  80. Course: Separate Settings Subtab for Registration
  81. Course: Course-Specific User Data: Boolean Format
  82. Course: Learning Plan - Relative Timetable
  83. Booking Pool: Extended Metadata for Booking Pools
  84. Test: Tinting examination screen
  85. Registration: Assigning roles and objects to user when registering
  86. Portfolio/Personal Desktop: Portfolios on Personal Desktop
  87. Media pools Move and copy of media objects in media pools
  88. Usability Improvements in Test: Straightforward Configuration of Result Presentation
  89. Usability Improvements in Test: Nice Presentation of Test Results
  90. Portfolio: »Set Portfolio Online« Message in Share-tab
  91. Portfolio: access to the portfolio via avatar in the headline
  92. Usability: URLs without cmd nodes
  93. Development Support: Autoloading
  94. Test: History Mode for Personal Skill GUI
  95. Data Collection: Summarize Columns
  96. Metadata: Location Multi-Part Custom Metadata
  97. Booking Tool: Linking Booking Pools to Courses
  98. Learning Module ILIAS: Continue as default
  99. Personal Profile: Change Password in Personal Data
  100. User Interface / Test: Indicator for hidden information in settings
  101. Error dumping workflow for loadbalanced setups, see discussionpost on Error handling and logging
  102. RBAC: Copy Permissions
  103. Split DB-Update
  104. Search results with additional information - Creation date
  105. Registration: Avoid multiple Accounts per User
  106. SOAP: Administration of SCORM-Learning-Modules via SOAP
  107. Repository: Copy to Multiple Locations
  108. Logging: Logging revision
  109. Database: Additional DB-Storage of Memberships in Course/Groups
  110. Competence Management: Usability Improvements in Competence Management
  111. IPE: Displaying of Accordions Successively
  112. Info Page: Revision of Info Page
  113. Repository and Categories: Disable Tree
  114. Language Handling: Multilingual Titles and Descriptions for All Object Types + Plugins
  115. UI: Object List in Container
  116. Learning Progress: Introduction of Individual Assessment
  117. Learning Progress: Learning Progress Settings link to Container
  118. Learning Progress: Learning Progress for Mediacasts
  119. Learning Progress: Learning Progress for file objects
  120. Metadata: Extend Custom Meta Data with Link-Type
  121. Support of OrgUnits in Courses and Groups
  122. Organisational Units - Organisational Units on Personal Desktop
  123. Development Support: Dependency Injection
  124. Online Help: Multilingual Support Online Help
  125. Online Help: Customizable Online Help Packages

4 Miscellaneous

  1. Autoloading: Postponed
  2. Registry pattern to get rid of global variables: Postponed
  3. Send as Mail with link to assignment: Postponed

Decision on Pull Requests from SIG Refactoring

  1. Dicto Rules https://github.com/ILIAS-eLearning/ILIAS/pull/32: Michael Jansen already merged the request.
  2. Whoops Error Handler https://github.com/ILIAS-eLearning/ILIAS/pull/33: The code is related to Stefan Meyers code. He will have a look at it and decide on the merge.

Re-Configuration of Mantis for New Bug Fixing Process

The current Mantis configuration knows the following values for the status of a bug report:

  • new
  • feedback
  • acknowledged
  • confirmed
  • assigned
  • resolved
  • closed
According to the concept of a revised bug fixing process as decided by the General Meeting of Members in Bern, the new process comes with the following values:
  • open: new value - substitutes "new"
  • feedback
  • postponed : new value - no equivalent
  • funding needed: new value - no equivalent
  • fixing acc. to priority: new value - no equivalent
  • resolved
  • closed
No change is required for all reports marked as feedback, resolved and closed. But how to proceed with all other bugs?
  1. Set all bugs marked as acknowledged, confirmed and assigned to assigned, delete acknowledged and confirmed and wait until all assigned bug reports have been resolved or closed, then delete assigned as well.
    • Advantages: clear distinction between old and new bug reports; no excessive demands to maintainers for managing bug reports
    • Disadvantages: Bugs with status assigned might never been closed or resolved due to number; Mantis interface offers a status that should no longer be used and lead therefore to irritations
  2. Set all bugs marked as acknowledged, confirmed and assigned to open and treat them as new made bug reports.
    • Advantages: no more outdated status values; Only new process is visualised
    • Disadvantage: hugh workload for developers as they have to check and assign every assigned bug report to one of the three new values - or close them.

The Jour Fixe decided that "Fixing acc. to priorisation" should become the default value for open but assigned bugs. The assignment of current values to the new concept should be as follows:

  • new -> open
  • feedback -> feedback
  • acknowledged -> fixing acc. priority
  • confirmed -> fixing acc. priority + flag reproduced by developer
  • assigned -> fixing acc. priority
  • resolved -> resolved
  • closed-> closed

Next Jour Fixe

Monday, June 22, 2015, from 12h30 until 17h30 at the office of ILIAS-Verein in Cologne

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