User can not import a match type level tagging report.

Issues found with reporting at keyword/matchtype levels.

Match type is not a formal entity in the system that can be uniquely identified. This is an issue with exporting reports because reports are written with only the descriptive value for the match type (there is no standardized id to represent match type) and importing tag reports. Tag import relies on mapping tag values to an id the represents the tagged item.

A mapping table will be needed to store match types, and conversions between the match type description and it's associated Id will be required in both the report service and tagging import component.