Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-33995

Roll-Up Jira for Import from Site, Duplicate and CourseSite creation from template

    Details

    • Test Plan:
      Hide

      Generic test:
      Create a site which will become your base/clone or template to copy as the starting point for other sites.

      1. In Administration Workspace > Sites: Create a new site in which the Site ID and the title are identical.
      2. Add at least one page with the Site Info tool on it.
      3. Now you can use Worksite Setup to add the rest of the tools you'd like to test.

      Determine which method you will use to copy with:
      A. Duplicate
      B. Import from Site
      C. Create a new shell in Worksite Setup, and choose "Re-use from Site" during setup

      (Your results will likely apply to backend processes as well in which the SIS files you send create your course shells based on a course site identified in the scripting process as your "template" from which settings, tool set etc are copied).

      Unexpected Results from Notre Dame's 11.4 instance:
      Default Toolset: LTI tools do not copy.
      Lessons which contains pre-configured content: Lessons are empty.
      Resources, LB-CSS folder copies, with the file(s) in it, but they are not applied to the Lesson copy
      Course Site Icon: Site Info > Edit Site Information > Icon URL (appears above the default toolset)
      Email Archive: (Duplicated version)No longer offers the ability to edit/change the email address.
      Web Content: References to internal URLs (html file in resources, for example)

       

      Show
      Generic test: Create a site which will become your base/clone or template to copy as the starting point for other sites. In Administration Workspace > Sites: Create a new site in which the Site ID and the title are identical. Add at least one page with the Site Info tool on it. Now you can use Worksite Setup to add the rest of the tools you'd like to test. Determine which method you will use to copy with: A. Duplicate B. Import from Site C. Create a new shell in Worksite Setup, and choose "Re-use from Site" during setup (Your results will likely apply to backend processes as well in which the SIS files you send create your course shells based on a course site identified in the scripting process as your "template" from which settings, tool set etc are copied). Unexpected Results from Notre Dame's 11.4 instance: Default Toolset: LTI tools do not copy. Lessons which contains pre-configured content: Lessons are empty. Resources , LB-CSS folder copies, with the file(s) in it, but they are not applied to the Lesson copy Course Site Icon : Site Info > Edit Site Information > Icon URL (appears above the default toolset) Email Archive : (Duplicated version)No longer offers the ability to edit/change the email address. Web Content: References to internal URLs (html file in resources, for example)  

      Description

      Community members are coalescing around these requirements

      Project Goals are here

      Two Issues:

      1. Duplicate and Import from Site should use the same behind the scenes method. I surmise they don't because results vary.
      2. A more and more common Use Case where site creation thru the use of templates is automated via script (Longsight uses this technique, for example), is hindered because of:
        1. Performance Issues
        2. Some content does not copy to the new site(s), such as:
          1. Fully configured LTI links (which existed in the 'template')
          2. Associations between Lessons css and the file in Resources
        3. Testing in both 11.4 and 12 RC05 indicates 12.x RC05 has fewer copying issues but more performance issues (upsidedown sakaiger).

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  lgekeler Laura Gekeler
                • Votes:
                  4 Vote for this issue
                  Watchers:
                  15 Start watching this issue

                  Dates

                  • Created:
                    Updated:

                    Git Source Code