Skip to content
This repository has been archived by the owner on Jan 3, 2023. It is now read-only.

Broader/narrower matches (continues convo in #2) #3

Open
atomrab opened this issue Dec 18, 2017 · 0 comments
Open

Broader/narrower matches (continues convo in #2) #3

atomrab opened this issue Dec 18, 2017 · 0 comments

Comments

@atomrab
Copy link

atomrab commented Dec 18, 2017

The reconciler will return narrower values as possible matches (e.g. "Orientalizing" will return "Early Orientalizing"), but it will not return broader values (e.g. "Early Uruk" will not return "Uruk" as a possible match). This seems to be because the algorithm will only consider possible matches that contain at least all words in the original term, including parenthetical statements, spatial adjectives, etc. Thus "Jordanian Chalcolithic" will not return "Chalcolithic", and "Vikingatid (600-1000 AD)" will not return "Vikingatid". I realize that this is related to efforts to create results sets that are narrow enough to be useful, but it will either require that the user carry out a major amount of data cleaning in advance, or that we accept a lot of false negatives. I would favor broader recall that would return "Uruk" among the possible matches for "Early Uruk" -- or at least testing this out to see how confusing it makes things.

@atomrab atomrab changed the title Broader/narrower matches (continues convo in #1) Broader/narrower matches (continues convo in #2) Dec 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants