Hackfest UK 2014/LTI: Difference between revisions
From MoodleDocs
No edit summary |
(→Code) |
||
(4 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
= LTI Usability improvements | |||
== LTI Usability improvements == | |||
This session is about exploring how to improve the use of external (LTI) tools in Moodle. | This session is about exploring how to improve the use of external (LTI) tools in Moodle. | ||
Participants | === Participants === | ||
* Michael Aherne, University of Strathclyde | |||
* Michael Aherne | * Michael Hughes, University of Strathclyde | ||
* Michael Hughes | * John Tutchings, Coventry University | ||
* John Tutchings | * Stephen Vickers, IMS Global | ||
Rationale | === Rationale === | ||
* Usability: enable instructors to more easily find external tools, particularly for high-profile / heavily-used tools (such as Turnitin) | * Usability: enable instructors to more easily find external tools, particularly for high-profile / heavily-used tools (such as Turnitin) | ||
* Usability: enable instructors to customise list of tools in activity chooser | * Usability: enable instructors to customise list of tools in activity chooser | ||
Requirements | === Requirements === | ||
# Tools can be defined by admins and appear as activities in the activity chooser | # Tools can be defined by admins and appear as activities in the activity chooser | ||
Line 23: | Line 24: | ||
# Tools should be able to be set up as activity or resource | # Tools should be able to be set up as activity or resource | ||
Suggestions | === Suggestions === | ||
# Ability to mark admin-set tools as "to be shown in activity chooser" (and show them) | # Ability to mark admin-set tools as "to be shown in activity chooser" (and show them) | ||
# Ability for plugins to dynamically define capabilities so that these LTI tools can be given their own "addinstance" capability | # Ability for plugins to dynamically define capabilities so that these LTI tools can be given their own "addinstance" capability | ||
# Ability for users to define which activities are available in a course (not just LTI tools - this would be a new general Moodle feature) | # Ability for users to define which activities are available in a course (not just LTI tools - this would be a new general Moodle feature) | ||
=== Questions === | |||
# Module sub-types are marked in the code as "legacy" and there is a strong suggestion that they aren't used. Why? ([https://github.com/moodle/moodle/blob/master/course/lib.php#L1281|"// NOTE: this is legacy stuff, module subtypes are very strongly discouraged!!"] in /course/lib.php) | |||
# Dynamic properties (i.e. created / controlled by module code, not pre-defined in access.php) - is this a reasonable proposal? | |||
=== Code === | |||
A proof-of-concept patch to dynamically show LTI tools in the activity chooser (as sub-types of "External Tool" - second best to being shown at top level) was developed during the hackfest: [https://github.com/mhughes2k/moodle/compare/LTI_HACKFEST] | |||
===Interesting Tracker issues=== | |||
# [https://tracker.moodle.org/browse/MDL-40899 Enable teachers to add (read config.xml uri) tools from the edu-apps.org LTI catalog] MDL-40899 |
Latest revision as of 15:21, 17 April 2014
LTI Usability improvements
This session is about exploring how to improve the use of external (LTI) tools in Moodle.
Participants
- Michael Aherne, University of Strathclyde
- Michael Hughes, University of Strathclyde
- John Tutchings, Coventry University
- Stephen Vickers, IMS Global
Rationale
- Usability: enable instructors to more easily find external tools, particularly for high-profile / heavily-used tools (such as Turnitin)
- Usability: enable instructors to customise list of tools in activity chooser
Requirements
- Tools can be defined by admins and appear as activities in the activity chooser
- It would be a good start to have these appear as subtypes of "External tool"
- Ideally, it should be possible to allows tools to appear as top-level activities.
- Ability to add these specific LTI tools to a course should be controllable by admins (currently anyone with LTI addinstance capability can add any tool)
- Tools should be able to be set up as activity or resource
Suggestions
- Ability to mark admin-set tools as "to be shown in activity chooser" (and show them)
- Ability for plugins to dynamically define capabilities so that these LTI tools can be given their own "addinstance" capability
- Ability for users to define which activities are available in a course (not just LTI tools - this would be a new general Moodle feature)
Questions
- Module sub-types are marked in the code as "legacy" and there is a strong suggestion that they aren't used. Why? ("// NOTE: this is legacy stuff, module subtypes are very strongly discouraged!!" in /course/lib.php)
- Dynamic properties (i.e. created / controlled by module code, not pre-defined in access.php) - is this a reasonable proposal?
Code
A proof-of-concept patch to dynamically show LTI tools in the activity chooser (as sub-types of "External Tool" - second best to being shown at top level) was developed during the hackfest: [1]