Notes Migrator for SharePoint contains the ability to do “best fit” design matching to help identify which applications are based on similar designs, regardless of whether or not they are currently inheriting from the same application template. This supports the “design consolidation” process which is crucial to reducing the cost/risk of large migration process. To start using this feature, you need to associate specific Notes templates to specific Technical Classes.
Prior to version 5.3, Notes Migrator for SharePoint already had the ability to assign a “Reference database” to a Technical Class, which was useful for detecting the deltas of each member of a Technical Class (the first checkbox). This feature assumed that we had already assigned Technical Classes to the databases – either automatically (by Rule) or manually. The most common kind of Class Rule used the database’s assigned Template name to assign classes.
In contrast to this, the new feature helps you use design comparisons to help figure out what Technical Class a given database might be, even if it does not have a Template assigned. By enabling “Include in Best Fit testing for all databases” (the second checkbox) you can now compare every database you scan with this Reference database.
You can set up as many Technical Classes as you want this way. Think of this as setting up a many-to-many comparison. Each database you encounter will be compared with the Reference databases of multiple Technical Classes. The actual comparison occurs when you do the Design Analysis. Simply check the Compare with class templates for best fit option when you do the analysis.
The design of each database is then compared with the designs of the templates you want to compare to (see below). This is similar to the existing feature for comparing the designs of applications and their assigned templates, but this is many-to-many instead of one-to-one.
Note that this is also be available in the new “Recompute” function. If you have already done the design scan for the database and the templates, you can adjust the list of Technical Classes to test for and re-run the Best Fit comparison without accessing the databases again.
The “best fit” for each database is displayed in two new view columns as well as on the Design Analysis tab. A details dialog shows all the partial matches over a certain threshold.
In the above example, notice that the even though the database appeared to be a normal document library, it was only a 90% match to the standard Document Library template. But it was a 100% match with the custom “Acme Enhanced Document Library”! If you decide that you want to make that the official Technical Class for this library, just select it and press the “Set as Technical Class for Database” button.
BONUS! To make this all easier to set up, we added a simple Create Technical Class action. You can use this to select a Notes database or template and quickly create a Technical Class that uses it as the Reference Database and is otherwise preconfigured for Best Fit testing. If it is a template, we also set up a class rule for recognizing it that way.