Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-44325

External Tools should have options for placement in UI



    • Type: Feature Request
    • Status: OPEN
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 20.1
    • Fix Version/s: None
    • Labels:


      When LTI tools are defined as External Tools in the Administration Workspace, instructors need to scroll to the bottom of the screen in Site Info > Manage Tools and expand the External Tools in order to find them.

      This doesn't make sense for users, since they expect to find tools in alphabetical order in the main list. The collapsible list can be expanded through the use of a property (see SAK-30371), but then the UI presents two separate alphabetical lists to users – and generally, users don't care about the distinction between native tools and external tools.

      Also, some LTI tools (e.g. Hypothes.is) do not work as "sidebar tools" but instead work from within Lessons. It's difficult for users to know which tools in the External Tools list are "sidebar tools" or "Lessons tools" without an administrator providing appropriate textual descriptions for each tool.

      At our institution we've been registering LTI tools that work as "sidebar tools" using IMSBLTIportlet.xml in order to have them appear in the list of "native Sakai tools"; this makes the user experience better, since they have a single list of sidebar tools to choose from. Tools which only work in Lessons are NOT defined in IMSBLTIportlet.xml so that they only appear in External Tools.

      The placement of an LTI tool in the UI could be an option when defining a tool. This could potentially replace the option of whether or not a tool is stealthed, since the absence of a selection would effectively remove the tool from the UI.

        Gliffy Diagrams



              Issue Links



                  csev Charles Severance
                  hauerwas@providence.edu Adam Hauerwas
                  0 Vote for this issue
                  4 Start watching this issue



                      Git Integration