savoirfairelinux-openerp team mailing list archive

[Daniel Reis <dgreis@xxxxxxx>]

Review: Needs Fixing

Gave a little more thought on this, and I find the use hr.employee a right design choice.

My reasoning:
* "Applications" are not "Applicants": the same Applicant can have many Applications.
* "Applicants" have a resume, and you can model them has "hr.employees" in a pre-hire/camndidate stage.
* Even better, with this design it's very simple to cover the use case where a Job posting can have both external (candidates) and internal (current employees) applicants!

The Applicant resume support would be a simple module, linking Application to hr.employees.

So it's, just the missing pot that needs fixing.
-- 
https://code.launchpad.net/~savoirfairelinux-openerp/openerp-hr/7.0-resume/+merge/195314
Your team Savoir-faire Linux' OpenERP is subscribed to branch lp:~savoirfairelinux-openerp/openerp-hr/7.0-resume.