Maybe you should follow the advice of Dirty Harry: "A man's gotta know
his limitations."
A job interview:
1. Has an estimated start time and end time
2. Has an actual start time and end time
3. Can be cancelled, postponed, or rescheduled
4. Includes a number of parties in various roles
5. includes a number of communication events
6. Has a location
7. Has a status (the outcome of the interview)
So, a job interview includes communication events, but it is not a
communication event. If anything, it resembles a Work Effort.
-Adrian
On 7/27/2012 8:43 AM, Hans Bakker wrote:
On 07/27/2012 02:33 PM, Adrian Crum wrote:
A sales order includes products, but a sales order is not a product.
A job interview might include communication events, but a job
interview is not a communication event.
Using your logic, a sales order should be a communication event -
because it records a contact between a buyer and a seller.
If you don't understand the data model, then you shouldn't change it.
thank you Adrian, for the nice and polite conversation, this could be
the reason we cannot get other committers than just framework
programmers for whom the communication via this medium could be improved.
First you do not not provide any reasoning and now you assume your
knowledge is far superior....
if you think that an order and a product is similar to an interview
and communication event, then i wonder who is understanding the data
model.....
sorry Adrian, not sound nice.......
-Adrian
On 7/27/2012 8:22 AM, Hans Bakker wrote:
Adrian,
Since you still do not provide reasoning, let me explain a bit more
to you.
From the data model resource book volume 1 page 47:
*A communication event records any type of contact between parties
with a relationship for example,phonecalls, meetings, emails and so
on.*
Why does an interview not fit in this example list?
Regards,
Hans
On 07/27/2012 02:02 PM, Adrian Crum wrote:
I don't agree that a job interview is just another communication
event.
-Adrian
On 7/27/2012 7:59 AM, Hans Bakker wrote:
Adrian,
Just telling me it should stay, is not enough, you have to provide
reasoning for that.
my opinion is that a job interview is just a communication event
of the new type 'Jobinterview' with the roles already there. A job
interview can then already relate to other communication events of
type email or others.....
Hans
On 07/27/2012 01:46 PM, 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
