Adding and Modifying Questions
Questions are separate from the feature registry. They are stored as database rows scoped to a specific configuration, and they appear in two places in the participant workflow: the Artifact Details step and the Container Metadata step.
The two question types are independent models but follow the same basic structure: question text, an input type (text, radio, multiselect, etc.), a required flag, and an active flag that controls visibility without deleting the row.
Artifact Details Questions
These questions are attached to the artifact review section of the workflow.
Each question can carry a source field that links it to a known external schema
(for example, an ACM Artifact Badging criterion), and an options field for
multiple-choice inputs.
To add a new question of this type, create a row in the corresponding model scoped to the target configuration. The active flag controls whether the question appears to participants; the required flag controls whether they must answer it before proceeding.
Metadata Questions
These questions drive the Container Metadata step and also populate the generated
manifest file. Each question has a manifest_properties field that maps the
participant’s answer to one or more properties in the manifest schema.
When adding a metadata question, set manifest_properties to the manifest key
the answer should populate. If a question covers multiple manifest fields (for
example, an author entry that contributes both a name and an affiliation), list
all relevant keys so the manifest generator picks them up correctly.
The display_section and display_subsection fields control how questions are
grouped on the metadata page. Assign the same section label to questions that belong
together so the UI renders them under a shared heading.
Importing Questions Between Configurations
When an organizer creates a new configuration and selects an existing one as an import source, all questions from the source are duplicated into the new configuration. The copy is independent — changes to questions in one configuration do not affect the other.
This means the recommended workflow for reusing a question set is to set up one “template” configuration with all desired questions and use it as the import source when creating new configurations for individual events.
Deactivating vs. Deleting Questions
Setting a question’s active flag to false hides it from participants without removing it from the database. This is preferred over deletion when a question may be needed again, or when historical submissions that already answered it need to remain consistent.
Delete a question only when it is no longer relevant to the configuration and its history does not need to be preserved.