Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Convert skills data structure #2805

Open
11 tasks done
mkimberlin opened this issue Jan 7, 2025 · 0 comments · May be fixed by #2810
Open
11 tasks done

Convert skills data structure #2805

mkimberlin opened this issue Jan 7, 2025 · 0 comments · May be fixed by #2810
Assignees
Labels
enhancement New feature or request server web-ui

Comments

@mkimberlin
Copy link
Member

mkimberlin commented Jan 7, 2025

I want to convert our data to use the same structure as Athena so that the two can be kept in sync.

Acceptance Criteria

  • A separate, nullable Boolean property on the MemberSkill entity is created to represent interested
  • Adjust the UI to make Interested in learning or doing more with this skill? a separate prompt and toggle on the bio, bound to the new interested property
  • Migrations have been created to adjust the database to contain the new property
    • Migrations correctly migrate convert any member skill entries with a 1 ("Interested") skill levels to a TRUE value in the new interested property
  • The slider on the user profile that represents skill levels should be converted to be four radio buttons: 0 - None, 1 - Novice, 2 - Practitioner, 3 - Expert
  • Migrations have been created to convert any member skill entry skill levels as follows:
    • 1 (Interested) -> TRUE in the interested column, 0 (None) in the skill level column
    • 2 (Novice) -> 1 (Novice) in the skill level column
    • 3 (Intermediate) -> 2 (Practitioner) in the skill level column
    • 4 (Advanced) -> 2 (Practitioner) in the skill level column
    • 5 (Expert) -> 3 (Expert) in the skill level column
@mkimberlin mkimberlin added enhancement New feature or request server web-ui labels Jan 7, 2025
@ocielliottc ocielliottc self-assigned this Jan 7, 2025
@ocielliottc ocielliottc linked a pull request Jan 8, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request server web-ui
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants