Also, the PerformanceReview model needs to be fixed in the same way as
JobInterview - relate parties to it using an intersection entity.
Taking it even further, JobInterview and PerformanceReview could be
based on a more generic entity - something like PartyInterview, then
each subtype can add its own properties.
-Adrian
On 7/27/2012 7:46 AM, Adrian Crum wrote:
I agree that employee leave belongs in the Work Effort entities.
The JobInterview entity should stay, but its model needs to be fixed.
There should be a JobInterviewRole entity that connects the
JobInterview with Party, then the jobIntervieweePartyId and
jobInterviewerPartyId fields can be removed. We can also add a
JobInterviewComm entity that connects JobInterview to communication
events.
-Adrian
On 7/27/2012 7:17 AM, Hans Bakker wrote:
Replacing them with the indicated entities......
On 07/27/2012 12:27 PM, Adrian Crum wrote:
I don't understand the question. Are you proposing removing those
entities?
-Adrian
On 7/27/2012 4:42 AM, Hans Bakker wrote:
we intend to reduce the number of entities in HR:
EmplLeave
EmplLeaveReasonType
EmplLeaveType -> workeffort+related-entities so it also appears on
the calendar
JobInterview
JobInterviewType -> communication event and related entities
any comments or suggestions?
Regards,
Hans
