See the section “What is an Event in HORTUS?” to better understand the importance of the research EVENT in the context of HORTUS
Event creation publishes a community-facing event object with title, type, abstract, conductors, schedule, timezone, tags, and optional project/institutional links. The schedule dialog is particularly important because it turns a generic announcement into a structured event record users can actually evaluate. Here is the event-creation workflow in the same format. Required fields are marked with * in the UI.
| Event Creation action | What id does | What it matters |
|---|---|---|
| Upload event image | Upload a visual cover for the event in the image area. The UI explicitly accepts JPG, PNG, GIF files up to 10 MB. In edit mode, the image can also be removed/replaced with the X icon shown on the preview. | A strong image makes the event easier to recognize in lists and gives the announcement a more professional, attractive presentation. |
| Enter event title | Fill in the Event title* field with the full public title of the event. This is the main identifier shown on the event page and in the Events list. | The title is the first thing researchers scan to decide whether the event is relevant to their topic. |
| Select event type | Choose a value in Event Type*, such as Webinar. This classifies the event and labels it consistently in the platform. | The event type helps users immediately understand the format of the activity and sets expectations before they open the detail page. |
| Add event link | Insert a URL in Event link when the event has an external landing page, registration page, meeting room, or reference page. | It gives participants a direct path to the operational or public page of the event without forcing them to search elsewhere. |
| Write event details | Use the Event Details* rich-text editor to describe the event. The screenshots show formatting controls for styles, bold/italic/underline, lists, alignment, links, media, and code-style actions. This is where the organiser can write the overview, rationale, and expected outcomes. | This is the core explanatory area. It helps researchers decide whether the event is worth attending and understand its academic value. |
| Add event conductors | Use Event Conductors* to assign one or more responsible people to the event. The UI shows selected people as removable chips, and more than one conductor can be added. | Listing conductors makes ownership clear and shows who is academically or operationally responsible for the event. |
| Set the timezone | Choose the correct value in Timezone*. The screenshots show Europe/Rome as the selected example. | Timezone control is essential for events involving multiple institutions or international participants, because it prevents misunderstandings about start times. |
| Add tags | Insert topic keywords in the Tags field. The UI shows tags as chips, for example Dante, Devotional practice, Divine Comedy, and Spirituality. | Tags improve searchability, filtering, and thematic discovery across the platform. |
| Link Project pages | Use the Project pages selector to associate the event with a relevant project page or institutional page. | This keeps the event connected to its broader research context and helps users navigate between related content. |
Define a schedule
| Event Creation action | What id does | What it matters |
|---|---|---|
| Start the schedule structure | In the Schedules* panel, click Add Schedule. The page clearly states that the event needs at least one schedule to specify when it will take place. | Without a schedule, the event has no operational time structure, so users cannot know when it happens. |
| Name the schedule | In the Add Schedule modal, fill in Title schedule* with the title of the session or block, such as a morning session or workshop segment. | A clear schedule title turns a generic date slot into a meaningful program element that participants can understand immediately. |
| Describe the schedule | Use the Description editor inside the schedule modal to explain the content, aim, or format of that specific session | It helps participants understand what will happen in that time slot, especially in events with multiple sessions. |
| Set schedule date and location | In the same modal, fill Date* with the date and time, and Location with the place or platform. After saving, the schedule appears in the right panel grouped by date and shown on a timeline with the visible start time, duration range, and place (for example, Bologna). | This is the minimum logistical information participants need to plan attendance. |
| Save the schedule | Click Add in the Add Schedule modal. The new schedule block is then displayed in the event editor as a dated card on the schedule timeline. | Saving the schedule turns draft logistics into a visible agenda structure that can be refined further. |
| Add more schedules | Repeat Add Schedule to create additional sessions on the same day or on different days. The screenshots show multiple schedule cards under the same event. | This supports multi-session and multi-day events without forcing everything into one generic block. |
Define program(s) with a schedule
| Event Creation action | What id does | What it matters |
|---|---|---|
| Add a program inside a schedule | Inside a saved schedule card, click Add Program. This opens a second modal used to create smaller agenda items nested inside that schedule. | This allows the organiser to move from a simple session plan to a detailed agenda with lectures, exercises, or sub-activities |
| Name and describe the program item | In the Add Program modal, fill Title program* and the Description field. The description area uses the same rich-text pattern as the other editors. | A program title and short explanation make each sub-activity understandable and easier to scan during the event. |
| Set program time and participant cap | Fill Time* with the specific time range for the sub-session. Optionally use Participants to define a maximum number of participants. | This adds operational precision, especially when activities have different durations or limited capacity. |
| Add program location details | Use Street, Housenumber, and Place/Room to define the exact venue details. Add Program Link when the program item has its own online entry point. | Fine-grained venue data is useful when a single event includes multiple rooms, spaces, or digital access points |
| Assign program conductors | Fill Program Conductors* with the person or people responsible for that specific sub-session. | This clarifies who leads each activity and helps participants identify the right contact or speaker. |
| Save the program item | Click Add in the program modal. The item then appears nested inside the schedule card, with its own title, time, short description, link indicator, and delete icon. | Saving the program item creates a readable agenda hierarchy: event → schedule → program item. |
| Review the generated agenda | After schedules and program items are added, review the right-hand timeline. The screenshots show the structure clearly: date heading, start times, schedule cards, and nested program blocks. | This lets the organiser check that the event reads well from a participant perspective before publication or final save. |