Reading the results
At the end of a run SmartMapper prints a summary:
Resolved=414 Mapped=294 WouldFix=294 WouldBreak=0
In-scope unfixed: NoMappingRules=0 IDMatchNotFound=0 NoDocIdTarget=0 Pending=0 (out-of-scope excluded: 198)
>>> Confidence (fix accuracy) = 100,00%
>>> Coverage (in-scope fixed) = 100,00%
[idx] per-file index IX_SRK_RunID_PathHash built (9,6s)
SmartMapper run summary - RunID 58
=====================================
Links (resolved+unresolved) : 612
Resolved : 414
Mapped (have NewLink) : 294
Unresolved : 198
Patterns (SearchReplaceKeys): 288
Confidence (fix accuracy) : 100,00%
Coverage (in-scope fixed) : 100,00%
ResolvedLinks grouping (by LinkType)
=====================================
LinkType Counter Mapped
Absolute 234 114
SameFolderLink 102 102
Relative 54 54
FileProtocol 24 24
----------------------------------------------------------
TOTAL 414 294
ResolvedLinks grouping (by SourceTable / SourceField)
=====================================
Source Counter Mapped
Hyperlinks.Link 348 228
LinkSources.ConnectionInfo 24 24
OLE.OLEObject 18 18
LinkSources.SourceFile 18 18
PivotTables.SourceFile 6 6
----------------------------------------------------------
TOTAL 414 294
SearchReplaceKeys grouping (by LinkType)
=====================================
Value Counter
Absolute 114
SameFolderLink 102
Relative 48
FileProtocol 24
------------------------------------
TOTAL 288
-> WouldFix=294 WouldBreak=0 Accuracy=100,00%
SearchReplaceKeys grouping (by PatternStatus)
=====================================
Value Counter
Generated 288
------------------------------------
TOTAL 288
UnresolvedLinks grouping (by UnresolvedReason)
=====================================
Value Counter
External 120
Internal 78
------------------------------------
TOTAL 198
UnresolvedLinks: UnsupportedType breakdown (by scheme, top 100)
=====================================
Value Counter
------------------------------------
TOTAL 0
=== done in 11,3s ===
|
Figure |
Meaning |
|
Resolved |
Links turned into a complete address |
|
Mapped |
Links a rule could convert |
|
Patterns |
Search/Replace keys generated |
|
WouldFix |
Links the keys will repair |
|
WouldBreak |
Links the keys would damage – should be 0 |
|
Coverage |
Share of in-scope links that will be repaired |
|
Confidence (fix accuracy) |
Of the links the keys change, the share changed correctly = WouldFix ÷ (WouldFix + WouldBreak). Separate from Coverage. |
Coverage and Confidence measure different things and move independently – read both. The run above scored WouldBreak=0, so every key it produced was correct, yet, for example, Coverage was only 81,13%: nearly a fifth of the in-scope links had no key at all. A high Confidence on its own does not mean the run is complete.
Why links may remain unmapped
|
Reason |
Meaning |
What to do |
|
NoMappingRules |
The location is in scope but no rule describes it |
Add a rule (use Suggest rules / Coverage gaps) |
|
External |
The link points outside the migration (internet, other systems) |
Nothing – correct behaviour |
|
IDMatchNotFound |
An ID link whose target document is not in the scan |
Widen the scan, or see Where to scan if you scanned at the target |
|
SameFolderLink |
A short link that does not need or cannot get conversion |
Nothing, unless a rule for that folder is missing |
|
SharingTokenUnresolved |
A sharing link whose token matches nothing in the scan |
Widen the scan to include the linked content, or re-share the item at the target |
|
Internal |
Bookmark or cell reference inside the document |
Nothing |
|
UnsupportedType |
mailto:, javascript: and similar |
Nothing |
|
OutsideOfParent |
A relative link pointing above the scanned root |
Widen the scan if those files matter |
A high number of External or Internal entries is normal and does not indicate a problem – coverage is calculated only over the links that are actually in scope.