New Tools/Capabilities

Builders

OS24 01 = 9 votes
Create "Builders" for the hard to create xsd, xsl, css, xhtml files.
In the short term, tools that enable faculty to build their own forms and their own custom presentations are also needed to reduce the bottleneck around programming staff.

Reporting

OS24 41 = 9 votes
Reporting capabilities and meta tagging are really key for us in the long term. Tools that would enable faculty to do data mining and generate reports as they work in their last year of the accreditation cycle are needed. A method for bulk exporting all of the contents of a cell within a matrix for all users at once might be an early approach to assist with these accreditation needs.

Goal Awareness

OS24 19 = 4 votes
Make Wizards, Matrices and Forms goal aware
I think that we have stated that making the Matrix and Wizard tools "Goal Aware" would be a good thing. This would allow evaluation to be normalized (or not) across a group of CIG's, enabling standard reporting of portfolio reviews

Workflow/Mutability

Publishing

OS24 37 = 9 votes
Improve ability to change objects once created and published (Matrices, Forms, etc.). 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?
Allow revisions. For forms, matrices, layouts, templates, etc., as well as for states of object (published, unpublished etc.)

Publishing

OS24 38 = 8 votes
Also key is the ability to change the matrix without destroying the data already entered by students into a matrix. Specifically, accreditation standards change. We need the capability to be able to add a row or column to a matrix without damaging data already entered into other places in the matrix.

Documentation/Samples

Documentation

OS24 09 = 7 votes
Documentation - simple 'start here'/cookbook docs that describe how the tools fit together, which roles (developer, author, user) use which tools when. A map of the flow.

Samples/Documentation

OS24 28 = 7 votes
Include complete sample portfolios with all templates, layouts, forms, matrices for a variety of portfolios - accreditation, self presentation, integrative learning, project portfolio. With doc on how they are put together and the use case for each role's interaction.

Samples/Documentation

OS24 27 = 6 votes
Ship with good example Forms, Templates, layouts, various Scaffolds with suggested context for usage, etc.

Documentation

OS24 07 = 4 votes
Identify 3 key types for portfolios and provide documentation on workflows for creating each and sample data structures

Documentation

OS24 08 = 5 votes
Provide Documentation for Authoring xsd, xsl, css, xhtml files (unless we have builders allowing end-users to create these)

Resources/Forms

Resources

OS24 42 = 6 votes
While working on the matrix as a student. When you add files and forms from your own resources you first have to navigate the resources tool to your own workspace. The resources tool should open with the users own resources in the focus.

Forms

OS24 21 = 5 votes
Better GUI in front of form tools.

Resources

OS24 44 = 5 votes
Why not have "resources" default to a user's "my workspace" area (instead of the common-interest worksite area) when selecting items to attach to a matrix or portfolio? save lots of frustratingly extraneous clicks that way!

Forms

OS24 13 = 4 votes
Enhancing the forms used in the matrix for review, feedback and evaluation; these forms should not be stored in the root area of the user's resources tool. It would be better to create a directory for each matrix with some structure for the cells, levels and matrix owners.

Forms

OS24 14 = 3 votes
Some the forms used in matrix make no sense in the context of a user. They should not show up in resources tool as forms that can be added by the user.

Forms

OS24 18 = 3 votes
Simpler (from user's standpoint) storage/creation method for Forms. Where you store it vs how you get to it - needs to be driven by use cases - don't know full answer yet. Resources is used for building the form, storing the form, storing the content of user's input with the form. Perhaps this needs splitting apart, rework the flow from a UI standpoint.

Resources/Forms

OS24 43 = 3 votes
The resources tool should display the form type in the overview of resources.

Publish/Presentation/Portfolio

Publish-preview

OS24 39 = 6 votes
Provide preview mode before publish. (Matrices, Wizards, Portfolios)

Presentations

OS24 36 = 5 votes
Control over who can see what pieces of a portfolio when (to not loose any functionality there). Include an aggregator so that an instructor for example can see 40 user portfolios w/o having to visit 40 user sites. Better ways to show status/progress in addition to the end portfolio artifact.

Portfolio Comments

OS24 02 = 3 votes
A guest user, invited by email to comment on a presentation, should be able to comment.

Portfolios

OS24 29 = 3 votes
Having to add forms that are used in a presentation prior to adding them in a template based presentation is something that needs a lot of explaining. It would be more intuitive and user friendly if these forms could be created while creating the porfolio presentation.

Usability/UI

UI

OS24 46 = 4 votes
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.

Simplify Language

OS24 22 = 4 votes
Simplify the language. There are portfolio templates, portfolio layouts, portfolios - need to reduce the terms to mean one thing and consistently use those terms throughout tools, and tool names.

Migration

Migration

OS24 24 = 4 votes
No changes that require difficult migration. Commit to building all migration scripts for a seamless upgrade from 2.2.x)