Events-Todo-Journal

Return to user
documentation index

Introduction

Software used to manage tasks/plannings/agenda (like Outlook, Lightning, Webcalendar, etc) can manage 3 different notions (normalized in norm RFC2445) that are:

• Event (event in the norm)
• Task (to-do in the norm)
• Journal (journal in the norm)

This 3 definitions are nearly similar but they are different terms and are used for different goals. This page describe the differences between each of them.

( If you are curious, you could access the full norm at www.ietf.org/rfc/rfc2445.txt ).

Event and rendez-vous (event)

An event (event in the norm), is something to define an action (a instant action or an action with a long duration that is in past or future).

Events has the folowing properties:

• A label (In the norm ical: summary)
• A description (In the ical norm: description)
• A start date (In the ical norm: dtstart)
• An end date (In the ical norm: dtend) or a duration (In the ical norm: duration) but it's one or other not both.
• A location, like a meeting-room for example (In the ical norm: location)
• A priority (In the ical norm: priority)
• Transparency (In the ical norm: transp) that says if actors of event are available for this task.
• A status (try, confirmed or canceled), rarely used.
• Other less important informations.

Example of use case: This is same thing that what you can find into an Outlook calendar (tab Calendar), Evolution, Thunderbird/Lightning or into Google calendar. We use the "events" to save rendez-vous for exemple, but you can also use them to save a work to do into a date range if you want.

Into Dolibarr: This concept is managed by Module Agenda. Dolibarr has added a percentage. There is also an option to add a type into Dolibarr.

The tasks (to-do)

A task has the following properties:

• A label (In the ical norm: summary)
• A description (In the ical norm: description)
• A start date (In the ical norm: dtstart)
• An end date (In the ical norm: due) or a duration (In the ical norm: duration) but one or other not both.
• A percentage of accomplishment (In the ical norm: percent-complete).
• A priority (In the ical norm: priority).
• A status (running, confirmed or canceled)
• Other informations less important.

Example of use case: This is same thing that you can found into Outlook Tasks feature (tab Tasks), Evolution or Thunderbird/Lightning. We use then in most cases to manage projects.

Into Dolibarr: This concept is managed by Module Projects.

The journals (journal)

A journal entry is an information. It has following properties:

• A label
• A description
• An information date
• A location
• A status (draft, confirmed, deleted).
• Other information less important.

Example of use case: Manage a personal diary.

Into Dolibarr: This concept is rarely used and does not exists in any standard module provided with Dolibarr.