| Table of Contents | ||
|---|---|---|
|
...
- Users can choose and install Neo4j source and sink plugins.
- Users should see Neo4j logo on plugin configuration page for better experience.
- Users should get relevant information from the tool tip:
- The tool tip should describe accurately what each field is used for.
- Users should not have to specify any redundant configuration.
- Users should get field level lineage for the source and sink that is being used.
- Reference documentation should be updated to account for the changes.
- The source code for Neo4j database plugin should be placed in repo under data-integrations.org.
- The data pipeline using source and sink plugins should run on both mapreduce and spark engines.
Fraud detection use case
Source: Neo4j website
Traditional fraud prevention measures focus on discrete data points such as specific accounts, individuals, devices or IP addresses. However, today’s sophisticated fraudsters escape detection by forming fraud rings comprised of stolen and synthetic identities. To uncover such fraud rings, it is essential to look beyond individual data points to the connections that link them.
No fraud prevention measures are perfect, but by looking beyond individual data points to the connections that link them your efforts significantly improve. Neo4j uncovers difficult-to-detect patterns that far outstrip the power of a relational database.
Enterprise organizations use Neo4j to augment their existing fraud detection capabilities to combat a variety of financial crimes including first-party bank fraud, credit card fraud, ecommerce fraud, insurance fraud and money laundering – and all in real time.
User Storie
- User should be able to install Neo4j specific database source and sink plugins from the Hub.
- Users should have each tool tip accurately describe what each field does.
- Users should get field level lineage information for the Neo4j source and sink.
- Users should be able to setup a pipeline avoiding specifying redundant information.
- Users should get updated reference document for Neo4j source and sink.
- Users should be able to read all the DB types.
...
| Section | User Facing Name | Widget Type | Description | Constraints |
|---|---|---|---|---|
| General | Label | textbox | Label for UI. | |
| Reference Name | textbox | Uniquely identified name for lineage. | Required | |
| Neo4j Host | textbox | Neo4j database host. | Required | |
| Neo4j Port | textbox | Neo4j database port. | Required | |
| Input Query | textbox | The query to use to import data from the Neo4j database. | Required | |
| Credentials | Username | textbox | User identity for connecting to the Neo4j. | Required |
| Password | password | Password to use to connect to the Neo4j. | Required | |
| Advanced | Splits Number | number | The number of splits to generate. If set to one, the orderBy is not needed. | |
| Order By | textbox | Field Name which will be used for ordering during splits generation. This is required unless numSplits is set to one. |
...
| Section | User Facing Name | Widget Type | Description | Constraints |
|---|---|---|---|---|
| General | Label | textbox | Label for UI. | |
| Reference Name | textbox | Uniquely identified name for lineage. | Required | |
| Neo4j Host | textbox | Neo4j database host. | Required | |
| Neo4j Port | textbox | Neo4j database port. | Required | |
| Output Query | textbox | The query to use to export data to the Neo4j database. | Required | |
| Credentials | Username | textbox | User identity for connecting to the Neo4j. | Required |
| Password | password | Password to use to connect to the Neo4j. | Required |
...