Guidance on the Equivalent Address Resolver?

[ginkgomzd]

The resolver docs mention:

Resolves (some) cases where the addresses are the same but one has more detail (eg. one is just the country & the other is a full address in that country)

I have a case where multiple imports were done without street addresses, but most other address fields.
Do I need to do something to make use of the EAR? Or is it working, but not for this case?

I'm still working my way through the docs... are there code-extension points I can use if the default EAR won't resolve this case?

Thanks!

[eileenmcnaughton]

@ginkgomzd I think it's a bit more limited than that - it's one of those things that obviously hits the use cases that we have had to deal with - issues around Country & postal_code

I haven't put much thought into making it extensible - but it would probably be easish to patch with a check for empty(street_address) - would it work to do a stristr to compare the 2 addresses - ie I think it comes out as an address string so if either one is a partial of the other we could pick the longer one?

[ginkgomzd]

I think just considering a sub-string-match would be too broad.

I need to think more on the problem. I'm not sure I can't just configure a traditional dedupe rule with threshholds to give me the confidence to do a force-merge.

Last time I enabled the extension, it caused errors. My first thought is that it has to do with the PHP(8) version. So I intend to get into the code in a development environment. Any pointers on where to look in the code for resolvers could be useful.

Thanks!

[eileenmcnaughton]

I'm guessing you found this section?

https://github.com/eileenmcnaughton/deduper/blob/master/CRM/Deduper/BAO/MergeHandler.php#L441-L486