General Chair/Co-Chair
I AM IN STAGE:
In Confy’s Initial Setup stage, responsibilities of General Chairs include:
– Consulting deadlines with the Conference Manager
– Appointing the Program Committee Chair
– Consulting the Program Committee Chair on the format of the conference, i.e. how many Technical Tracks the conference will comprise
– Connecting the Conference Manager with the Web Chair in order to manage the conference website
Technical Tracks are dedicated to main paper submission. Any number of Technical Tracks is allowed per conference. If there is more than on Technical Track in a conference, all Technical Tracks – Deadlines
– Paper Types
– Review Model
For that reason, all Technical Tracks move through stages in Confy simultaneously. Changing the conference stage therefore affects all Technical Tracks, while non-Technical Tracks remain unaffected.
The interdependency of Technical Tracks helps maintain a steady flow in conference production and creates fair conditions for all submitting authors. It is therefore compulsory and cannot be overriden.
Non-Technical Tracks include:
– Workshop Tracks
– Demo Tracks
– Poster Tracks
– Invited Tracks
– Other Tracks
These Tracks are managed independently of Technical Tracks by their respective Track Chairs.
Each non-Technical Track can follow its own Deadlines, Paper Types and Review Model after consultation with the General Chairs, Program Committee Chairs, and the Conference Manager.
Workshop Track is a type of non-Technical Track typically dedicated to a Workshop. Any number of Workshop Tracks is allowed per conference.
answer
Demo Track is a type of non-Technical Track typically dedicated to Demos. Only one Demo Track is allowed per conference.
answer
Poster Track is a type of non-Technical Track typically dedicated to Posters. Only one Poster Track is allowed per conference.
answer
Invited Track is a type of non-Technical Track typically dedicated to Invited Papers. An Invited Track will only be visible to external user who receive its specific link.
Please make sure that you create a shadow track for every Track (Technical and non-Technical). A shadow track should have the same name as its parent track. When creating an Invited Track, please make sure to select the “Invited Track” type from the drop-down list in the Create Tracks interface, and that you tick an “Invited Authors Only” box underneath.
The Track Chair appointed to a shadow track should be the same as in its parent track. This way, all Track Chairs will have a convenient way of organizing Invited Sessions in their tracks to create a more compelling program, elevating the entire conference.
Papers submitted to an Invited Track are automatically in a fast track, requiring a single review. Since Invited Tracks are non-Technical Tracks, they do not need to comply with Deadlines and Properties of Technical Tracks.
answer
Any number of Technical Tracks is allowed per conference. It is recommended to consider whether the scope of a conference is broad enough to warrant several specialized Technical Tracks, or narrow enough to warrant a single Technical Track.
Any number of Workshop Tracks is allowed per conference.
Only one Demo Track is allowed per conference.
Only one Poster Track is allowed per conference.
Only one Invited Track is allowed per conference.
*All* Tracks – Technical and non-Technical, should be created by Program Committee Chairs.
Paper Types and Review Model of all Technical tracks should be set up by Program Committee Chairs.
Track Chairs for all Tracks – Technical and non-Technical – should be appointed by Program Committee Chairs.
Deadlines, Paper Types and Review Model of non-Technical Tracks should be set up by their respective Track Chairs.
Stages of Technical Tracks are moved by Program Committee Chairs.
Stages of non-Technical Tracks are moved by their respective Track Chairs.
If there is a single Technical Track, the role of a Track Chair is typically filled by the Program Committee Chair. In this case, it is required that Program Committee Chair appoints themselves the role of a Track Chair.
Submission in Technical Tracks opens by moving conference into Paper Submission stage in Confy. This is possible only after all items in the Initial Setup have been completed by the General Chair and Program Committee Chair.
Moving the conference stage is the responsibility of Program Committee Chairs.
To ensure a quick response, please be as specific as possible in the description of the error or a bug you have encountered, including your precise flow of actions and information about your web browser.
In the Paper Submission stage, Confy does not require any actions from General Chairs.
However, General Chairs need to make sure that the Submission Deadline is set up appropriately. While it is generally not recommended to extend the Submission Deadline, Organizing Committees are allowed to do so maximum two times, for the total duration of no more than 30 days.
Submission closes by moving the conference stage in Confy from Paper Submission to Submission Verification. This is typically done by the Program Committee Chair.
You may extend the Submission Deadline by clicking on Deadlines in the top row of the conference dashboard in Confy, changing the date next to Submission Deadline to your new desired date, and clicking Save.
Please note that it is generally not recommended to extend the Submission Deadline.
Organizing Committees are allowed to extend the Submission Deadline maximum two times, for the total duration of no more than 30 days.
Since authors are allowed to edit their submissions until the submission deadline, it is not possible to begin processing submissions until after the submission deadline. You will be able to do so immediately after – in the Submission Verification stage.
If the conference has multiple Technical Tracks, please note that they all comply to the same submission deadline, and these Tracks therefore cannot be processed separately.
In order to provide fair conditions to all submitting authors, creation of Late Tracks to supplement main paper submission after the submission deadline is not permitted.
To ensure a quick response, please be as specific as possible in the description of the error or a bug you have encountered, including your precise flow of actions and information about your web browser.
In the Submission Verification stage, Confy does not require any actions from General Chairs.
To ensure a quick response, please be as specific as possible in the description of the error or a bug you have encountered, including your precise flow of actions and information about your web browser.
In the Submission Verification stage, Confy does not require any actions from General Chairs.
To ensure a quick response, please be as specific as possible in the description of the error or a bug you have encountered, including your precise flow of actions and information about your web browser.
In the Submission Verification stage, Confy does not require any actions from General Chairs.
To ensure a quick response, please be as specific as possible in the description of the error or a bug you have encountered, including your precise flow of actions and information about your web browser.
In the Submission Verification stage, Confy does not require any actions from General Chairs.
To ensure a quick response, please be as specific as possible in the description of the error or a bug you have encountered, including your precise flow of actions and information about your web browser.
In the Submission Verification stage, Confy does not require any actions from General Chairs.
To ensure a quick response, please be as specific as possible in the description of the error or a bug you have encountered, including your precise flow of actions and information about your web browser.
answer
answer