EngineeringWiki
  • Introduction
  • Top level Overview of the application
  • FAQs
  • Back End
    • Agent Pipeline
    • Mention Pipeline
    • Profile Pipeline
    • Errors
    • Overview of the Mention/Profile/Cluster Process
    • Adding a New Service
    • Activity and Status Tracking
  • Setup
    • Overview
    • How to Setup Your Local Machine
    • Setup - Cloud Machine
    • Infrastructure
    • Docker
    • Bash Commands
    • Setting up front end in Ubuntu 16.04 desktop
  • Gems/Libraries
    • Bax
    • Creating fixtures for Unit Tests
    • Audienti-Retriever
    • Scour
    • Haystack
    • Audienti-Indexer
    • Audienti-Api
    • Handler
    • Blackbook
    • Allusion
  • Code
    • Multi-step Modal Wizard
    • Structure
    • Audienti DataTables
    • Javascript
      • Passing Props From Root
      • Looping in JS
      • Binding Actions to App
      • CSSTransitionGroup
      • Code Best Practices
      • Reducer Updating an Array with Item in Middle
      • Organizing Javascript
      • Filter Array by Id
    • Design Language
  • Working
    • PostgresSQL
    • S3
    • Terminology
    • Interview Tests
    • Application Descriptions
    • Best Practices
      • Code Organization
      • Code Documentation (using Yard)
      • Git Workflow
      • Tasks and Queues
      • Working in Backend
    • Profiles & Enrichment
      • Profile ID Rules
  • Management
    • API Management
    • Bastion
    • Splash Proxy
    • Rancher
      • OpenVPN Server
      • Traefik Reverse Proxy
  • Teams & Interviews
    • Interview Questions
  • Culture
    • What Makes a World Class Engineer
  • Situational Statuses
    • 2017-11-03
    • 2018-01-09
  • Operations
Powered by GitBook
On this page
  1. Working
  2. Profiles & Enrichment

Profile ID Rules

  • By default, a Profile URL should be resolved into a service and a username

  • If the user is reachable by EITHER a username or a user_id, then use the username as the service_id.

  • If the user is reachable only by a series of numbers, then place this series of numbers in the username field.

  • If the user's profile is only reachable by a combination of a username and another attribute, such as a user_id or a subdomain, put the subdomain in the user_id field, and the username in the username field.

  • If a URL is parsable by the SocialUrlParser, is should be generatable by the SocialUrlGenerator.

  • If a service is listed in the SocialUrlParser, there must be a list of Ids to reject in the Bax::Data::Store::Profiles folder.

  • If a service is listed in either the the SocialURLParser or Generator, it's service must be listed in the global_service_keys mixin (Bax::Mixins::SocialParsingData.

PreviousProfiles & EnrichmentNextManagement

Last updated 7 years ago