Conflict System
From Pentabarf
The Conflict System of Pentabarf checks for common errors, enforces constraints and keeps the database in a consistent state. Whether a conflict is triggered can be setup in the conflict editor. You can define a severity for each conflict for every Conference Phase.
Conflicts are separated into 5 groups (person, event_person, event_person_event, event, event_event). There is a master procedure for each group which collects the conflicts of this group. Each conflict is implemented as stored procedure in either sql or plpgsql.
Currently the following conflicts are implemented:
Contents |
Person conflicts
- Speaker or moderator without contact email address
- Person with inconsistent public link
- A confirmed speaker or moderator has no abstract
- A confirmed speaker or moderator has no description
- The abstract length of a person is above the recommended size
- The description length of a person is above the recommended size
Event conflicts
- Accepted and confirmed event without confirmed speaker
- Event without coordinator
- Accepted Event with incomplete schedule data (day,room,time)
- Event with missing tag
- Event with incorrectly named tag
- Accepted event without paper
- Event with inconsistent public link
- Event with no language set
- Event with no track set
- Event is in a language which is not a conference language
- An accepted event has no abstract
- An accepted event has no description
- Accepted event without slides
- The abstract length of an event is above the recommended size
- The description length of an event is above the recommended size
- Accepted and confirmed event without timeslot
- Accepted and unconfirmed event with timeslot
- Accepted event with unknown paper state
- Accepted event with unknown slides state
Event Person conflicts
Conflicts resulting from a person being bound to a specific event.
- Speaker or moderator does not speak the language of the event
- A confirmed speaker or moderator has an event before arrival
- A confirmed speaker or moderator has an event after departure
Event Person Event conflicts
Conflicts resulting from a person being bound to two different events.
- Speaker or moderator at two simultaneous events
- Speaker or moderator is visitor at another event at the same time
- A person is visitor of two simultaneous events
Event Event conflicts
Conflicts between two diffent events.
- Two events are in the same timeslot in the same room
- Event with duplicate tag
