Join tables together on inexact matching
OTHER License
knitr::opts_chunk$set(
collapse = TRUE,
comment = "#>",
cache = TRUE,
fig.path = "tools/README-",
cache.path = "README-cache/",
message = FALSE,
warning = FALSE
)
The fuzzyjoin package is a variation on dplyr's join operations that allows matching not just on values that match between columns, but on inexact matching. This allows matching on:
difference_inner_join
)stringdist_inner_join
)regex_inner_join
)distance_inner_join
)geo_inner_join
)interval_inner_join
)genome_inner_join
)One relevant use case is for classifying freeform text data (such as survey responses) against a finite set of options.
The package also includes:
regex_
, stringdist_
, difference_
, distance_
, geo_
, and interval_
, variations for the six dplyr "join" operations- for example,
regex_inner_join
(include only rows with matches in each)regex_left_join
(include all rows of left table)regex_right_join
(include all rows of right table)regex_full_join
(include all rows in each table)regex_semi_join
(filter left table for rows with matches)regex_anti_join
(filter left table for rows without matches)fuzzy_join
) that allows you to define your own custom fuzzy matching function.distance_col
argumentInstall from CRAN with:
install.packages("fuzzyjoin")
You can also install the development version from GitHub using devtools:
devtools::install_github("dgrtwo/fuzzyjoin")
stringdist_inner_join
: Correcting misspellings against a dictionaryOften you find yourself with a set of words that you want to combine with a "dictionary"- it could be a literal dictionary (as in this case) or a domain-specific category system. But you want to allow for small differences in spelling or punctuation.
The fuzzyjoin package comes with a set of common misspellings (from Wikipedia):
library(dplyr)
library(fuzzyjoin)
data(misspellings)
misspellings
# use the dictionary of words from the qdapDictionaries package,
# which is based on the Nettalk corpus.
library(qdapDictionaries)
words <- tbl_df(DICTIONARY)
words
As an example, we'll pick 1000 of these words (you could try it on all of them though), and use stringdist_inner_join
to join them against our dictionary.
set.seed(2016)
sub_misspellings <- misspellings %>%
sample_n(1000)
joined <- sub_misspellings %>%
stringdist_inner_join(words, by = c(misspelling = "word"), max_dist = 1)
By default, stringdist_inner_join
uses optimal string alignment (Damerau–Levenshtein distance), and we're setting a maximum distance of 1 for a join. Notice that they've been joined in cases where misspelling
is close to (but not equal to) word
:
joined
Note that there are some redundancies; words that could be multiple items in the dictionary. These end up with one row per "guess" in the output. How many words did we classify?
joined %>%
count(misspelling, correct)
So we found a match in the dictionary for about half of the misspellings. In how many of the ones we classified did we get at least one of our guesses right?
which_correct <- joined %>%
group_by(misspelling, correct) %>%
summarize(guesses = n(), one_correct = any(correct == word))
which_correct
# percentage of guesses getting at least one right
mean(which_correct$one_correct)
# number uniquely correct (out of the original 1000)
sum(which_correct$guesses == 1 & which_correct$one_correct)
Not bad.
If you wanted to include the distance as a column in your output, you can use the distance_col
argument. For example, we may be interested in how many words were two letters apart.
joined_dists <- sub_misspellings %>%
stringdist_inner_join(words, by = c(misspelling = "word"), max_dist = 2,
distance_col = "distance")
joined_dists
Note the extra distance
column, which in this case will always be less than or equal to 2. We could then pick the closest match for each, and examine how many of our closest matches were 1 or 2 away:
closest <- joined_dists %>%
group_by(misspelling) %>%
top_n(1, desc(distance)) %>%
ungroup()
closest
closest %>%
count(distance)
Note that stringdist_inner_join
is not the only function we can use. If we're interested in including the words that we couldn't classify, we could have use stringdist_left_join
:
left_joined <- sub_misspellings %>%
stringdist_left_join(words, by = c(misspelling = "word"), max_dist = 1)
left_joined
left_joined %>%
filter(is.na(word))
(To get just the ones without matches immediately, we could have used stringdist_anti_join
). If we increase our distance threshold, we'll increase the fraction with a correct guess, but also get more false positive guesses:
left_joined2 <- sub_misspellings %>%
stringdist_left_join(words, by = c(misspelling = "word"), max_dist = 2)
left_joined2
left_joined2 %>%
filter(is.na(word))
Most of the missing words here simply aren't in our dictionary.
You can try other distance thresholds, other dictionaries, and other distance metrics (see [stringdist-metrics] for more). This function is especially useful on a domain-specific dataset, such as free-form survey input that is likely to be close to one of a handful of responses.
regex_inner_join
: Classifying text based on regular expressionsConsider the book Pride and Prejudice, by Jane Austen, which we can access through the janeaustenr package.
We could split the books up into "passages" of 50 lines each.
library(dplyr)
library(stringr)
library(janeaustenr)
passages <- tibble(text = prideprejudice) %>%
group_by(passage = 1 + row_number() %/% 50) %>%
summarize(text = paste(text, collapse = " "))
passages
Suppose we wanted to divide the passages based on which character's name is mentioned in each. Character's names may differ in how they are presented, so we construct a regular expression for each and pair it with that character's name.
characters <- readr::read_csv(
"character,character_regex
Elizabeth,Elizabeth
Darcy,Darcy
Mr. Bennet,Mr. Bennet
Mrs. Bennet,Mrs. Bennet
Jane,Jane
Mary,Mary
Lydia,Lydia
Kitty,Kitty
Wickham,Wickham
Mr. Collins,Collins
Lady Catherine de Bourgh,de Bourgh
Mr. Gardiner,Mr. Gardiner
Mrs. Gardiner,Mrs. Gardiner
Charlotte Lucas,(Charlotte|Lucas)
")
Notice that for each character, we've defined a regular expression (sometimes allowing ambiguity, sometimes not) for detecting their name. Suppose we want to "classify" passages based on whether this regex is present.
With fuzzyjoin's regex_inner_join
function, we do:
character_passages <- passages %>%
regex_inner_join(characters, by = c(text = "character_regex"))
This combines the two data frames based on cases where the passages$text
column is matched by the characters$character_regex
column. (Note that the dataset with the text column must always come first). This results in:
character_passages %>%
select(passage, character, text)
This shows that Mr. Bennet's name appears in passages 1, 2, 4, and 6, while Charlotte Lucas's appears in 3. Notice that having fuzzy-joined the datasets, some passages will end up duplicated (those with multiple names in them), while it's possible others will be missing entirely (those without names).
We could ask which characters are mentioned in the most passages:
character_passages %>%
count(character, sort = TRUE)
The data is also well suited to discover which characters appear in scenes together, and to cluster them to find groupings of characters (like in this analysis).
passage_character_matrix <- character_passages %>%
group_by(passage) %>%
filter(n() > 1) %>%
reshape2::acast(character ~ passage, fun.aggregate = length, fill = 0)
passage_character_matrix <- passage_character_matrix / rowSums(passage_character_matrix)
h <- hclust(dist(passage_character_matrix, method = "manhattan"))
plot(h)
Other options for further analysis of this fuzzy-joined dataset include doing sentiment analysis on text surrounding each character's name, similar to Julia Silge's analysis here.
A few things I'd like to work on:
Shortcuts on string distance matching: If two strings are more than 1 character apart in length, the method is osa
, and max_dist
is 1, you don't even need to compare them.
More examples: I've used this package in other powerful ways, but on proprietary data. I'm interested in ideas for use cases that can be provided as vignettes.
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.