-
Notifications
You must be signed in to change notification settings - Fork 2
Home
Welcome to the profile_service_react wiki!
A single profile-as-a-Service that contains core user data accessible across the OADW and by other authenticated applications. The profile will contain biographic, geographic, organizational, skill, relational and interest-related data as well as demographic data in a reserved partition. Users will have full control over which elements of their data will be used or displayed in each element of the OADW.
The profile will include a flexible set of fields and relationships between users as well as serving as a hub for an array of recommendation micro-services.
Intent is that this will be a single profile for Government of Canada employees and OADW users that is usable by any authorized application. Could eventually be expanded to a single universal profile.
Profile: Core object representing a person or organization as part of the OADW. Linked to authentication service.
Sub-objects: Data Fields, Relationships
Data Fields: elements of the Profile that can be accessed through other applications. Each object should have robust permission sets that gives users the option of allowing other applications to access and use the data on a one time, time-limited or ongoing basis.
These access permissions should be tracked and easily displayed to the user with a simple interface for adjusting permissions.
Logs of data calls should be kept and should be easily viewed by the user.
E.g.: The core collaboration app would request permission to access and display the users name, avatar, about me, education, work history, relationships, geo-data, work portfolio and interests (may be more too). The user would be able to authorize the application for all or some of these elements.
Each application would let the user know of the impact of not allowing access to some data elements: “This app uses geo-data to help you find open work places and the location of your colleagues. By refusing to provide access to this data, you won’t be able to use this functionality.”
Applications would be able to add new Data Fields to a Profile with the user’s permission. E.g.: adding a unique identifier for a separate system like health care.