Challenge 4 - Reactive Analysis into Transaction Parties
This challenge involves reactive analysis into transaction parties, specifically processing a reactive data matching request. Competition participants are required to replicate this analysis. The supplied list of parties is required to be submitted against the party search API to identify matching parties within the dataset. The unstrucutured extension for this analysis involves micro analysis into the top hit (by transaction reporting value) to determine this party's complete footprint in the data. Please note the source data is regularly changed thus your output will be different.
Load Up Party Details for Matching
The source data for matching can be found here. There are 4,000 parties for matching (way to many to do manually). In this step we also structure our search requests based on what is considered a matching. I.e. all of the following are considered matches:
- Name and Address hit
- Name and Account hit
- Name and Identification hit
- Address and Account hit
- Identification and Address hit.
Basically if two of the key attributes hit then we consider that as a match.
Competition Unstructured Extension
Competition participants are required to identify the complete financial footprint of the network associated with the party with the greatest value of total transactions identified above. Please use the consolidated party and network API end points to perform this analysis. Then extract the reported transactions from the redtongue
API for disemination as evidentiary(raw) data.