There are a number of logical constraints that can be applied. Not sure if these should be in the PSM or in the template (or both)
- I assume that a contact person is a person in the organization of interest, so I would expect to provide either a contractor or a contractorContact (that would provide both the person and the organization) but unlikely to provide both. Similarly with contractee
- We probably need a constraint that startDate should be before endDate
- assignedTo dates cannot be assigned if there is no assigned to supplied so constraint them so they are only valid if assignedTo is supplied (also need to consider date issue here)
> - I assume that a contact person is a person in the organization of interest, so I would expect to provide either a contractor or a contractorContact (that would provide both the person and the organization) but unlikely to provide both. Similarly with contractee
The contractor is the organization that the contract is with,
The contractorContact is the point of contact in that organization.
You need optioanlly both - not either or.
The current structure allows you to identify a contractor to be organizationA and a contractorContact to be personB in organizationB (unrelated to organizationA). I was proposing that we change this so that you either supply a contractor or a contractorContact which provides both the person and organization.
It is possible to have a contact for a contract in a different organization to the organization that the contract is with.
The contact may be a legal representative that is a third party.
CCB Call 2013-01-07
Accept to add a constraint that start date is before the end date