Allows users to submit ideas for Events that they would like to run.
You must have the scheduling
ConventionPrivilege to manage this,
but you need no special privilges to submit them or update the ones you created.
Event Submissions are accessed via /api/eventsubmission
.
See "Object Properties" in Introduction for basic shared properties.
Complete details in EventSubmissionProperties.
Field max_tickets
is deprecated and replaced in use by max_quantity
.
See "Related Objects" in Introduction for how to use them.
The DayPart this event submission would like to start at if the preferred daypart is not available.
The Convention this event submission belongs to.
The DayPart this event submission would like to start at.
The EventType this event submission will conform to.
See "Relationships" in Introduction for how to use them.
The list of Events that was generated from this submission.
The list of Users with EventReservations for this event (if any).
EventReservations for this event (if any).
EventSubmissionSessions created for this event submission. Note this set does not include the information for the submission's first session, which is stored with the submission.
See "Includes" in Introduction for how to use them.
Returns 1
if the event submission has an existing Event,
0
if not.
Adds two additional properties: is_multi_session
,
which is if the event has more than one session,
and is_multi_day
,
which is if the sessions occur on more than one conventionday.
1
if true,
0
if not.
Note that events have a session_count
field which will show the total number of separate sessions the event has,
and this is always returned with an object read.
Returns an array of reservations in the following format:
[ { "name" : "John Q. Normal", "champion" : 1, }, { .. } ]
The services used to fetch and manipulate event submissions.
Searching for event submissions across all conventions is no longer supported. To search on a single convention see "Relationships" in Convention.
POST /api/eventsubmission
Returns the same as a normal read.
GET /api/eventsubmission/xxx
Returns:
{ "id" : "xxx", "name" : "The Captain is Dead", ... }
PUT /api/eventsubmission/xxx
Returns the same as a normal read.
DELETE /api/eventsubmission/xxx
Returns:
{ "success" : 1 }
Queues this submission for scheduling.
POST /api/eventsubmission/xxx/queue
Rejects this submission.
POST /api/eventsubmission/xxx/decline
A message the submitter will be able to see.
Move this submission to the In-Review queue.
POST /api/eventsubmission/xxx/review
A message the submitter will be able to see.
Ask for changes for this submission.
POST /api/eventsubmission/xxx/change
A message the submitter will be able to see.
Adds a reservation to an EventSubmission. For users without elevated privileges, the only Users who can be given a reservation are the user's TTE friends (see Friendship).
POST /api/eventsubmission/xxx/attendee-reservation
Returns the same as a normal read.
Removes a reservation from an EventSubmission. See also EventSubmissionReservation.
DELETE /api/eventsubmission/xxx/attendee-reservation/:reservation_id
Returns the same as a normal read.