Hi all, I wanted to solicit some feedback about the proposed portlet lifecycle changes at http://www.ja-sig.org/wiki/display/UPC/Portlet+Lifecycle, as well as discuss some implementation specifics. This lifecycle work is currently planned as part of the implementation of the new Portlet Administration Portlet (UP-2047).
I think we could accomplish the proposed changes by simply adding two new columns to represent a channel expiration (expiration date and expiration-setting user id). After these two new columns are available, we could write logic to interpret the presence and values of the approval, publishing, and expiration date fields as proposed in the wiki document. In addition to the specifications in that document, I'd also like to propose allowing users to specify future dates for the publish and expiration dates. Specifying a future publish date would cause a portlet to automatically become fully published and viewable at that date and time, while setting a future expiration date would cause a portlet to automatically be expired at the specified time. Once the backend logic and database is updated, we could create a user interface in the new Portlet Administration Portlet that would allow users to perform workflow steps such as approving and publishing channels. We'd also need to address import/export of the workflow data, as those timestamps and userIds aren't currently represented in *.channel files. Does anyone have thoughts on the wiki proposal or on potentially using date fields to represent future dates? - Jen -- Jen Bourey -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
