use the generalized (and now built-in) data query mechanism for downloading "merged" data.
refactor into reusable methods such that queries can be constructed from different form interfaces.
fix the optional "include questions" checkbox so that it actually toggles the option.
added support for merging response data with question-level metadata
only include checked metadata
detokenize
add dataquery construction via js.used in the first XSL-housed style sheets
switch to jsp
de-tokenize (finally)
render the pages using the common settings
switch to jsp (first of many steps...)
include changes to the first/metacat integration projectmerging/union across multiple datapackages now supported
save point before extending to allow merging across assessments
use the first (0) column as the index for questionId when selecting only a subset of the assessment data
add handling for qti metadata in resultset view
adjust xpaths to match changes to edml/qti output by FirstMorpho
Changes to remove ANT tokens for the turnkey install project
add support for selecting records for only one question from a set of one or more assessment response data files
no padding on the table header lefthand side
render multiple mattext elements if they exist...
return immediately if there is no resultset to displayuse getString() to display resultset for each column
add CSV download as an option for retrieving datasets.NOTE: depends on opencsv jar in the /first project...
include both assessments and questions in the results of a search (driven by option in search form)
add ability to retrieve response data using datamanager lib (note that this requires both the datamanager.jar and firstMetacatIntegration.jar from /eml and /first modules respectively...)yes, this is more ajax...and still mostly Proof Of Concept-ish
organize css references
less emphasis on emphasis class (reduced font size)
included assessmentId in search results.TODO: search for both assessment and question doctypes in same query and have the result page display them intelligently (segregate by doc type).
organize the bulk of the stylesheets in their own xsl directory.note that these xsl files are being maintained in the "first" cvs module and should be copied from there.
get the ajax-specific first skins organized with some better naming.these essentially provide a pointer to custom resultset style sheets so that we can just use Ajax.Updater from prototype and inject the returned html.they do rely on the first skin (which makes it nice for changing the look and feel - not a bunch of css files lying around messing things up, etc...).
add very minimal skin for transforming ajax search resultset for 'first' skin
use updated edml schema to get correct element/attribute for assessment
initial skin draft for FIRST project as metacat deployment.will require [much] more customization to be fully useful for project, but this is a start.