npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

person-name-match

v0.1.3

Published

Fuzzy matching full name provided by user against names extracted using OCR from an ID

Downloads

136

Readme

person-name-match

Suppose that in an application there is a form where the user enters his full name in separate fields:

  • FirstName
  • Middle Name
  • Last Name
  • Second Last Name

Then in a different CIP process using OCR or other means, the user's full name is captured in a single field or several fields, but not necessarily in the same order as the form. OCR's are not perfect and can make mistakes, so the name may not be captured correctly. Error goes from misspelling to missing names or adding extra names or change the order of the names. So using fast-fuzzy library this simple project tries to solve this problem.

The objective of this project is to create a function that receives the name entered by the user and the name captured by the OCR and returns a score of how similar they are.

Example of use, for a misspelled lat name and order change:

const requiredName = {
    firstName: "John",
    lastName: "Doe",
};
  
let res = namesFuzzyMatch(requiredName, "Dow Jonn Franciss");

// response:
// Test on: Dow Jonn Franciss:
// Total score: 0.7083333333333334
// Success: true
// Reason: Average score is 0.7083333333333334
// Matches:
// 	 firstName -> match: Jonn score: 0.75
// 	 lastName -> match: Dow score: 0.6666666666666667

If last name is more important and you can accept a lower score, you can use the lastNameMinTreshold parameter, for example set it to 0.9:

const requiredName = {
    firstName: "John",
    lastName: "Doe",
};
  
let res = namesFuzzyMatch(requiredName, "Dow Jonn Franciss", {
    lastNameMinTreshold: 0.9,
});

// response:
// Test on: Dow Jonn Franciss:
// Total score: 0.7083333333333334
// Success: false
// Reason: Best last name match has score less than lastNameMinTreshold=0.9
// Matches:
// 	 firstName -> match: Jonn score: 0.75
// 	 lastName -> match: Dow score: 0.6666666666666667

As levenstein distance between Doe and the nearest match Dow is 0.6^ < 0.9, the match is rejected.

To use this function, the following conditions must be met:

  • There must be a structured name, a sort of user declaration in a form.
  • The target is a string that represents the full name obtained by another means, in this case we assume an OCR.
  • The set of names from OCR must be greater than or equal to the one declared by the user.
  • The absence of a name declared by the user in the captured by OCR is punished in the score

This funtion will no fire an exception if the name is not found, it will always return a report with the score and the reason of the score.