ConflictsSelfAssign This is accomplished through the implementation of a series of SelfAssign Rules that the Chapter However, there are many situations where Assignors do have to be involved in making Assignments, for all sorts of predictable and unpredictable reasons. Whenever this happens, it becomes very possible (and often times, quite likely) that the Assignor making a "manual Assignment" could, inadvertently, assign a Referee to an Assignment that is in violation of one or more SelfAssign Rules for the Assignment. The Assignor does have mechanisms (Assignor: Assignment-SelfAssign) to mitigate this, but...the fact remains that the Assignment schedule is, periodically, simply in conflict. And, of course, when there are a large number of Referees, Matches, and corresponding Assignments it is quite a difficult task for a human Assignor to double check all aspects of each Assignment for each Referee. Feature=Conflicts The basic concept is that if we can forewarn the User (Referee, Assignor, Administrator, ...), then we can head off an Assignment problem BEFORE the Match date arrives. Think of Feature=Conflicts as an early warning system for one or more Assignments that have potential to be a problem and MAY need looking into. The Feature is customized via Setting (Rules.Conflicts) and can be installed in the Chapter site in full or partial implementation (depending upon the Chapter's Policies and Webmaster instructions). | ||||||
|