{"id":325,"date":"2019-04-07T19:36:32","date_gmt":"2019-04-07T19:36:32","guid":{"rendered":"http:\/\/llama.scholar360.com\/?page_id=325"},"modified":"2019-04-24T14:01:50","modified_gmt":"2019-04-24T14:01:50","slug":"mothership-learning","status":"publish","type":"page","link":"https:\/\/edvance360.com\/lms\/mothership-learning\/","title":{"rendered":"Mothership Learning"},"content":{"rendered":"\n
\n
\n

Mothership Project<\/h3>\n

Essentially, the Mothership Project is a high-level LMS that doubles as a central course catalog. Multiple second-level LMS iterations (for each client\/sub-site) are tied to this top-level LMS (i.e., the Mothership). Then via common cartridge imports\/exports, the Mothership LMS exports course cartridges into each second-level LMS (client\/subsite). This capability provides clients with a central course catalog through which they can easily distribute and manage content and associated Learning Outcomes across their multiple clients\/sub-sites. Each sub-site has their own unique LMS site\u2013their own brand\/ logo, etc. There would be no difference for the administrators or users at these second-level learning management system sites. The course content is simply controlled at the top level and then synced up with the second-level learning management system sites for each client\/sub-site.<\/p><\/div>\n\n

\n
\nDashboard<\/strong>\n\n

Mothership LMS<\/p>\n<\/div>\n<\/div>\n\n

 <\/div>\n<\/div>\n\n\n\n
\n
\n
Push content to client\/sub-site<\/div>\n\n
Set global settings and permissions<\/div>\n\n
 <\/div>\n<\/div>\n\n
 <\/div>\n<\/div>\n\n\n\n
\n
\n
\n
Client Site<\/strong>\n\n

Secondary LMS<\/p>\n<\/div>\n<\/div>\n\n

\n

Independent of all other clients<\/p>\n\n

(separate DB, Users, and Content)<\/i><\/p>\n<\/div>\n\n

\n
Client Site<\/strong>\n\n

Secondary LMS<\/p>\n<\/div>\n<\/div>\n<\/div>\n\n

This Mothership functionality may be particularly relevant to businesses, programs, or companies that have the need to report on and manage Learning Outcomes\/Objectives, provide accountability in the form of reports and course management, and other administrative functions. These entities would seemingly significantly benefit from a customized solution that had a network comprised of several learning management systems, rather than just one learning management system on which all clients are served. The flexibility provided with the Mothership solution enables you to tailor each LMS to its local context.<\/p><\/div>\n\n

 <\/div>\n<\/div>\n\n\n\n
\n
\n
\n
\n

Mothership Process<\/h2>\n\n
    \n\t
  • Course Created in Client\/Sub-site Account<\/li>\n\t
  • Course shows in SuperAdmin Dashboard. Browse-able by selecting a Client\/Sub-site, then listing courses after selecting the Term<\/li>\n\t
  • SuperAdmin selects Bundles or Courses* and pushes to Client sub-site. If client sub-site already has the course, the # of licenses are added to any existing licenses they have<\/li>\n\t
  • Nested \u2018Bundles\u2019 can be created. Courses may be added to any bundle<\/li>\n\t
  • Cart is created in the background and imported to the Dashboard Cart Repository. Course is listed in the Dashboard by Category, with a hidden relation to the cart<\/li>\n\t
  • Client administrator can now see the course(s). They can assign a course to any facilitator by selecting a Term and then a facilitator<\/li>\n\t
  • In the background, the original Cart in the Dashboard repository is unpacked and the course is created. Course setup is complete<\/li>\n\t
  • Each time a user is enrolled in a course, it subtracts from the purchased licenses<\/li>\n<\/ul>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n
    \n\t
    \n\t\t

    Mothership Overview<\/h1><\/center>\n\n