[Deploying Sakai] [Building Sakai] Creating new course types

[Tom Hall]

Thanks everyone.  I think this is the solution.  I'll let you know.

Tom

On 2/17/2011 3:05 PM, Matthew Jones wrote:
> Agreed, this was part of the current (and past) University of Michigan 
> CTools deployment process. The current process uses a xslt to 
> transform the tool registrations to add categories that are custom to 
> CTools (mostly for gradtools).
>
> The transform is here
> https://source.sakaiproject.org/svn/msub/umich.edu/ctools/ctools-buildscripts/groovybuild/xslt/fixcategory.xslt
>
> It has a dependency on verb.xsl also in that same directory for 
> removing categories. (For correctly commenting out the xml, couldn't 
> figure it out without this mode)
>
> Assiuming xalan and serializers are in $LIBDIR 
> (http://www.ibiblio.org/maven/xalan/jars/) you'd run it with something 
> like this
> java -cp $LIBDIR/xalan-2.7.1.jar:$LIBDIR/serializer-2.7.1.jar org.apache.xalan.xslt.Process -PARAM 'category.add' 'adhoc' -XSL fixcategory.xslt -IN sakai.resources.xml
> You'd have to put this in a 'find . -name "*.xml" | xargs . . . ' to 
> find all of the xmls files but it should work out. I'm not 100% sure 
> as the build process uses groovy to recurse through the xml files 
> looking for matches to transform.
>
> https://source.sakaiproject.org/svn/msub/umich.edu/ctools/ctools-buildscripts/groovybuild/src/main/groovy/edu/umich/ctools/Builder.groovy
>
> -Matthew
>
> On Thu, Feb 17, 2011 at 2:46 PM, Anand Mehta <anand.mehta at yahoo.com 
> <mailto:anand.mehta at yahoo.com>> wrote:
>
>     Hi Tom,
>
>     You probably have to add that site type to each tool's
>     registration file. Please see slides 6-17 here:
>     http://www.slideshare.net/jleasiaum/configuring-sakai-boston09.
>     You should also duplicate !group.template.course for group
>     permissions.
>     Thanks,
>     Anand
>
>
>     ------------------------------------------------------------------------
>     *From:* Tom Hall <thall at brocku.ca <mailto:thall at brocku.ca>>
>     *To:* sakai-dev Developers <sakai-dev at collab.sakaiproject.org
>     <mailto:sakai-dev at collab.sakaiproject.org>>;
>     "production at collab.sakaiproject.org
>     <mailto:production at collab.sakaiproject.org>"
>     <production at collab.sakaiproject.org
>     <mailto:production at collab.sakaiproject.org>>
>     *Sent:* Thu, February 17, 2011 1:27:36 PM
>     *Subject:* [Deploying Sakai] Creating new course types
>
>     Hi everyone
>
>     We need to create an additional site type with the same roles as our
>     'course' type.  The difference between the two site types is to be
>     that
>     'course' will not allow the join functionality while the new type
>     'adhoc' will.  I created a copy of the !site.template.course as
>     !site.template.adhoc (using the 'save as' operation from
>     !site.tempate.course.
>
>     We are able to create sites and everything appears to be OK until an
>     attempt is made to add tools via the site Info tool and selecting
>     Edit
>     Tools.  The list of tools appears and can be selected.  Pressing the
>     Continue button produces a list of tools which only includes Home
>     (sakai.iframe.site) rather than the complete list of existing tools
>     added during the creation process (via web service calls) and the new
>     ones added via the web page.  Clicking the finish button results
>     in all
>     tools being removed from the site.  It also appears that the page
>     property 'is_home_page' is not being added to the 'Home'
>     (sakai.iframe.site) tool via the web service.  The web service calls
>     being used are the same ones that we use to create our course
>     sites with
>     the site type set accordingly.
>
>     Does anyone have any suggestions?
>
>     Thanks
>
>     Tom
>     _______________________________________________
>     production mailing list
>     production at collab.sakaiproject.org
>     <mailto:production at collab.sakaiproject.org>
>     http://collab.sakaiproject.org/mailman/listinfo/production
>
>     TO UNSUBSCRIBE: send email to
>     production-unsubscribe at collab.sakaiproject.org
>     <mailto:production-unsubscribe at collab.sakaiproject.org> with a
>     subject of "unsubscribe"
>
>
>     _______________________________________________
>     sakai-dev mailing list
>     sakai-dev at collab.sakaiproject.org
>     <mailto: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
>     <mailto: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/20110218/f48a578e/attachment.html