Skip to end of metadata
  • Created by Former user, last modified by Former user on Oct 27, 2006
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 13 Next »

Discussion of the scope for the OSP 2.4 release. Consider that the release is planned for the April 2007 timeframe and the code freeze for the release is on March 15th. List items that you believe are important to include in the upcoming release. Ultimately the scope will be determined by the folks who commit to work on the 2.4 project, the resources available, and the time constraints.

Draft Scope

  • OSP Reports
  • UI rework to make OSP easier to use (consistency, clarity on workflows between tools, etc.)
    • One specific example is to be able to complete forms and add files when creating a portfolio, rather than adding everything in Resources first.
    • Also, add ability to upload files/documents in the comments area of a portfolio.
  • Improve ability to change objects once created and published (Matrices, Forms, etc.)
  • Provide preview mode before publish. (Matrices, Wizards, Portfolios)
  • Design the personal presentation portfolio experience (the individual user's ability to collect, organize, and showcase work in a creative way... In My Workspace)
  • No changes that require difficult migration. Commit to building all migration scripts for a seamless upgrade from 2.2.x)
  • Ship with good example Forms, Templates, layouts, various Scaffolds with suggested context for usage, etc.
  • Ability to export stuff and import it into another instance of the software (maybe even collections of stuff - i.e. Forms and portfolios that are designed to work together)
  • Move forms out of resources and increase forms flexibility (custom form views for specific forms, etc).
  • Support use of groups (e.g., a) a matrix would be limited to and used by individuals within a specific subgroup in a site – each person completes their own matrix; b) a matrix is created for a group where a matrix cell could be completed by an individual and fill the requirement for the whole group. The second of these would be particularly useful for faculty wanting to use this with group projects.
  • Create "Builders" for the hard to create xsd, xsl, css, xhtml files.
  • Provide Documentation for Authoring xsd, xsl, css, xhtml files (unless we have builders allowing end-users to create these)
  • Identify 3 key types for portfolios and provide documentation on workflows for creating each and sample data structures
  • Rethink immutable design of published items such as forms, matrices, wizards etc. When does it make sense to allow changes to published data structures. (ie) Should it be possible to add on to a matrix once it's already in use? (see 4th bullet point above)
  • Provide better differentiation between user's portfolio experience kept in My Workspace and user's interaction created in a group space.Site centric vs User centric portfolio experience.
  • Add notification for published data structures (ie you have 1 new wizard assignment)
  • Add notification for submitted data structures (ie you have 1 new wizard submission)
  • Make Wizards, Matrices and Forms goal aware
  • No labels