Child pages
  • OSP-SPEC-5 - Aggregated View of Matrix and Portfolio
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 4 Next »

td.osp-spec-head {
  border-bottom: 1px solid #CCCCCC;
  padding-left: 0;
  padding-bottom: 1.0em;

td.osp-spec-head table.confluenceTable {
  display: table;
  margin: 0;
  padding: 0;

td.osp-spec-head th.confluenceTh, td.osp-spec-head table.confluenceTable th.confluenceTh {
  text-align: left;
  vertical-align: top;
  background-color: transparent;
  padding-left: 0;
  padding-right: 3em;
  border: 0;

td.osp-spec-head td.confluenceTd, td.osp-spec-head table.confluenceTable td.confluenceTd {
  border: 0;

.osp-spec h1, .osp-spec h2, .osp-spec h3, .osp-spec h4, .osp-spec h5, .osp-spec h6 {
  font-weight: bold;
  background-color: inherit;
  color: inherit;
  border: none;
  margin: 1.0em 0 0.2em;
  padding: 0;
.osp-spec h1 { font-size: 1.4em; }
.osp-spec h2 { font-size: 1.2em; }
.osp-spec h3 { font-size: 1.0em; }
.osp-spec h4 { font-size: 1.0em; font-style: italic; }
.osp-spec h5 { font-size: 0.9em; text-decoration: underline; }
.osp-spec h6 { font-size: 0.8em; font-style: italic; text-decoration: underline; }

.osp-spec table.confluenceTable {
  margin: 1.0em 2.0em;

.osp-spec p {
  margin: 0 0 0.5em 0;

.osp-spec { width: 80em; margin: auto; border: 1px solid #CCCCCC; }

td.logocell, div.license, div.bottomshadow, div#poweredby, div.pageheader { display: none; }
div#PageContent table.pagecontent td.pagebody td.pagebody td.pagecontent > table { display: none; }
Unknown macro: {table}
Unknown macro: {tr}
Unknown macro: {td}

Specification ID:


Working Title:

Aggregated View of Matrix and Portfolio

Related Issue(s):

SAK-10135, SAK-10137, SAK-10140


(Matrix, Portfolio)

Confirmation Status and Date:

Status: Confirmed
Date: August, 2007

Unknown macro: {tr}
Unknown macro: {td}






The requirement originated at the OSP/Sakai 2.5 Planning Meeting in May 2007 (Ann Arbor).

Community Acceptance

Discussed in weekly conference calls, documented in minutes and JIRA.


Aggregated Portfolio

  • MyWorkspace Portfolio tool aggregates portfolios for all worksites. All portfolios that are shared or owned will appear in My Workspace tool.
  • Permissions are based on originating worksite.
  • Users are not allowed to add porfolios within the MyWorkspace worksite.

Aggregated Matrix

Portfolio Share


Workflow Steps

(Unique, short, representative name of the step)

Prerequisite Conditions or Step:

(Conditions or Step name)


(Objective, verifiable behavior)

Post-step Conditions or Next Step:

(Conditions or Step name)


List any entities or actors that are used or affected by this feature. Each should link to an entry in the OSP Terminology page.

Quality Metrics

Describe any non-functional requirements of the feature, such as usability, performance, or design. Provide objective and, where possible, quantitative measures against which actual implementations can be evaluated.


Provide any assumptions about implementation path, availability of other required features, schedule concerns or otherwise.

Outstanding Issues

The Outstanding Issues section is a placeholder for the evolution of this specific feature. It should mention any explicit design or implementation decisions that are pending. There must be no outstanding decisions as of the confirmation of the feature as a requirement.

  • No labels