I don't see that pushing the LinkedIn data for Experience to a table and Academic to another would be a problem. I would rather concentrate on choosing the data model that better fits the use cases in OpenERP.
>From and end-user PoV, Experience, Academic and Certifications are different >things. And for an end-user, it's reasonable for Certifications to go alongside other skills: after all they are a just a special type of skill, that is independently certified. I think a user expects to see a "Experience" field, and an "Academic" field. Same for a resume report: you expect them to be in separate sections. Also, the fields needed to describe "Academic" and "Experience" are quite different, so there's also no rationale there for having them on the same table. -- https://code.launchpad.net/~savoirfairelinux-openerp/openerp-hr/7.0-experience/+merge/195315 Your team Savoir-faire Linux' OpenERP is subscribed to branch lp:~savoirfairelinux-openerp/openerp-hr/7.0-experience. -- Mailing list: https://launchpad.net/~savoirfairelinux-openerp Post to : [email protected] Unsubscribe : https://launchpad.net/~savoirfairelinux-openerp More help : https://help.launchpad.net/ListHelp
