[Building Sakai] lti and copying sites

[Raymond Naseef]

Hi All,

Here are some thoughts, hope they do not confuse things.

1) Is "EntityTranserer" actually "EntityTransferer"? Transfer is "someone
who transfers something".  I am unaware of word "transerer".

2) One thing that could be used for sending parameters, such as original
site's ID, to LTI would be to use custom parameters.  That may be a good
method, as each LTI and new site may have different requirements to
duplicate.

For example, with LTI for Google Drive, it is associating an existing
Google Drive folder tree with a site.  That same folder tree could be
associated with multiple sites.  That may be improper in some cases, as
each site may need to be able to modify the resources independently,
without affecting others (i.e., I do not want to know that Jane changed the
name of the Google Document, and do not want Jane to see my changes).

-Ray


On Thu, May 30, 2013 at 6:10 PM, John Bush <john.bush at rsmart.com> wrote:

> but how would you do that without something in LTI that supports it?
> Your only mechanism to communicate with an external tool is during
> launch.
>
> On Thu, May 30, 2013 at 1:52 PM, Zhen Qian <zqian at umich.edu> wrote:
> > Well, there is currently no property in new site pointing back to old
> site.
> >
> > I think the producer should have done the lti tool clone during the site
> > dupl time, not when the new site is first accessed.
> >
> > - Zhen
> >
> >
> > On Thu, May 30, 2013 at 4:41 PM, John Bush <john.bush at rsmart.com> wrote:
> >>
> >> hmm, that's interesting.  So for example, you could make a new
> >> EntityTranserer impl that simply stores what site a site was copied
> >> from as a site property or something (I'm not sure that's stored
> >> anywhere already is it?), and then when you do the launch pass the
> >> original context id thru the payload.  Then it would be up to the
> >> producer to do whatever it needs to do to clone its own content based
> >> on the original context id.  For the use case I'm thinking of that
> >> might work, and sounds pretty easy.
> >>
> >> On Thu, May 30, 2013 at 10:58 AM, Zhen Qian <zqian at umich.edu> wrote:
> >> > I believe to have entities copied along with site duplication, the
> >> > EntityTranserer interface needs to be implemented, especially the
> >> > transferEntities() function inside it.
> >> >
> >> > I am not aware of such implementation inside basiclti project. But I
> >> > imagine
> >> > this could be done, like adding new LTIContent objects, with some
> >> > existing
> >> > LTI tool attributes?
> >> >
> >> > Thanks,
> >> > - Zhen
> >> >
> >> >
> >> > On Thu, May 30, 2013 at 1:21 PM, John Bush <john.bush at rsmart.com>
> wrote:
> >> >>
> >> >> Has there been any traction in the LTI space about how to deal with
> >> >> duplicating sites?  It seems it would be helpful to have some sort of
> >> >> arrangement by which the consumer could be notified when a site is
> >> >> copied to be able to duplicate content if appropriate.  I'm not sure
> >> >> how this arrangement is best negotiated, and wondering if its ever
> >> >> been thought about ?
> >> >>
> >> >> --
> >> >> John Bush
> >> >> 602-490-0470
> >> >> _______________________________________________
> >> >> 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"
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> John Bush
> >> 602-490-0470
> >
> >
>
>
>
> --
> John Bush
> 602-490-0470
> _______________________________________________
> 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/20130530/8b186a1f/attachment.html