Implement boomer workflow for data model harmonization

[balhoff]

Some folks on the data model team (@mbrush, @bfurner) expressed interest in testing the boomer tool for evaluating mappings between data model elements. It should be straightforward to set this up, so we should give it a try and see if it is a useful approach.

[balhoff]

I'm going to move this to Q4, as the data model development isn't currently ready to try this sort of approach.

[gaurav]

@balhoff: What do you need from the model to try this out in quarter?

[balhoff]

This would make sense if we wanted to make sense of a collection of mutual mappings across several models, especially if one or more of the models constituted a hierarchy.

[gaurav]

Tools discussion: this is probably not very useful right now, but we want to get the Boomer workflows working well, so eventually we can have a workflow for checking mappings between entities. Boomer needs some kind of class hierarchy -- without that, all we can look for is whether the multiple properties are mapped to the same property. What we really need is:

1. Hierarchies for CRDCH, GDC, PDC, etc.
2. Mappings between fields

With some custom code, you could create instance graphs according to proposed mappings and try a bunch of configurations and see which mappings work.

[gaurav]

Moving to the next quarter as it it dependent on cancerDHC/ccdhmodel#64.