Notes
There is a need to maintain the lifecycle of portlets. From beginning to end there needs to be ownership of content and an understanding of maintenance from anyone wanting to develop content in the portal. Also, who should be contacted if the portlet fails? An agreement with the help desk or support team?
Discussion about looking to extend portlet manager to possibly incorporate this.
Metadata
- Functional Owner
- Technical Owner
Actual Data
- On what layouts?
- How many users have added it to their layout?
Things to consider
- The portal is usually considered to be 24 X 7 but the content it displays is not, i.e. weekly database maintainence
- Consider that the framework is able to handle this?
Other Additional Data
Peoplesoft Portal has a content registry that may be worth looking into as something to model against. Hopefully looking for screenshots or more information on this since not all universities have this.
A Portlet?
Maybe a portlet to view the data and metadata. It could also quickly produce reports that export this data.
Related JIRA Issue(s)
Consider voting and commenting on these issue(s)
UP-2047 - Create administrative portlet for managing channels, groups, and permissions