MonsterDB – Quality Rules

query language

It is no secret that monsterDB query language is based upon the syntax that is used by MongoDB, this doesn’t mean we use mongoDB, we are built from the ground up as a pure Java engine.

Quality Rules

Fuzzy commands will configure the fuzzy capability of the installation  this page shows the command available to influence the controlled vocabulary system (nicknames, synonyms, antonyms, etc)

setRuleSetPath

usage from API:
   client.setRuleSetPath(string)

usage from CLI: 
   dq.setRuleSetPath(string) 

This command re-seeds the data quality rules with the files located in the local directory specified. The directory should contain the two files ruleset.map and ruleset.custom, custom can be edited to include custom rules and reloaded using this command. To use the command first copy the ruleset files to a new specified directory and alter the custom file, once you are complete issue this command pointing at your new files, they will be copied to each node in the cluster and stored locally.

dq.setRuleSetPath("/somedir/")

 

saveQualityRule

usage from API:
  client.saveQualityRule(document)

usage from CLI: 
  dq.saveQualityRule(document) 

The document represents a quality rule, please refer to the Quality Rule definitions on the schema documentation page here : https://entitystream.com/entitystream-schema-instructions/

dq.saveQualityRule({rulePurpose: "MatchCompanyName", type:  "TK" , parent:  "LTD", children:  [ "Limited", "Limtd", "LTD"]})

findQualityRule

usage from API:
  client.findQualityRule(document)

usage from CLI: 
  dq.findQualityRule(document) 

The document represents a query against the quality rules, please refer to the Quality Rule definitions on the schema documentation page here : https://entitystream.com/entitystream-schema-instructions/

dq.findQualityRule({type:  "TK"})