[sakai-pmc] Sakai support for better OOTB integration with uPortal

[Matthew Jones]

Looks like some old historical (1.x) way of naming things based on
celestial bodies. I'm happy with making the names make sense since we never
called it Charon portal to anybody anyway.


   - The protocol between the aggregation layer and the tools was cleaned
   up and fully documented.    The new default aggregator was called Charon
   and maintained the Varuna ability to use iFrames for portal integration.
   Sakai also shipped with a second portal called Mercury that was much
   simpler than Charon and intended for use by developers during tool
   development.

http://www-personal.umich.edu/~csev/papers/2006/2006_07_arch_history_v02.doc<http://www-personal.umich.edu/~csev/papers/2006/2006_07_mellon_final_interim.pdf>


On Wed, Oct 9, 2013 at 7:58 AM, Steve Swinsburg
<steve.swinsburg at gmail.com>wrote:

> It will be done in the sample data load activated on sakai.demo=true
>
> https://jira.sakaiproject.org/browse/SAK-25267
>
> I've also created a Jira to move the mercury site into the demo load and
> remove from normal build - that was suggested before. No one knows what
> mercury is and why its not called 'test site'... Comments in the ticket:
> https://jira.sakaiproject.org/browse/SAK-25268
>
>
>
> On Wed, Oct 9, 2013 at 3:01 AM, Aaron Zeckoski <azeckoski at vt.edu> wrote:
>
>> Is there a jira for this? How would the change be implemented?
>> On Sep 27, 2013 2:51 AM, "Steve Swinsburg" <steve.swinsburg at gmail.com>
>> wrote:
>>
>>> Hello
>>>
>>> The Sakai Connector Portlet has passed the Jasig/Apereo incubation
>>> process and is in the midst of being incorporated into the next uPortal
>>> release.
>>>
>>> This portlet uses the trusted mode of the Basic LTI support in Sakai to
>>> allow a user with the same username in both systems to embed tools from
>>> their Sakai sites inside uPortal.
>>>
>>> Sakai currently has LTI configuration in the experimental sakai props to
>>> support this, ie the demo of uPortal hooks up to the Sakai experimental
>>> server.
>>>
>>> It so happens that uPortal ships with an admin user so for that user the
>>> OOTB experience works fine. However uPortal also ships with two other demo
>>> users called student and faculty. These have no equivalent in Sakai so the
>>> demo does not work for those users. These users are important in
>>> demonstrating the various layouts and portlet that uPortal offers.
>>>
>>> What I propose is that these two users are added to Sakai by default.
>>> The student would be an access user in mercury, the faculty would be a
>>> maintain user.
>>>
>>> This also ties in with my earlier emails of providing a better OOTB
>>> experience for Sakai.
>>>
>>> Please reply with any comments or concerns. I would like to get this in
>>> as soon as I can if there are no objections.
>>>
>>> Regards
>>> Steve
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> sent from mobile device
>>>
>>> _______________________________________________
>>> sakai-pmc mailing list
>>> sakai-pmc at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
>>>
>>>
>
> _______________________________________________
> sakai-pmc mailing list
> sakai-pmc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-pmc
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-pmc/attachments/20131009/43711099/attachment-0001.html