事件-待办事项-日志: Difference between revisions
PolyglotBot (talk | contribs) m (Adding interlang links (links to translated versions of this page in other languages) triggered by origin English page "Events-Todo-Journal" update.) |
|||
| Line 11: | Line 11: | ||
{{TemplateDocUser}} | {{TemplateDocUser}} | ||
[[Category:AgendaEn]] | [[Category:AgendaEn]] | ||
= | =简介= | ||
用于管理任务/计划/日程的软件(如Outlook,Lightning,Webcalendar等)可以管理3种不同的概念(使用规范RFC2445进行规范化),它们是: | |||
* | *事件(规范中的 '''event''' ) | ||
* | *任务(规范中的 '''to-do''' ) | ||
* | *日志(规范中的 '''journal''' ) | ||
这 3 个定义非常相似,但它们是不同的术语,用于不同的目标。本页描述了它们之间的差异。 | |||
(如果您感兴趣,可以去 www.ietf.org/rfc/rfc2445.txt 查看完整的规范)。 | |||
=Event and rendez-vous (event)= | =Event and rendez-vous (event)= | ||
Revision as of 07:10, 4 August 2023
简介
用于管理任务/计划/日程的软件(如Outlook,Lightning,Webcalendar等)可以管理3种不同的概念(使用规范RFC2445进行规范化),它们是:
- 事件(规范中的 event )
- 任务(规范中的 to-do )
- 日志(规范中的 journal )
这 3 个定义非常相似,但它们是不同的术语,用于不同的目标。本页描述了它们之间的差异。
(如果您感兴趣,可以去 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.