[Building Sakai] LTI ease of use

Adrian Fish adrian.r.fish at gmail.com
Tue Nov 20 07:18:19 PST 2012


Your knowledge of Sakai JIRAs is encyclopaedic. I salute you.

Thanks. I don't suppose there are any plans to backport SAK-22108 to 2.9.x?
It's a real nice to have ...

Cheers,
Adrian.


On 20 November 2012 14:59, Matthew Jones <matthew at longsight.com> wrote:

> SAK-22108 is implemented in trunk to do what you describe, though
> SAK-16600 is an extension of this to clean up that entire page since
> there's way too many tools.
>
> Having an extra button was just the fastest way to get in in there (
> SAK-20899).
>
>
> On Tue, Nov 20, 2012 at 9:50 AM, Adrian Fish <adrian.r.fish at gmail.com>wrote:
>
>> Ah, I've woken up now. It was in site info as an extra menu item. I still
>> think it would be nicer to just have them appear in the standard tools pick
>> list among the other tools. Why even declare them to be external?
>>
>> Is anybody looking at these at the minute?
>>
>> Cheers,
>> Adrian.
>>
>>
>> On 20 November 2012 14:39, Matthew Jones <matthew at longsight.com> wrote:
>>
>>> Yea, some of it is *in* 2.9.x but hidden by (SAK-21763) because BLTI-142
>>> isn't in until BasicLTI 2.1 (currently trunk). 2.9.x is using 2.0 BasicLTI.
>>> There was just some usability issues with the workflow as described in that
>>> jira.
>>>
>>>
>>> On Tue, Nov 20, 2012 at 9:36 AM, Adrian Fish <adrian.r.fish at gmail.com>wrote:
>>>
>>>> It's in 2.9.x as well, I think. You can add the 'External Tools' tool
>>>> to the admin site via the Sites tool and then precan tools for Lessons to
>>>> pick up. I'll have a look at those JIRAs, but I think it's actually in
>>>> already.
>>>>
>>>>
>>>> On 20 November 2012 14:28, Matthew Jones <matthew at longsight.com> wrote:
>>>>
>>>>> Hi Adrian,
>>>>>
>>>>> This sounds like the Basic LTI Admin tool that Dr. Chuck and Zhen
>>>>> worked on in
>>>>> https://jira.sakaiproject.org/browse/BLTI-121
>>>>>
>>>>> This was something that was in development from last year targeted for
>>>>> 2.9, but usability issues and other bugs caused it to be removed. There
>>>>> were options so that either only pre-configured tools (that an admin added)
>>>>> could be added by instructors or to allow instructors to configure and add
>>>>> their own individual.
>>>>>
>>>>> Some additional work was done that *looks* to put it back on track for
>>>>> a later 2.9 or at least a 2.10 release.
>>>>> https://jira.sakaiproject.org/browse/BLTI-142
>>>>>
>>>>> Would probably want some additional feedback from Michigan as it looks
>>>>> like they've got it in their build and did most (all?) of the work on it.
>>>>> On trunk, it's already in site info as "External Tools" or you can add the
>>>>> tool (sakai.basiclti.admin) to some site. I don't *think* these tools
>>>>> actually appear in the regular list of tools yet, though Michigan is doing
>>>>> a lot of work on the tool selection process too in SAK-16600.
>>>>>
>>>>>
>>>>> On Tue, Nov 20, 2012 at 8:52 AM, Adrian Fish <adrian.r.fish at gmail.com>wrote:
>>>>>
>>>>>> That's what I meant. Sakai admins precan the LTI tool and site
>>>>>> maintainers can just add them as any other tool, with no config whatsoever.
>>>>>> Maybe they shouldn't even know that it is an external tool they are adding.
>>>>>> That's the way Lessons does it, although they are still called External
>>>>>> tools in the more tools dropdown.
>>>>>>
>>>>>> Cheers,
>>>>>> Adrian.
>>>>>>
>>>>>>
>>>>>> On 20 November 2012 12:34, Adam Marshall <adam.marshall at it.ox.ac.uk>wrote:
>>>>>>
>>>>>>>  One problem with allow user full control over setting up LTI
>>>>>>> ‘tools’ is that they may link to unscrupulous systems that do nasty things
>>>>>>> with the information that they are handed. We have taken the opinion that
>>>>>>> it is a necessary evil for us admins to set up the LTI tool instances so we
>>>>>>> can do basic vetting.****
>>>>>>>
>>>>>>> ** **
>>>>>>>
>>>>>>> We don’t really have any set rules about how to decide whether a
>>>>>>> target LTI-enable application is trustworthy or not, a basic google search
>>>>>>> is about as probing as we get, but we are aware that there is a potential
>>>>>>> issue in this area.****
>>>>>>>
>>>>>>> ** **
>>>>>>>
>>>>>>> adam****
>>>>>>>
>>>>>>> ** **
>>>>>>>
>>>>>>> *From:* sakai-dev-bounces at collab.sakaiproject.org [mailto:
>>>>>>> sakai-dev-bounces at collab.sakaiproject.org] *On Behalf Of *Adrian
>>>>>>> Fish
>>>>>>> *Sent:* 20 November 2012 11:45
>>>>>>> *To:* sakai-dev
>>>>>>> *Subject:* [Building Sakai] LTI ease of use****
>>>>>>>
>>>>>>> ** **
>>>>>>>
>>>>>>> Is there a way of showing the configured LTI tools in the Site Info
>>>>>>> tool list, under the configured name? For instance, Panopto as 'Lecture
>>>>>>> Videos'?****
>>>>>>>
>>>>>>> ** **
>>>>>>>
>>>>>>> I know you view lti tools by configured name in Lessons but it would
>>>>>>> be good to just be able to add it as any other tool with zero
>>>>>>> configuration. The way the consumer currently works is the same as core
>>>>>>> Moodle's, unless I'm barking up the wrong tree, and will eventually just
>>>>>>> generate lots of load on Sakai admins as they add Basic LTI tools to sites.
>>>>>>> Basiclti4moodle makes things a lot easier as staff can just pick the
>>>>>>> activity as any other.****
>>>>>>>
>>>>>>> ** **
>>>>>>>
>>>>>>> I can imagine this being a fair bit of work but it needs to happen
>>>>>>> if Sakai's going to be a serious consumer of LTI providers.****
>>>>>>>
>>>>>>> ** **
>>>>>>>
>>>>>>> Am I missing something?****
>>>>>>>
>>>>>>> ** **
>>>>>>>
>>>>>>> Cheers,****
>>>>>>>
>>>>>>> Adrian.****
>>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> sakai-dev mailing list
>>>>>> sakai-dev at collab.sakaiproject.org
>>>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>>>>
>>>>>> TO UNSUBSCRIBE: send email to
>>>>>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>>>>>> "unsubscribe"
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20121120/d2932299/attachment.html 


More information about the sakai-dev mailing list