Feature request: `combine_wpa()` - a function to join WpA person queries

[moralec]

Is your feature request related to a problem? Please describe.
We currently expect users to use dyplr or other packages to combine data when needed. It would be nice to have a simple function to combine wpa person queries.

Describe the solution you'd like
Function will:

• Compare if two person queries have the same frequency, date range and individuals.
• If positive, the function will join the two queries in a new combined dataset, ignoring repeated columns
• If negative it will display a error message. For example: (1) Date range does not match, (2) Frequency does not match or (3) Population does not match

[martinctc]

Is the intention of this to enable users to combine queries when they have different date ranges? In other words, this would be something akin to rbind() but with checks. This is interesting and requires some thinking / consideration on the extent of checks and the design:

• If Date and PersonId values duplicate for a row, do we omit by default?
• If Date and PersonId values duplicate for a row, do we check for value match / mismatches?
• If variable names do not fully match (e.g. one dataset has more org data, should they auto-fill based on joining PersonId or should they populate as missing values?)
• If the variable names do not fully match - esp. in the case of metrics - (e.g. one set of data has Unscheduled_call_hours, and the other set does not) should we issue a warning? If not, the output could be misleading.
• Should the datasets be supplied as a list? Or should we only compare data_x and data_y, and then inform the user to use purrr::reduce() if they have more datasets to join?

[moralec]

I was thinking this more as a join (ie. combining hourly collaboration query and standard person query ) than an append. But it could work either way.

We can take the most conservative approach possible