5.1.1.3.5 Organization admins can list multiple volunteer skills/resources needed about allready HOT 16 CLOSED

I'll try this one

from allready.

The skills/resources being listed - are they associated with a campaign, activity, or task?

from allready.

Thanks, at the activity level

From: John Strobelmailto:[email protected]
Sent: ‎8/‎8/‎2015 8:28 AM
To: HTBox/allReadymailto:[email protected]
Cc: Tony Surmamailto:[email protected]
Subject: Re: [allReady] 5.1.1.3.5 Organization admins can list multiple volunteer skills/resources needed (#36)

The skills/resources being listed - are they associated with a campaign, activity, or task?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/36#issuecomment-128990520.

from allready.

I discussed this feature with Jim and Richard. For now, we're going to defer the resource part of this feature. Below is my understanding of the skill system we'll be implementing - please feel free to comment on, correct, question, or add to any part of it!

• Skills will be hierarchical (i.e. Medical -> MD -> surgeon, Medical -> CPR Certified)
• Skills will exist in pre-defined templates
  • The administrator will be able to import the template into a campaign
  • The administrator will be able to search for templates
  • The administrator will be able to customize the templates
  • The administrator will be able to select the lexicon for the templates (such as using the UN names or not)
• Skills will be attributed to users
  • The administrator can add skill to user
  • The user can add the skill to themselves
    • Possible verification/override function? TBD
• Skills will be assignable to Activities
• Skills will be assignable to Tasks

from allready.

I'll take over ownership of this issue.

http://blog.stevensanderson.com/2010/07/12/editing-a-variable-length-list-knockout-style/

from allready.

Can somebody clarify the difference (if any) in this context between a skill and a resource? In @DevUnit1's comment, "resources" are not mentioned. I want to make sure I'm not missing something.

from allready.

@mheggeseth - per discussion we are focusing on skills only and delaying any work on resources to a later date. Therefore you are not missing anything and the clarification from @DevUnit1 is complete (until we bring resources back into it at a later date). Thanks.

from allready.

@tonysurma can you clarify what "Skills will exist in pre-defined templates" means? Is this like having "skill presets"? E.g. My organization runs a campaign each semester during finals to deliver pizza and wings to hungry college students and each time we need the same skill sets so populate that from a template.

Or does "template" mean something else in this case? Can you give an example of how a "template" would be used?

from allready.

Also, does associating skills to Activities and Tasks still include the "optional date ranges and locations {‘skill/resource A’ needed [from ‘x’ to ‘y’ date range] [in ‘z’ location scope]}" requirement? Or is that more of a "resource" thing?

from allready.

@mheggeseth "date ranges and locations" that is more of a resource thing so ignore

@mheggeseth the skills templates is referencing the same idea from the crisischeckin project meaning that the goal is to have 'classification hierarchies' like the UN has the cluster system etc so an admin can say this campaign uses the blahblah hieararchy break down and then pick from there
I think for this timeframe we can skip the template hierarchy stuff and just make them ad-hoc entry and we can later add in template hierarchies and retro as needed - both to make this easier for now and so we don't have to survey all hierarchies or make a big CRUD interface for that (also we may be able to steal it from crisischeckin once that is done)

from allready.

I've got some working bits and a plan for knocking the rest of this one out (at least at the limited scope we have defined). Quick sanity check:

• Skill model just has a name and references a single parent skill (if applicable)
• Skills will have CRUD views
  • Split off into new issue/PR
• A many-to-many model will be created for each skill association. These models do nothing more than associate entities but could be extended in the future.
  • Activities to Skills
  • Tasks to Skills
  • Users to Skills (create separate issue/PR)
• Editing associated skills in the views will be done via a simple list of drop-downs
  • Knockout will facilitate adding/removing skills.
  • KO validation: any set of skills will be allowed for an activity/task/user so long as a given skill appears at most once in the set. The Save button will be disabled if this is violated.
  • Upon saving, controller will ensure deletion of any skill associations that are no longer on the activity/task/user in addition to saving the current associations.

Anybody have any issues/concerns/comments about this?

from allready.

quick review tells me this all looks good from a requirements point of view @mheggeseth

from allready.

@mheggeseth Is this one complete then?

from allready.

@MisterJames Technically no. Waiting on #112

from allready.

@mheggeseth Are you still working on #112?

from allready.

Closing this, as the only remaining task is detailed in #112, which references this issue.

from allready.