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 fills out a form the resultant item gets stored in the* root directory of the user's  workspace/resources tool.  A bit more structure in the storage locale will make it easier to locate these artifacts, understand their provenance and reuse them in other contextsadds 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 filling out adding forms to a matrix.
Users viewing list of resources with form structures included.

Steps

From Matrix of Resource, create new form, locate resulting artifact in your "My Workspace" Resources.

Variations

Several. 2 main choices are:

1. Type/provenance
2. Provenance/type"Type" can be 2 tiered: category (feedback, evaluation, etc.) and form type ("Field trip report", "Workplace Safety Log Entry")
   Provenance can detail the originating site, as well as the context ("PUL Learning Matrix")
   But a first pass should at least present one of the two levels above.
   

Issues

In resource list hspace is at a premium - this militates against overly complex hierarchiess

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

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.

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

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.

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

Issues

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

2. User clicks on 'Add' button
3. 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
4. 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-14  - A preview capability to wizards.
History
Nov 22 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 22 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.

Actors

Steps

Variations

Issues

Id

OSP-UI-16  - User centric design
History
Nov 22 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 22 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 22 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