Migrator for Notes to SharePoint 7.1

Table 15. Assign properties
Property	Description
Lock all	This quick set option will select all of the Locked check boxes in the selected databases’ properties. The Locked check boxes keep manual changes from being over-ridden in future design scans.
Unlock all	This quick set option will deselect all of the Locked check boxes in the selected databases’ properties. By de-selecting all of the Locked check boxes, any manual changes made in to the database properties may be over-ridden in future design scans.
Disposition	This will set the disposition value in the Migration Status tab of the selected databases’ properties.
Technical Class	This will set the Technical Class value in the Classification tab of the selected databases’ properties.
Business Class	This will set the Business Class value in the Classification tab of the selected databases’ properties.
Choose Target Site	This allows you to define the Target Site in Migration Targets tab of the selected databases’ properties.
Clear Target Site	This allows you to remove the site that is defined in the Target Site property of the Migration Targets tab of the selected databases’ properties. The purpose of this is to remove any specific target site that has been applied either directly or through the application of class rules. If any of the databases migration jobs have SharePoint target assignments in them, then this site would be used when running that particular job. So the job supplied target is the last resort target. Jobs built within the console do not have a SharePoint target site in the job. When jobs were created in the designer and imported, then they'd retain whatever target site was in that job, but that would get overridden by any target set directly to the database or applied through class rules.
Map Notes Users to Domain Users	Enable or disable the highlighted databases’ Map Notes Users to Domain Users option of the Migration Targets tab. If enabled, this will cause any Notes users listed in the source database's Access Control List to be added to the target SharePoint list or library. The Notes user names are mapped to Site Collection identities based on the rules configured in the tool's User Mapping options and those Users are granted access to the target SharePoint site.
Map Notes Groups to Domain Groups	Enable or disable the highlighted databases’ Map Notes Groups to Domain Groups option of the Migration Targets tab. If enabled, this will cause any Notes groups listed in the source database's Access Control List to be added to the target SharePoint site. The Notes group names are added to the Site Collection as external groups and are granted access to the target SharePoint list or library. Each group name must correspond to an actual Domain group.
Expand Notes Roles to SharePoint Groups	Enable or disable the highlighted databases’ Expand Notes Roles to SharePoint Groups option of the Migration Targets tab. If enabled, it causes a new SharePoint Site Collection Group to be created for each Role defined in the Notes database ACL.
Expand Notes Groups to SharePoint Group	Enable or disable the highlighted databases’ Expand Notes Groups to SharePoint Groups option of the Migration Targets tab. If enabled, it allows you to take what was once a Domino Directory group (scoped to the entire Notes Domain) and convert it to a SharePoint group (scoped to just one Site Collection). As part of this conversion, the tool will query the Domino Directory for any groups listed in the ACL, extract all its members (expanding any sub-groups as needed), and add those members to the new SharePoint group.
Use Existing Security Groups	Enable or disable the highlighted databases’ Add to existing SharePoint groups option of the Migration Targets tab. If enabled, Migrator for Notes to SharePoint will provision security by adding people to one of the predefined SharePoint groups rather than setting permission on the site members.
Migration Jobs	This allows you to set various properties in the highlighted databases’ migration jobs.

Analyze databases

This action will run various scans on the selected databases. When selected, you will be prompted with options of which types of scans you want run. This action contains the following:

Table 16. Analyze databases

Property

Description

Scan Database Headers

Select this to run a scan of the usage history in the selected databases. This will produce detailed usage information like database size, number of reads, writes and uses by user and by form used. To exclude certain users from this analysis, see Excluded User Names .

You can view these results in the Usage Analysis tab of the Database Property sheet. This action is also available as a button on the Usage Analysis tab of the Database property sheet.

Scan Data Documents

Select this to run a direct scan of all the data documents in a database to produce a summary of data patterns in use there. This action is also available as a button on the Complexity tab of the Database property sheet.

There are three levels of Data Analysis to choose from:

•

Analyze Rich Text – Full scan reading the rich text identifying Docs with Notes Rich Text, Docs with MIME, Docs with Images, and Docs with DocLinks.

•

Analyze Documents – Opens each document and counts up documents, but does not read rich text fields. Up to twice as fast as the full scan.

•

Data Tally only – Counts documents but does not open them. Typically 5 times as fast as the full scan.

NOTE: In Quickr, many "design elements", including custom pages and custom fields, are stored as data documents. Similarly, in Domino.Doc, many "design elements", including custom binder and document type descriptions, are stored as data documents. The data analysis does not treat these as data documents.

Scan Design Elements

Select this to run a direct scan of all the design elements in a database to produce a summary of data patterns in use. This action is also available as a button on the Complexity tab of the Database properties sheet.

NOTE: In QuickPlace/Quickr, many design elements, including custom pages and custom fields, are stored as data documents. Similarly, in Domino.Doc, many design elements, including custom binder and document type descriptions, are stored as data documents. The design analysis process recognizes these documents as constituting the interesting application design and looks at those abstractions rather than true Notes design elements.

The following options are available for this design scan:

•

Compare with class templates for best fit: Select this option to do a best fit design matching in order to recognize which applications are based on similar designs, regardless of whether or not they are currently inherited from the same application template. The design of each database is compared with the designs of the technical class templates you want to compare to. 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. The best fit for each database is then displayed in two results view columns (Best Fit Class and Best Fit Percent) as well as on the Design Analysis tab.

NOTE: For a technical class template to be considered in this Best Fit analysis, it’s property, Include in “Best Fit” testing for all databases, must be checked in the Class Template tab of the Technical Class Properties sheet. For a quick way to include all the Notes databases and templates that you want as technical class templates for Best Fit analysis, use the Create Technical Class database action. If you have already done the design scan for the database and the templates, you can adjust the list of things to test for and rerun the comparison using the Recompute database details function.

•

Assign default templates for database comparison (if none assigned): If selected, this will automatically set the reference database using the database’s default template. To do this, it uses the database’s template name to locate a matching template database. This reference database is then used in the design analysis for measuring deviations.

•

Copy database designs to local folder: When enabled, a partial copy of each scanned Notes database is made on the local machine. While all the design elements are copied, none of the data documents are. The copies are placed in a folder that defaults to ProgramData\Quest\Migrator for Notes to SharePoint\Design Copies. This may be changed on the Analysis tab of the Advanced Configuration Options dialog. The design copies are named <replica id>.nsf in the file system and the database titles will be appended with the string "- DESIGN COPY". Since the replica id is the unique identifier for design copies, they will be shared by all replicas of the database. If you analyze two servers with replicas of the same database, the second one will not be copied unless the Override prior copies option is checked. The design copy provides an easy way for a developer to look deeper into the design when needed.

Scan Doclink

Select this check box to scan all Doclinks in one or more databases. This action is also available using the Doclink Scan button on the Data Analysis tab of the Database properties sheet. To see details of the scan, see the Doclinks button in the Data Analysis tab .

Scan Design Scripts

Select this check box to scan all design scripts of one or more databases. To see details of the scan, see Script Analysis tab .

Advanced

Run task in background: If selected, this action will run in the background as a task. To see the status and log files generated, go to Task history . If deselected, this action will run in the foreground with the task properties dialog box displaying progress, status and logs.

Please select your product:

To serve you better, please complete the Purpose of your Chat:

Recommended Solutions for Your Problem

Migrator for Notes to SharePoint 7.1 - User Guide

Copy to custom view

Export list

Assign properties

Analyze databases