...
UI rework/refinement. Focus on making the user experience more integrated and cohesive. This will involve assessing current user workflow'sworkflows, reducing clicks, potentially reducing tools, increasing UI consistency between tools, language consistency, etc.
Documentation. 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 interrelating sets of various data structures such as including forms, portfolio templateswizards, etcand portfolios.
Sample data structures. Include complete sample portfolios with all templates, layouts, forms, matrices interrelating sets of data structures with examples of populated forms, wizards, and portfolios for a variety of portfolios portfolio purposes - accreditation, self presentation, integrative learning, project portfolioportfolios. With doc Include documentation on how they are put together and the use case for each role's interactionthe data structures are created and use cases for the interaction of roles in relation to the purpose for each set of data structures.
Improve authoring flexibility. Improve ability to change edit and completely delete data structures (forms, wizards, portfolios) once created and published (Matrices, Forms, etc.). Rethink the immutable design of published items such as forms, matrices, wizards etc. When does it make data structures and when it makes sense to allow changes to published data structures. (ie) Should in them, i.e., should it be possible to add on pages to a matrix wizard once it 's is already in use? Also allow changing the state of objects (published/unpublished)
Reports. Complete the reports tool to include functionality for creation of report templates that allow users with permission to aggregate and display data from forms, wizards, and portfolios across all sites and users to which they have access.
Integration with Goal Management Tool. Make Wizardsassignments, wizards, Matrices and Forms forms goal aware. Allow users to select assignments, wizards, and forms from all of their sites for inclusion in a single portfolio. Provide additional functionality to integrate goal-associated assignments with wizard pages.
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.
Create "Builders" for the hard to create xsd, xsl, css, xhtml files. Create "Builders" for the hard to create xsd, xsl, css, xhtml files. In the short term, tools that enable faculty site organizers to build their own forms and their own custom presentations portfolio templates are also needed to reduce the bottleneck around programming staff.