Raible's Wiki: StrutsResumeArchitecture

At line 3 changed 1 line.

* Should skills and skill_groups be related to a single resume, or should they be separate? By separate, I mean to say that there are join-table (i.e. resume_skill_group and group_skills) that allow you to choose from a list of skills/groups to assign to your resume. The current architecture has a resume_id in the skill_group table and a group_id in the skill table. The potential problem with this is that a user has to manually enter their skill groups and skills and they can't pick from a pool. An example of a skill group is "Markup Languages" as demonstrated in [Russ's Resume|http://www.russellbeattie.com/Russell_Beattie_resume.html].

* Should skills and skill_groups be related to a single resume, or should they be separate? By separate, I mean to say that there are join-table (i.e. resume_skill_group and group_skills) that allow you to choose from a list of skills/groups to assign to your resume. The current architecture has a resume_id in the skill_group table and a group_id in the skill table. The potential problem with this is that a user has to manually enter their skill groups and skills and they can't pick from a pool. An example of a skill group is "Markup Languages" as demonstrated in [Russ's Resume|http://www.russellbeattie.com/Russell_Beattie_resume.html]. One idea I had is to have a bunch of skills/groups with null resume_id/group_id's and these would be the pool. When users want to assign them to their resume, new records would be inserted and then the user could customize any part of the group or skill.

Raible's Wiki

AppFuse

Other Applications

StrutsResumeArchitecture