There are a number of details that are specific to the agent-prospect relationship that currently stored in the prospect record. We need to separate things out so that most of this relationship specific stuff will live in a mongo collection that is called by ui-api and merged with search results before being returned to ui. The initial test case for this will be:
[ ] interactions around user edit fields (i.e. name, etc)
[ ] user input around prospect demographics
Context
there will be user interaction that will allow a user to submit how they know the particular prospect (i.e. "How do you know Sarah?" (allow more than one button to be selected, e.g. FRIEND, CLASSMATE), "How well do you know Sarah?" and change slider to three buttons (only one can be selected at a time): Never Met (Cold), Acquaintance (Warm), Very Well (Hot))
Possible Implementation
MONGO WAY:
[ ] ui: add interaction component and have them hit correct ui api endpoints
Detailed Description
There are a number of details that are specific to the agent-prospect relationship that currently stored in the prospect record. We need to separate things out so that most of this relationship specific stuff will live in a mongo collection that is called by ui-api and merged with search results before being returned to ui. The initial test case for this will be:
Context
there will be user interaction that will allow a user to submit how they know the particular prospect (i.e. "How do you know Sarah?" (allow more than one button to be selected, e.g. FRIEND, CLASSMATE), "How well do you know Sarah?" and change slider to three buttons (only one can be selected at a time): Never Met (Cold), Acquaintance (Warm), Very Well (Hot))
Possible Implementation
MONGO WAY:
NEO4J WAY: