OFBiz - Re: Users - Party Education and Work Experience Entities

OFBiz › OFBiz - User

Re: Users - Party Education and Work Experience Entities

Posted by Si Chen-2 on Feb 20, 2006; 10:00pm
URL: http://ofbiz.116.s1.nabble.com/Users-Party-Education-and-Work-Experience-Entities-tp137515p137517.html

Vinay,

If you really feel that you need all that information about each
institution, then I suppose a Party/PartyGroup would be the best thing.
The degree completed might be an enumId so you can store several status
fields: PLANNED, IN_PROGRESS, COMPLETED, DEFERRED, etc. etc. While you
may not need all of them now, it might be nice to have this field
capable of accommodating different states, instead of just Y/N. Perhaps
you should have some other enum/state field to track whether this
particular qualification is verified or not, and if so, by whom and
when. (Again, if you need them.)

I guess I view a qualification and an education history to be similar,
with education history requiring more fields. For example, a Cisco
Network Engineer certification and a university degree share many
similar attributes. Some fields may not be used for certain
qualifications, but if the key approve/state codes, etc. are the same,
then the code for working through them would be much easier if it is one
entity.

The Resume, at least according to the Data Model Resource Book, is just
for text data. I think the idea is to keep a pure text version of
someone's resume for text-based searching (ie, anyone with "OFBiz"
experience?)

Don't let the lack of party qual types deter you--it's just because
nobody has contributed those yet. If you contribute some of your
changes I can look at them and put them in for you.

Si

Vinay Agarwal wrote:

>Si,
>
>If I understand it correctly, in order to accommodate my requirements,
>PartyQual would add the following fields
>1. Institution or company name
>2. Degree
>3. Student/employee id (needed for verification)
>4. Last job title or major
>5. Degree completed or not (I added it since I first sent the email)
>..etc
>
>I also think that institution/company contact information is also needed for
>verification although it may be found from public sources after spending
>some time. For this reason, I am leaning toward creating party for
>company/institution. That would change item 1 to partyId.
>
>Lastly, if there are only a few PartyQualType, how are they envisioned to be
>used? It seems to have its root in job/task requirements which has
>predefined qualifications. A party bidding for that job/task may state their
>experience with that qualification type. Resume seems to be a bit different
>functionality and therefore it may be better to keep them separate.
>
>Regards,
>Vinay
>
>-----Original Message-----
>From: [hidden email] [mailto:[hidden email]]
>On Behalf Of Si Chen
>Sent: Monday, February 20, 2006 11:21 AM
>To: OFBiz Users / Usage Discussion
>Subject: Re: [OFBiz] Users - Party Education and Work Experience Entities
>
>
>
>
>>Regarding using the PartyQual and PartyQualType, it would work for my
>>purpose but adds 2 entities (excluding institution/company) for each
>>education/experience instead of 1. I am OK with either approach and would
>>let others suggest the preferred approach.
>>
>>
>>
>>
>>
>Actually you would only be using PartyQual most of the time. You'd just
>be adding a seed data for PartyQualType.
>
>Si
>
>
>
>>Regards,
>>Vinay Agarwal
>>
>>-----Original Message-----
>>From: [hidden email] [mailto:[hidden email]]
>>On Behalf Of Chris Howe
>>Sent: Monday, February 20, 2006 10:20 AM
>>To: [hidden email]
>>Subject: [OFBiz] Users - Party Education and Work Experience Entities
>>
>>I agree with Adrian. It's much more reusable to use
>>the Party Entity. If there's information about
>>educational institutions that needs to be modeled
>>differently use the "hasTable" in the partyType
>>entity.
>>
>>============Adrian Crum wrote:
>>
>>Vinay's suggestion includes an "instituteId" field -
>>which I assume points to
>>information about an educational institution. That is
>>no different than making
>>the institution a party, so why introduce an
>>unnecessary entity? If Vinay's
>>"instituteId" can be accomodated by the Party entity,
>>then why make a custom
>>entity to tie the two together? Just use
>>PartyRelationship.
>>
>>It looks to me like the amount of data stored in
>>Vinay's suggestion is no
>>different than the one I suggested.
>>
>>
>>Si Chen wrote:
>>
>>
>>
>>
>>
>>>I agree with Jeffrey. There is no need to create
>>>
>>>
>>>
>>>
>>Party and
>>
>>
>>
>>
>>>PartyRelationship unless you are actively working
>>>
>>>
>>>
>>>
>>with that Party. If
>>
>>
>>
>>
>>>an employee went to a certain high school at some
>>>
>>>
>>>
>>>
>>point but that's that,
>>
>>
>>
>>
>>>and you don't have any other activities with that
>>>
>>>
>>>
>>>
>>high school, why
>>
>>
>>
>>
>>>create a Party for it?
>>>
>>>Si
>>>
>>>Blessing, Jeffrey J wrote:
>>>
>>>
>>>
>>>
>>>
>>>
>>>>Wouldn't this mean that every possible college,
>>>>
>>>>
>>>>
>>>>
>>university, school of
>>
>>
>>
>>
>>>>higher learning, etc. would potentially need to be
>>>>
>>>>
>>>>
>>>>
>>entered as an entity
>>
>>
>>
>>
>>>>into the database just to model education? This
>>>>
>>>>
>>>>
>>>>
>>sounds like a lot of
>>
>>
>>
>>
>>>>work just to represent the fact that someone has a
>>>>
>>>>
>>>>
>>>>
>>degree from
>>
>>
>>
>>
>>>>somewhere!
>>>>
>>>>-----Original Message-----
>>>>From: users-bounces at lists.ofbiz.org
>>>>[mailto:users-bounces at lists.ofbiz.org] On Behalf
>>>>
>>>>
>>>>
>>>>
>>Of Adrian Crum
>>
>>
>>
>>
>>>>Sent: Monday, February 20, 2006 11:00 AM
>>>>To: OFBiz Users / Usage Discussion
>>>>Subject: Re: [OFBiz] Users - Party Education and
>>>>
>>>>
>>>>
>>>>
>>Work Experience
>>
>>
>>
>>
>>>>Entities
>>>>
>>>>This seems to duplicate the PartyRelationship
>>>>
>>>>
>>>>
>>>>
>>entity. I would recommend
>>
>>
>>
>>
>>>>making
>>>>the educational institution a party (or party
>>>>
>>>>
>>>>
>>>>
>>group), create roles for
>>
>>
>>
>>
>>>>the
>>>>institution and student, then link them together
>>>>
>>>>
>>>>
>>>>
>>using
>>
>>
>>
>>
>>>>PartyRelationship.
>>>>
>>>>You'll still need an entity or property to persist
>>>>
>>>>
>>>>
>>>>
>>the degree.
>>
>>
>>
>>
>>>>Vinay Agarwal wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>Hello,
>>>>>
>>>>>
>>>>>
>>>>>I need party education and work experience entities
>>>>>
>>>>>
>>>>>
>>>>>
>>to build resume
>>
>>
>>
>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>like
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>structure for a party. The entities that I came up
>>>>>
>>>>>
>>>>>
>>>>>
>>for them are
>>
>>
>>
>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>detailed
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>below.
>>>>>
>>>>>
>>>>>
>>>>>1. Am doing it write?
>>>>>2. Is it worth putting them back on OFBiz?
>>>>>
>>>>>
>>>>>
>>>>>Regards,
>>>>>
>>>>>Vinay Agarwal
>>>>>
>>>>>
>>>>>
>>>>> <entity entity-name="Education"
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>package-name="org.ofbiz.grayzilla"
>>
>>
>>
>>
>>>>> title="Party
>>>>>
>>>>>
>>>>>
>>>>>
>>Education Entity">
>>
>>
>>
>>
>>>>> <field name="partyId"
>>>>>
>>>>>
>>>>>
>>>>>
>>type="id-ne"></field>
>>
>>
>>
>>
>>>>> <field name="instituteId"
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>type="id-ne"></field>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> <field name="degree"
>>>>>
>>>>>
>>>>>
>>>>>
>>type="id-long"></field>
>>
>>
>>
>>
>>>>> <field name="studentId"
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>type="id-long"></field>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> <field name="fromDate"
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>type="date-time"></field>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> <field name="thruDate"
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>type="date-time"></field>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> <prim-key field="partyId"/>
>>>>>
>>>>> <prim-key
>>>>>
>>>>>
>>>>>
>>>>>
>>field="instituteId"/>
>>
>>
>>
>>
>>>>> <prim-key field="fromDate"/>
>>>>>
>>>>> <relation type="one"
>>>>>
>>>>>
>>>>>
>>>>>
>>fk-name="EDU_PRTY"
>>
>>
>>
>>
>>>>>rel-entity-name="Party">
>>>>>
>>>>> <key-map
>>>>>
>>>>>
>>>>>
>>>>>
>>field-name="partyId"/>
>>
>>
>>
>>
>>>>> </relation>
>>>>>
>>>>> <relation type="one"
>>>>>
>>>>>
>>>>>
>>>>>
>>fk-name="EDU_INST"
>>
>>
>>
>>
>>>>>rel-entity-name="Party">
>>>>>
>>>>> <key-map
>>>>>
>>>>>
>>>>>
>>>>>
>>field-name="instituteId"
>>
>>
>>
>>
>>>>>rel-field-name="partyId"/>
>>>>>
>>>>> </relation>
>>>>>
>>>>> </entity>
>>>>>
>>>>>
>>>>>
>>>>> <entity entity-name="Experience"
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>package-name="org.ofbiz.grayzilla"
>>
>>
>>
>>
>>>>> title="Party
>>>>>
>>>>>
>>>>>
>>>>>
>>Experience Entity">
>>
>>
>>
>>
>>>>> <field name="partyId"
>>>>>
>>>>>
>>>>>
>>>>>
>>type="id-ne"></field>
>>
>>
>>
>>
>>>>> <field name="companyId"
>>>>>
>>>>>
>>>>>
>>>>>
>>type="id-ne"></field>
>>
>>
>>
>>
>>>>> <field name="titleLast"
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>type="id-long"></field>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> <field name="description"
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>type="id-vlong"></field>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> <field name="fromDate"
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>type="date-time"></field>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> <field name="thruDate"
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>type="date-time"></field>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>> <prim-key field="partyId"/>
>>>>>
>>>>> <prim-key
>>>>>
>>>>>
>>>>>
>>>>>
>>field="companyId"/>
>>
>>
>>
>>
>>>>> <prim-key field="fromDate"/>
>>>>>
>>>>> <relation type="one"
>>>>>
>>>>>
>>>>>
>>>>>
>>fk-name="EXPER_PRTY"
>>
>>
>>
>>
>>>>>rel-entity-name="Party">
>>>>>
>>>>> <key-map
>>>>>
>>>>>
>>>>>
>>>>>
>>field-name="partyId"/>
>>
>>
>>
>>
>>>>> </relation>
>>>>>
>>>>> <relation type="one"
>>>>>
>>>>>
>>>>>
>>>>>
>>fk-name="EXPER_COMP"
>>
>>
>>
>>
>>>>>rel-entity-name="Party">
>>>>>
>>>>> <key-map
>>>>>
>>>>>
>>>>>
>>>>>
>>field-name="companyId"
>>
>>
>>
>>
>>>>>rel-field-name="partyId"/>
>>>>>
>>>>> </relation>
>>>>>
>>>>> </entity>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>------------------------------------------------------------------------
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>_______________________________________________
>>>>>Users mailing list
>>>>>Users at lists.ofbiz.org
>>>>>http://lists.ofbiz.org/mailman/listinfo/users
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>_______________________________________________
>>>>Users mailing list
>>>>Users at lists.ofbiz.org
>>>>http://lists.ofbiz.org/mailman/listinfo/users
>>>>
>>>>_______________________________________________
>>>>Users mailing list
>>>>Users at lists.ofbiz.org
>>>>http://lists.ofbiz.org/mailman/listinfo/users
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>_______________________________________________
>>>Users mailing list
>>>Users at lists.ofbiz.org
>>>http://lists.ofbiz.org/mailman/listinfo/users
>>>
>>>
>>>
>>>
>>_______________________________________________
>>Users mailing list
>>[hidden email]
>>http://lists.ofbiz.org/mailman/listinfo/users
>>
>>_______________________________________________
>>Users mailing list
>>[hidden email]
>>http://lists.ofbiz.org/mailman/listinfo/users
>>
>>
>>
>>
>>
>
>_______________________________________________
>Users mailing list
>[hidden email]
>http://lists.ofbiz.org/mailman/listinfo/users
>
>_______________________________________________
>Users mailing list
>[hidden email]
>http://lists.ofbiz.org/mailman/listinfo/users
>
>
>

_______________________________________________
Users mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/users