New fn to compare data to dictionary of allowed values and return tidy data frame of non-matching values · Issue #12 · reconhub/matchmaker · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm realizing that my workflow for generating/updating dictionaries to use with matchmaker::match_df() is inefficient. I basically just rely on printed warnings in the console to identify non-valid value/variable pairs, and copy them into my .csv recoding dictionary.
A better approach might be a function that compares a data frame to a dictionary of allowed values, and returns a tidy date frame of non-allowed values (if any) by variable, which could then be more easily appended to the recoding dictionary.
I've added an initial version to my branch (tentatively called check_df()). If you're interested I can add tests etc. and submit a PR. E.g.
(This is loosely related to reconhub/linelist#49 perhaps)
I'm realizing that my workflow for generating/updating dictionaries to use with
matchmaker::match_df()
is inefficient. I basically just rely on printed warnings in the console to identify non-valid value/variable pairs, and copy them into my .csv recoding dictionary.A better approach might be a function that compares a data frame to a dictionary of allowed values, and returns a tidy date frame of non-allowed values (if any) by variable, which could then be more easily appended to the recoding dictionary.
I've added an initial version to my branch (tentatively called
check_df()
). If you're interested I can add tests etc. and submit a PR. E.g.Created on 2020-05-11 by the reprex package (v0.3.0)
The text was updated successfully, but these errors were encountered: