This wiki does not contain official documentation and is currently deprecated and read only. Please try reading the documentation on the Liferay Developer Network, the new site dedicated to Liferay documentation. DISCOVER Build your web site, collaborate with your colleagues, manage your content, and more. DEVELOP Build applications that run inside Liferay, extend the features provided out of the box with Liferay's APIs. DISTRIBUTE Let the world know about your app by publishing it in Liferay's marketplace. PARTICIPATE Become a part of Liferay's community, meet other Liferay users, and get involved in the open source project. Journal Article Publishing Algorithm
How Journal Articles are Published#
A definitive algorithm needs to be defined for how Journal Articles are published and displayed throughout the portal.
There are currently several ambiguous and opposing use cases which differ on how this should be done, and whether we choose a single or have a number of configurable ones is not the issue. Definitions of these algorithms is the issue.
Definition of Terms #
- PUBLIC: Having one or more ways a non-editor can access the content of a particular article version. This can be through any portlet that displays Journal content, through searches, RSS, SOAP or any other means.
- NOT APPROVED: This version is not ready, and not allowed to be public in any way regardless of other settings.
- APPROVED: This version is ready to go public according to it's timing settings.
- DISPLAY DATE: First point in time at which this version is allowed to be public.
- EXPIRE DATE: Last point in time at which this version is allowed to be public.
- REVIEW DATE: ???
- EXPIRED: This version is no longer allowed to be public. Either because time has passed it's expire date, or because the editor has manually marked it as expired.
Article Version Lifecycle #
Below is a simple attempt to capture the lifecycle of the versions of an article with Id Art_A:
This illustration uses the logic which has been in place up to version 4.4.2, which is that several articles can be approved at the same time, and as a higher version expires, the underlying lower version can once again be the the visible version.
Use Cases #
1) User creates new Article A (OID 11000) 2) User sets
Journal User Interface #
The Journal portlet provides a user interface for content administrators to add, delete, and update content. It also displays a list of content that have been approved.
In the current interface, Journal displays a list of all versions of a given journal article. For instance, Journal Article with an ID of 11040 has 2 versions. All versions will be displayed in the list of available Journal Articles. The following shows this behavior.
The example is using the current logic which will automatically expire all previous versions when a new version is created.
The new proposed interface will only display the currently visible version of a given article. All other versions (those pending display and expired versions) are displayed when a user chooses to edit the article.
