What's new in Remadder 2.3.0.0
Sep 12, 2017
- Main changes are:
- More similarity metrics are included under the hood, for better matching efficiency.
- Option of using full-text search dictionaries is added.
- New parameters “Use Dictionaries” and "Dictionary" are introduced. The parameters determine whether a full text search dictionary will be used to lexemize strings before strings similarity calculation is applied. If "Use Dicionary" option is checked, then the ReMaDDer will use the dictionary to identify words and transform them into lexemes. This way, various forms of the same basic word will be treated as the same word. This can improve string matching efficiency.
- For example, if english dictionary is used, Remadder will consider word "run", "runs", "ran" and "running" to forms of the same lexeme "run".
New in Remadder 2.2.0.1 (Feb 21, 2017)
- Main changes are:
- The ReMaDDer software is now completely FREE, no license fee is required.
- Increased speed of execution and reduced memory consumption.
- Various bug fixes.
New in Remadder 2.1.0.0 (Jan 15, 2017)
- New parameter "blocking similarity limit" is added.
- The parameter controls similarity threshold to be used in blocking phase.
New in Remadder 2.0 (Dec 6, 2016)
- Main changes are:
- Instead of using only Levenshtein and Trigram similarity functions, multiple other similarity metrics are added to the server engine.
- Matches and non-matches are not based on similarity thresholds any more. Instead, ReMaDDer now utilizes machine learning techniques. Advanced algorithms infer and automatically detect duplicates and record matches.
- Threshold parameters are removed as obsolete.
- “Use composite field” parameter is removed as obsolete.
- “Use inclusive OR”parameter is removed as obsolete.
- New parameter “Machine Learning Strictness” is introduced. The parameter defines how strictly artificial intelligence will distinguished between matches and non-matches. The options are: match, strict match and potential match.
- New parameter “Join Type”is introduced. Join Type attribute determines how SQL joins between left and right tables will be established, via solution base table. There are three options of joining: a) inner join, b) left outer join, c) right outer join.
- The "inner join" option is default behavior, meaning that the resultset will contain all rows from left and right datasets which meet matching criteria.
- In case of "left outer join" option, resultset will contain all rows from left dataset and only those rows from right dataset that satisfy matching criteria.
- In case of "right outer join" option, resultset will contain all rows from right dataset and only those rows from left dataset that satisfy matching criteria.
- New parameter “Return Only Best Match” is introduced. The parameter can have True or False value and determines whether SQL query will return only best matching record or multiple records satisfying similarity criteria.
- Check this option if you wish to return only the best matching records for each left or right record, when using corresponding left or right outer joins.
- If this option is unchecked (default), multiple matching rows will be returned.
New in Remadder 1.1.0.22 (May 30, 2016)
- Normalized levenshtein distance and trigram similarity functions are replaced by a common similarity function incorporating both. Better handling of various non-ascii characters in field names. Many minor improvements in performance and bugfixes.