01.12.2012 Views

7 Components: the Function Pages - Developers

7 Components: the Function Pages - Developers

7 Components: the Function Pages - Developers

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Workshop<br />

TWikis<br />

Checking in<br />

Adjusting <strong>the</strong><br />

RegistrationWeb<br />

Internal<br />

Administration<br />

Identification<br />

320<br />

��<br />

��<br />

��<br />

After <strong>the</strong> workshops, participants can immediately supplement texts<br />

and publish <strong>the</strong>ir results. For instance, in “open space” conferences,<br />

short summaries are written directly after an event, which are posted<br />

in a central location. This makes it easier to pick up on ideas from<br />

o<strong>the</strong>r events. Fur<strong>the</strong>rmore, it offers <strong>the</strong> possibility for participants to<br />

centrally collect addresses and exchange ideas via <strong>the</strong> wiki.<br />

21.2<br />

Participant Administration/Registration Status<br />

The bottleneck of a conference is <strong>the</strong> check-in. Participants must definitively<br />

register, pay <strong>the</strong> fee and receive conference materials.<br />

To be able to complete as many of <strong>the</strong> formalities of <strong>the</strong> registration<br />

office as possible in TWiki, let us have ano<strong>the</strong>r look at our RegistrationWeb.<br />

As a reminder, <strong>the</strong> registration form and user pages of<br />

registered participants are located on that web. It will now be expanded<br />

by three more pages: InternalAdministration, Receipt and<br />

ParticipantList. They primarily serve to take <strong>the</strong> load off of employees<br />

in registering <strong>the</strong> expected rush of visitors on <strong>the</strong> first day as<br />

quickly as possible while still keeping an overview of participant<br />

numbers and finances – because nothing is more frustrating for visitors<br />

than standing in line for hours right at <strong>the</strong> start of <strong>the</strong> conference<br />

all because registration is not optimally coordinated.<br />

21.2.1<br />

The InternalAdministration Page<br />

First we will generate <strong>the</strong> page InternalAdministration. It represents<br />

<strong>the</strong> central contact point from which all activities originate during<br />

<strong>the</strong> check-in procedure. We recommend simply generating a link to<br />

this page in <strong>the</strong> left side menu bar of <strong>the</strong> RegistrationWeb.<br />

The first step is entering visitors in <strong>the</strong> data management. The page<br />

InternalAdministration must now be prepared for two scenarios:<br />

1. A visitor is not yet registered and must thus be entered in <strong>the</strong><br />

TWiki system with all of his or her data.<br />

2. A participant – in our case Mr. Stonecake – has already registered.<br />

For <strong>the</strong> first case, <strong>the</strong> page contains a link to conference registration,<br />

where an employee can enter <strong>the</strong> new person's data in <strong>the</strong> registra-<br />

21 Executing and Documenting an Event

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!