[Building Sakai] LTI ease of use

Wed Nov 21 01:30:18 PST 2012

I think it should be switchable in config. A tutor shouldn't really have to
make a decision on whether to trust a Sakai tool based on the fact that it
is 'external'. Plenty of contrib tools are flaky, should we mark them in
some way? If we could hide the fact that LTI tools are external in the
props then everybody's happy.

Cheers,
Adrian.

On 21 November 2012 01:29, Neal Caidin <nealcaidin at sakaifoundation.org>wrote:

> As long as individual institutions can label and group things the way they
> want, I think it will work well.
>
> -- Neal
>
> On Nov 20, 2012, at 8:23 PM, Steve Swinsburg <steve.swinsburg at gmail.com>
> wrote:
>
> I think having a note about them being external is useful, but having them
> on a separate page is not.
> The tool categories should provide this grouping ability.
>
> cheers,
> Steve
>
>
> On 21/11/2012, at 5:26 AM, Matthew Jones <matthew at longsight.com> wrote:
>
> Yea, I think it's very useful to make it clear to the person adding the
> tool that those external tools are not part of the system, may not be as
> reliable as the internal tools, and may not have the same features. There
> is generally very different (or no) support for those tools, as compared to
> internally available tools.
>
> I remember a number of instances when external services were down and we
> got many support requests. Since these were often free services with no
> SLA, there was essentially nothing we could do, and this is useful to make
> clear for those who might depend on it separately.
>
> After tool categories are fully implemented, it would likely be up to the
> local institutions which categories they put them in, either the same
> categories as regular internal tools or some new separate categories.
>
>
> On Tue, Nov 20, 2012 at 12:55 PM, Neal Caidin <
> nealcaidin at sakaifoundation.org> wrote:
>
>> +1 . The concept of LTI tools being exposed in Sakai sites after they are
>> configured, as the tools that they represent, sounds great, though I'm not
>> sure if it is important to visually separate as "External Tools".  In my
>> experience, users don't care if a tool is internal or external, local or
>> hosted. They mostly care that the tool works and with implicit assumptions
>> that their data is safe and backed up, and the the tool and information are
>> secure.  2 pennies.
>>
>> It does matter, of course, to support folks, system admins, and others
>> who maintain systems to know which are external vs internal.
>>
>> -- Neal
>>
>> On Nov 20, 2012, at 11:34 AM, Adam Marshall <adam.marshall at it.ox.ac.uk>
>> wrote:
>>
>>  Ah I wondered what you were on about!****
>>
>> What a good idea.****
>>
>> adam****
>>
>> *From:* Adrian Fish [mailto:adrian.r.fish at gmail.com]
>> *Sent:* 20 November 2012 13:53
>> *To:* Adam Marshall
>> *Cc:* sakai-dev
>> *Subject:* Re: [Building Sakai] LTI ease of use****
>> ** **
>> 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"
>>
>>
>>
>> _______________________________________________
>> 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"
>>
>
> _______________________________________________
> 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"
>
>
>
>
> _______________________________________________
> 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/20121121/07c96ffe/attachment.html 