The Edit Fields tool offers powerful options to customize the information you receive from your conference delegates.
Administrators can use this tool to quickly and easily change the questions which new users are asked to answer on sign up, make specific questions mandatory, and change the wording of these lines to suit your conference and your organizations terminology.
To access this tool, go to Tools -> Users -> Edit Fields. You can select from Conference Sign-up (32 & 90), which pertains to the user sign up screen, as well as registration fields and several CID-wide conference settings, or use the drop-down to modify Membership if you use it (113).
It is important to note that all of the different tools in the system that require user information (e.g., abstract submission, registration, membership) will pull these data from user profiles when appropriate. This saves our users from having to enter their details over and over again. This link is reciprocal, as information stored in the user profile is added to a form, and details added to a form are stored in the profile. In order to accommodate the specific needs of each tool, we allow you to control what information each form is set up to collect. This can lead to complications if different forms have different required fields (e.g., for registration you collect an affiliation but not in membership), and thus changes in one form can affect the profile which in turn affects another form. Therefore, the best practice is to make the information that you gather in each form as uniform as possible. Although each form collects different user details, many of the fields (e.g., name, email, affiliation) are consistent.
The Edit Fields tool can be used to change the fields that are shown when users create a new account before submitting an abstract, during registration, or to change the fields that are shown when new or returning users use the Membership Form.
The settings for these two tools are separate - changes made to the Conference Sign-Up form will not be enacted on the Membership form, for example. This tool also enables conference organizers to set different text for different language options that are being made available in your community. This means that administrators can change the wording of many of the system-generated fields in the Abstract Submission Form, the Registration Form, and the Membership Form in English and French separately. The language shown is be determined by the language settings for the user viewing the form.
The Conference Sign-Up section also includes settings for post-sign up buttons and system-generated sign-up confirmation emails.
An extensive list of fields can be changed using the Edit Fields tool for the Abstract Submission Form, the Registration Form, and the Membership Form. Not every field can be changed, however - some system text cannot be edited.
The fields that can be changed include the wording for items like License, Rank, Workphone, Company Contact, and Terms and Conditions, as well as the naming for each page of the Abstract Submission and Membership Forms. Users can also create custom wording for automatic confirmation emails and for New User Account Email.
The Default Text column shows the default wording for each field. This wording is pre-loaded in new communities, and can be changed. The wording which is shown in your form is the text in the Current Label column.
It is generally recommended that you not change the purpose of a field in changing the label. For example, changing the text for Email to Primary Email Address would be a safe change, but changing the text from Email to Department would cause difficulties.
Not every question is equally important for every conference. In recognition of this, the Edit Fields tool allows you to hide or require each type of question.
If you select Invisible, the question will not be shown at all to users submitting the form. If the question is set to Optional, users are able to enter information if they wish - or skip the question if they don't want to answer it. Required questions must be answered before the user is allowed to proceed to the next page of the form. If they do not answer a Required question, they will be prompted to fill in an answer before they can proceed.