...
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 interrelating sets of various data structures including forms, matrices, wizards, portfolio templates, styles, and portfolio layoutsportfolios.
Sample data structures. Include sample interrelating sets of data structures with examples of populated forms, matrices, wizards, portfolio templates, styles, and portfolio layouts and portfolios for a variety of portfolio purposes - accreditation, self presentation, integrative learning, project portfolios. Include documentation on how the 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 edit and completely delete data structures (matricesforms, wizards, forms, styles, portfolio layoutsportfolios) 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 rows or columns pages to a matrix wizard once it is already in use?
Reports. Complete the reports tool by creating to include functionality for creation of report templates to ship with the application that allow site participants, site organizers, and administrators that allow users with permission to aggregate and display data from forms, matrices, wizards, and portfolios across all sites and users to which they have access.
Integration with Goal Management Tool. Make Assignmentsassignments, Wizardswizards, Matrices and Forms forms goal aware. Allow easy exposure of data from users to select assignments, wizards, matrices, and forms from all of their sites in which a user has data for the purpose of association with for inclusion in a single portfolio template. 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.