I am working on a relatively small project for our internal staff using Confluence, to collect staff skills information. A brief description of the application process:
- User logs in, and answers some specific questions about their skills. For sake of discussion, let's say whether they speak French, Spanish, or Swahili, and whether they have experience with Confluence, Jira, or Snowboarding. The skills we need are pulled from lookup tables in a secondary data source.
- After the questions are answered, the answers are recorded as a Skills Profile, and I have been thinking of this as a Confluence page, a skills profile for that person.
- Another staff member reviews the person's skills page, verifying that they speak Swahili and have used Jira. Once vetted, the page is marked as "approved".
- Other users can search or browse "approved" skills profiles for particular skills they need, and connect those people through their Confluence profile information.
The main difference between this and some random skills you might put in the Confluence profile is that they are looking for very specific skills, the skillset being examined may change over time as needs change, and the approval process to vet the skills is somewhat rigorous. You can't just say "I know Spanish" if you know how to order a chicken chimichanga at Taco Bell.
Part 1, I've been able to get somewhere using the {card} and {deck} macros from Adaptavist to create a tabbed form, and using the SQL plugin I've been able to dynamically generate the forms I need. I've generated those forms using the FormMailNG plugin, but form mail will not work as an option, because we really want searchable pages, not e-mails flying about.
So, my general question is how would you approach this problem? What tools would you use or have you used to solve similar problems? What plugins work well and would fit in with the goals of this effort? My preference here is to pull from the pull of available plugins, rather than developing a new, one-off plugin for this effort. Also, budget constraints mean a preference for low-cost or no-cost plugins, rather than some fancy set of expensive plugins.
Looking forward to your suggestions, and a lively discussion!
Sincerely,
Chris van Hasselt, FHI360
