| Page Properties | ||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
The user profiling module should interact with the activity tracking components in order to ensure that the needed data is produced (e.g. tracking of time spent on decks)
The following table lists static data (manually specified by the user), i.e. user demographic and contextual data, that could be relevant for other WP3 learning analytics as well.
| Name | Description | Status | Extra info | Comments |
|---|---|---|---|---|
| country | user's country | active | ||
| gender | user's gender | inactive | Could be introduced on user profile creation | |
| age | user's age (e.g. 0-20, 21-30,31-40...) | inactive | Could be introduced on user profile creation | |
| education | user's highest education | inactive | Could be introduced on user profile creation | |
| disability | boolean - whether user has any disability | inactive | Could be introduced on user profile creation |
Action Items
- Extend User Data Model for User Profiling and Skills Recognition
- Implement/Extend API routes in User Service for CRUD methods
- Implement data ingestion controllers using user engagement data (i.e. from activity service) and static data (from user service and deck service)
- Design and implement algorithms for skills extraction/recognition