Submission Type¶
A Submission Type controls the definition and behaviour of a set of Submissions in a Project.
Each Project can have one or more Submission Types and each Submission Type can have multiple Submissions.
Submission Types are managed from the Submission Types List which is available from the Project Settings Page.
Properties¶
Each Submission Type has the following properties:
Name¶
A name for the Submission Type that is unique within the project. The name can only contain AlphaNumeric characters and cannot have any whitespace.
Warning
The Name is used in Templates for reports and emails. Changes to the Name may cause Templates and other settings to stop working.
Singular Label¶
The label used to describe a single Submission of this Submission Type
Example
Submission, Award Application, Sponsor
Plural Label¶
The label used to describe a set of Submissions of this Submission Type
Example
Submissions, Award Applications, Sponsors
Data Definition¶
Submissions have a number of dynamic fields defined by a Data Definition.
It is the Submission Type that identifies the Data Definition to use for those Submissions.
The Data Definition is not part of the Submission Type but instead the Submission Type references the Data Definition to be used.
The same Data Definition can be used by more than one Submission Type.
The Data Definition is specified when the Submission Type is first created and cannot be changed to reference a different Data Definition.
Edits to the Data Definition will affect all Submissions that have a Submission Type referencing that Data Definition.
Workflow¶
Submissions can be in one of a number of different Submission Statuses as defined by a Workflow.
It is the Submission Type that specifies the Workflow to use for those Submissions.
The Workflow is not part of the Submission Type but instead the Submission Type references the Workflow to be used.
The same Workflow can be used by more than once Submission Type.
The Workflow is specified when the Submission Type is first created and cannot be changed to reference a different Workflow.
Edits to the Workflow will affect all submissions that have a Submission Type referencing that Workflow.
Settings¶
Each Submission Type can have a number of Settings controlled through the Edit Settings screen.
The settings control how submission of this Submission Type behave. See Settings for more details.
Example
Control is submitters are allowed to add new submissions of this type.
Examples¶
Submissions and Symposia¶
A project could have a Submission Type for normal submissions and a Submission Type for Symposia Submissions. Each of these Submission Types could have its own Workflow and its own Data Definition.
In this way it is possible for normal submissions to store different data and follow a different workflow to Symposia submissions.
Submissions and Sponsors¶
A project needs to collect normal submissions but also information from sponsors of a conference.
A Submission Type for normal submissions is created and a Submission Type for sponsors.
The sponsor data is different to the normal submission data and sponsor data does not need to be reviewed. So each Submission Types have their own Workflow and Data Definition.
Award Applications for different Categories¶
An award ceremony has several different categories and each category needs to ask different questions from the nominees. Each category follows the same judging process.
A Submission Type is created for each category. Each Submission Type uses a different Data Definition so that different questions can be asked but they share the same Workflow because they follow the same process.