These define the start and end times of each day of yuor Convention.
You must have the everything ConventionPrivilege to access this.
Convention Days are accessed via /api/conventionday.
See "Object Properties" in Introduction for basic shared properties.
Complete details in ConventionDayProperties.
See "Related Objects" in Introduction for how to use them.
The Convention this conventionday belongs to.
See "Relationships" in Introduction for how to use them.
Manages the relationship between convention days and BadgeTypes.
The list of BadgeTypes that use this convention day.
The list of DayParts that are within this convention day.
The list of Shifts that are on this day.
The list of Slots that are within this day.
The services used to fetch and manipulate convention days.
Searching all convention days across conventions is no longer supported. To search on a single convention see "Relationships" in Convention.
POST /api/conventionday
Returns the same as a normal read.
GET /api/conventionday/xxx
Returns:
{
"id" : "xxx",
"name" : "Friday",
...
}
PUT /api/conventionday/xxx
Returns the same as a normal read.
DELETE /api/conventionday/xxx
Returns:
{
"success" : 1
}
Copy the volunteer Shifts from one convention day to this one. Requires the volunteers privilege.
POST /api/conventionday/xxx/copy/shifts
Returns:
{
"success" : 1,
"copied_count" : [integer]
}
POST /api/conventionday/xxx/dayparts/add
DayPart creation no longer accepts parameters for Day Part fields, such as name, start_date, and so on. DayPart names are created automatically and times are also limited according to the Convention Day event schedule time range and the Convention's slot_duration.
Where to add the daypart. Can be start, end, or all; defaults to all. start will add a single daypart closest to Convention Day start (where missing); end will add a single daypart closest to Convention Day end (where missing). all will fill in all the ConventionDay's missing dayparts.