Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

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
  • Planned outages and custom error messages

Actual Data

  • On what layouts?
  • How many users have added it to their layout?

Things to consider

  • Support arbitrary number of CPDs in global CPD registry; add a global CPD; more default metadata?  Support for arbitrary metadata
    • Bring metadata into portal for monitoring and support workflow; notify the right people;
    • Framework needs to capture the data; then what we do with it is up to institution.
  • Policy question - what should the default metadata grow to be?
  • 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.

Questions to ask for new Portlet

From Yale: How are portlets vetted before being allowed into the framework?

  • Call to portal team to describe proposed content
  • Portal team will facilitate new content
  • Standard set of questions - governance
    • Sla
    • Expectations
    • Registry information
    • How the real estate is used
    • What layout
    • 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)

Consider voting and commenting on these issue(s)
UP-2047 - Create administrative portlet for managing channels, groups, and permissions

  • No labels