Tips & Tricks for Managing Large and Complex Networks - Update for 2.5 & 2.6
As an investigator you may have found that the use of entities and networks are helpful for identifying potential risk in the investigation process, using connections across documents and entities. However, seeing all the available data connected by way of transaction flows, trades, direct links or indirect links can present its own challenges. Substantial amounts of data in a network can sometimes be difficult to navigate. Where do you start? How do you find how many hops to expand then stop? What do you do with the information which is no longer useful to the investigation? Read the full article Tips & Tricks for Managing Large and Complex Networks for the latest functionality which can help simplify how to view and use networks to their full potential. Tips & Tricks for Managing Large and Complex Networks - Quantexa Community As an Investigator, you may have found that entities and Networks are helpful for identifying potential risk in the investigation process, using connections across documents and entities. However, seeing all the available data connected through transaction flows, trades, direct links, or indirect links can present its own…🔎 Data Fusion: qmodels and qentities
Models and qmodels Models are a type of file in Data Fusion that represents a Document in your system, such as a: Customer Watchlist Transaction A Model contains a collection of fields, attributes, and inputs, depending on the data in the associated Document. Model configuration files have the extension .qmodel, such as customer.qmodel. After loading the data, you can represent it in The Quantexa Platform as Nodes within a Network. Entities and qentities Entities are created by associating data Records that represent something in the real world, such as information found in Documents about an individual, address or bank account, which is then resolved to form an Entity, such as an Individual, Address, Email or Business Entity. Entities are represented in the UI as Nodes and can be changed or adjusted using Entity Lab. 🔎 Interested in learning more? Why not explore these Community posts (did you know if you're logged in, you'll unlock even more resources): Designing a New Document Model Qmodel Qentities Or further Documentation can be found on the Docs site: How to configure Models and the different types of Models Entities and qentities🔎 Address Parser: Libpostal and jpostal
The Address Parser uses Libpostal. This is an open source library for parsing and normalizing street addresses using a natural language processing model trained on global open source address data. To improve the performance of Libpostal, the Address Parser repository includes functionalities built on top of Libpostal, including the following: Country-specific Parsers Custom regex to extract particular fields Reference files of common terms Normalization of Elements Libpostal is written in C. Using Libpostal in Scala or Java requires bindings provided by jpostal. 🔎 Interested in learning more? Why not explore these Community posts (did you know if you're logged in, you'll unlock even more resources): Libpostal jpostal Or further Documentation can be found on the Docs site: Setting up Libpostal
FAQ - List of Technical Business Analyst (BA) Academy Frequently Asked Questions
Below is a list of FAQ's for the Quantexa Technical Business Analyst (BA) Academy. Search configuration could not be loaded Setting up the training-tutorial project for the Scenario-based Tasks Not able to access search option on UI application. check-all.sh script showing all started UI Entity search not working BA Academy Task Part 2 CSV files missing Have an idea for an FAQ? Please let us know by emailing training@quantexa.com with the idea!💭 All things Glyph!
Hi Community, We wanted to help direct you to some useful Q&A relating to Quantexa Glyphs: Glyph sizes Glyph with total score condition I'm not getting the glyph shown for the document. How to get glyph icon working correctly Watchlist Contextual Search glyph error in v2.0.3 On a Contextual Search node, is possible to apply custom glyph logic based on the search result? Cannot find name 'SigmaHighlightColor' Final assessment : Glyphs Re: Adding glyphs : Final Assessment Custom Glyphs not rendering in UI after upgrade to v2.0 Glyphs not displaying text correctly in UI Re: [Module 6.1] UI customizations — what's expected? (accessible to customers & partners only - log in required)
🔧 Common Errors 🔧
Introducing Common Errors - a new series of articles troubleshooting error messages and issues that are frequently searched for by you - our Quantexa Community users! These guides will provide debugging tips, configuration examples and references to relevant pages on the Documentation site or related Community posts, and will act as a resource to help you identify troubleshooting steps you can take before seeking any additional support. Where do I find them? Jump directly to our Common Errors section of the Community Library, here: https://community.quantexa.com/kb/categories/87-common-errors OR Click on the shortcut to ‘Common Errors’ under Quantexa Platform Links - you’ll find this on the right hand side of the Quantexa Platform Topic page OR Navigate via: Help & Learning > Platform Documentation > Support > Common Errors Please log in, or sign up, to unlock the first (of many!) series of Common Errors articles: Troubleshooting on Dependency not found The investigation could not be fetched / timed-out Error loading libpostal parser modules Otherwise known as: Could not find org.springframework.boot:spring-boot-starter-test:2.3.10.RELEASE | spring-boot-starter-test | AskTimeoutException | Failed: ErrorResponse(Investigations request failed, Status: 503 Service Unavailable | 503 | Investigation Datasources
🔎 Resolver Config
Resolver config (or resolver-config) is the technical backbone of entity resolution. 🔎 Interested in learning more? Why not explore these Community posts (did you know if you're logged in, you'll unlock even more resources): Read about resolver config in the best practice library section on Entity Resolution Explore Community posts related to resolver config: Resolver config All posts tagged with resolver config Further documentation can be found on the Docs site: Resolver configuration reference Resolver YAML configuration Resolver JSON configuration Resolver Elasticsearch configuration Resolver security Resolver custom Attributes Resolver Attributes migration
Tips and Tricks for Understanding Entity Lab
Entity Lab can be quite complex to understand and review when searching for Entity Resolution problems. To help with this, we've compiled some tips and tricks for what to watch out for that may help you quickly understand the health of your entities as well as some common shapes you may encounter, including: Signs of Possible Overlinking Signs of Underlinking Possible Aggregation Issues Read the full article: Tips & Tricks for Understanding Entity Lab (login required) Tips and Tricks for Understanding Entity Lab - Quantexa Community Entity Lab can be quite complex to understand and review when searching for Entity Resolution problems. Below are some tips and tricks for what to watch out for that may help you quickly understand the health of your entities as well as some common shapes you may encounter. Signs of Possible Overlinking Look for lots of…
Scoring Concepts: Alerting and Re-alerting 📖
Alerting is the name for the process that comes after Scorecard creation and before Task loading into a Quantexa Deployment. Alerting decides which Subjects in the Scorecard output should alert to the end-users. Re-Alerting is an Alerting process that occurs after the first Alerting cycle, when new Scorecard data becomes available. Re-alerting logic compares a Subject's Scorecard output with all previous Scorecard outputs. The aim of this process is to ensure that there is new material risk that an Investigator would like to review. It is strongly encouraged that all deployments with Batch Scoring implement Alerting. Read about the Alerting Framework, Alerting Threshold, and Score Types in Scoring Concepts: Alerting and Re-alerting. Read the full article (login required): 4. Scoring Concepts: Alerting and Re-alerting - Quantexa Community This article builds upon the concepts introduced in Scoring Concepts: Scoring Levels and Scorecards. Alerting is the name for the process that comes after Scorecard creation and before Task loading into a Quantexa Deployment. Alerting decides which Subjects in the Scorecard output should alert to the end-users. Re-Alerting…
Useful Elasticsearch API Calls
, Solutions Architect, outlines how to manage Elasticsearch (Elastic) clusters and indices which are crucial for maintaining a Quantexa implementation. This article provides an overview of common Elasticsearch API calls that can be used for cluster and index management. Key topics: Cluster Management: Retrieve cluster statistics using the _cluster/stats endpoint. Index Manipulation: Create an index with specific settings. Delete an index. Open and close an index. Enable read/write on an index. Reindex data from one index to another. Force a merge operation for better read performance. Move shards within the cluster. Alter the number of replicas for redundancy. Disable and re-enable shard allocation. Index Interrogation: List aliases. List indices, including their health and status. List shards and their details. List segments within an index. Retrieve index mapping. List unassigned shards. Check the progress of a force merge operation. Index Entry Manipulation: Add an entry to an index. Nodes: List nodes in the cluster, including their roles and resource usage. List nodes with detailed queries. Search: Perform a search query within an index using cURL requests. Tasks: List active tasks within the cluster. List detailed task information. This serves as a practical guide for managing Elasticsearch clusters and indices in the context of a Quantexa implementation, providing essential commands to effectively maintain and optimize the Elastic search environment. Useful Elasticsearch API Calls - Quantexa Community Managing your Elasticsearch clusters and indices is an important part of building and maintaining your Quantexa implementation. In this blog we have outlined and explained some of the more common Elasticsearch API calls that you may need. The example cURL requests below assume you are on an Elastic node. If that’s not the…
