Global Data Management Forum

We are using a searchPerson layer in our customized search service. However, we would require the results considering all the inputs provided in the request rather than the input precedence followed by searchPerson.

Can someone please guide on how to achieve this?

avoidance to a new structure: multiple task-precedence posets ... for the associated permutations avoiding collections of patterns of length https://ghd-sports.com/

What do you mean by consider all inputs. The SE algorithm comparisons are each configured to use in matching and/or searching, maybe some of yours are configured for matching only. Alternatively, maybe you are talking about where the scores returned don't match what you see returned due to data being split across member records. For example, if one system held name and address, and another held name and date of birth, then if you searched on all 3 items, the first member would be scored on name and address only, and the second one on name and date of birth. Returned could be the complete entity data of all 3 components, but the score would be the maximum of the 2 member matches. That is, searching and scores are always on the member records, but you maybe returning the entity version. Another possibility might be the algorithm is anonymising some of your search values.

But as I said at beginning, really need more information to understand your issue.