This PR introduces fuzzy address matching & validation to the new /pins/vhers-create and /pins/vhers-regenerate endpoints. These are separate from the ones used by our frontend, which does not have this kind of automated validation.
The /pins/create and /pins/regenerate request requirements have also been largely simplified. These now only require the following fields from the frontend:
The thresholds, fuzzy match coefficients, and weights are all adjustable by editing matchWeightsThresholds.json at the root of the project, and this is parsed on function run, so it should be able to be temporarily adjusted by replacing the file directly in openshift without triggering a build. It will only last until the pod restarts however. For a permanent change, you can always push to github, but that always triggers a build. Currently, the match score is displayed by the logger, so you can check to see how your adjustments are affecting things.
Please take a look at the full fuzzy match explanation here for more information on how the match is scored.
Added rated scoring
Added the pins/vhers-create and /pins/vhers-regenerate endpoints with this scoring implemented
Removed the exact match requirements from the existing /pins/create and /pins/regenerate endpoints, as these addresses should be validated by service BC personnel and not automatically
This PR introduces fuzzy address matching & validation to the new /pins/vhers-create and /pins/vhers-regenerate endpoints. These are separate from the ones used by our frontend, which does not have this kind of automated validation.
The /pins/create and /pins/regenerate request requirements have also been largely simplified. These now only require the following fields from the frontend:
{ "livePinId": "string", "email": "string", "phoneNumber": "string", }The thresholds, fuzzy match coefficients, and weights are all adjustable by editing matchWeightsThresholds.json at the root of the project, and this is parsed on function run, so it should be able to be temporarily adjusted by replacing the file directly in openshift without triggering a build. It will only last until the pod restarts however. For a permanent change, you can always push to github, but that always triggers a build. Currently, the match score is displayed by the logger, so you can check to see how your adjustments are affecting things.
Please take a look at the full fuzzy match explanation here for more information on how the match is scored.