search

moqui / mantle-udm

Mantle Universal Data Model
http://www.moqui.org/mantle.html
Other
41 stars 58 forks source link

[Discussion] Modeling PartyQualification #34

Closed shendepu closed 6 years ago

shendepu commented 7 years ago

Currently the PartyQualification defined as 

<entity entity-name="PartyQualification" package="mantle.humanres.ability" use="nontransactional">
    <field name="partyId" type="id" is-pk="true"/>
    <field name="qualificationTypeEnumId" type="id" is-pk="true"/>
    <field name="fromDate" type="date-time" is-pk="true"/>
    <field name="thruDate" type="date-time"/>
    <field name="description" type="text-medium"/>
    ...
</entity>

Would it be better to define it in the pattern like ContactMech as abstract entity which has PostalAddress, TelecomNumber extends it. In this pattern, for the QualificationTypeEnumId such as EXPERIENCE, DEGREE, there may be concrete entity to extend PartyQualification and fill with more details.

e.g. for qualificationTypeEnumId DEGREE, a Education entity may be defined to maintain school, major, degree information, start date, end date, for EXPERIENCE, a WorkExperience entity may be defined to maintain employer info, position, department, start date, end date, job detail, responsibility etc.

And it seems that fromDate and thruDate in PartyQualification should not be used to represent duration (start, end date) of acquiring the qualification since they are used in the pattern for telling it is expired or not.

jonesde commented 6 years ago

Closing as part of general cleanup for the move to HiveMind and for no recent activity on this issue. If this comes up again or anyone wants to pursue it feel free to create a request on moqui.org. For more information see:

https://www.moqui.org/m/docs/moqui/Community+Guide