...
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? All content should have a functional and technical stakeholder.
Discussion about looking to extend portlet manager to possibly incorporate this.
Metadata
- Functional OwnerTechnical Ownerowner, including contact information
- Technical owner, including contact information
- Support plan, e.g. central Help Desk, including contact information
- General SLA information
- Planned outages and custom error messages
...
Maybe a portlet to view the data and metadata. It could also quickly produce reports that export this data for external reporting options.
...
New Portlet Vetting Process
From Yale: How are portlets vetted before being allowed into the framework?
...
- For new content, a call to portal team to describe proposed content
- There are Portlet and Content Developers. The later is expected to NOT develop and deploy JSR-168 Portlets, but instead provide a backend service that generates XML (e.g. REST, Web Service)
- All new content looking to be published to Portal is considered a new project (or sub-project). The Portal team will facilitate new contentStandard , however not necessarily manage the project.
- Looking to establish a standard set of questions - governance
- SlaSLA expectations
- Expectations
- Registry information
- How Review of how the portal real estate is used
- What layout should content be included
- Is there an existing layout
- Can this new content be combined with existing content
- SDR
- Performance review - how do we certify new content?
- What happens if they have been showing an error page and is not fixed? What do you do? Disable? Delete?
- Centralized portlet developers
- Distributed content providers
- Ideally content will be delivered through an ESB
Related JIRA Issue(s)
From Wisconsin: (Note from meeting should be reviewed)
- Service team - leader is a product manager - public face but not highly technical; gathers information; can it use existing infrastructure or needs something new?
- Info passed to tech team for additional evaluation
- Topics
- Who will do the work
- How paid for
- Guidelines for content
- Branding
- Look and feel
- Performance
- QA Environment
- Content provider responsible for testing and final QA
- Load testing runs automatically
- Before go-live
- Help desk document
- Who to contact
- Documentation for knowledgebase - internal and external
- How should calls be handled
- Help desk document
Possible Actionable steps
- Consider voting and commenting on
...
- Jira issue: UP-2047 - Create administrative portlet for managing channels, groups, and permissions
- Wisconsin and Yale should look to publish their current content deployment process and procedure, with intent to produce a "reference best practice" document.