Rename 'factor_file' to 'value_coding' so it can be extended with built-in converters?

[DesiQuintans]

I really like the file-based workflow of factor conversion; it means that one file can be reused not just in several variables, but in several PROJECTS. For example, I've converted the Standard Australian Classification of Countries into a factor file that I can paste into all of my future projects.

However, there are many cases where making even a simple factor file is pointless busywork. For example: a variable coded as 1 = Yes, 0 = No. It's such a common situation that it should be handled by the package, and a Factor is also the wrong variable type for it anyway (see #12).

I think that the factor_file column should be renamed to value_coding, and that this change should be combined with a suite of tags that trigger built-in converters. These tags should probably be <tagname> because <> are not allowed to be used in Windows filenames.

Proposed tags

• [x] <truefalse> --- Logical conversion for 1, y, yes, t, true to TRUE and 0, n, no, f, false to FALSE.
• [x] <yesno> --- Factor conversion for 1, y, yes, t, true to "Yes" and 0, n, no, f, false to "No".
• [ ] <likert5> --- Factor conversion for the Likert 5-point scale: (1) Strongly Disagree; (2) Disagree; (3) Neither Agree nor Disagree; (4) Agree; (5) Strongly Agree.
• [ ] <likert4> -- Factor conversion for the Likert 4-point scale.
• [ ] <likert7> --- Factor conversion for the Likert 7-point scale.
• Others later

[DesiQuintans]

Closed by commit https://github.com/DesiQuintans/tsv2label/commit/5c0c7584279cd10b8351b3764bf888f0e6c90162. It is now called recode_with.