What's New In Senzing v4

New System Requirements

New Packages

Package Name Purpose
senzingsdk-runtime The main Senzing SDK package.
senzingsdk-tools Contains er/bin utilities, such as sz_command, sz_configtool, and the EDA tools (sz_explorer, sz_audit, and sz_snapshot).
senzingsdk-setup Contains er/bin upgrade utilities sz_dbupgrades, sz_configupgrade, and er/resources files and templates.
senzingsdk-poc Installs senzingsdk-runtime, senzingsdk-setup, and senzingsdk-tools. Contains files required for a Senzing v4 Linux Quickstart PoC , including er/bin utilities sz_create_project, sz_setup_config, sz_update_project, sz_fileloader, and a SQLite database.

New Capabilities

Here are just some of the great new capabilities in the Senzing v4 release:

SDK Improvements

  • Revamped Python and Java SDK for greater ease of use as well as the addition of .NET. code-snippets are provided in the Senzing GitHub for all languages

  • Factory/Environment object to make the init calls more intuitive

  • preprocess_record() function that allows preprocessing of a record, with output similar to get_record(). Great for evaluating JSON record mapping or generating statistics prior to loading data

  • whySearch function to give whyEntities explainability to search requests. In case you ever wondered why Senzing did or did not match a particular entity when searching.

Matching & Resolution Enhancements

  • Support for semantic embedding and cosine similarity

  • CJK (Chinese, Japanese, Korean writing systems) cross-script matching for names and addresses

    118, Fengcheng 10th Road, Xi'an, Weiyang District, Shaanxi 710000
vs
710000陕西未央区西安凤城十路118

    1-1 Chuo-ku Osaka Osaka 540-0002
vs
〒540-0002大阪府大阪市中央区1-1

    Ping An Insurance
vs
平安保険

    Alibaba Group
vs
アリババグループ

  • Regional address models for superior parsing

  • Enhanced PlaceKey support that leverages the address component for matching as well as the name and address components for key creation. BUSINESS usage type allowed.

    222-224@5x4-4b6-mff
vs
14xyqtz6ty@5x4-4b6-mff

  • Newly created configurations will leverage Metaphone 3 for key generation

  • Overused FTYPE logic now uses most common feature values for the entities instead of completely disabling the FTYPE

  • Reduced entity ID movement. If a record is updated, the existing ID will be reused if possible

Response Document Enhancements

  • MATCH_KEY_DETAILS section of response documents has three sections to describe MATCH_KEY confirmations, denials, and disclosed relationships. This is a JSON structured representation of the MATCH_KEY which also provides the details on specifically what supported the token in the MATCH_KEY.

    "MATCH_KEY_DETAILS": {
  "CONFIRMATIONS": [
    {
      "TOKEN": "ADDRESS",
      "FTYPE_CODE": "ADDRESS",
      "SCORE_BEHAVIOR": "FF",
      "SOURCE": "ADDRESS",
      "SCORE": 100,
      "ADDITIONAL_SCORES": {
        "FULL_SCORE": 100
      },
      "INBOUND_FEAT_ID": 2,
      "INBOUND_FEAT_DESC": "111 1st St, Las Vegas, NV 89111",
      "CANDIDATE_FEAT_ID": 2,
      "CANDIDATE_FEAT_DESC": "111 1st St, Las Vegas, NV 89111",
      "SCORE_BUCKET": "SAME"
    }
  ]
}

  • SZ_ENTITY_INCLUDE_RECORD_FEATURE_DETAILS flag enables mapping attributes to features for get_record, get_entity, and search_by_attributes response documents. This tracks specifically which JSON key/values created the feature.

    "FEATURES": {
  "NAME": [
    {
      "LIB_FEAT_ID": 1,
      "USAGE_TYPE": "PRIMARY",
      "FEAT_DESC": "George Washington",
      "ATTRIBUTES": {
        "PRIMARY_NAME_LAST": "Washington",
        "PRIMARY_NAME_FIRST": "George"
      }
    }
  ]
}

Infrastructure & Tooling

  • Optimized tables and indexes to reduce size and improve query plans

  • RES_ENT table has an ENT_STATE column flagging entities that were shown to need reevaluation, but not yet reevaluated. This is a bit flag that may get used for other things in the future.

  • sz_command DB performance check command, check_datastore_performance, now checks all nodes if using a multi-node repository back-end

  • macOS support now requires Apple Silicon (Intel no longer supported)

Migration Guides

If you have any questions, contact Senzing Support. Support is 100% FREE!