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 6 Next »

Integration of Goal Management Tool

(Syracuse / rSmart)

OSP-GM-01 - Develop linking ability between a wizard page and goals in the GMT.

  • When a wizard author creates/edits a wizard page, they will have the option to link published goals to the cell from associated sites. This will allow goals to be linked to matrix cells and pages of hierarchical and sequential wizards.
  • This will allow evaluations of cells/pages to be accomplished by a blend of Evaluation Forms and goal ratings/comments. Evaluators will be presented with an evaluation interface that combines the goal management ratings helper and the selected evaluation form.

OSP-GM-02 - Auto-populate a wizard page with assignment artifacts (turned in assignments) based on the relationship between the wizard page and goals in GMT, and relationships between the same goals and Assignments in the Assignments tool.

  • When a wizard author creates/edits a wizard page, they will be required to set a "population method" option for that page. Example options for this setting might include:
    • Auto-populate page/cell with work that meets linked goals
    • Prompt student to add items to page/cell with work that meets linked goals
    • Do not auto-populate or prompt user with items.

OSP-GM-03 - Present the student user with a workflow that allows the user to choose which artifacts from OSP-GM-02 should be referenced in a given wizard page.

UI rework/refinement

(U Michigan / ASU)
Focus on making the user experience more integrated and cohesive. This will involve assessing current user workflow's, reducing clicks, potentially reducing tools, increasing UI consistency between tools, language consistency, etc.

Type I

OSP-UI-01 - Define and implement folder structure for items like feedback, evaluations, reflections, etc.

Type II

Type III

OSP-IU-02 - Define and implement an auto-naming scheme that simplifies the creation & storage of reflections, completed forms, evaluations, feedback.

Documentation & Sample data structures

(Need leader / IU / VTech / UVA / Syracuse)
Documentation should include a map and description of how all the tools work together, simple 'start here' cookbook type docs, documentation on how to construct the various data structures such as forms, portfolio templates, etc.

User Documentation

Authoring Documentation

Library of Sample structures

Improve authoring flexibility

Reports

(rSmart / Syracuse)

Forward compatibility

No changes that require difficult migration. The project team is making a commitment to building all migration scripts for a seamless upgrade from 2.2.x.

"Builders" for the hard to create xsd, xsl, css, xhtml files.

(IU / U Michigan / ASU)

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.

  • No labels