Skip to content

Convert skills data structure #2805

Description

@mkimberlin

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions