The following steps should be sufficient to set up a small to mid-sized conference, i.e., with a single track and a few dozen to a few hundred paper submissions. By necessity, the description omits many of the options available to conference chairs. Almost all options of interest are found in the Conference:Configure and Reviews:Configure tabs.
In general, it is useful to know the icon conventions within EDAS: a
pencil
is used to edit
information, a plus symbol
to
add items, and a trash can
to delete something.
EDAS models the basic work flow for most conferences: Authors register papers, providing information such as abstract and title, then upload the manuscript. Chairs and other members of the technical program committee assign reviews to papers, which reviewers will fill out online. Based on the reviews, chairs select the papers to be presented and notify authors. Authors of accepted papers upload their final manuscripts.
EDAS also supports other aspects of organizing a conference, such as hosting conference web pages, administering travel grants, creating visa letters, collecting registration fees, preparing CD-ROM or USB content and printing badges. These aspects are not covered below.
From your home page, click on the Chairing tab, as below.
Follow the link to create the conference, which leads to a page that establishes the basic conference parameters, including one track. The conference is set up immediately; there is no confirmation email.
Every conference has to have at least one track before authors can submit papers. Authors submit papers to a specific track, although papers can later be move to other tracks by the chair. Tracks within a conference can have different deadlines, paper lengths and manuscript format requirements.
Via Reviews:Configure, check the basic review parameters
to make sure that they reflect your conference. You can edit these
parameters by clicking on the
pencil.
Among the most important choices for you is to decide whether reviews
are double-blind or single-blind and whether you follow a single-level
or two-level review structure.
The standard model is a single-blind review, where authors do not see the identity of the reviewer, but reviewers can see the names and affiliations of the authors. In double-blind reviews, reviewers do not get to see the author identities. (Obviously, authors also need to "blind" their papers by removing author names from the paper.)
Most (smaller) conferences operate single-level mode, i.e., all TPC members review papers, using the same review form. In some cases, conference want to implement a two-level review system, where each paper is reviewed by a set of (say) three reviewers, and then a TPC member, assigned for each paper, performs a meta-review of the other reviews, using a separate review form. This meta-review is called a TPC review in EDAS, as opposed to the (regular) review. This meta-reviewer can either be one of the reviewers who has also reviewed that same paper, or can be somebody else.
In either model, the conference may allow TPC members to assign additional outside reviewers to the paper, but only to perform a regular review. (This would increase the number of reviews for a paper from, say, three to four or more.) TPC members may, if permitted by configuration, delegate their review to somebody else. A delegated review does not increase the number of reviews; it simply shifts the review burden to somebody else.
While conferences come with a default set of email templates for
notifying authors, reviewers and TPC members, you should check their
content to make sure they reflect how you want to run your conference.
All email templates can be found at Conference:Configure:
Each conference can define its own review form, with (almost) any number of questions. Questions can be either free text or choices; choices are mapped into numeric scores. For each question, you can decide who can view the question, so that some questions can be seen by authors (but always only after they have received a notification about the fate of their paper) and others only by TPC members or the conference chair. Also, numeric questions can be assigned weights. These weights are used to compute the average review score in the paper listing. To edit a question, including its weights and other parameters, click on the item in the "Label" column.
Technical program committee members are those members of the conference organization responsible for reviewing papers. All members of the TPC can review papers, but several categories of TPC members are granted additional powers. You can change the "rank" of a TPC member at any time; small and mid-sized conferences typically do not need these additional ranks. EDAS distinguishes three higher ranks of TPC members, namely group leaders, track chairs and chairs. If you are configuring a conference, you are a chair and have full access to all review details. Track chairs and group leaders gain additional rights to inspect reviews, see reviewer identities and assign reviewers, depending on the review configuration. Track chairs, as the name indicates, gain such rights for the papers in their track. Group leaders have special rights for papers assigned to their TPC group.
The review process goes through a number of stages:
In manual mode, the TPC chair can assign papers to TPC members by checking off names from a matrix.
Alternatively, the chair can go to each paper record and assign reviewers from the TPC or outside the TPC one by one. The paper records are found after listing papers via Papers:List.
Finally, for some conferences, each paper is assigned to every TPC
member; this mechanism is accessible via a link at Reviews:Assign.
Once the reviews have been collected, the chair decides which papers to accept and reject, via
the Reviews:Accept/Reject tab. This decision can be made
for all papers in one sitting ("judge papers in a list"), by score
(Reviews:Accept/Reject) or one-by-one for each paper on the
paper status page. Authors cannot see the review decision until the
author notification email has been sent out via Reviews:Notify
authors tab, using the email templates defined in the conference
configuration or via the
icon.
Most conferences require authors to submit copyright forms. EDAS supports several mechanisms, such as author upload, IEEE eCopyright and chair collection. With author upload, authors upload a scanned version of the form. A zip file containing all scanned forms can then later be collected by the chair. Generally, for IEEE-sponsored conferences, IEEE eCopyright is the most convenient mechanism. After a request from the conference chair, EDAS will ask IEEE for a copyright code. This copyright code is then used to connect to the IEEE server. When clicking on the copyright icon for their paper, authors are led to the IEEE server, with most of the paper information already filled in. After an author signs the form electronically, the IEEE server reports back completion to the EDAS server, making it easy to track who has submitted the form. The EDAS server won't allow the author to upload the final version until the copyright form has been submitted.
If you want to produce a conference program within EDAS, you have to create sessions via Conference:Sessions and then assign papers to those sessions.