[#SAK-16419] Add the ability to create a site from a template within the Worksite Setup tool

Sakai

Add the ability to create a site from a template within the Worksite Setup tool

Created: 26-May-2009 03:19 Updated: 03-Feb-2010 10:45

Component/s:

Worksite Setup

Affects Version/s:

2.5.x

Fix Version/s:

2.7.0-b01

Time Tracking:

Not Specified

File Attachments:

chef_site-copy.vm (1 kB)
2.

SAK-16419.patch (6 kB)

Image Attachments:

1. copy_screen.jpg
(26 kB)

2. new_site_type.jpg
(33 kB)

3. site_templage.jpg
(87 kB)

Issue Links:

Depend

This issue is depended on by:

~~SAK-16859~~ site created with template doesn't carry over skin, description, etc

Relate

This issue relates to:

~~SAK-12868~~ Template Functionality for Sites

This issue is related to:

~~SAK-16774~~ Hide "Create Site From Template" choice when there is no template defined in the system

2.6.x Status:	None
2.5.x Status:	None
2.4.x Status:	None

Description

« Hide

Add the ability to create a site from a template within the Worksite Setup tool. By marking any site that you want to use as a template, via the 'Sites' admin tool, with a property called template set to true, we could make these sites available to be copied as new sites. Then, in the Worksite Setup tool we could add another option to the site type screen named 'from template' and if this were selected present a new screen from where to pick a template etc.

I've attached a patch for SiteAction and a velocity template that achieves this. I've also attached some screenshots of it in action.

All

Comments

Work Log

Change History

Subversion Commits

git Commits

Sort Order:

[ Permlink | « Hide ]

Peter A. Knoop added a comment - 26-May-2009 07:41

~~SAK-12868~~ describes current (2.6) implementation of templates.

[ Permlink | « Hide ]

Adrian Fish added a comment - 26-May-2009 08:56

To apply the patch copy it into your SAKAI_SRC/site-manage directory, cd into the site-manage directory and then execute 'patch -p0 < ~~SAK-16419~~.patch' from there.

You also need to copy chef_site-copy.vm into SAKAI_SRC/site-manage/site-manage-tool/tool/src/webapp/vm/sitesetup

[ Permlink | « Hide ]

Adrian Fish added a comment - 28-May-2009 02:51 - edited

I just replaced the chef-site_copy.vm template as I forgot to set the back index and the template-index.

[ Permlink | « Hide ]

Zhen Qian added a comment - 28-May-2009 05:27

Just FYI, here in umich, we are working on applying the patch with small UI changes. Will check back into trunk once finished.

[ Permlink | « Hide ]

Zhen Qian added a comment - 18-Jun-2009 13:15

r63854.

The features of recognizing template site by "template" property setting and site creation workflow changes are checked into trunk in r63854.

User is not allowed to specify site id. The site id will always remain as UUID. However user would be able to specify human readable site alias in Site Info tool after the site is created.

There are checkboxes for copy user and copy content. When selected, user and/or content from the template site would be copied into the newly created site.

[ Permlink | « Hide ]

Adrian Fish added a comment - 28-Jul-2009 09:03

Nice one Zhen. I like the UI and the copy content is cool.

Adrian.

[ Permlink | « Hide ]

Zhen Qian added a comment - 28-Jul-2009 09:18

Thanks, Adrian. All UI accolades goes to Gonzalo :)

[ Permlink | « Hide ]

Adrian Fish added a comment - 31-Jul-2009 04:01

NIce one Gonzalo as well :)

I've made a change to my 2.5 version where I've swapped the title field for a text area so you can copy and paste a list of site titles in. I needed to create multiple sites at once from one template. What do you reckon to getting that into your trunk code? It's a nice admin tweak.

Adrian.

[ Permlink | « Hide ]

Gonzalo Silverio added a comment - 31-Jul-2009 11:22

Thanks Adrian.

We have discussed your suggestion. If we could restrict that functionality to a role equivalent to dept or school administrator or something of that nature - like the person in charge of creating all the sites for one unit, then your addition would be incredibly useful across the board. Otherwise it would just be useful to environments where course creation is carried out by admins, no?

I would hesitate to put this functionality in front of normal users, in any case.

So in a few words, we either need to enable that role or be able to disable that functionality. A third option would be to surface the template functionality in the Admin Workspace/Sites tool where it would be nicely quarantined.

[ Permlink | « Hide ]

Adrian Fish added a comment - 19-Oct-2009 14:59

What are the odds of this getting merged into trunk? Any idea?

[ Permlink | « Hide ]

Zhen Qian added a comment - 03-Feb-2010 10:45

verified fix on QA3 server, sakai-2.7.0-b01