>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #1512414. --> Reported by: [bloke_zero](https://www.drupal.org/user/272179) >>> <p>git clone --branch master git.drupal.org:sandbox/bloke_zero/1504400.git pubdate<br> <a href="http://drupal.org/sandbox/bloke_zero/1504400">http://drupal.org/sandbox/bloke_zero/1504400</a><br> Initially Drupal 6.x, D7 port in progress.</p> <h2>What is Pubdate?</h2> <p>Pubdate was developed as a solution to a common problem facing publishers, how to publish the online version of a print magazine using a simple and robust admin interface.</p> <p>The module for replicates a magazine type relationship between content allowing the nomination of parent and child nodes, for example front_cover and in_this_issue, where the content is published together depending on the dates specified for the parent node. The use case is for a magazine publisher wanting to mirror their publishing cycle on line, so content is gathered together in issues, and often presented as a cover and articles.</p> <h2>Features</h2> <ul> <li>Content can be loosely organised into 'issues' and can be displayed in a view as a complete issue with the parent and child nodes, for example, with a views attachment display</li> <li>Simple admin interface for nominating parent and child content types (more than one content type can be nominated as a child)</li> <li>The Date module is a dependency so the date fields are standard Drupal date fields and so can use the date picker etc.</li> <li>Providing parent/child relationship means that dates can be entered only once for the parent and inherited by children</li> <li>Child nodes can override the parent dates in 2 ways, either individually or for nodes that need to stay published after the parent has been unpublished can be defined by type</li> <li>Pubdate fields are exposed to views for display, filtering and sorting</li> <li>Admin views where nodes are grouped by 'issue' can be created</li> <li>CCK node_reference can be removed and the parent/child relationship provided by pubdate can be used via views arguments</li> </ul> <h2>Other modules</h2> <h3>Scheduler</h3> <p>Scheduler is a more general module and has some deficiencies when used in a publishing content, for example scheduler deletes its own data when the scheduling is over, this module keeps that information and exposes it for use, for example, in an admin view. It also doesn't provide the relationship between content.</p> <h3>Rules etc.</h3> <p>This functionality could be created using Actions, Rules and workflow but this module provides a simple one stop solution to a common use case for publishers</p> <h3>Auto expire, node expire</h3> <p>This module is different in scope and intention, these modules expire content, pubdate also organises content.</p> <h2>Project reviews</h2> <p><a href="http://drupal.org/node/1505236#comment-5880984">http://drupal.org/node/1505236#comment-5880984</a><br> <a href="http://drupal.org/node/1517856#comment-5915284">http://drupal.org/node/1517856#comment-5915284</a><br> <a href="http://drupal.org/node/1529386#comment-5885590">http://drupal.org/node/1529386#comment-5885590</a></p>