Create Initial Corrections File for DD 2.0 Testing

[darnjo]

In addition to using automated matching techniques for field and lookup mapping, we will also be using manual mappings collected from the Industry Aggregates service to suggest the correct value when we find alternate ones.

The corrections file can include both fields and lookups, but the attached item only includes lookups at the moment.

• Field corrections will be suggested at the top level.
• Fields that have lookups will have corrections in a nested lookups object with each of the suggestions contained within.

There's also a possibility that some values only apply for some property classes, such as RESI. In that case, the item should include a propertyClasses array with those items included.

Another case is that a given item might also have a related field and value that goes along with it, in which case there's a relatedFields object nested within that item.

See "Commercial Land" in the mapping file for an example of both of the above cases.

If a given item looks incorrect but does not have any suggested mappings, or if we don't know the mappings at this point and want to come back to it later, an empty array may be added to flag the item but not provide any values. See "Vacant Commercial Lot" for an example of this.

The mappings file for the branch related to this issue is contained here and should be committed back to the branch with each batch of changes: https://github.com/RESOStandards/web-api-commander/blob/135-create-initial-corrections-file-for-dd-20-testing/src/main/resources/disallowed-values-dd-2.0.json

This file will be used by the Commander for DD 2.0 certification, and we'll also make a service out of it so people can look up the correct mappings if they want.