Id

OSP-UI-01  - Displaying description and instructions from xsd in the form when form is being filled out
History
Nov 16 2006: Created
Nov 20 2006: Updated Actor to "resources tool"

Description

The form xsd contains a node locale (<xs:documentation source="ospi.description" />) for instructions associated with an element (a label/input pair) but this is not available to user when form is being filled out. This forces form creators to overload the label with instructions, to the detriment of the form's legibility.

Assumptions

Forms and Resources tool will continue to be integrated

Actors

The resources tool

Steps

When the tools displays the HTML edit form to fill out a form for each item in the form definition that has an associated description that description should be rendered

Variations

Various layout possibilities. See associated wire frames
If no description - omit all traces of description (including any markup block associated with it) from response.

Issues

Questions of layout. Please see associated wire frames.

Id

OSP-UI-03  - Resolve issues with forms not rendering properly.
History
Nov 16 2006: Created
Nov 21 2006: Updated description

Description

Failure on validation (ie. forget to fill in a required field) wipes out data.
SAK-6126 (resolve xs:anyURI issue) - maybe make control an "Attachment" like button instead of a link.
Form display (when filling out) difficult to parse - specially with RT and textarea label/input pairs.
Hierarchical relationships are also hard to visually discern and also cause hspace issues.

Assumptions

Forms and Resources tool will continue to be integrated

Actors

Users filling out forms.

Steps

User fills out form - either from Matrix or from Resource

Variations

See associated wire frames

Issues

Questions of layout. Please see associated wire frames.

Id

OSP-UI-04  - The resources tool should display the form type.
History
Nov 16 2006: Created
Nov 20 2006: Edited

Description

Form type (ie. "Personal Information") needs to be displayed at least in two places: in the Resources list and in the Form title.

Assumptions

Forms and Resources tool will continue to be integrated

Actors

The resources tool

Steps

From Matrix or Resource, create new form, view same in Resources list context
When the form is diplayed in either the resources list view or the form views it's type should be rendered.

Variations

See associated wire frames

Issues

In list hspace is at a premium; could use a mouse over text for the form type.

Id

OSP-UI-05 - Select the default location in resources when using the selection helper based on the user's context and role
History
Nov 16 2006: Created
Nov 20: modified

Description

At present when a user adds an item to a wizard page the resource helper opens in de context of the current site.  The user then has to navigate to their own resources to pick the resource they want to add. This is repeated for each time that the helper is opened and requires a lot of clicks. For a user creating a wizard it makes more sence to open the resource helper in the contect of the site that the wizard is in.

Assumptions

Forms and Resources tool will continue to be integrated

Actors

Users adding forms to a matrix.
Users creating or revising a wizards

Steps

1. If the user is creating or revising the matrix
   • Then: Open the resource helper in the context of the site.
2. If the user is adding items to the matrix page
   • THen: Open the resource helper in the contect of the user my workspace.

Variations

Issues

Id

OSP-UI-06 - Template-based portfolios need to be updated to use the resource helper as an option for choosing items where a user has to select items from resources.
History
Nov 16 2006: Created
Nov 21 2006: Updated description to refer to OSP-UI-05

Description

Using a Portfolio Template a user is constrained to selecting pre-existing items created with forms that fall within the scope of that template. A "Contact Information" template for example will allow content selection from items created with the "Contact Information" form and graphic file types (for the picture). This is done by populating a <select /> with the pertinent items. Default location to which the resource helper opens should be set as specified in OSP-UI-05 above

Assumptions

Forms and Resources tool will continue to be integrated

Actors

Users creating a portfolio based on a template.

Steps

From Portfolios tool click on "Add"
Select "Use a template"
Select an existing template.
Click "Continue" - give the portfolio a name, expiration date.
Click Continue

Variations

Issues

If original login obeyed the need to constrain user to selecting specific information in a given template how will this work when user is using the file picker/attachment helper to populate the portfolio?

Id

OSP-UI-07  - Storing Feedback, Evaluation and Reflections form data entered in a wizard page
History
Nov 20 2006: Created 

Description

Define and implement a folder structure for forms like feedback, evaluations, and reflections created as a part of a wizard. These forms should be automatically stored in the author's resources, in a folder patterned like: "portfolio-interaction"/// where type is either "Reflections", "Evaluations", or "Feedback." This is a means of improving the storing of Feedback, Evaluation and Review forms (fer-forms) in the resources area of the user My Workspace in such a way that the root area of the resources does not get cluttered with forms. The forms are saved in a patterned folder structure and are named by use case OSP-UI-09

Assumptions

The page that the form is added to belongs to a published matrix.

Actors

Users that have 'use' permission on the wizard (students)
Users that have 'review' permission on the wizard (reviewers)
Users that have 'evaluate' permission on the wizard

Steps

1. User navigates to the wizard Page
2. User enters the form editor by clicking on:
   1. 'Complete reflection', or
   2. 'Add Feedback', or
   3. 'Add Evaluation'
3. User enters data into the form
4. User clicks on 'Add' button
5. System stores the form
   1. System determines the folder to store the form
   2. System creates the folder
   3. System determines the name of the form
   4. System checks is there is a file in the folder by that name                                                            
        i.      If Yes: a number is appended or increased and step 5d is repeated
   5. System stores the form in the folder
6. Users is returned to the existing workflow

Variations

#5b: if the folder exists no operation is performed

Issues

1. We need feedback on what the best option is for the folder structure adnd form name.
2. For functional scalability the eid of the student could be appended to the student name to distinguish between students with same first and lastname in wizards that host large numbers of students.

Id

OSP-UI-8  - hidden forms
History
Nov 20 2006: Created

Description

Add a property to a form in the form tool to specify that this form is a 'hidden' form. 'Hidden' forms show up in wizards but not in resources tool.

Assumptions

Actors

Form creators
Resources tool

Steps

• When creating a form through the sakai.forms tool there should be a checkbox in the add/revise forms page that reads "make this form hidden"
• A hidden form may be added to the matrix as one the 4 form types (item/custom, feedback, review, reflection)
• A hidden form cannot be created through the resources tool "add" function when specifing "form"

Variations

Issues

Id

OSP-UI-09  - auto-naming scheme  for wizard forms
History
Nov 20 2006: Created

Description

Define and implement an auto-naming scheme that simplifies the creation and storage of forms that have been
completed by the end user as part of their work in a matrix page. The simplification is acomplished by removing
the need for the end user enter a file name for saving the form to.
This includes three types of forms:

1. Pre-defined forms in 'Items' area ('custom' form)
2. Reflection and Feedback forms
3. Evaluation forms
   Examples of names:
   Presentation Skills-One (start level presenting) - Feedback (matrix sample)
   Presentation Skills-One (start level presenting) - Review (matrix sample)
   Discussion Skills - Feedback (sequential wizard sample)
   

Assumptions

These assumtions apply to the resources tool:
- A folder in resources may contain multiple items with the same name
- Items are ordered by date and time (although only date is shown)
This naming scheme makes sense when OSP-UI-07 adds enough structure to the folders that the forms are saved to.

Actors

Wizard Tool

Steps

1. A portfolio user ends the workflow of adding a reflection,evaluation, feedback, or custom type form to a wizard by clicking on the add button.
2. The wizard tool determines in what folder to store the form (see OSP-UI-07)
3. The wizard tool determines the name of the form via the following auto naming scheme:
   1. File name for feedback forms: "[Wizard-Page] - Feedback "
   2. File name for reflection forms: "[Wizard-Page] - Reflection "
   3. File name for review forms:     "[Wizard-Page] - Review "
   4. File name for custom forms:    "[Wizard-Page] - form type "
       Naming scheme for Wizard Page:
      
4. If this is a Matrix wizard
   1. Then: '[rowName]-[columnName] ([Page Name])'
5. For hierarchical and sequential Matrix
   1. '[Page Name]' |

Variations

Issues

Row and Column names and Wizard Page Names may be very long, how should we deal with that? Suggestion: take a number of characters
from the beginning followed by  a number of characters from the end

Id

OSP-UI-10  - Make the ability to preview portfolios more intuitive
History
Nov 20 2006: Created

Description

Make the ability to preview portfolios more intuitive.  To preview a portfolio now,  the user needs to click "finish" to complete
the workflow and then click on the portfolio name. This is a way to preview a portfolio, but it is not very user friendly.

Suggested approach:
Add a button to the "Create Portfolio" workflow that is named "Preview".
When this button is clicked a new window opens that displays the presentation.
This preview display does not render a form for comments but does show a text like "Comments and a comment form will
be rendered here"

Id

OSP-UI-11  - enable wizards in wizards
History
Nov 20 2006: Created

Description

Add the ability to attach wizards to a wizard page in order to create complex workflows.

Id

OSP-UI-12  -
History
Nov 22 2006: Created

Description

Finish the work to make matrices a part of wizards as was originally intended.

Assumptions

Actors

Steps

Variations

Issues

Would it make sense to make it possible to have multple wizard tools in a site that each have their own wizards. That was an implementer could
decide to have the matrix wizards under "competenties" and the sequential and hierarchical wizards under a differntly names menu option.

Id

OSP-UI-13  - form entry form optimisation
History
Nov 20 2006: Created

Description

Change the UI for completing a form so that the "resources" parts are more clear. Move the "title" and "description" to the top and change "title" to "save as". Remove the "access", "copyright", "meta-data", and "groups". Configure Sakai properties as the means for determining whether or not to include these fields. The default should be to hide the properties. If they are shown, they should appear below the rest of the form.

Moving the "title" and "description" items to the top of the page enabled these to be rendered in the same place all the time. Changing "title" to "save as" complies with standards used in operating systems such as Windows and quickly enables the user to understand what they are naming.

As the forms tool is going to be removed from resources tool an be implemented as a resource type the following aspects of these types could be made configurable:

Id

OSP-UI-14  - A preview capability to wizards.
History
Nov 20 2006: Created

Description

A preview capability to wizards. This would display the wizard as a user would see it. In preview mode the wizard should be testable
to the extend where the wizard can be navigated and forms and files can be added to it.

Assumptions

Actors

Step

• A user creates a wizards and sets it state from "not published" to "preview mode"* The list view of wizards shows an option to preview the matrix* Users with preview permisson can see the matrix in the list and use the preview option* The preview option renders the wizard as if it was published and it functions as if that is the case
• While in preview mode the contents of the matrix may be droped by a person with edit permissions
• When switching to "unpublished" or to "published" mode all the content that was added while previewing is deleted

Variations

Issues

Id

OSP-UI-15  - Comments should allow file attachments.
History
Nov 20 2006: Created

Description

Comments should allow file attachments.

Assumptions

Forms are used to specify a format for the comments on presentations. The person creating the presentation template specified which form should be used
for comments. The presention outline (xsl) should be responsible for rendering the comments.

Id

OSP-UI-16  - User centric design
History
Nov 20 2006: Created

Description

Design and develop a new UI for portfolio tools that shows the user an appropriate, task-based view of portfolio tools. Most users would only see wizards and portfolios. Others would see wizards, portfolios, and evaluations. Another screen accessed from the global actions, would be for authoring and administrative tools. See the whiteboard shot from the Phoenix meeting

Assumptions

Actors

Steps

Variations

Issues

This is a broad requirement that needs to elaborated on before use cases can be specified at this level

Id

OSP-UI-17  - Tools work according to context
History
Nov 20 2006: Created

Description

Make sure OSP tools work according to context. If a tool appears in My Workspace, it shows the items across sites (customizable by the user for site type, specific sites, etc.). If it appears in a site, it shows only the items for that site.

Assumptions

Actors

Steps

Variations

Issues

This is a broad requirement that needs to elaborated on before use cases can be specified at this level

Id

OSP-UI-18  - Create a porftolio supported by a wizard
History
Nov 20 2006: Created

Description

Add the ability at the end of a wizard to "automagically" create a portfolio using the items created during the wizard, and a portfolio template.

Assumptions

Actors

Steps

Variations

Issues

This may not be needed if OSP-UI-06 can be implemented