Project Name

Timder App - Analysis

Roadmap

View the project roadmap here

Contributing

See CONTRIBUTING.md for contribution guidelines.

Table of Contents

1. Usage
2. Requirements
3. Development
   1. Installing Dependencies
   2. Tasks

Usage

Database Schema

API Usage

Show User Weight

Returns weight data about a single user.

• URL

/analysis/:id

• URL Params

  Required:

  id=[integer]

• Data Params

  None

Input

  {
    user_id: INT,
    start_date: STRING,
    end_date: STRING
  }

• user_id Query for specific user's id
• start_date Request start date
• end_date Request end date

Example Weight Request Parameters

  {
    user_id: 23151,
    start_date: '2017-10-1',
    end_date: '2017-10-8'
  }

Output

 {
   weight_id: INT,
   user_id: INT,
   photo_count_weight: {
     0: INT,
     1: INT,
     2: INT,
     3: INT
   }
 }

• weight_id User's specific weight ID
• user_id User's specific ID number
• photo_count_weight User's calculated weights for photo count

Additional Information:

The calculated weights table is generated by joining Event Service, Swipes, and User Info tables. The photo_count_weight number will be calculated by measuring a specific user with X amount of photos to user matches for a given time range. Each photo count will have a weight attributed to it and based on how much weight is given, the Match service will prioritize and sort user cards accordingly.

Requirements

-Node 6.9.x -Postgresql 9.6.x -express -pg -chai -mocha