Portlet Lifecycle

Five proposed stages of portlet lifecycle within uPortal: Creation, Reviewed, Published, Expired, and Deleted.

• Akin to content/document management.
• More granular roles and permissions assigned and utilized through the lifecycle - everything does not have to be done by the Portal Administrator(s).
• After initial creation, a portlet will have aspects of tracking and analytics assigned to it that can be viewed and moderated, and will grow in data as the portlet moves through the lifecycle.

 

---

Stages

1. Creation

"In development" - Not Public

• Allow a content idea to be created by an author with no harm to the system.
• Instantiate in the portal registry an unpublished (non-public) content container.
• Content authors work in a sandbox to define the portlet and refine the content.

2. Reviewed

"Approved for production" - Not Public

• Standard workflow would have all portlets put through a review process prior to public consumption.
• The review process should be flexible to accommodate variety of institutional review requirements.
• Privileged administrators may bypass the review process.
• Reviewers could be assigned to divisions and departments.
• Reviewers may have broad editorial authority, or may be limited to a certain aspect of the portlet (assigning a Support Owner, for example).
• A Portlet cannot be published for public consumption until it successfully passes the review process (under normal circumstances).

3. Published

"In production" - Public

• Content Owners can authorize publication of portlets, resulting in public consumption of the portlet.
• Public consumption (those who can subscribe the portlet) is based on the groups and permissions assigned to the portlet.

4. Expired

"Might need it later, but not using it now" - Not Public

• Based on an end-date setting or manual Admin user action, a portlet can be expired or "unpublished".
• The portlet is removed from public consumption, but is not removed from the portal registry.

• A portlet may be re-published from this state at any time, though it may require another pass through the review process.
  
  

   

5. Removed

"Don't need that" - Not in portal

• This action may be performed on portlets that are not in the Published stage.
• This action permanently removes a portlet from the portal registry.
• Some record data is left behind for reference.

 

---

Portal Administration

• Define review process
• Review process override
• Portlets-at-a-glance

 

---

Auxiliary Systems

Notifications

• Portlet down
• Portlet published
• Portlet expired

Taxonomy

• Categories and labels