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 Current »

OSP 2.4 Requirements

Vote Now!

Please add a comment to this page prioritizing at least the top 10 or so requirements for your local institution. Please vote once for each institution and please use only the numbers (OS24 01) listed below. Thanks!

Number

Category

Description of requirement

OS24 01

Builders

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.

OS24 02

Comments

A guest user, invited by email to comment on a presentation, should be able to comment.

OS24 03

Comments

Add ability to upload files/documents in the comments area of a portfolio.

OS24 04

Dates

Date picker should allow all possible datesv

OS24 05

Dates

Instead of three pull-down menus for day month and year, why not use an orbitz/travelocity-like calendar interface? internally an SQL date is an SQL date behind the scenes; imagine how much simpler it would be to set up assignment due dates and close dates and last-accept-dates if each was a calendar click instead of a day click plus a month click plus a year click...

OS24 06

Dates

Dates are displayed in various formats, this should be a single and i18n-able format.

OS24 07

Documentation

Identify 3 key types for portfolios and provide documentation on workflows for creating each and sample data structures

OS24 08

Documentation

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

OS24 09

Documentation

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.

OS24 10

Export/Import

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)

OS24 11

Forms

Move forms out of resources and increase forms flexibility (custom form views for specific forms, etc).

OS24 12

Forms

It would be nice to see the existing forms in the context of the resources tool. Righty now any hierarchy that the user had created with folders to order the forms is lost in the screen where forms are added to the presentation

OS24 13

Forms

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.

OS24 14

Forms

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.

OS24 15

Forms

An api should be provided to progammatically add forms to a students resources.

OS24 16

Forms

XML files that are uploaded to the repository that comply with the XSD for a specific forms should be recognized as a form of that type.

OS24 17

Forms

Attachments to forms should be shown in the form view and should be download-able

OS24 18

Forms

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.

OS24 19

Goal Aware

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

OS24 20

Groups

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.

OS24 21

GUI

Better GUI in front of form tools.

OS24 22

Language

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.

OS24 23

Matrix

When giving feedback to large amount of matrix/wizard cells it would be nice to be able to reuse feedback that have been given earlier.

OS24 24

Migration

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

OS24 25

Notification

Add notification for published data structures (ie you have 1 new wizard assignment)

OS24 26

Notification

Add notification for submitted data structures (ie you have 1 new wizard submission)

OS24 27

OTB

Ship with good example Forms, Templates, layouts, various Scaffolds with suggested context for usage, etc.

OS24 28

OTB

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.

OS24 29

Presentation

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.

OS24 30

Presentation

A staff member that is invited to many portfolio should have to option to hide those portfolios that are not relevant any more. An option should be available to unhide hidden presentations.

OS24 31

Presentation

The content of the e-mail that is sent to invite an external user to a presentation should be configurable, preferable based on a template.

OS24 32

Presentation

It should be possible to link from one presentation to the other. This way a student can combine several presentations in a single one.

OS24 33

Presentation

Begin able to change the order of resources that are added to a portfolio presentation.

OS24 34

Presentations

The list of presentations the user has access to should be sortable. The list should clearly divide presentations from others that the user is invited to from the users own presentations.

OS24 35

Presentations

the possibility to dynamically add all the forms or files from a folder in the CIG resources to a presentation. A CIG participant would create a folder in the workspace resources with a specific name, for instance 'facebook'. Next a portfolio presentation is created that takes all the forms of files of a specific type from that folder and adds them to the presentation. Any files or forms that are of the specified type that are at any time added to the 'facebook' folder should be include (dynamically) in the presentation.

OS24 36

Presentations

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.

OS24 37

Publishing

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.)

OS24 38

Publishing

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.

OS24 39

Publishing

Provide preview mode before publish. (Matrices, Wizards, Portfolios)

OS24 40

Publishing

Provide 'publish to' options - specify groups, global, individuals. Publish just to group members of a particular site, just to a manually created list, or all site members of globally or everyone of a specific role in a site(s) etc.. When hierarchy comes, allow publishing to 'levels' in the hierarchy.

OS24 41

Reports

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.

OS24 42

Resources

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.

OS24 43

Resources

The resources tool should display the form type in the overview of resources.

OS24 44

Resources

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!

OS24 45

Search

When inviting a user to a portfolio in a CIG with many members a search field should be available to search by name (first/last). The search should have an option to search outside the CIG as well.

OS24 46

UI

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.

OS24 47

UI

A general UI normalization as has been done with most of the other tools.

OS24 48

User-centered

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.

OS24 49

Workflow

Optimize workflows - at times several clicks are required to get to the point where you can start the task. An example is starting a reflection. Offer less choices instead of every choice for every step.

OS24 50

?

the ability for a student artifact created in the context of meeting a course assingment to automatically populate a portfolio template that underlies a student portfolio. For example, if I were enrolled in an English course and assigned an essay, my essay should be available to the instructor as an assignment and as a portfolio entry available for comment at the same time.

OS24 51

?

the capacity to upload a portfolio in which the content was created using a WSYWIG website editor, such as Apple's iWeb, Macromedia's Contribute, or an open source alternative. This capability would go a long way toward addressing some of the UI issues we've been discussing in the OSP community.

OS24 52

?

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 labels