Feature Description:
Currently, we are able to store contacts, but we want to be able to distinguish between clients/caseworkers/coworkers/ etc.
Proposed Solution:
Add a couple more fields to each contacts entry that contains information on the relationship.
{
person: <webId>, //required: the webId of the connected person
pod: <podUrl>, // optional: the person's preferred pod url. If not present, we fetch the first pod url on the profile document. If that's not present, we derive it from the webid
relationship: <client / case manager / associated organization>, // optional: an enum value describing how the user is related to this person
relationship_status: <active / archived / etc>, // optional: an enum describing if the user is actively working with the person, or if this is a dormant or past relationship
}
Feature Description: Currently, we are able to store contacts, but we want to be able to distinguish between clients/caseworkers/coworkers/ etc.
Proposed Solution:
Add a couple more fields to each contacts entry that contains information on the relationship.