Terms and troubleshooting
Use consistent terms when discussing a problem. Include the edition, task, visible status and concrete error code; a screenshot alone does not always show which action was performed.
Common terms
Organisation: the administration and data context. Edition: one occurrence of a conference, with its own dates and records.
Call for Papers (CFP): the journey for collecting and selecting session proposals. Call: a specific invitation for proposals, with a submission window and offered session types.
Draft: saved preparation that need not be public. Submission: a proposal within a call; as a draft it has not been handed in and reviewers cannot assess it. Speaker profile: a speaker’s details for this edition; its existence does not confirm participation.
Decision: the selection team’s internal outcome. Release: the deliberate action that informs the speaker and starts the normal follow-up effects.
Confirmation: recorded participation of the primary speaker or relevant participant. Handover: the integration through which CFP passes relevant accepted content to Programme.
Occurrence: a concrete scheduled appearance of a session. Published revision: the version attendees see, which may differ from the latest draft.
Favourite: personal interest. Reservation: a recorded place under the relevant participation conditions. Ticket entitlement: current permission that can allow an activity or entry.
Frequent misunderstandings
- “I accepted it, but cannot see a session.” Check release, primary confirmation and handover; acceptance alone is insufficient.
- “The website shows an old title.” Check whether the draft change was published.
- “I cannot score it.” Check own participation, group assignment, conflict and whether a decision was already taken.
- “My change was refused.” Check version and deadline. Refresh current state first, then deliberately repeat the intended action.
- “We have a decision, but the speaker has no message.” Check that the decision was actually released. If needed, ask whoever handles communication to investigate delivery; an internal status or queued message does not establish receipt.
Use the coverage register for known version boundaries and local installation for startup problems.