Type Mapping Transformation: Autopopulate Keys Update

[DnOberon]

Bug Description

The "autopopulate keys" function during type mapping transformations uses an exact match and is case sensitive. However, the json payload typically uses syntax (e.g., data.description) that is different than the "cleaner" version of the ontology in Deep Lynx (e.g., Description). Also, the ontology (e.g., Control Center) may not be a perfect one to one match with the payload value (e.g., controlcenter), so a bag of words or closest match technique would greatly simplify large type mappings.

Steps to Reproduce

Using container 49 in Deep Lynx Acceptance, type mapping the Windchill data source.

Impact

This is not a blocker by any means, but a type mapping of 23 shapes took ~1 hour with all the button clicks whereas with a flexible autopopulate function, it probably would've been 10 minutes. This would be beneficial when we have larger data sources and type mappings.

[browjm4]

this is a feature request, not a bug