I would like to suggest to replace the jobinterview , jobinterviewtype
with communicationEvent and communicationEventType and add the
relationship entity CommunicationEventJobReq.
in this case the relation to workeffort, content and attribute are
already there....
Regards,
Hans
On 05/25/2012 05:04 PM, Chatree Srichart wrote:
> Hi Community
>
> I see there is only one entity about an interview which specific for job
> interview named JobInterview.
> In an organization might have more than one types of interview, for
> example, complain interview or interview to get more information from an
> employee.
> I am thinking about creating new entities:
>
> Interview
> - interviewId
> - interviewTypeId
>
> InterviewType
> - interviewTypeId
> - description
>
> InterviewParty
> - interviewId
> - partyId
> - roleTypeId
> - fromDate
> - thruDate
>
> InterviewWorkEffort
> - interviewId
> - workEffortId
>
> InterviewContent
> - interviewId
> - contentId
>
> InterviewAttribute
> - interviewId
> - attrName
> - attrValue
>
> some thing like these.
>
> Any suggestion?
>
> Regards,
> Chatree Srichart
>
Locked
