Project

General

Profile

Actions

Task #121

open

User Preference Master / Partner Preference

Added by Dana Basheer 16 days ago. Updated 9 days ago.

Status:
Resolved
Priority:
High
Start date:
02/18/2026
Due date:
02/18/2026 (15 days late)
% Done:

0%

Estimated time:

Description

The Preference Module allows users to define their expected partner criteria.
These preferences are used by the system to:

  • Generate daily match recommendations
  • Filter search results
  • Improve matchmaking accuracy

Users can edit preferences anytime from the dashboard

Table

user_preference_table

  • id INT PK Unique identifier
  • profile_id INT FK References registration_table(id)
  • age_min INT — Minimum preferred age
  • age_max INT — Maximum preferred age
  • marital_status_id INT FK Preferred marital status
  • state_id INT FK Preferred state
  • district_id INT FK Preferred district
  • city_id INT FK Preferred city
  • education_id INT FK Preferred education
  • occupation_id INT FK Preferred occupation
  • star_id INT FK Preferred star
  • raasi_id INT FK Preferred raasi
  • sub_caste_id INT FK Preferred sub caste
  • physical_status_id INT FK Preferred physical status
  • employed_in_id INT FK Preferred employment type
  • created_date DATETIME — Created timestamp
  • updated_date DATETIME — Last updated timestamp
  • is_active BOOLEAN — Status

Validations

profile_id

  • Mandatory
  • Must exist in registration_table
  • One profile can have only one active preference record

age_min

  • Mandatory
  • Minimum value: 18
  • Must be less than age_max

age_max

  • Mandatory
  • Maximum value: 80
  • Must be greater than age_min

marital_status_id

  • Mandatory
  • Must exist in marital_status_master
  • Must be active

state_id

  • Mandatory
  • Must exist in state_master
  • Must be active

district_id

  • Mandatory
  • Must belong to selected state
  • Must exist in district_master

city_id

  • Mandatory
  • Must belong to selected district
  • Must exist in city_master

education_id

  • Mandatory
  • Must exist in education_master
  • Must be active

occupation_id

  • Mandatory
  • Must exist in occupation_master
  • Must be active

star_id

  • Optional
  • Must exist in star_master if provided

raasi_id

  • Optional
  • Must exist in raasi_master if provided

sub_caste_id

  • Optional
  • Must exist in sub_caste_master if provided

physical_status_id

  • Mandatory
  • Must exist in physical_status_master

employed_in_id

  • Mandatory
  • Must exist in employed_in_master

created_date

  • Auto-generated
  • Cannot be edited

updated_date

  • Auto-updated when edited

is_active

  • Default value: true

  • Used to enable/disable preference

  • Each user must have only one active preference

  • Preference affects:

    • Daily recommendations
    • Search results
    • Match suggestions
  • Users can edit preferences anytime

  • Preference changes must reflect immediately in matchmaking

Actions #1

Updated by Varsha Venugopal 16 days ago

  • Status changed from New to In Progress
Actions #2

Updated by Varsha Venugopal 9 days ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF