[Deploying Sakai] [Building Sakai] [Portfolio] OSP QA for Sakai 10

[Kirschner, Beth]

Hi Janice,

What I would propose is not stealthing the many OSP tools themselves, but disabling the portfolio site type. This would mean that existing portfolio sites  _could_ add OSP tools to existing sites, but users could _not_ create new portfolio sites in the default sakai distribution. Re-enabling the creation of portfolio sites would require a configuration change and re-deploy. Alternately, I believe that an admin user could simply change the site type in the Sites tool to convert newly created sites to portfolio sites.

I've written up the following JIRA for this -- I'd be happy to check it in if there is no objections or alternate proposals.
	https://jira.sakaiproject.org/browse/SAK-25587

- Beth

On Jan 22, 2014, at 4:22 AM, Adrian Fish <adrian.r.fish at gmail.com> wrote:

> You're right Neal. Site maintainers cannot see stealthed tools in the Site Info tool - they are just not available to be picked. As you correctly note, there is a Sakai property. This excerpt is from the default sakai.properties file ...
> 
> # STEALTH TOOLS
> # A stealth tool is a tool that is running in Sakai but is not available to be added to a site in Worksite Setup.
> # List any tools to be stealthed, using their tool ids, in a comma-separated string (no spaces).
> # In this example, the rwiki tool, su tool, roster tool, and the assignment tool w/o grading are stealthed:
> # stealthTools at org.sakaiproject.tool.api.ActiveToolManager=sakai.rwiki,sakai.su,sakai.site.roster,sakai.assignment
> # DEFAULT: none (No tools are stealthed)
> # stealthTools at org.sakaiproject.tool.api.ActiveToolManager=sakai.rwiki
> 
> You just modify the last line and uncomment it to alter the default, so if osp was in there, you'd just remove it and restart Tomcat. Stealthing affects all sites; it is not site specific.
> 
> Cheers,
> Adrian.
> 
> 
> On 21 January 2014 23:27, Neal Caidin <neal.caidin at apereo.org> wrote:
> Hi Janice,
> 
> This is a question for the dev list (or maybe production list, so I'm cc'ing both) to be sure. But I think the point of stealthing is that the owner of the site does not see the tool, so it would require an administrator to turn it on for that site or multiple sites. However, my understanding is also that it is extremely easy to unstealth a tool. So if your institution wants it unstealthed you just configure a property and restart Sakai. 
> 
> The devs will correct me if I'm wrong, I hope. 
> 
> Cheers,
> Neal
> 
> 
> 
> 
>> 	janice.smith	January 21, 2014 at 6:00 PM
>> Hi Neal
>> 
>> A question. Once the administrator adds the OSP tools to a Sakai instance, can each portfolio site owner in that instance of Sakai add the tools to any particular portfolio site? I sure hope so. Please let me know.
>> 
>> Janice
>> 
>> Janice A. Smith, Ph.D.
>> Three Canoes LLC
>> 1204 Laurel Avenue
>> Saint Paul, Minnesota 55104, USA
>> 651-642-9069, 207-841-6262 (cell)
>> janice.smith at threecanoes.com
>> http://threecanoes.com
>> 
>> 
>> ---- On Tue, 21 Jan 2014 07:03:02 -0600 Neal Caidin<neal.caidin at apereo.org> wrote ---- 
>> 
>> 
>> 	Neal Caidin	January 21, 2014 at 8:03 AM
>> Hi Janice,
>> 
>> There looks like there is momentum in the community for a proposal to stealth the OSP tool for Sakai 10. I'm wondering how this group feels about this? For those not familiar with the concept, a stealth tool is a tool that is running in Sakai, but is not available to be added to a site in Worksite Setup. It must be added to the site by an administrator. The thinking is that there is not enough commitment to maintaining and enhancing the OSP tool to keep it visible as a standard tool selection.
>> 
>> Thanks,
>> Neal
>> 
>> 
>> 
>> 
>> 	janice.smith	January 20, 2014 at 5:01 PM
>> Hello Neal (and OSP Community members),
>> 
>> The next OSP Community meeting is scheduled for 11 AM EST on Monday, February 3. I have placed an item on our agenda to discuss options for the QA of OSP items in Sakai 10.
>> 
>> So far, our agenda for the February OSP Community meeting is as follows:
>> 	• OSP QA for Sakai 10
>> 	• Update on the Karuta (new portfolio functionality from HEC Montréal) Apereo Incubation Proposal
>>  I hope the other members of the OSP Community will join me then.
>> 
>> Janice
>> 
>> Janice A. Smith, Ph.D.
>> Three Canoes LLC
>> 1204 Laurel Avenue
>> Saint Paul, Minnesota 55104, USA
>> 651-642-9069, 207-841-6262 (cell)
>> janice.smith at threecanoes.com
>> http://threecanoes.com
>> 
>> 
>> 
>> _______________________________________________
>> portfolio mailing list
>> portfolio at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/portfolio
>> 
>> TO UNSUBSCRIBE: send email to portfolio-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> 
> -- 
> Neal Caidin
> Sakai Community Coordinator
> Apereo Foundation
> neal.caidin at apereo.org
> Skype me! (but let me know in advance for the first interaction) - nealkdin
> 
> 
> _______________________________________________
> 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/production/attachments/20140122/49af07bc/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: compose-unknown-contact.jpg
Type: image/jpeg
Size: 770 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/production/attachments/20140122/49af07bc/attachment.jpg