PKP Bugzilla – Bug 6917
Issues with date_published usage
Last modified: 2013-02-15 18:33:31 PST
(Courtesy of current oncology) -- The published_articles.date_published value is set when an article is scheduled to be published, and isn't updated otherwise. -- Likewise, the issues.date_published value is set when the issue itself is published. -- If the published_articles.date_published value is not null, then this value is used wherever the article's publication date is needed, eg. in metadata tags such as citation_date, and in the "How to Cite Item" Reading Tool. -- This is problematic in cases where the article has been scheduled well before the issue itself is published. Solution: -- possibly rename published_articles.date_published to published_articles.date_scheduled for clarity; -- possibly rename published_articles to scheduled_articles; -- when displaying a publication date, use published_articles.date_published ONLY IF it is a more recent date than issues.date_published value (ie. the article has been published later than the issue, as may be the case for rolling publications).
James, if I understand correctly, all of these are back-end changes except the following: - when displaying a publication date, use published_articles.date_published ONLY IF it is a more recent date than issues.date_published value (ie. the article has been published later than the issue, as may be the case for rolling publications). I'm not sure it's worth the trouble to rename all the functions, tables, and columns. (We also have to be consistent with other apps that use the same conventions.) However, the change proposed above sounds OK to me.
Deferring; this seems like more of a 3.0 kind of thing. Will likely take on after the help work has been completed.