|
V2 /
SchedulingV2.Scheduling HistoryHide minor edits - Show changes to output Changed line 17 from:
* [[config_ to:
* [[config_sessions]] (existing, needing revision, was 'config_event') - Definitions of [=SESSIONs=] for each [=EVENT=] Changed line 11 from:
* con_detail (existing) - Holds definitions for [=EVENTs.=] to:
* [[con_detail]] (existing) - Holds definitions for [=EVENTs.=] Changed line 13 from:
* config_venue (new) - A master summary of [=VENUEs=], with details on managing the venue - This table does not change from EVENT to EVENT to:
* [[config_venue]] (new) - A master summary of [=VENUEs=], with details on managing the venue - This table does not change from EVENT to EVENT Changed line 15 from:
* config_room (new) - A master summary of [=ROOMs=] defined for each VENUE - This table does not change from EVENT to EVENT to:
* [[config_room]] (new) - A master summary of [=ROOMs=] defined for each VENUE - This table does not change from EVENT to EVENT Changed line 17 from:
* config_event (existing, needing revision) - Definitions of [=SESSIONs=] for each [=EVENT=] to:
* [[config_event]] (existing, needing revision) - Definitions of [=SESSIONs=] for each [=EVENT=] Changed line 19 from:
* config_category (new) - Definitions of SESSION categories for each EVENT (also referred to as 'tracks') to:
* [[config_category]] (new) - Definitions of SESSION categories for each EVENT (also referred to as 'tracks') Changed lines 21-22 from:
* config_roomlayout (new) - [=VENUEs=] have predefined 'room layouts' they will use to help specify how a room should be configured for a specific SESSION. "panel" "dance floor" etc etc. This table specifies the roomlayout required for each SESSION. * config_department (new) - A way of categorizing groups within the [=SESSION=]. This is separate from 'tracks'. to:
* [[config_roomlayout]] (new) - [=VENUEs=] have predefined 'room layouts' they will use to help specify how a room should be configured for a specific SESSION. "panel" "dance floor" etc etc. This table specifies the roomlayout required for each SESSION. * [[config_department]] (new) - A way of categorizing groups within the [=SESSION=]. This is separate from 'tracks'. Changed line 26 from:
* reg_events - Associations between a registrant (rid), a EVENT (cid), and a SESSION (sid) This table would show if someone is subscribed to the SESSION (as in, added it to their favorites), or has signed up to attend the SESSION. Can also be used to assign staff to an SESSION (such as panel moderator, assistant, etc) to:
* [[reg_events]] - Associations between a registrant (rid), a EVENT (cid), and a SESSION (sid) This table would show if someone is subscribed to the SESSION (as in, added it to their favorites), or has signed up to attend the SESSION. Can also be used to assign staff to an SESSION (such as panel moderator, assistant, etc) Changed line 5 from:
* A SESSION is an activity within the to:
* A SESSION is an activity within the EVENT, such as a panel, dance, dinner, or presentation Changed lines 4-6 from:
* * * A VENUE is the location where the to:
* An EVENT is a single convention / meeting / get together. * A SESSION is an activity within the convention, such as a panel, dance, dinner, or presentation * A VENUE is the location where the EVENT is being held. Changed line 11 from:
* con_detail (existing) - Holds definitions for [= to:
* con_detail (existing) - Holds definitions for [=EVENTs.=] Changed line 13 from:
* config_venue (new) - A master summary of [=VENUEs=], with details on managing the venue - This table does not change from to:
* config_venue (new) - A master summary of [=VENUEs=], with details on managing the venue - This table does not change from EVENT to EVENT Changed line 15 from:
* config_room (new) - A master summary of [=ROOMs=] defined for each VENUE - This table does not change from to:
* config_room (new) - A master summary of [=ROOMs=] defined for each VENUE - This table does not change from EVENT to EVENT Changed line 17 from:
* config_event (existing, needing revision) - Definitions of to:
* config_event (existing, needing revision) - Definitions of [=SESSIONs=] for each [=EVENT=] Changed line 19 from:
* config_category (new) - Definitions of to:
* config_category (new) - Definitions of SESSION categories for each EVENT (also referred to as 'tracks') Changed lines 21-22 from:
* config_roomlayout (new) - [=VENUEs=] have predefined 'room layouts' they will use to help specify how a room should be configured for a specific * config_department (new) - A way of categorizing groups within the [= to:
* config_roomlayout (new) - [=VENUEs=] have predefined 'room layouts' they will use to help specify how a room should be configured for a specific SESSION. "panel" "dance floor" etc etc. This table specifies the roomlayout required for each SESSION. * config_department (new) - A way of categorizing groups within the [=SESSION=]. This is separate from 'tracks'. Changed line 26 from:
* reg_events - Associations between a registrant (rid), a to:
* reg_events - Associations between a registrant (rid), a EVENT (cid), and a SESSION (sid) This table would show if someone is subscribed to the SESSION (as in, added it to their favorites), or has signed up to attend the SESSION. Can also be used to assign staff to an SESSION (such as panel moderator, assistant, etc) Changed line 18 from:
** Name, summary, start time, end time, ROOM, room layout, owner, category, department, maxattendees, cost, open, to:
** Name, summary, start time, end time, ROOM, room layout, owner, category, department, maxattendees, cost, open, visible, service tags Changed line 18 from:
** Name, summary, start time, end time, ROOM, room layout, owner, category, maxattendees, cost, open, visible to:
** Name, summary, start time, end time, ROOM, room layout, owner, category, department, maxattendees, cost, open, visible Added line 22:
* config_department (new) - A way of categorizing groups within the [=EVENTs=]. This is separate from 'tracks'. Changed line 18 from:
** Name, summary, start time, end time, ROOM, owner, category, maxattendees, cost, open, visible to:
** Name, summary, start time, end time, ROOM, room layout, owner, category, maxattendees, cost, open, visible Added line 12:
** Name, location, start, end, website, email, comment, description Added line 14:
** Name, location, website Added line 16:
** Name, section-within-venue, dimensions, capacity Added line 18:
** Name, summary, start time, end time, ROOM, owner, category, maxattendees, cost, open, visible Added line 20:
** Name, summary Added line 22:
** Name, summary, setup time, teardown time, requirement notes. Added line 16:
* config_roomlayout (new) - [=VENUEs=] have predefined 'room layouts' they will use to help specify how a room should be configured for a specific EVENT. "panel" "dance floor" etc etc. This table specifies the roomlayout required for each EVENT. Changed lines 16-17 from:
to:
Changed line 18 from:
* reg_events - Associations between a registrant (rid), a convention (cid), and an event (eid). This table would show if someone is subscribed to the event (as in, added it to their favorites), or has signed up to attend the event. to:
* reg_events - Associations between a registrant (rid), a convention (cid), and an event (eid). This table would show if someone is subscribed to the event (as in, added it to their favorites), or has signed up to attend the event. Can also be used to assign staff to an event (such as panel moderator, assistant, etc) Changed line 13 from:
* config_room (new) - A master summary of ROOMs defined for each VENUE - This table does not change from CONVENTION to CONVENTION to:
* config_room (new) - A master summary of [=ROOMs=] defined for each VENUE - This table does not change from CONVENTION to CONVENTION Changed line 12 from:
* config_venue (new) - A master summary of VENUEs, with details on managing the venue - This table does not change from CONVENTION to CONVENTION to:
* config_venue (new) - A master summary of [=VENUEs=], with details on managing the venue - This table does not change from CONVENTION to CONVENTION Changed line 11 from:
* con_detail (existing) - Holds definitions for CONVENTIONs. to:
* con_detail (existing) - Holds definitions for [=CONVENTIONs.=] Added line 16:
* config_staff (new) - Definitions of registrants assigned to the EVENT, such as Panelists, staff members, crew, etc Added line 15:
* config_category (new) - Definitions of EVENT categories for each CONVENTION (also referred to as 'tracks') Added line 10:
!!Configuration tables Added lines 15-17:
!!Operational tables * reg_events - Associations between a registrant (rid), a convention (cid), and an event (eid). This table would show if someone is subscribed to the event (as in, added it to their favorites), or has signed up to attend the event. Changed lines 1-3 from:
The to:
The Scheduling module within CONGO allows an administrator to manage events / panels / sessions / activities within a convention. Changed line 3 from:
The Scheduling module within CONGO allows an event administrator to manage to:
The Scheduling module within CONGO allows an event administrator to manage events / panels / sessions / activities within an convention. Changed lines 3-15 from:
The Scheduling module within CONGO allows an event administrator to manage panels / sessions / activities within an event. to:
The Scheduling module within CONGO allows an event administrator to manage panels / sessions / activities within an event. !Terminology * A CONVENTION is a single convention / meeting / get together. * An EVENT is an activity within the convention, such as a panel, dance, dinner, or presentation * A VENUE is the location where the CONVENTION is being held. * A ROOM is a space or location within the VENUE !Table overview * con_detail (existing) - Holds definitions for CONVENTIONs. * config_venue (new) - A master summary of VENUEs, with details on managing the venue - This table does not change from CONVENTION to CONVENTION * config_room (new) - A master summary of ROOMs defined for each VENUE - This table does not change from CONVENTION to CONVENTION * config_event (existing, needing revision) - Definitions of EVENTS for each CONVENTION Added lines 1-3:
!Scheduling Overview The Scheduling module within CONGO allows an event administrator to manage panels / sessions / activities within an event. |