Line 1:
Line 1:
+
<!-- BEGIN origin interlang links -->
+
<!-- You can edit this section but do NOT remove these comments
+
Links below will be automatically replicated on translated pages by PolyglotBot -->
+
[[fr:EvenementTacheJournal]]
+
[[es:EventoTareaDiario]]
+
[[pt:EventoTarefaDiario]]
+
[[zh:事件-待办事项-日志]]
+
<!-- END interlang links -->
+
{{TemplateDocUser}}
{{TemplateDocUser}}
[[Category:AgendaEn]]
[[Category:AgendaEn]]
−
= Introduction =
+
=Introduction=
Software used to manage tasks/plannings/agenda (like Outlook, Lightning, Webcalendar, etc) can manage 3 different notions (normalized in norm RFC2445) that are:
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)
+
*Event ('''event''' in the norm)
−
* Journal ('''journal''' 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.
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.
−
See norm at www.ietf.org/rfc/rfc2445.txt
+
( If you are curious, you could access the full norm at www.ietf.org/rfc/rfc2445.txt ).
−
= Event and rendez-vous (event) =
+
=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).
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 folowwing properties:
+
Events has the folowing properties:
−
* A label (In the norm ical: summary)
+
−
* A description (In the ical norm: description)
+
*A label (In the norm ical: summary)
−
* A start date (In the ical norm: dtstart)
+
*A description (In the ical norm: description)
−
* 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 start date (In the ical norm: dtstart)
−
* A location, like a meeting-room for example (In the ical norm: location)
+
*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 priority (In the ical norm: priority)
+
*A location, like a meeting-room for example (In the ical norm: location)
−
* Transparency (In the ical norm: transp) that says if actors of event are available for this task.
+
*A priority (In the ical norm: priority)
−
* A status (try, confirmed or canceled), rarely used.
+
*Transparency (In the ical norm: transp) that says if actors of event are available for this task.
−
* Other less important informations.
+
*A status (try, confirmed or canceled), rarely used.
+
*Other less important informations.
'''Example of use case''':
'''Example of use case''':
Line 32:
Line 44:
Dolibarr has added a percentage. There is also an option to add a type into Dolibarr.
Dolibarr has added a percentage. There is also an option to add a type into Dolibarr.
−
= The tasks (to-do) =
+
=The tasks (to-do)=
A task has the following properties:
A task has the following properties:
−
* A label (In the ical norm: summary)
+
−
* A description (In the ical norm: description)
+
*A label (In the ical norm: summary)
−
* A start date (In the ical norm: dtstart)
+
*A description (In the ical norm: description)
−
* An end date (In the ical norm: due) or a duration (In the ical norm: duration) but one or other not both.
+
*A start date (In the ical norm: dtstart)
−
* A percentage of accomplishment (In the ical norm: percent-complete).
+
*An end date (In the ical norm: due) or a duration (In the ical norm: duration) but one or other not both.
−
* A priority (In the ical norm: priority).
+
*A percentage of accomplishment (In the ical norm: percent-complete).
−
* A status (running, confirmed or canceled)
+
*A priority (In the ical norm: priority).
−
* Other informations less important.
+
*A status (running, confirmed or canceled)
+
*Other informations less important.
'''Example of use case''':
'''Example of use case''':
Line 50:
Line 63:
This concept is managed by [[Module Projects]].
This concept is managed by [[Module Projects]].
−
= The journals (journal) =
+
=The journals (journal)=
A journal entry is an information. It has following properties:
A journal entry is an information. It has following properties:
−
* A label
+
−
* A description
+
*A label
−
* An information date
+
*A description
−
* A location
+
*An information date
−
* A status (draft, confirmed, deleted).
+
*A location
−
* Other information less important.
+
*A status (draft, confirmed, deleted).
+
*Other information less important.
'''Example of use case''':
'''Example of use case''':
Line 63:
Line 77:
'''Into Dolibarr''':
'''Into Dolibarr''':
−
This concept does not exists in any standard module provided with Dolibarr.
+
This concept is rarely used and does not exists in any standard module provided with Dolibarr.