Skip to main content
Events are the top-level entity in SIGEP. Every other record — inscriptions, schedules, spaces, rubrics, and reports — belongs to an event. The Evento model lives in the administrador app and drives the entire platform lifecycle.

Event fields

FieldTypeDescription
tituloCharField(200)Event title displayed across the platform
descripcionTextFieldFull description of the event
fechaDateFieldThe scheduled date of the event
lugarCharField(150)Physical or virtual location
cupoPositiveIntegerFieldMaximum number of participants (0 = unlimited)
estadoCharFieldCurrent lifecycle state: BORRADOR, PUBLICADO, or CERRADO
creado_porForeignKey(User)The user who created the event
creado_enDateTimeFieldTimestamp when the event was created (auto-set)
actualizado_enDateTimeFieldTimestamp of the last update (auto-set)

Event lifecycle

Events move through three states in a fixed progression. The state controls what participants, speakers, and evaluators can do within the event.
The initial state when an event is created. In this state:
  • The event is not visible to participants or speakers for registration.
  • The coordinator can configure all event details, schedule activities, define spaces, and set up rubrics.
  • No inscriptions can be submitted by participants or speakers.
Who can set this state: Administrators (via /administrador/eventos/) create events in BORRADOR by default. Coordinators can also create events via /coordinador/evento/crear/.

Lifecycle transitions

BORRADOR → PUBLICADO → CERRADO
State transitions flow in one direction only. The coordinator triggers transitions by sending a POST request to /coordinador/evento/<pk>/estado/. There is no path from CERRADO back to PUBLICADO or BORRADOR.

Managing events

1

Create the event

An administrator creates the event at /administrador/eventos/, or a coordinator creates it at /coordinador/evento/crear/. The event starts in the BORRADOR state.
2

Configure details

With the event selected, the coordinator accesses the full event management dashboard at /coordinador/gestion/ to configure schedules, spaces, rubrics, and inscriptions.
3

Publish the event

When configuration is complete, the coordinator changes the state to PUBLICADO via /coordinador/evento/<pk>/estado/. Participants and speakers can now register.
4

Close the event

After the event concludes, the coordinator changes the state to CERRADO. Reports and certificates can then be generated from the archived data.

URL reference

RoleURLPurpose
Administrator/administrador/eventos/Create and list all events
Coordinator/coordinador/eventos/List events scoped to the coordinator
Coordinator/coordinador/evento/crear/Create a new event
Coordinator/coordinador/evento/<pk>/estado/Change event state
Coordinator/coordinador/evento/<pk>/eliminar/Delete an event
Coordinator/coordinador/gestion/Full event management dashboard

Build docs developers (and LLMs) love