Version 2 (modified by dlewis, 10 years ago) (diff)


Using the Admin system with TNG

The new-generation TNG LMS servers are now in production use for over 200 districts in the 2009-2010 academic year.

During the transition of our districts to the new LMS, we are continuing to support the Agile Assessment (AA) service based on an earlier server techology and database implementation. To bridge between the LMS and AA facilities, we are using a hybrid strategy in the near term to continue providing Support services through the existing Agile Mind Admin system ( to manage district and school configurations and manage classes and enrollments.

System Overview and Workflow Timelines

There are 3 principal elements in our current system for supporting TNG operations:

  1. the Admin system and its district databases for managing districts, classes, enrollments, etc
  1. the TNG LMS servers and their databases
  1. the TNG warehouse database that supports Admin usage reports

The workflow and data flow forward through these three system elements with nightly maintenance updates to push data and changes through the system. The current nightly sync process means that in some cases there are delays between when something happens and when it shows up on a LMS:

  • changes to schools, districts, classes, user accounts, and enrollment made on the Admin system are synced nightly and are available on the LMS the next day
  • LMS data with participant updates and user usage activity data are synced nightly to the TNG warehouse and available for Admin usage reports the next day

Note that these two distinct date sync stages mean that changes in classes and user accounts will not be available on the warehouse Admin reports until the second day after changes are entered on the Admin system.