ATTACHMENT_3_-_Data_Migration.docx

Attachment 3 – Data Migration Migrating Existing LMS Systems

General

1. Migration strategy options:

a. Migrate all courses and user accounts as is OR

b. Migrate/redesign courses to leverage new LMS functionality and start with a new Active Directory sync so we only have active/validated users

Courses

1. Courses in existing system shall be backed up without user data for restoration in new LMS. This shall be in standard Moodle .mbz format.

2. Moodle courses are containers for all activities associated with a course and can contain multiple instances of any of the following:

a. ACTIVITIES

i. Adaptive Quiz

ii. Advanced Forum

iii. Assignment

iv. Certificate

v. Chat

vi. Checklist

vii. Choice

viii. Database

ix. External tool

x. Flash Card Set

xi. Forum

xii. Glossary

xiii. HotPot

xiv. Journal

xv. Lesson

xvi. Questionnaire

xvii. Quiz

xviii. SCORM package

xix. Survey

xx. Wiki

xxi. Wiziq Live Class

xxii. Workshop

b. RESOURCES

i. Book

ii. File

iii. Folder

iv. IMS content package

v. Label

vi. Lightbox Gallery

vii. Page

viii. URL

3. Sample Course Excerpt

4. Question Bank & Dynamic Feedback Examples to the contractor solution shall allow for multiple question types and provide dynamic feedback to Peace Corps learners. Legacy question banks shall be transferable to the new system or will have to be rebuilt. A sample of question types available in the current system can be seen below.

Users

1. User accounts currently exist in two instances of Moodle (volunteer and staff).

a. Accounts include custom profile fields and it is anticipated that these and new custom fields will need to be created in the new system.

b. User accounts can be exported to a flat file for import into a new system, however, it may be preferable to use an integration with the PC Active Directory for account creation and maintenance in the new system.

c. In addition to the account and custom profile fields, to the solution shall include organizational and positional attributes such as (not inclusive):

i. Supervisor’s contact information

ii. Supervisor or Individual role

iii. Title

iv. Start date

v. Supervisor y/n

vi. Supervisor name (last, first)

vii. Supervisor email

viii. Entry on duty date

ix. Tour end date

x. Real position title

xi. Series (for USDH)

xii. Personal Service Contract (PSC) Y/N

xiii. Assigned office if HQ, e.g. OGO/OPATS/KLU

xiv. Status (active or not)

Data source

1. 2 instances of current externally hosted LMSs with separate user groups

Data size http://learning.peacecorps.gov <- volunteer LMS

Web directory Size: 659.30 MB Data directory Size: 10.46 GB Database name Size: 4.16 GB

Moodle release: 3.0.4 (Build: 20160509) ELIS release: 3.0.3.0 (Build: 20160509)

Number of users: 25182 Number of courses: 29 Number of plugins: Active: 230 Total instances: 13995 Number of config settings: 772 http://training.peacecorps.gov <- staff LMS

Web directory Size: 648.70 MB Data directory Size: 4.78 GB Database name Size: 2.10 GB

Moodle release: 3.0.4 (Build: 20160509) ELIS release: 3.0.3.0 (Build: 20160509)

Number of users: 8077 Number of courses: 53 Number of plugins: Active: 204 Total instances: 3374 Number of config settings: 771

Migration timeline All courses and data must be fully migrated for the final deployment eight (8) months after contract award. The Peace Corps anticipates that a pilot deployment (during soft-launch) will be required to populate the database with sufficient user data and 15-20 courses for user acceptance testing. This pilot deployment shall occur no later than five (5) months after contract award in accordance with SOO 2.4.3.

image1.png image2.png image3.png