Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@MorganaFuture
Copy link
Contributor

Implement TF-IDF (Term Frequency - Inverse Document Frequency) weighting to improve name matching accuracy. Rare terms now receive higher weight than common business terms like "Trading", "Ltd", "Company".

Key changes:

  • Add internal/tfidf package with Index, Config, and weighted scoring
  • Build TF-IDF index from entity names during data refresh
  • Add BestPairsJaroWinklerWeighted() for TF-IDF weighted scoring
  • Thread TF-IDF index through search service and similarity functions

This helps reduce false positives for common names and improves ranking for distinctive/rare names in search results.

@gemini-code-assist
Copy link

Summary of Changes

Hello @MorganaFuture, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the name matching accuracy by integrating TF-IDF (Term Frequency-Inverse Document Frequency) weighting. This approach assigns higher importance to rare and distinctive terms in entity names while down-weighting common business terms like "Trading" or "Company". The goal is to reduce false positives in search results and improve the ranking of truly unique matches, leading to more precise and relevant search outcomes.

Highlights

  • TF-IDF Package Introduction: A new "internal/tfidf" package has been added, containing "Index", "Config", and related functions for Term Frequency-Inverse Document Frequency calculations.
  • Dynamic Index Building: The TF-IDF index is now built dynamically from entity names during the data refresh process, ensuring up-to-date term weighting.
  • Weighted Name Matching: New "BestPairsJaroWinklerWeighted()" and "BestPairCombinationJaroWinklerWeighted()" functions have been introduced in "internal/stringscore" to apply TF-IDF weights to Jaro-Winkler similarity scoring.
  • Integrated Search Service: The TF-IDF index is now passed through the search service and similarity functions, allowing name matching to leverage the new weighting system.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces TF-IDF weighting for name matching, which is a great enhancement for improving search accuracy. The implementation is well-structured within a new internal/tfidf package and is cleanly integrated into the existing search pipeline. The addition of comprehensive unit and integration tests, including those using real OFAC data, is particularly commendable and provides high confidence in the new functionality. My main feedback is a suggestion to refactor some duplicated logic in the string scoring functions to improve long-term maintainability.

@adamdecaf

This comment was marked as off-topic.

MorganaFuture and others added 3 commits December 24, 2025 14:49
Implement TF-IDF (Term Frequency - Inverse Document Frequency) weighting
to improve name matching accuracy. Rare terms now receive higher weight
than common business terms like "Trading", "Ltd", "Company".

Key changes:
- Add internal/tfidf package with Index, Config, and weighted scoring
- Build TF-IDF index from entity names during data refresh
- Add BestPairsJaroWinklerWeighted() for TF-IDF weighted scoring
- Thread TF-IDF index through search service and similarity functions

This helps reduce false positives for common names and improves
ranking for distinctive/rare names in search results.
@adamdecaf adamdecaf force-pushed the MorganaFuture/fear/addTF-IDFweightingForNameMatching branch from 6ead602 to 29de083 Compare December 24, 2025 20:49
@adamdecaf adamdecaf merged commit 6b4dcb1 into moov-io:master Dec 24, 2025
9 of 10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants