Ticket #13 (closed New Feature)

Opened 3 years ago

Last modified 3 years ago

publish from/to date

Reported by: stevenn@… Owned by:
Priority: Minor Milestone:
Component: Version: 2.0
Keywords: Cc:

Description

[jira2trac import : issue created on August 30, 2004 6:32:29 AM CEST ​http://issues.cocoondev.org/browse/DSY-13 ]

Allow to specify:
 * when a document should become live, and which version of the document should then become live
 * when a document should retire

Either we can add this as a feature to a document, or create a general schedule of thing to be done, which could include things like putting a document live or retiring it (possibly multiple times for the same document). The second option is more flexible but will also be more difficult to use, so that we'll probably choose for the first one.

Change History

comment:1 Changed 3 years ago by paul

  • Status changed from new to closed

[jira2trac import : comment created by ja@… on September 1, 2004 7:40:24 AM CEST]

On second thought, a short-term and ok solution would be to use a cronjob which would then trigger a Java client program. This program can read an xml file which contains the documents which have to go live or retire on a specified date.

It can be removed from the road map to save some time to work on other issues.

comment:2 Changed 3 years ago by paul

[jira2trac import : comment created by stevenn on September 3, 2004 8:41:57 AM CEST]

changed priority to reflect Johan's sentiment (cron-job idea)

comment:3 Changed 3 years ago by paul

[jira2trac import : comment created by bruno on February 19, 2007 4:04:44 AM CET]

This is covered by workflow timers in Daisy 2.0. More specific issues can be opened if needed.

Note: See TracTickets for help on using tickets.