Version 3 (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 data 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.

General Principles for TNG-Admin Syncing

In designing the new LMS system, changes and improvements were made in the underlying database design to better position our systems to provide evolving capabilities and future improvements. Some of these changes have an effect on how the systems behave and are useful to understand in order to work more effectively with the Admin system.

Managing Users

The new LMS has a stronger model of the people in a district who comprise the population of teachers, students, administrators, and staff engaged in learning activities. This enables improved reporting and analysis, but means that care must be taken when performing certain operations on the Admin system so that the system is able to follow a person when changes are made such as what school they are enrolled in, what classes they are in, etc.

Classes and Academic Years

The new LMS has a stronger notion of academic year as a means of organizing and managing district activities. In particular, classes are marked with the academic year they belong in and this information affects the visibility (or not) of classes on the LMS and in warehouse reports.

The current academic year is ay0809. Managing the AY value on classes is not directly exposed through the Admin system - it is handled automatically by LMS configuration and syncing tools.

Common Admin Activities

###TODO: describe convention for expiring a class

###TODO: describe ....??