|
 
|
|
|
|
Identifying the scope of the project
When reviewing your database to determine the scope of the cleanup projects and best course of action during the migration keep in mind the following questions:
- How many records are affected by this issue?
- Is this a problem that will affect retrieval or display of records?
Once you've identified your database's particular problems and issues, there are four main options for resolution of these data issues:Or, you may decide that the problem is not a high priority and does not require resolution at this time.
- FCLA may be able to resolve the issue either before or during the output of data to the new LMS.
- The new LMS vendor may be able to resolve the issue before or during the load of data.
- Data may need to be sent to a third-party vendor for correction.
- If the issues affect only a small number of records it may be more efficient to simply make changes manually.
In general, it is far easier and more efficient to perform data review and cleanup while you're still using the current LMS. Once the migration process is underway you'll be kept busy learning the new software. In addition, reviewing and cleaning up your databases now will put you in a better position to evaluate and test your data on the new system. You will be much more aware of the state of your data, and there will be fewer surprises after your data is loaded into the new system.
The most important challenge of a system migration is to make sure that all necessary data is migrated, but being aware of records that should not migrate is important as well. Records flagged for deletion, if migrated by mistake to a new database without being flagged as such, can cause problems in the new catalog. You may want to examine any records suppressed from the public catalog to determine if they should be migrated to the new system, but if the answer is not clear then it may be better to migrate the records and if necessary delete them from the new system.
 |
 |