Synonym sync: Refactor capitalization columns

[joeflack4]

Overview

In the first draft of the synonym sync, I introduced several extra columns that are supposed to help with analysis and curation, specifically with situations where the capitalization is different between the source and Mondo. They were: synonym_case_diff_mondo and synonym_case_diff_source (see: v8). In #720, I added additional columns to deal with cases where Mondo or the source had multiple capitalization variations. Now the columns are: synonym_case_mondo, synonym_case_diff_mondo, synonym_case_mondo_is_many, synonym_case_source, synonym_case_diff_source, synonym_case_source_is_many (see: v9).

Note: There is a UX issue in #720, where for rows where there are not multiple capitalization variations (that is, for most rows), the values in the new columns will be blank. I can fix that, but I have a better solution below.

Proposed changes

Existing columns (keep or drop):

• synonym: Keep same. Shows the synonym capitalization in Mondo.
• synonym_case_mondo: Drop. Duplicate of synonym column.
• synonym_case_source: Keep.
• synonym_case_diff_mondo & synonym_case_diff_source: Drop these in favor of new columns below. Currently, this is empty for rows where there is no capitalization difference, else it shows the synonym. If multiple values, pipe-delimited.
• synonym_case_mondo_is_many & synonym_case_source_is_many (bool): Drop these in favor of new columns below.

New columns

• synonym_case_differs (bool): If there is a case diff between Mondo and source.
• synonym_case_alts_source: Pipe delimited variations
• synonym_case_alts_mondo: Pipe delimited variations

Sub-tasks

• 1. Make the proposed column changes
• 2. At the same time, could possibly solve Bug: Synonym Sync: synonym_case_diff_* variations amongst multiple templates #742

Additional info

• Google Sheet: synonym_sync_combined_cases

[joeflack4]

@twhetzel Note that I would prefer to combine this with #720, but we do not have to. If we are able to merge in #720 in time for the January release, I think we should do that instead.