|
Main /
TerminologyMain.Terminology HistoryHide minor edits - Show changes to output Changed line 15 from:
** FullWeekend - A Registrant who has full access to the event, all weekend to:
** [=FullWeekend=] - A Registrant who has full access to the event, all weekend Changed line 19 from:
Templates are used for preformatted text, usually when sent in email. Any number of templates may be defined, and they can contain variables that will be substituted in when the email or the page is generated. See the template editor for a list of available variables to:
Templates are used for preformatted text, usually when sent in email. Any number of templates may be defined, and they can contain variables that will be substituted in when the email or the page is generated. See the template editor within CONGO for a list of available variables Changed lines 36-37 from:
* CheckedIn (Registrant Status\\ A person who has been marked as 'checked in' - to:
* [=CheckedIn=] (Registrant Status\\ A person who has been marked as 'checked in' - i.e., has picked up their badge. Changed line 39 from:
Every time a transaction happens within that involves money, an Invoice is generated. Invoices track payments through CONGO. A single invoice may be responsible for registering multiple people. to:
Every time a transaction happens within CONGO that involves money, an Invoice is generated. Invoices track payments through CONGO. A single invoice may be responsible for registering multiple people. Changed line 47 from:
Registrants can be 'linked' together so one person can see the registration status of another, or register them. A common link setup would be parents who are registering multiple children. When they log into the public interface, their 'linked' registrants will show up and can be registered all at once. This can also be used for groups. to:
Registrants can be 'linked' together so one person can see the registration status of another, or register them. A common link setup would be parents who are registering multiple children. When they log into the public interface, their 'linked' registrants will show up and can be registered all at once. This can also be used for groups. Links can be created in the public interface by the registrant (using the Link function), or can be maintained by an Operator in the administrative interface. Changed line 53 from:
to:
Anything that happens to a Registrant is recorded in their History. Registrations, transfers, emails, payments, all are visible on the History tab for each Registrant Changed lines 57-60 from:
A Registrant that has full control over a CONGO environment, including granting / revoking access for other users. All Administrators are by default Operators (See Main/RegistrantProperties ) to:
A Registrant that has full control over a CONGO environment, including granting / revoking access for other users. All Administrators are by default Operators (See Main/RegistrantProperties ) !!See Also * [[Main]] Changed line 21 from:
A discount code can be configured by the Administrator to allow special circumstances on registrations, such as a discount, making a registration type only avialable to people who have the discount code, etc. See [[DiscountCodesHowTo]] for details on setting up discount codes to:
A discount code can be configured by the Administrator to allow special circumstances on registrations, such as a discount, making a registration type only avialable to people who have the discount code, etc. See [[V2/DiscountCodesHowTo]] for details on setting up discount codes Changed line 14 from:
When a Registrant signs up to attend an Event, they register for the event using a Registration Type. Registration Types are used by event organizers to set different pricing and access levels for the event. Here are some example Registration Types: to:
When a Registrant signs up to attend an Event, they register for the event using a Registration Type. Registration Types are used by event organizers to set different pricing and access levels for the event. Registration Types have their own individual pricing, so when a person buys a registration on line, they will be presented with the appropriate amount. Here are some example Registration Types: Deleted line 17:
Changed lines 13-30 from:
* Template * Discount Code * Session * Venue * Room * Category * Subscribed * Registered * Badged * CheckedIn * Invoice * COMP * Badge * Banner * Link * Note * Property to:
* Registration Type\\ When a Registrant signs up to attend an Event, they register for the event using a Registration Type. Registration Types are used by event organizers to set different pricing and access levels for the event. Here are some example Registration Types: ** FullWeekend - A Registrant who has full access to the event, all weekend ** Friday - A single day pass ** Exhibitor - A person who has access to the exhibitor areas as well as full attendance. Registration Types have their own individual pricing, so when a person buys a registraiton on line, they will be presented with the appropriate amount. * Template\\ Templates are used for preformatted text, usually when sent in email. Any number of templates may be defined, and they can contain variables that will be substituted in when the email or the page is generated. See the template editor for a list of available variables * Discount Code\\ A discount code can be configured by the Administrator to allow special circumstances on registrations, such as a discount, making a registration type only avialable to people who have the discount code, etc. See [[DiscountCodesHowTo]] for details on setting up discount codes * Session (in Scheduling)\\ A single function within an Event. Sometimes called Panels, Talks, etc. * Venue (in Scheduling)\\ The location an Event is held in, such as specific hotel or convention hall. * Room (in Scheduling)\\ An identifier specific to a Venue that defines a room's specific characteristics (size, location, accessibility, services offered, etc) * Category (in Scheduling)\\ When doing sheduling, Categories may be set up to organize Sessions into groups. For example, a Session may be part of the "Writers" grouping. * Subscribed (Registrant Status)\\ A person who has logged into the event via the public interface, but has not yet registered. * Registered (Registrant Status)\\ A person who has successfully completed the registration process for the event (Registered and Paid) * Badged (Registrant Status)\\ A person who has had a badge printed for them. * CheckedIn (Registrant Status\\ A person who has been marked as 'checked in' - ie, has picked up their badge. * Invoice\\ Every time a transaction happens within that involves money, an Invoice is generated. Invoices track payments through CONGO. A single invoice may be responsible for registering multiple people. * COMP\\ A general term used in many events to refer to someone who has been granted free admission to the event. * Badge\\ A printed item that can contain artwork, information about the attendee, etc. Usually displayed on a lanyard or clip while at the event. * Banner\\ A bit of text that can be printed on a badge related to a specific registration type. For instance, it is common for day badges to have large text saying the day the badge is limited to printed on the badge. * Link\\ Registrants can be 'linked' together so one person can see the registration status of another, or register them. A common link setup would be parents who are registering multiple children. When they log into the public interface, their 'linked' registrants will show up and can be registered all at once. This can also be used for groups. * Note\\ Notes may be attached to a Registrant to convey information about that registrant, such as comments, information the checkin person may need, etc. Notes are only visible to Operators or Administrators. A Note may be flagged as a 'registration note', which means it will be prominently displayed to any Operator that looks up that registrant. * Property\\ Properties may be set up to add additional information to registrant records. The Properties system is better described in the [[Main/RegistrantProperties]] page. * History\\ ANything that happens to a Registrant is recorded in their History. Registrations, transfers, emails, payments, all are visible on the History tab for each Registrant * Operator\\ A Registrant that has access to the CONGO maintenance / administrative page (See Main/RegistrantProperties) * Administrator\\ A Registrant that has full control over a CONGO environment, including granting / revoking access for other users. All Administrators are by default Operators (See Main/RegistrantProperties ) Changed lines 5-8 from:
* Registrant * Event * Event ID or CID to:
* Registrant\\ A registrant is a single person within the CONGO system. A single registrant may attend multiple Events, but there should be only one Registrant associated with any individual * Registrant ID or RID\\ CONGO assigns a unique number to every Registrant. This number is neve re-used, and stays with the Registrant from event to event. * Event\\ An Event can be thought of as a 'convention','conference', 'meeting', or the like. It is usually the thing you are inviting people to attend. A single Event may have (and usually does) have multiple Sessions going on within it (such as panels or talks). * Event ID or CID\\ Each Event is assigned a unique ID when it is created. This ID is sometimes also referred to as a CID (or 'Convention ID', a holdover from older versions of CONGO. Changed lines 3-24 from:
Registration Type Template Discount Code Session Venue Room Category Subscribed Registered Badged CheckedIn Invoice Registrant Registrant ID or RID Event ID or COMP Badge Banner Link Note Property to:
CONGO uses a lot of specific terminology when talking about running an event. Here's a summary of terms you'll likely encounter while working with the system. * Registrant * Registrant ID or RID * Event * Event ID or CID * Registration Type * Template * Discount Code * Session * Venue * Room * Category * Subscribed * Registered * Badged * CheckedIn * Invoice * COMP * Badge * Banner * Link * Note * Property Added lines 1-24:
!!CONGO Terminology Event Registration Type Template Discount Code Session Venue Room Category Subscribed Registered Badged CheckedIn Invoice Registrant Registrant ID or RID Event ID or CID COMP Badge Banner Link Note Property |