Right now this is a page for gathering requirements for Matrix Mutability. The matrix, once it has been published, limits the properties that may be edited. This prevents columns and rows from being deleted after site participants have added materials to it -which is good. However, to some extend the matrix needs more flexibility so that for example rows and colums may be added once the matrix is in use, but not deleted.
Mutabilty of Matrix properties
A Matrix wizards is a scaffolding that consists of Columns and Rows. By these means a rubric is created that contains cells that we will refer to as pages. Each page belongs to a row and a column and defines the entity that student work in matrices is focused around. Rows may be defined as competencies and columns as the levels at which the competency can be met.
These are screenprints of adding a matrix wizard, adding rows and adding columns
Add Matrix
Add Column
Add Row
The following lists the properties of a matrix wizard.
Property/Feature
type
Mutable
Matrix properties
Title
Displayed in the list of matrix wizards and when viewing the matrix.
No
Description
A richtext description that is Displayed in the list of matrix wizards and when viewing the matrix
Yes
Style
An uploadable stylesheet to customize matrix style
Yes
Column Label
Supply a label to specify what your columns represent. (Competenties, Levels, Stages, _etc.)
Yes
Add Column
Button to add a column
No
Row label
Supply a label to specify what your columns represent.
Yes
Add Row
Button to add a row
No
Matrix progression
None/ Horizontal/ Vertical/ Open/ Determined by Instructor
No
Matrix status colors
Use a color picker to specify which colors denote the cell status (Ready, Pending, Completed, Locked)
Yes
Columns
Column Name
When adding a column, specify its name
Yes
Move Column
Button for moving columns left or right
No
Remove Column
Button for removing a column
No
Revise Column
Button for editing a column
Yes
Column Background color
The background color of the display area that holds the column name
Yes
Column Font Color
The fontcolor that is used for displaying the column name
Yes
Rows
Row Name
When adding a row, specify its name
Yes
Move Row
Button for moving columns left or right
No
Remove Row
Button for removing a row
No
Revise Row
Button for editing a row
Yes
Row Background color
The background color of the display area that holds the row name
Yes
Row Font Color
The fontcolor that is used for displaying the row name
Yes
Mutability of Page properties
The cells in the matrix wizard are refered to as 'pages' and they are effectively the same as the pages that occur in the sequential wizard and hierarchical wizard. The every so slight difference is that a matrix wizard page displays the name of the column and the row it belongs to. Column and row are not relevant in the context of sequential and hierarchical wizards.
The following displays a wizard page in edit mode after it was first created
Add Wizard page
Add Instructions
Add reviewers
Editable properties for a new page are:
Property/Feature
type
Mutable
Title
Displayed when the cell is viewed
Yes
Description
Displayed when the cell is viewed
Yes
Initial status
Ready or locked
Yes
Style
Associated style
Yes
Forms
pre-added forms, particpant enters data or selects existing form
No
Instructions
Richtext and attachments
Yes
Rationale
Richtext and attachments
Yes
Examples
Richtext and attachments
Yes
Reflection
Specify which form should be used for reflection
No
Feedback
Specify which form should be used for feedback
No
Evaluation
Specify which form should be used for evaluaion
No
Evaluators
Specify who will evaluate the page
Yes
Requirements for mutability
( U Michigan / rSmart )
Improve ability to edit and completely delete data structures (forms, wizards, portfolios) once created and published. Rethink the immutable design of published data structures and when it makes sense to allow changes in them, i.e., should it be possible to add pages to a wizard once it is already in use?
A matrix designer has the need to test matrix before publishing. This could be part of the preview mode. Besides the status published, unpublished there would be a status named preview. In the status anyone with the appropriate permission can use and/or revise the matrix. On publishing the matrix all data is removed.
Id
OSP-WF-06 - An author will be able to delete a published matrix (and wizard)
If a designer needs to make more extensive changes than allowed by these rules, a new matrix may need to be designed and an existing matrix deleted.
A matrix designer may decide to delete a matrix from a site after the matrix has been published. The user should be prompted that this "can't be undone" and that "data is in there" if users have already attached forms and resources to the matrix.
Mark, we are at design time right now, so if there is a need for such a button w...
Mark, we are at design time right now, so if there is a need for such a button we should add it. do you have a scenario or use case in mind for such a button?
I understand and it doesn't have to be a button, it could be a link ;) I can i...
I understand and it doesn't have to be a button, it could be a link
I can imagine a scenario where I want to demo a matrix to some faculty and remove the data afterwards to demo it to someone else. Since the data would already be removed implicitly when the matrix is published I figured it would be a small step to make this functionality explicitly available to the user.
Closed
Comments (3)
Nov 20, 2006
Mark Breuker says:
Being able to test a matrix: Will there be a button to remove all matrix data wh...Being able to test a matrix: Will there be a button to remove all matrix data while in preview mode?
Nov 20, 2006
Bas Toeter says:
Mark, we are at design time right now, so if there is a need for such a button w...Mark, we are at design time right now, so if there is a need for such a button we should add it. do you have a scenario or use case in mind for such a button?
Nov 21, 2006
Mark Breuker says:
I understand and it doesn't have to be a button, it could be a link ;) I can i...I understand and it doesn't have to be a button, it could be a link
I can imagine a scenario where I want to demo a matrix to some faculty and remove the data afterwards to demo it to someone else. Since the data would already be removed implicitly when the matrix is published I figured it would be a small step to make this functionality explicitly available to the user.