@swashapp/dpp-client

v1.0.0

Published

2 years ago

0High
0Medium
0Low

swashapp

Swash Data Product Provider Client

Swash Data Product Provider SDK is a simple typescript project that helps the users to create a data request, check the status of the request, buy a data and download the data with this SDK in their projects without any UI.

Issues & Questions

For reporting issues or asking questions please use the github issues or contact [email protected].

Getting Started

Before getting started, you need to install the latest LTS version of nodejs. Also, It is better to use yarn as package manager, for this purpose you can use the following instruction:

# Install via npm
npm install --global yarn

# Install via Chocolatey
choco install yarn

# Install via Scoop
scoop install yarn

yarn --version

How to install dependencies

Installing all the dependencies is just simple as running one of the following commands:

NPM:

npm install

Yarn:

yarn install

How to deploy in production

Build

First you have to build the project by the following command:

NPM:

npm run build

Yarn:

yarn run build

Bundle

Running build command will compile, optimize and minify the source code and will save the output in the build directory in the root of project. Now you have to add this SDK as a dependency of your project.

Client Creation

When you want to use the SDK, you have to create a new instance of the DataProviderClient. As you know this client helps you order your data requests, and the requests have to be validated and authenticated, So you have to define your authentication mechanisem to communicate with Swash stack.

Private Key

If you have a valid ethereum account, then Its private key could be used for authentication. To prepare your desire data, your account is in charge of paying data fee, therefore you have to define related provider.

Authentication with private key:

const dppClient = new DataProviderClient({
    auth: {
        privateKey: 'your-private-key',
        provider: 'ether-wallet-provider',
    }
})

Web3

If you want to use the client in your browser, and have a MetaMask account, you can create a web3 from window.ethereum and use that for authentication.

Authentication with web3:

const dppClient = new DataProviderClient({
    auth: {
        web3: new Web3(window.ethereum),
    }
})

Access Token

If you have an access token, the client can use that as an authentication key. However, providing an ethereum account(web3 or privateKey) is necessary.

Authentication with token:

const dppClient = new DataProviderClient({
    auth: {
        web3: new Web3(window.ethereum),
        session: {
            token: 'your-access-token',
            onExpired: () => logout()
        }
    }
})

Data Requests

Data preparation process is introduced by data request. You can define various filters to reach your desire data by adding a data request.

For example:

dppClient.dataRequest.add(`DataRequestDetails`)

Table below shows data request management capabilities of DataProviderClient, for a data request with an id you can use this methods:

For example:

dppClient.dataRequest.with(`your-request-id`).get()

Data Lake

Swash data lakes schema is accessible using data provider client. It may helpful to define filters and requests appropriately.

For example:

dppClient.dataLake.getSchema(`the-name-of-data-lake`)

API Documentations

| Name | Description | Input Parameters | Output Result | | ----------------- | ---------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | -------------------------------- | | add | Send Data Request to the data product provider backend | DataRequestDetails | DataRequest | | provide | Purchase data request and prepare | PurchaseConfig | | | delete | Delete a data request | | | | getAll | List all data requests of user | | DataRequest[] | | get | Get data request | | DataRequest | | getPrice | Get data request price | | {title: string, price: number}[] | | getSchema | Get the data lake details by its name e.g: VISITATION, SEARCH_REQUEST, SEARCH_RESULT, SHOPPING | The data lake name that can be one of these values:ENUM: VISITATION, SEARCH_REQUEST, SEARCH_RESULT, SHOPPING | DataLakeSchema | | getAcceptedValues | Get the accepted values for one column, e.g. for the sex column male and female are acceptable | The column name, e.g. country | string[] |

DataRequestDetails

| Name | Description | Type | | ----------- | ------------------------------------------------------ | ------------ | | params | JSON format of all request parameter | RequestParam | | fileName | The file name of data that system crete after purchase | string | | requestDate | The date of the request | number |

DataRequest

Request Parameters

OrderBy

RequestJob

PurchaseConfig

DataProductDto

DataDictionaryDto

How to create request parameter JSON?

Let's start with an example:

{
  "params": {
    "fromDate": 1642414746814,
    "toDate": 1673518689839,
    "dataType": "VISITATION",
    "repeatType": "ONCE",
    "selectedDpFields": [
      "browser_name",
      "platform",
      "os_name",
      "os_version",
      "Country",
      "Gender"
    ],
    "orderBy": [{"field": "Timestamp", "sortMod": "desc"}],
    "filterCondition": {
      "combinator": "and",
      "rules": [
        {
          "id": "r-0.9092211207828882",
          "field": "country",
          "operator": "in",
          "valueSource": "value",
          "value": "Australia,Turkey"
        }
      ],
      "id": "g-0.4676271133369242",
      "not": false
    }
  },
  "fileName": "test",
  "requestDate": 1667390981356
}

In this JSON, the parameter fields contain this information:

fromDate determine the data that generated after this date
toDate determine the data that generated before this date
dataType that determines which type of data user wants and must be one of these values: VISITATION, SEARCH_REQUEST, SEARCH_RESULT, SHOPPING
repeatType If user want to get the data only one time this field must have ONCE , and the other values must be WEEKLY, MONTHLY or DAILY that means this data must be generated each week or each month or each day
orderBy is optional and is used for grouping conditions it get an array of column names
sortBy is optional and is used for sorting conditions it get an array of sort objects that have sort column name for its field value and "asc" or "desc" for its sortMod value.
selectedDpFields is an array of acceptable column name based on repeatType. You can call loadDataProductByName function and pass the repeatType to it and read the dataDictionaries fields to see the name, and the other details of all acceptable columns of this dataType.
filterCondition you can see this link to know how to create filter query based on your data columns: QueryBuilderModel to find out the acceptable value for each column you can call the getAcceptedValues function and send the column name to it and get an array as a result.

Published

Vulnerabilities

Links

Maintainers

Keywords

Readme

Swash Data Product Provider Client

Issues & Questions

Getting Started

How to install dependencies

How to deploy in production

Build

Bundle

Client Creation

Private Key

Web3

Access Token

Data Requests

Data Lake

API Documentations

DataRequestDetails

DataRequest

Request Parameters

OrderBy

RequestJob

PurchaseConfig

DataProductDto

DataDictionaryDto

How to create request parameter JSON?

Copyright