iMIS provides the ability to perform a one time migration of Desktop Certification data to the web. This migration will allow you to transfer any certification programs from your old style into the new certification programs.
From the Staff site, navigate to iMIS_URL/Staff/iMIS/CertificationManagement/MigrateLegacyCertification.aspx. You must be logged in as a SysAdmin user to access this content record. After clicking Migrate legacy certification, the migration will run in the background even if you navigate away from the page. This process may take several minutes or hours depending on the volume of existing certification data that is being migrated. Occasionally check the MigrateLegacyCertification.aspx page to verify if the process has completed and if any errors or warnings were encountered during the migration. If the migration process is interrupted, a button will be available to resume the process.
First migrate your data on a test database to verify no errors were encountered. The migration will not resume once errors have been encountered.
If program requirements have changed over an extended amount of time, older certification registrations may contain components that are no longer required for program completion. If a migration on a test database results in warnings about a program not containing a component, you can choose to temporarily add the component to the program and then remove it from the migrated program requirements after the migration has completed. For example, Registration found for component "ABC", student id "101" and program "Program A - Initial" (SEQN 56789), but the program does not contain this component.
All programs and components that are migrated have a default setting of Not requiring approval. This is necessary in order to be able to migrate previously completed registrations without requiring staff to manually approve the registrations after the migration. All program components will have a default setting of Requires grade so that they will not be automatically set to Complete when enrollments are migrated. Consider updating the programs and components to Require approval after the migration in order to prevent registrants from completing certifications without staff approval.
Several areas in the Desktop program or component definitions do not have equivalent fields in the web Certification.
Since there are no functional equivalents in the web Certification, data from these fields will be placed in the Description for future reference:
In Desktop Certification, components gave credit to all programs or a specific program using the Tie to program option. This option could be overridden at enrollment by adding or removing the Program ID from the component enrollment. An exception to this functionality is if a program component was added as a Joint Certification component. For more information, see Joint Certification.
For web Certification, if the same component is a part of multiple programs, any student who receives credit for the component in one program will automatically receive credit for the component in any other program to which it belongs.
It is possible to receive dual credit for a component if defined as Joint Certification in each program. For example, if Component 1 was only configured for Joint Certification in Program A, then enrolling for the program within Program A would also give credit for Component 1 in Program B. However, if Component 1 was registered in Program B, Program A did not receive credit for the component. After the migration, all Joint Certification components will become two-way, meaning that enrolling for Component 1 from Program B will also receive credit for Program A.
Program components that had a setting of Tie to program are migrated to one component per program where the component exists. A code in the form of Program Id_Component Code will be provided. All other components will be added once with a code equal to the original component code. All category components that have enabled the option Tie to Program will created a component for each Program_Category that is currently configured.
The component functionality does not exist for web Certification, nor does the ability for students to complete a specific number of hours from a list of courses. A similar equivalent is either:
- A component with multiple offerings, where the student is required to complete one of the offerings in order to complete the requirement.
- A conditional requirement where the student is required to complete one of two or more offered sets of requirements.
Category components are migrated with a description explaining which components can be chosen. Once the student has fulfilled all required credits, they can mark the entire category component as Completed.
The subcomponent functionality does not exist for web Certification. All subcomponents are migrated as an extra component required for completing the program for which the main component was a part. If the subcomponent is not required, the subcomponent will have two offerings:
- An offering for the subcomponent
- An offering to decline the subcomponent
If a student is registered for the main component and not the subcomponent (and the subcomponent is not required) the student will automatically have the subcomponent added to their registration with the decline offering selected.
If a Desktop component has associated fees, a new product will be created with a product category of CERTIFY. This product will be available for purchase on the web. The product will be linked to an offering on the newly migrated component. Since the Desktop component was considered a product, the product code cannot be reused for the web product. The new product will have a code in the form of the Desktop product code_C (for example, ACCT101_C). However, if that product code exceeds 15 characters or if the product code is already being used, a new product code will be created in the form of 00001_C.
Each location that was defined within a component will be migrated to an offering within a component. The following fields have been added to the offering Description:
- Start date
- End date
- Primary contact
- Toll Free
Each of the offerings will have a new associated provider. The provider will associate the correct contact as the offering provider, but it might not select the correct address. For this reason, the address in the old location will be copied to the description of the offering. As registrations for the component are migrated, if any are found without a location specified, a new Location-less offering will be created.
Program registrations for web Certification migrate the following fields:
- Enrollment date
- Grace period begins
- Expiration date
- Completion date
The following fields will not be migrated:
- Good thru date
- Board notified
- Student notified
- User defined fields
For web Certification component registrations have only one date field of Completion date. Students do not enroll for a component separately, but instead it is assumed that students must complete all required components with a given program once enrolling in the program. The following fields have been added to the component registration Notes:
- UD fields (if defined)
- Enrollment date (if different than completion date)
- Good Thru Date
Note: If Desktop component enrollment is not completed, it will be migrated with a Completion date of either the Cancelled or the Enrollment date depending on which is defined. The component will have a status of Awaiting grade, therefore it will not actually be completed.
Note: The pass or fail portion of the grade will migrate, but the grade (for example: A, B, 100, 90) is recorded in the Notes.
After migration, the component status will be slightly different:
|Desktop Status||Web Status|
|No Show (N)||Rejected|