AU2004283320A1 - Qualitative data analysis system and method - Google Patents

Description

WO 2005/041058 PCT/AU2004/001451 QUALITATIVE DATA ANALYSIS SYSTEM AND METHOD FIELD OF INVENTION The present invention relates to the field of qualitative data analysis. In one aspect, the present invention relates to a system, method and schema 5 relating to the analysis of data collected in commercial research projects, such as group discussions and in-depth interviews, etc. BACKGROUND ART The inventor has found that in conducting research, the result gathered needs to be analysed so that insight, interpretations and conclusions can be 10 distilled from the research conducted. A number of software products exist which assist researchers in handling and interpreting relatively complex data, but they are considered only generally suitable for thorough'and time-consuming work in an academic context. The inventor has also found that researchers involved in commercial 15 research projects, on the other hand, generally have tighter research guidelines, less structured data and less time for analysis. Researchers conducting these commercial projects generally rely on manual methods of analysis or using standard office packages, like 'Microsoft Word'. The inventor has further found that a research project generally has three 20 phases, the first being Conducting Groups and/or Interviews, the second being Collecting and Sorting data, and the third being Analysing, Interpreting data and Reporting findings to a Client. Time pressures are a common problem in this type of research, and due to the commercial nature of the research, work plans tend to be changeable, which means that researchers may work on several projects at 25 the one time. Sometimes, a researcher is forced to change the approach taken to the research analysis due to the time available for the project. For example, the researcher may prefer to work by reviewing audio or video together with detailed text of a focus group or in-depth interview, but may not be able to do so within the constraints of the project time frame available. 30 Furthermore, projects vary both in size and design. They may comprise any number of respondents, such as focus groups (including mini-groups) and/or in-depth interviews and/or small surveys. Researchers use a numrnber of WO 2005/041058 PCT/AU2004/001451 2 techniques to assist them in discovering the information the client requires, such as: S Projective Techniques - techniques used to stimulate discussion among participants. Participants are encouraged to attribute their feelings, beliefs 5 or motivations to another person, object or situation. Examples of projective techniques are word association, sentence completion, expressive drawing and thematic apperception tests (bubble drawings), S Association Technique - is a form of projective technique where participants are presented with some stimulus material and they are then 10 asked to respond with the first thing that comes to their minds, and * Completion Technique - is a form of projective technique where participants are asked to complete an incomplete situation. Any discussion of documents, devices, acts or knowledge in this specification is included to explain the context of the invention. It should not be 15 taken as an admission that any of the material forms a part of the prior art base or the common general knowledge in the relevant art in Australia or elsewhere on or before the priority date of the disclosure and claims herein. It is an object of the present invention to provide an improved market research tool for use by researchers in conducting qualitative data analysis. 20 It is also an object of the present invention to alleviate at least one disadvantage associated with the prior art. SUMMARY OF INVENTION The present invention provides, in one aspect, a method of and/or device for inputting data into a qualitative research tool, the method comprising the step 25 of inputting the data in association with a heading, such as a concept heading. The present invention provides, In another aspect, a method of and/or device for inputting data into a qualitative research tool, the method comprising the step of inputting the data in association with a sample, such as a respondent. The present invention provides, in still another aspect, a method of and/or 30 device for inputting data into a qualitative research tool, the method comprising the step of inputting or analysing the data in commentary format, such as an AVI format.

WO 2005/041058 PCT/AU2004/001451 3 In a preferred embodiment, commentary, such as AVI represents: Articulation which is substantially what the research participant said, preferably expressed in the words of the researcher, Verbatim which is substantially a reproduction of substantially all, or a 5 representative part, of a respondent's comment, such as a direct quotation from a research participant, and Interpretation which is substantially the researcher's . observations, interpretations and conclusions on what the research participants said. AVI is applicable as a manner of input. AVI is more generally a manner of 10 classifying input and/or data. AVI may be attached to concept and/or respondent. Preferably, the present invention enables the marking-up on an originally imported document. The present invention provides, in still another aspect, a method of and/or device for inputting data into a qualitative research tool, the method comprising 15 the step of defining relationships between data, based on unique indicia, The present invention provides, in yet another aspect, a method of and/or device for arranging data in a qualitative research tool, the method comprising providing analysis frameworks, such as a brand sort analysis framework for inputting, analysing andlor interpreting research findings wherein the framework 20 has a structure that supports the research method in use. The present invention provides, in still another aspect, a schema as herein disclosed. Other aspects and preferred aspects are disclosed in the specification and/or defined in the appended claims, forming a part of the description of the 25 invention. In essence, it has been found that commentary, such as AVI substantially mimics the way that commercial researchers interpret the data. Also having features such as marking-up on original material, concept headings and brand/picture sort functions enable qualitative research analysis to be enhanced. 30 The present invention provides a number of advantages, such as: * Allowing a quick way to import research data, * Providing for flexible identification of themes for a project, WO 2005/041058 PCT/AU2004/001451 4 * Allowing research data to be allocated to a theme(s), * Allowing interpretations to be recorded in an organised format and to provide an insight into proceedings, * Allowing analysis to be ongoing as data is received, 5 * Allowing data from multiple researchers to be collected into one project, * Providing for review of research data that has been already allocated as analysis data, * Allowing verbatims to be recorded in an organised format while performing analysis, 10 * Provide for a flexible analysis framework that can be altered in line with findings, * Providing a structured approach to working with commonly used QMR techniques, * Additionally, Analysis Frameworks enable users to use different QMR 15 techniques within the same project: - input the data in the manner which best supports the technique (e.g. use Concept Analysis Framework to evolve concepts from predecessors) - analyse the project's data as a whole (i.e. query across Analysis 20 Frameworks; difficult to do manually) - and/or combine results from different Analysis Frameworks to produce project outputs (reports/presentations). Further scope of applicability of the present invention will become apparent from the detailed description given hereinafter. However, it should be understood 25 that the detailed description and specific examples, while indicating preferred embodiments of the invention, are given by way of illustration only, since various changes and modifications within the spirit and scope of the invention will become apparent to those skilled in the art from this detailed description. DESCRIPTION OF DRAWINGS 30 Further disclosure, objects, advantages and aspects of the present application may be better understood by those skilled in the relevant art by reference to the following description of preferred embodiments taken in WO 2005/041058 PCT/AU2004/001451 5 conjunction with the accompanying drawings, which are given by way of illustration only, and thus are not limitative of the present invention, and in which: Figure 1 Illustrates an overview of the product features of the market research tool according to the present invention, 5 Figure 2 illustrates a logical representation of the market research tool according to an embodiment of the present invention, Figure 3 illustrates data entered and/or formatted according to AVI, Figure 4 illustrates schematically an example use of the present invention, and 10 Figure 5 illustrates a data model according to the present invention. DETAILED DESCRIPTION OVERVIEW Figure 1 illustrates schematically an overview of the market research tool according to the present invention. A schema providing a substantial enabling 15 disclosure of the present invention is provided below. Various functions (often implemented as screens) of the embodiment are schematically represented. The present invention should not be limited to only these screens, as screens may be deleted, added or re-configured according to the particular use of the present invention. 20 The research tool 101 has a project or template function 102. This function facilitates configuration of: * new project or template definitions which are freshly used for each project. In essence a new file is created, *. project or template properties, which facilitates the set up of background 25 information to the project in a manner that enables it to be used as a reference, such as project name, client contact, researcher, etc. The import function 103 facilitates the import and merging of projects or templates. In one embodiment, this function is performed by: 1. User finds and selects a project or template to import 30 2. System displays import options 3. User accepts default options or selects other options 4. System checks for data match and imports requested data WO 2005/041058 PCT/AU2004/001451 6 One aspect of the present invention relates to a user being able to optionally mark-up sections of data in an imported document. The process is marked on the original material. This marking function allows certain or selected data to be allocated to a selected heading and/or sample as a commentary such 5 as AVI. The mark-up is performed by highlighting the desired text, then it is visually changed, and then a copy/paste function is performed. The function enables a user to know what areas have been covered and it assists in the promotion of data to the correct area. Researcher's interpretation can be input at the same time as data is collected. The document records the mark-ups in a 10 manner that enables the mark-up to be identifiable. In one embodiment, this function is performed by: 1. User selects data 2. User selects to apply a mark-up 3. System marks up the selected data. 15 The project explorer function 104 facilitates navigation of various project components and application functions. The document function 105 facilitates importing, searching, printing or marking up of various documents. In one embodiment, this function is performed by: 20 1. User finds and selects a data file to import 2. System displays document types (with default) 3. User accepts the default document type or selects another. 4. System imports the data file, ensuring the name is unique 5. System opens the newly imported document 25 The report function 106 facilitates the creation of reports or presentations which can be created from the project data and saved in a prescribed manner, It enables the outputs to be edited as desired. The Respondents function 107 facilitates configuration of; * Respondents which define the sample which has sample characteristics, 30 and the characteristics have values for the data sets. * New/Edit Respondents allows creation or modification of respondents.

WO 2005/041058 PCT/AU2004/001451 7 The Sample Characteristics function 108 facilitates configuration of: S Sample characteristics which define the attributes of the sample, such as those based on demographic or other information. They facilitate the creation of sub-samples, which enables the comparison of sets of data, 5 * New/Edit Sample Characteristics which allows editing or creation of new sample characteristics, * Assign Chalacteristic values which enable certain values to be assigned to a data set for each sample. The Sub-samples function 109 facilitates the configuration of various 10 samples into sub-groupings based on a shared value. The Analysis function 110 facilitates configuration of: * Interpretations which are the researcher's observations and conclusions on what the research participants said, and * Analysis frameworks which provide a structure for inputting, analysing and 15 interpreting research findings. Depending on the project, there may be o a draft analysis framework to structure data collection o an analysis framework based on the results of field work in general, a generic analysis framework enables the creation of a hierarchical heading structure to suit a project. The analysis framework facilitates 20 the process by which sense and meaning are made of the data, gathered in qualitative research, and by which the emergent knowledge is applied to the client's problems. Through processes of revisiting and immersion in the data, and through complex activities of structuring, re-framing or otherwise exploring it, the researcher looks for patterns and insights relevant to the key research issues and 25 uses these to address the client's brief. A framework can be applied in a general sense i.e. a generic framework or be specific to a particular type of data/research technique e.g. concept, brand, picture sort framework. A concept analysis framework enables the tracking of the evolution of a concept based on feedback by participants and facilitates the analysis of an idealconcept or set of ideas. This 30 might be used to develop a new product or service, or an extension or amendment to an existing one. A brand sort analysis framework facilitates the division of brands into discrete segments based on shared WO 2005/041058 PCT/AU2004/001451 8 characteristics/requirements/needs/benefits/etc. A picture sort analysis framework facilitates the division of pictures by brands based on shared characteristics/requirements/needs/benefitsf etc. In accordance with one embodiment of the Analysis function, if a User 5 wants to add a hierarchical heading to a generic or concept Analysis Framework, then 1. User selects a hierarchical heading 2. User selects to add a heading 3. System displays; 10 * Image style S Heading Name 4. User enters Heading text (mandatory). 5. User continues 6. System validates that heading name is unique within headings of 15 the same parent. 7. System adds the new heading Furthermore, in accordance with the Analysis function, if a User wants to modify a concept heading, then: 1. User selects a concept heading 20 2. User selects to modify the concept heading 3. System displays; * Heading style * Heading Samples * Heading text .25 * Heading image - only if 'picture style' heading defaults 4. User modifies one or more of the following; * Changes the heading text (mandatory field) * Changes the heading style (mandatory field) * Adds Sample(s) to associate to the Concept (mandatory 30. field). 5. User continues WO 2005/041058 PCT/AU2004/001451 9 6. System validates that heading text is unique within the concept headings of the Analysis Framework 7. Concept is modified Furthermore, in accordance with the Analysis function, if a User wants to 5 evolve a concept heading to a new concept from one or more predecessor(s), or terminate a concept, then: 1. User selects one or more existing concept headings 2. User selects to evolve to a single concept heading 3. User enters evolution interpretation(s) 10 4. System displays for the new concept heading: * Predecessor concept heading(s) (selected concept headings from step 1) * default heading style * default Samples 15 * default heading text * default heading image - only if 'picture style' heading defaults 5. System creates new Concept heading, setting up relationships. In accordance with another aspect of invention, a brand/sort function is provided. This is also associated with Analysis 110 of Figure 1. The brand/sort 20 function provides a unique problem statement, such as a statement of a commercial problem or issue. It is used to define relationships. In accordance with the Analysis function, if a User wants to replace the heading text or the associated heading image, which facilitates a brand / picture sort function, then: 25 1. User selects 'parent' or 'child' heading 2. User selects to modify the heading text 3. User modifies the text of the heading 4. User continues 5. System validates heading text 30 6. System checks for related data 7. System displays message - all related data will also be updated 8. User acknowledges message WO 2005/041058 PCT/AU2004/001451 10 9. System updates heading and any related data Furthermore, in accordance with the Analysis function, if a User wants to add a commentary, such as an AVI, to a sub-sample/ heading, then: 1. User-selects; 5 * Sub-Sample S 'Heading' (any type) 2. User selects to add either an Articulation, Verbatim or Interpretation 3. User enters text (mandatory) 4. User continues 10 5. System adds the AVI 6. Optional: repeat step 2 -5 to add any additional AVIs for the same SubSample/Heading Again, in Figure 1, the Query screen 111 comprises various screens which enable the interrogation of data and/or project information. In accordance with 15 still another aspect of invention the query function 111, as illustrated in Figure 1, provides a query by heading against commentary or AVI or query against heading. In accordance with one embodiment, the query function is performed by: 1. User selects to create a query and nominates the query type 20 2. System sets default query parameters 3. User optionally changes default query. parameters and executes the query 4. System displays query results Furthermore, in accordance with the Query function, if a User wants to 25 query other notation, headings, concepts or indicia, a query function is able to be established, such as by selecting an appropriate filter to be applied to the data field, corresponding to the query to be undertaken. AVI In the prior art, the research data has been introduced into the research 30 tool in one large 'dump' of information. The research data would be then be investigated and interpreted/amended in order to give the research output. This WO 2005/041058 PCT/AU2004/001451 11 requires a large amount of time and analysis. The present invention has been developed to be more aligned with the needs of commercial researchers. In accordance with one aspect of the present invention, research data is input in accordance with Commentary, such as Articulation, Verbatim or 5 Interpretation (AVI), In Figure 1, this feature is associated with Analysis 110 and its associated Analysis Framework, and In Figure 2, as described below, a logical representation of this feature is illustrated. Figure 3, however, provides some more detailed in which the AVI 301 comprises: 10 : Articulation 302, which is substantially what the research participant said, preferably expressed in the words of the researcher, * Verbatim 303, which is substantially a reproduction of substantially all, or a representative part, of a respondent's comment, such as a direct quotation fro a research participant, and 15 * Interpretation 304, which is substantially the researcher's observations and conclusions on what the research participants said. The advantage of entering andlor formatting input data in accordance with AVI is that the research data can be analysed and/or queried as the data is gathered. This provides time benefits in reporting and interpreting the data, and 20 enables the researcher to modify (if necessary) the research as it is conducted. SAdditionally, using the different AVI types (Articulation, Verbatim, Interpretation), a user can easily distinguish the source of the data (i.e. whether it came from respondents indirectly or word-for-word, or whether it represents their own interpretive thinking). It has been found that AVIs make it easier for users to find 25 what they're looking for. For example: * to look through the Verbatims to find an interesting quote that supports their argument * to query Interpretations only to provide an outline of findings for their client report 30 The present, invention gives a relatively immediate analysis response I interpretation of the research that is conducted. Thus the research may be able to be adjusted, if necessary.

WO 2005/041058 PCT/AU2004/001451 12 In accordance with another aspect of the present invention, research data, such as AVI, is assigned at the level within the project to which it applies, which may be the project itself, an analysis framework representing a topic or research methodology, or a heading and/or sample within an analysis framework, where a 5 heading may represent a topic or an emergent theme and a sample may represent a respondent. It has been found that AVI substantially mimics the way that commercial researchers interpret the data. Figure 2, illustrates one representation of the logical relationship of various 10 data entities of the present invention. With regard to the embodiment illustrated: S Project- a Project represents an entire piece of research that can be persisted as a Project or a Template. A Project has zero or more Analysis Frameworks, Commentaries (Project Interpretations), Documents, Persons, Queries, Sample Characteristics, Samples. 15 * Document - a Document represents a Research Data, Project Artefact, Report or Presentation. * Person - a Person represents a Client Contact or Researcher. * Analysis Framework - an Analysis Framework represents a structure for inputting, analysing and interpreting research findings. An Analysis 20 Framework has zero or more Headings and Commentaries. * Concept Analysis Framework - a Concept Analysis Framework is a specialisation of Analysis Framework that tracks the evolution of a concept. A Concept Analysis Framework has zero or more Concept Headings, Hierarchical Headings, Analysis Framework Commentaries and Concept 25 Commentaries. * Generic Analysis Framework - a Generic Analysis Framework is a specialisation of Analysis Framework that provides generic analysis using Hierarchical Headings. A Generic Analysis Framework has zero or more Hierarchical Headings and Analysis Framework Commentaries. 30 * Sort Analysis Framework - a Sort Analysis Framework is a specialisation of Analysis Framework that facilitates the division of brands (Brand Sort) into discrete segments based on shared characteristics or the division of WO 2005/041058 PCT/AU2004/001451 13 pictures (Picture Sort) by brand segments based on shared characteristics. A Sort Analysis Framework has zero or more Sort Headings, Segment Sorts, Segment Sort Commentaries, and Analysis Framework Commentaries. 5 * Commentary - a Commentary represents an Articulation, Verbatim, or Interpretation. * Analysis Framework Commentary - an Analysis Framework Commentary is a specialisation of a Commentary that is used within Analysis Frameworks. An Analysis Framework Commentary may be associated to 10 zero or one Headings and zero or one Samples. * Concept Commentary - a Concept Commentary is a specialisation of a Commentary that is used within Concept Analysis Frameworks. A Concept Commentary may be associated to one or two Concept Headings (predecessor and/or successor) and one or more Samples. 15 * Segment Sort Commentary - a Segment Sort Commentary is a specialisation of a Commentary that is used within Sort Analysis Frameworks. A Segment Sort Commentary must be associated to a Segment Sort and optionally to a Sort Heading. * Heading - a Heading represents a theme or a Way of structuring the 20 analysis. * Concept Heading - a Concept heading is a specialisation of a Hierarchical Heading that is used within Concept Analysis Frameworks. * Hierarchical Heading - a Hierarchical Heading is a specialisation of a Heading that is used within Generic Analysis Frameworks and Concept 25 Analysis Frameworks. A Hierarchical Heading may be associated to zero or more child Hierarchical Headings. * Sort Heading - a Sort Heading is a specialisation of a Heading that is used within SortAnalysis Frameworks. A Sort Heading in a Brand Sort is known as a Brand, and in a Picture Sort is known assa Picture. 30 * Segment Sort - a Segment Sort represents a segment as a Category in a Brand Sort or a Brand in a Picture Sort. A Segment Sort is associated to one Sample and must have one or more Sort Headings.

WO 2005/041058 PCT/AU2004/001451 14 * Query - a Query represents a means of extracting and representing analysis information from different perspectives. A Query is associated to many different items. * Query Commentary - a Query Commentary is a specialisation of Query 5 that is used to analyse Commentaries. * Query Concept - a Query Concept is a specialisation of Query that is used to analyse Concepts. * Query Segment Sort - a Query Segment Sort is a specialisation of Query that is used to analyse Segments. 10 * Query Text - a Query Text is a specialisation of Query that is used to analyse heading and commentary text. * Sample - a Sample represents the project's sample and is a generalisation of Respondents and Sub Samples. A Sample is associated to zero or more Sample Characteristic Values. 165 * Respondent - a Respondent represents a Group, Depth, or Other. A Respondent is a specialisation of a Sample. * Sub Sample - a Sub Sample represents one or more Respondents or one or more Sample Characteristic Values. A Sub Sample is a specialisation of a Sample and is associated to zero or more Respondents. 20 * Sample Characteristic - a Sample Characteristic represents an aspect common to the Samples. A Sample Characteristic has zero or more Sample Characteristic Values. * Sample Characteristic Value - a Sample Characteristic Value represents a trait of a Sample Characteristic, 25. Figure 4 provides a relatively simple representation of the use of the present invention. A project is created 401, and then a query 402 is raised as to whether the project has any artefacts. Artefacts can be stored at 403. The qualitative research is then conducted 404, and data is collected, Any online research data can be stored 406, otherwise, one or more analysis frameworks 30 can be completed 407, followed by analysis 408 (perhaps on-line) as required, and as described above. A reporting framework 409 can thereafter be WO 2005/041058 PCT/AU2004/001451 15 completed, and exported 410. The report can be reported to the client 411, and if necessary, further analysis 412 can be conducted. Schema Figure 5 illustrates a data model according to the present invention. The 5 data model represents relatively generally the manner in which information represented by the logical entities in Figure 2 can be saved. The data model is notated as an Entity-Relationship diagram; where each box represents an entity (table), each row in the box represents a field (column) with its data type, and Each line between entities represents the relationship (link between tables). 10 An example of the data model is provided in the form of the described Below, which is given as only one example according to an embodiment of the present invention: <?xml version="1.0" encoding="utf-8" ?> <xs:schema targetNamespace="http://qsr.com.aulXSight.xsd" 15 xmlns="http://qsr.com.au/XSight.xsd" , xmlns:mstns="http:/qsr.com.aulXSight.xsd" xmIns:xs="http://www.w3.org/2001 /XMLSchema" xmlns:msdata="u rn:schemas-microsoft-com:xml-msdata" version="1.0"> 20 <xs:element name="Project"> <xs:complexType> <xs:sequence> <xs:element name="Title" type="xs:string" nillable="false" /> 25 <xs:element name="Description" Stype-"xs:string" nillable="false" /> <xs:element name="CommissioningClient" type="xs:string" nillable="false"/> <xs:element name="OnBehalfOfClient" 30 type="xs:string" nillable="false" /> <xs:element name="VerbatimQuotationCharacterEnabled" type="xs:boolean" nillable="false" WO 2005/041058 PCTAU20011001451 16 <xs:element* name="VerbatimSampleCha racteristicincluded" type=I"xs:b oolean" nillab le=-iaI s I> <mselement 5 name- VerbatimQuotationCharacter" type="xs:stririg"nilable="false" 1> <.xs:element na me="Ve rbati mitalias" type="xs:bool'ean" nillable="false'1> <xs:element name="Password" type= xs:stri ng" n ila ble=TalIse" /> 10 <xs:element name=71Hi nt" tyPe="xs:string" <xs:element name- Version" tyPe="xs:stririg" nillable='"false> <xs: element name='Type' type="xs: string" 15 nillable=-false" I <hxs:sequence> </xs:complexType> </Ks:etemeflt> <xs:element name&'Perscn"> 20 <xs:complexType>" <xs:sequence> etxs:element name="Identifler" type--"xs: integer" n illable &Talse" I> <xs:elernent riame="N arme' type= "xs: stri ng" 25 nillable="false" /> <xs:element name- Position" type="xs:string" nillable='"false" I> <xs.-element name="Description' type="xs :strIng" nilllab9="false" I> 30 <xs:element name="Ro le" type="xs :string" nillabte='Talse" /> <xs~lement namo="PrimaryContact' tyPe="xs:buolean" nillable="false" I> WO 2005/041058 PCT/AU20011001451 17 </xs:sequence> <xs :complexType> <xs:key name="PersonPrImaryKey' msdata :PrimaryKey--"trueu> 5 <xsselector xpath="." /> <cxs:field xpath="Identifier" I> <Ixs:key> <Ixs:element> cxs:eement name="Dacu menV5 i0 <xs:oomplExType> <xs:sequence> <xs:element riame="Identifierr type="xs :integer" *niIlable="false" / <xs:element name="Name" type "xs: string" 15 niIlable="false" /> <mxselement narne="Type" type="xs: string" *niIlable='"falsd" I> <1xs'-sequence> </xs:compl exType> 20 * xs; key name="DocumentPrimaryKey" madata:PrimaryKey--true"> <xs: selector xpath="." I> <xs:fieid xpath="Identifier" I> </xs :key> 25 ,::Ix:element> <xs:element nam e='SamnpleCharacteristic"> <xs:complexType> <xs:sequ ence> <xs:elemerit name=Identifier type="xs: integer" 30 nillable=laalse" /> <xs-.element name="Name" type="xs:strlng'* *nillable="false"l I> </xs:sequence> WO 2005/041058 PCT/AU2004/001451 18 </xs:complexType> <xs:key name="SampleCharacteristicPrimaryKe/y" msdata:PrimaryKey="true"> <xs:selector xpath="." /> 5 <xs:field xpath="Identifier" I> </xs:key> <Cxs:element> <xs:element name="SampleCharacteristicValue"> <xs:complexType> 10 <xs:sequence> <xs:element name="Identifier" type="xs:integer" nillable="false"/> <xs:element name="Name" type="xs:string" nillable="false" /> 15 <xs:elemrnent name="SampieCharacteristicldentifier" type="xs: integer" nillable="false" 1> </xs :sequence> <fxs:complexType> <xs:key name="SampleCharacteristicValuePrimaryKey" 20 msdata:PrimaryKey="true"> <xs:selector xpath="." /> <xs:field xpath="Identifier" /> <fxs:key> <xs:keyref 25 name="SampleCharacteristicSampleCharacteristicValue" refer="Sam pleCharacteristicPrimaryKey"> <xs: selector xpath 1 ="."/> <xS:field xpath="SampleCharacteristicidentifier" /> <lxs:keyref> 30 </xs:element> <xs:element name="Respondent"> <xs:complexType> <xs:sequence> WO 2005/041058 PCT/AU20011001451 <xs:element name="Sampleldentifier T type="xs~intege"nillable="false" /> <xs:element name="Type type="xs:sting" nillable="false" I> 5 'xs:element name="DateT ime" type="xs:string" niIlable=Ifalse /> '<xs:elemrent name="Description" type=nxs:stririg" niIlable=ffalse" I> 10 e-lxs:compIexType> <xs :key na me=ulRespondentPri maryKey" msd ate :PrImaryKey="true"> <xs:selector xpath='." I. <xs:field xpathm"Sampleldentifier" I> 10 </xs:key> '<xs:keyref nre"apoepnet <xs:selector xpath=R" I> <xs:fleld xPath-"Sampleldentier" /> 20 <Ixs:keyreft' <xs :GlEment name=

T

SamnpleSampleCharactertsticValue'5 <xs :oomplexType> <xs:sequence> 25 <xs:element name="Sampieldentifier' type="xsinteger" nilIable='false"1> <xs~elemnent name=I"SampleCharacteristicVal ue Identifier". type="xs: integer" nilable~lalse" 1> <Ixs~sequence> 30 </xs:complexType> .- xs:key name="RespondentSampleCharateristicValueP rimaryKey" msd ata: PrimaryKey="t rue"> WO 2005/041058 PCT/AU20011001451 20 <xs:selector xpath="." I> <xs:fld xpath="Sampleldentifier" I> <xs:field xpath=nSampleCharacteristiVaue Identifier" I> 5 </xs:key> <xs~keyref name="Sample~haracteristicValu eRespon dentSampleCharacteristicValue" refer"eSampleCharacteristiValuePrimaryKe'> <xs:selector xpath="." /> 10 <,cs:field xpath='Sam-peCharacteristicValu eldentifier' <txs keyref> <xs:keyref name- 1 SampleSampleSampleCharacteristicValue" refer="Sam pleP? rime ryKey"> 15 <xs: selector xpath="." 1> ,exs:field xPath ="Sampleldentifier M I </xs:keyref> </xs:element> elementt name="Su bSampleRespondent"> 20 <xs:comnplexType> <xs:sequence> <xs:element namne="Sampleldeitifier" type="xs:integer" riillable~false" I <xs:element namne="Respondentlcdentifier' 25 type="xs:integer" nillable="trueu 1> </>xs:seq uence> <xs:complexType> <xs:unique na me="Su bSam pleCom position Prima ryKey" msdata: Prima ryKey~true"> 30 <xs:selector xpath="." f <xs :fleld xpathr="SaMple Identifier" 1> <xs :fiel d xpath=" Respondentidentifie r" /> </xs~unique> WO 2005/041058 PCT/AU20011001451 21 'xs:keyref nm=$bapeu~ml~moiin refer--"SamplePrimaryKey-> <xsselector xpath="." /> <xs:fieid xPath="Sampleldentifier" I> 5 </xs:keyref> <xs:keyrdf narne="Respond entSu bdampleRes pond ent" refer="Respo'ndentPrimaryKey">. <xs:selector xpath="." 1> 'zxs:field, xpath="Respandenldentifier" I> 10 <txs:keyref> </xs:eIemnent> < xs~element name="AnalysisFramework'> 5xs:complexType> <xs:sequence> 15 <xs:e lement name="ldentifier" typa="xs :inieger" nlabe="fase">-,/txs:element> <xs~element name="Name" type "xwstri ng" niIlabe="false"J> '<xsereent namne=Type" type 'xs:string" 20 niIlable~ m false" J> <xs:sequence> <Txs:complexType> <xs:key narne="AnalyssFrameworkPri maryKey" msdata: Pri maryKey= 1 'truell> 25 <txs; selector xpath='." /> e<xs:field xpath=wldentifior /> <Ixs:key> <fxs:elament> <xs:elerrent nam'e'"Heading"> 30 <xs: complexType> <xs:sequence>. <xs: element na me="I dentifier" type="xs intag er" nillable='Talso" 1> WO 2005/041058 PCT/AU20011001451 22 <xs:element rname="Name!I type="xs:string" nillable~false" I> <xs:element na me"An alysisFrameworkl dentif ie r"type="xs:integee' n I [able ="false" /> 5 <xs:element name= "Irnage" type="xs:hexBinatry" niIlable="tru e" /> <cxs:eement name="Typ a" type="xs :string" nhiabe&"fase'k/ </xs:sequen ce> 10 <Ixs:complexType> <xs:key name="HeadingPrImaryKey' rnsdata:PrI maryKey="true"> <xs: selector xpath="." /> <xs:fielId xpath="Identifier" /> 15 <fxs:key>? <xig:keyref name"=,AnalysisFrame workHe ad ing' refe r="Analysie Framewo rkPrim aryKey"> <xs:selector xpath="." I> <xs:flald xpath ="Anal ys isFramewo rkld entifi er > 20 </xs:keyref> <xs:element name="HeadingHierarchy'> <xs:complexType> <xs:sequence> 25 <xs.:element name=" Headingl dentifier"' type="xs:integer"' nillabie="false" /> <xs:element name="Child Head ingldentif ier"l type="xs:integer Y nillable='false" /> <Ixs:seq uence> 30 </xs: comnplexType> <xs :key name="Hie rarchical Heading Prima ryKey" msdata. Prima ryKey--wtruel> <.ka:selector xpath=". /> WO 2005/041058 PCT/AU20011001451 23 <xs:field xpath= Heading Identifier" /> <xs:field xpatli"ChildHead ingidentifier"!> <fxs:key> <xs:keyref name="Heading~eadingHierarchy" 5 .refer--"Hea ding Prima ryKey 5 -,xs:selector xpath="." 1> <xs:field xpath="HeadingldentIf ~le > </xs:keyref> <xs:keyref name="Head fngHeadingHierarchyl"I 10 refer="HeadingPrimaryKey"> <xs:selector xpath="." I> <xs:field xpath="Ch ild Heading ld entifier" f> <(xs:keyref> <xs.:element> 15 <xs:element namne="HeadingConcept"> '<xs: complexType> <xs:sequence> 'xs:element name="Headingldentfier typo="xs: integer" n illable="false" f> 20 <xs:element na me= Terminated" type="xs:bolean" nil lable="fal se" I> </xs:sequence> <lxs:compexType> <xs:key name="ConceptHeadingPrimraryKeyI 25 msdata:PrimaryKey="tru eU> <xs:selector xpath= . 1> <xs:fld xpath~nHeadingdentifier~ /> -<1xs:key> <xs:keyrof nam e="H ead ing Head ingConce pt" 30 refer="HeadingPrimaryKey V> -,xs:selector xpath="." 1> <xs:field xpath="Headingldentilit /> <Ixs~keyref> WO 2005/041058 PCT/AU2004/001451 24 </xs:element> <xs:element name="HeadingConceptSample"> <xs:complexType> <xs:sequence> 5 <xs:element name="Headingldentifier" type="xs:integer" nillable="false" I> <xs: element name="Sampleldentifier" type="xs:integer" nillable="true" /> </xs:sequence> 10 </xs:oomplexType> <xs:unique name="ConceptHeadingRespondentPrimaryKey" msdata:PrimaryKey="true"> <xs:selector xpath="." /> <xs:field xpath="Headingldentifier" /> 15 <xs:field xpath="Samplelidentifier" /> </xs:unique> <xs:keyref name="Head ing HeadingConceptSample" refer="HeadingPrimaryKey"> <xs:selector xpath="." > 20 <xs:field xpath="Headingldentifier" I> </xs:keyref> <xs:keyref name="SampleHeadingConceptSample" refer="SamplePrimaryKey"> <xs:selector xpath='"." I> 25 <xs:field xpath="Sampleldentifier" /> </xs:keyref> </xs:element> <xs:element name="SegmentSort"> <xs:complexType> 30 <xs:sequence> <xs:aelement name="ldentifier" type="xs:integer" nillable="false" /> WO 2005/041058 PCT/AU20011001451 25 <xs:elemnent na me="atego ryBrandHeadingdentifi er" type="xs-.integer nillablo='falso" /> <xs: element name'Samnplelde ntifier" type="xs:integer~ nillable='true" /> 5 </xs:sequence,> </xs:complexType> <xs:key name="SegmentSortPrina ryKey" mad ata: PrimaryKey="true,"> c<xs:selector xpath=". " /> 10 xs:field xpath="Identifier" 1> </xs:key> <xa: ke yref name="HeadingSegmentSort" refer--"Heading Primary Key"'> <xs:selector xpath="." /> .15 <xs:field xpath="CategoryBrandHeading Identifie" > <xs:keyref> ,<xs~keyrof .name="SamnpleSegmentSort" refor="SamplePri maryKey"> <xs:selector xpath="." I> 20 . <xs:fleld xpath=;"SamnpIeIdeniiier" 1> <Ixs: keyref> <Ixs:element:> <xs elementt nanie="fSegmentSort~omnposition"> <xs :complexType> 25: <xs:sequence> <xs:element name="SegmentSortdentifier" typ9="xs:integer" nillable="false" J> <xs:element nane ="Brand Picture Head ing Identifier" type="xs:integer" nil Iable ="false" I> 30 </xs:sequence> </xs:complexType> msdata: PrimaryKey="truen> WO 2005/041058 PCTAU20011001451 26 <xs~selector xpath=".

t P> <xs:field xpath="SegmnentSortld entifier 1> <xs:field xpath"B rand Pictu reHeading Identifier' f> <Ixs:key>. 6<xs:keyref name="SegmentSortSegmentSortComposition" refer--"SegmentSortPrima ryKey">. <xs:selector xpath=" /> <xs:field xpath="S egmentSortl dentifier" I> <qxs:keyref> 10 <xs:keyref namne="HeadingSegmentEortComposition" refer--"Heading PrmaryKey"> <xs~selector xpath="." /> <xs:field xpathB rand P ictu reH eadi ng Identifier" I> <fxs:keyref> 15 </xs:elemnent> <xs:element nameo="Commentary"> <xs:complexType> -ixs:sequence> <xs: element namne="Identfier"' type="xs: integer"* 20 nilI abe="false"></xs: element> <xs: element name=HAnalysisFra meworkldentiler" type="xs: integ or" nillable="false" /> <xs:element name='Type" type="xs:striJng" nillable="false" /> 25 <xs:element name="Text" type='xs: string" nillabe='Talse" /> </xs:sequ onco> </xs:compIexType> <xs:key name="CommentaryPrimaryKey" 30 msdata: Prima ryKey="true"> <xs:selector xpath=: " I> <xs:field xpath="ldentifier" /> <z/xs: key> WO 2005/041058 PCT/AU20011001451 27 '<xs: koyref name="Ana§IysisFrameworkComme ntary" refer="'AnalysisFramewo rkPrimaryKey"> -xs:seleclor xpath="." /> <xs:field xpath='AnalysisFrameworkIdentifiee' > 6 <Ixs:keyref> <4xs elementn> <xswelement name="aCommentaryAnaysisFramework"> <xs:o~omplexType> <xs.:sequence> 10 '<xs:oerement name="Commentary~cdentifier" type='xs: integer" nillable="falSe"I>" <xselemnent name="Headingldentifier' type="xs: integer" n iI~able="true" I> <xs:element flame="Sampleldontifier" 15 type="xs:integer" nillable='trud I> <Jxs.,sequence> </xs;:co mplexTyp'e> <xs:key name ="Analysis Fra mework~omme nto ryPri mnaryKey" mnsdata :PrimaryKey="true"> 20 <xs:selector xpath=".' t I> <xs:field xpath="Commentaryl dentifier" I> </xs;key> <xs:keyref name="CommentaryCommentaryAnalysisFramework" 25 refer--"CommentaryPrimaryKey 1 > <xs:selector xpath=,,.l I> <xs:field xPath="Commentaryidentifier" 1> <fxs:keyref> <xs: keyref name="H-eadingCommentaryAnalysi s~rameworK' 30 refer="H-eadingPrimaryKey"'> <xs:selector xpath="," /> <xs:field xpath=" Head ingl dentifierV' /> </xs: keyref> WO 2005/041058 PCT/AU20011001451 28 .cxs:keyref name="Sam pleCommentaryAnalysisFramework" refer="SamplePrimaryKey"> <xs:selector xpath="." I> <xs:fleld xPath="Sampleldentifier" I> 5 </xs:keyref> <fxs:elementp <xBelement name="CommentarySegmentSort"> <xs:complexType> <=ssequence> 10 <xs-elerent name="Co-mentaryIdentifier"' type="xsintegr" niIIabIe= faIse" /> <xs:eleme nt name=!SegmentSortIdentifie r' type="xs: iitege e' n illabl-e="false" /> <msellement name="Headingidentifie'. 15 type="xs: integef" niIIable="false" I> <1xs :sequence> </xs:complexType> <xs: key name="CommentarySegmentSortPrimaryKey" msdata :PrimaryKey="tru e"> 20 <xs:seiector xpath= ." /> <xs:fleld xpath="Com mentaryientitier" I> <Ixs:key> <,xs:keyref name=

M

"CommnentaryCommentarySegmentSort' refer='CommentaryPrimaryKey'> 25 <xs: selector xpath=~ /> <~xs:fleld xpath=*Commentarydentifier />, <fIxs:keyref> <xs:keyref riame="SegmentSortCommentarySegmentSort" refer--"Seg mentSortPrimaryKey'> 30 <msselector xpath="." /> '<xs:fleld xpath="SegmentSortldentifier 1> <fxs:keyref> WO 2005/041058 PCT/AU20011001451 29 <xs:keyref narne="HeadingCommentaryS egmentSort' refer- HeadinqPrimnaiyKey"> <xs~selector xpath=".' /> <cxs:field xpath"HadingIdentifier" 1> 5 </xs: keyref> <lxs:elemnenp <xs:elemnent name ="Comnmenta ryC orceptProdecesso r> <xs:complexType> <xs~sequernce> 10<xs:element namne="Comnmentaryidentifier" type="xs:integer nillable=--false& 1> <xs elementt nae-Pe~cso~ednietfe' type="xs:integer" niIlable="falsew 1> <xselemnent 15 name='SuccessorH eading Ientifier" type="xs: integer" n ilable="fai se" J> <fxs:sequence> <fxs:cornpI exType> <xs: keyref namne="CommentaryComm-enta ryConceptPredecessor" 20 trefer--"CommentaryPrimaryKey"> <xs:selector xpath=".- I> <xs:field xpath="Commentarydentifier"' /> </xs:keyref> <xs:keyref 25 na me="HeadingComnmenta ryConceptPredeacessore' refer='Heading PiraryKey"> <xs-.selector xpath=. /> <xs:field xpath="PredecessorHeading Identifier" /> <I/xs: keyref> <xe :keyrof 30 na me="Headin gCommentaryConceptFredecessorl" refer="HeadingPrima ryKey"> <xs-.selector xpath='." I> .s :field xpath="SuccessorH lead ing Identifier" /> WO 2005/041058 PCT/AU2004/001451 30 </xs:keyref> </xs:element> <xs:element name="Query"> <xs:complexType> 5 <xs:sequence> <xs:element name="Identifier" type="xs:integer" nillable="false" /> <xs:element name="N~me" type="xs;string" riillable='"false" /> 10 <xs:element name="Type" type="xs:string" nillable="false" I> </xs:sequence> <txs:complexType> <xs:key name="QueryPrimaryKey" 15 msdata:PrimaryKey="true"> <xs:selector xpath="." > <xs:field xpath="Identifier" /> </xs:key> </xs:element> 20 <xs:element name="QueryAnalysisFramework"> <xs:complexType> <xs:sequence> <xs:element name="Queryldentifier" type="xs:integer" nillable-"false" /> 25 <xs:element name="AnalysisFrameworkldentifier" type="xs: integer" nillable="false" /> </xs:sequence> </xs:complexType> <xs:key name="QueryAnalysisFrameworkPrimaryKey" 30 msdata:PrimaryKey="true"> <xs:selector xpath="." /> <xs:field xpath="Queryldentifier" /> <xs:field xpath="AnalysisFrameworkldentifier" [> WO 2005/041058 PCTAU20011001451 31 <fxs:key> <xs: koyref name ="Q u eryQu eryAna lysis Framework" refer='QueryPrimaryKey 5 <xs-: selector xpath= ." /> 5 <xs:field xpath ="Querylde ntifier /> <Ixs:keyref> <xs:keyref name='AnalysisF rameworkQueryAnalysisFrartework" refer='-Ana lysisFrameworkPrjirKey"> 10 <xs~selector xpath="." I> <xs:field xpath =Analysis Fram eworkld entifier' /> <I xs:keyref> <Ixs:elemnent> <xs:oiement name="Querylleading'> 15 <xs:complexType> <xs.-sequence> <xs: element name="Querydentifie' type="xs:integer" nilIlable="false" /> elementt name ="Headi n gidenifier" 20 1type=wxs:integer" nillable="false& 1> <fxs:sequence> </xS:Compl exType> <xs:key namne='QuaryHead inglPrirnarylKey" msdata:Pri mnaryKey='true'5 25 <xs:selector xpath=".' I> <xs:field xpath= 1 'Queryldentifier" 1> <xs~leld xpath=" Heading Identifier" 1> <Ixs:key> <xs:keyref narme ="QueryQueryl-e ading" 30 refer--"QuerYPrimarKey"> <xs:selector xpath="." I> <xs:field xpath=1"Queryldentifier" /> </xs:keyref> WO 2005/041058 PCT/AU20011001451 32 <xs:keyref namne="HeadingQueryHeading" refer="HeadiingPri maryKey"'> <xs:selector xpath="." I> <xs:fleld xPath="Headingidentifier" I> 5 <Ixs:keyref> </xs:element>, <xs:element name="Qu eryS ample"> -<xs:complekType>. <xs:sequence> 10 <xs:element name="Queryidentifier" type="xs:integer" nillab e="false /> <xs:element name="Sampl elden Wiier' type="xs: integer' nillabi e;-"true" /> </xs:sequence> 15 </xs:comnplexType> <xs:unique namne= t QuerySampIePrimaryKey" msdata:Pri maryKey=-"true"> '<xs:selector xpath=".U I> <xs:fieid xpath="Queryldertifier" /> 20 <xs:fleld- xPath="Sampleldentifier" /> e-/xs:unique> <xs:keyref name=h QueryQuerySample"a refer--"QuerPrimnaryKoy"> <xs:selector ,cpath=".

1 ' I> 25 <Xs:field xpath="Queryldentfier" 1> -</xs:koyref> <xs: keyref namne="SampleQuerySample" refer--"Samnp~ePrimnaryKey'> <xs:selector xpath="." /> 30 <xs:field xpatIh="SamnplIdentifier" / <Ixs: keyref> </xs:eIernent> <xs:ejlsment name="QueryCommrentary'> WO 2005/041058 PCT/AU20011001451 33 <xs~complexType> <xs:sequence> <xs:element name="Queryldentifier" Iype="xs:integer" nillable="falsel" /> 5 'xs:elemnent name="CommentaryType" type="xs:stri ng" nillable="falWe 1> </xs sequenceo> <Ixs:complexType> '<xs: key name="QueryCommentaryPrimaryKey 1 10 msdata :PrlmaryKey="true"> <xs:selector xpath="' k <xs:fIeld xpath="QueryIde ntifier" 1> 'Ixs:key> <xGkoyrof name="QueryQueryCommentary"' 15 refer--"QueryPrImaryKay"> <xs.,selector xpth=.wI i> <xs:fleld xpath="QuerYldentifier" I> <1xs: keyref> </xs:element> 20 <xs:element na mo='QuerySegmentSorv'> <xs:complexType> <xs:sequence> <xs:element name="Queryldeitifier" type ="xs: 1ntege r' nil Iable="false" 1> 25 <xs:eiement name L" Resu ItType" type="xs:string" nillable='faise 1 ' I> <xsvelemont name="ScopeType" type="xs:string" nillable="false" I> <xs: element na me="Pare ntl-leadingsOnly' 30 tYpe="xs:boolean" nilfable=' t false" /> '1Ks:sequence> </xs~complexryp9> WO 2005/041058 PCT/AU2004/001451 34 c<xs-.key name="QuerySegmentSortPrimaryKey" msd ata:PrimaryKey='true'5 <xs:selector xpath="." /> <xsvfield xpath="Queryldenifier"' > 5 <Ixs:key> <xs:keyref name="QueryQuerySegmentSort" refer--"QueryPrmaryKey 9 > <xs:selector xpath=".". P. <xs:fleld xpath="Queryldeiifier" I> 10 <ixs:keyref> <xS;element> <xs:element flame="QueryText"> <xs:oomplexTypo> <xs:sequence> 15 .cxs:element na me="Queryldentifier' type="xs:linteger' nillable="false" I <xs:element name="searchFor" type="xstring" nillable="false" J> <xs:element n ame= "Match Case" 20 type="xs:boolean" nlllable="fala' 1> <xs: element name="FindWholeWor-dsOnly" type="'xs:boolean" nil Iable="false" I> <xs: element name-"Commextary#Type" type=wxs: -string" n illable="rfalseK P 25 <xs:element name="ScopeType" type~uxs: string" n illable=Lfalse,7 /> </xa:sequonoo> </xS:complexType> <xs:key name="Qu eryTextP rimaryKey" 30 -msdata:PrimaryKey="true"> <xs~soector xpath="." I> <xs:field xpath="Queryldentifier"I/> </xs:koy> WO 2005/041058 PCTAU20011001451 36 <xs: keyref n ame="QueryQueryText" refer--"QueryPrimaryKey"> <xs:select6r xpath=".' /> <xs:field xpath="Queryldentifier" 1> 5 </xs:keyref> </xs:elemenI> <mse lenient name='Que rySampleCharateristicValue"'> <xs:complexType> <xs~sequence> 10 <xs:element name="QueryI dentifier" type="xs: integer" nillable="false" /> <xsmelement name- SampleC haracteristic~alu elde ntifier' type="xs:integer" nilla blae'alse 1 /> <Ixs :sequence>, 15 </xs:complexType>. <xs: key name="QuerySa mpleCharacteristicVa luePrimaryKey" msdata :PrimaryKey='tru a"> <'xs: selector xpat-= o.## /> 20 <xs:field xpath="Queryldentifier" /> <xs:field xpath="SampleCharacte risticVaiu eldentifier" 1> <Ixs:key> <xs:keyref name="QueryQuerySampleCharateristicValue" 25 refer-"QueryPrima ryKey"> <xs:selector xpath="." 1>. <xs~fjeld xpath="Querydeitifi er" /> <xs:keyref 30 name- SampleC haracteristicValueQuerySampleCharacteristicValue" refer="SampleCharacteisticValuePimaryKey"> <,,xs:selector xpath="." I> WO 2005/041058 PCT/AU2004/001451 36 <xs:field xpath="SampleCharacteristicValueldentifier" I> </xs:keyref> </xs:element> 5 <xs:element name="Sample"> <xs:complexType> <xs:sequence> <xs:element name="ldentifier" type="xs:integer" /> 10 <xs:element name="Name" type="xs:string" I> </xs:seq u ence> </xs:complexType> <xs:key name="SamplePrimaryKey" msdata:Prima ryKey="true"> 15 <xs:selector xpath="." /> <xs:field xpath="ldentifier" /> </xs:key> </xs:element> </xs:schema> 20 While this invention has been described in connection with specific embodiments thereof, it will be understood that it is capable of further modification(s). This application is intended to cover any variations uses or adaptations of the invention following in general, the principles of the invention and including such departures from the present disclosure as come within known 25 or customary practice within the art to which the invention pertains and as may be applied to the essential features hereinbefore set forth. As the present invention may be embodied in several forms without departing from the spirit of the essential characteristics of the invention, it should be understood that the above described embodiments are not to limit the present 30 invention unless otherwise specified, but rather should be construed broadly within the spirit and scope of the invention as defined in the appended claims. Various modifications and. equivalent arrangements are intended to be included within the spirit and scope of the invention and appended claims. Therefore, the WO 2005/041058 PCT/AU2004/001451 37 specific embodiments are to be understood to be illustrative of the many ways in which the .principles of the present invention may be practiced. In the following claims, means-plus-function clauses are intended to cover structures as performing the defined function and not only structural equivalents, but also 5 equivalent structures. For example, although a nail and a screw may not be structural equivalents in that a nail employs a cylindrical surface to secure wooden parts together, whereas a screw employs a helical, surface to secure wooden parts together, in the environment of fastening wooden parts, a nail and a screw are equivalent structures. 10 "Comprises/comprising" when used in this specification is taken to specify the presence of stated features, integers, steps or components but does not preclude the presence or addition of one or more other features, integers, steps, components or groups thereof.

Claims (21)

1. A method of inputting data into a qualitative research tool, the method comprising the step of 5 inputting the data in association with a heading.

2. A method as claimed in claim 1, wherein the heading is a concept heading.

3. A method as claimed in claim 2, wherein the concept heading comprises a 10 concept and predecessor concept.

4. A method of inputting data into a qualitative research tool, the method comprising the step of inputting the data in association with a sample, 15

5. A method as claimed in claim 4, wherein the sample is a respondent.

6. A method as claimedin claim 4, wherein the sample is a sub-sample. 20

7. A method of inputting data into a qualitative research tool, the method comprising the step of: inputting the data in Commentary format, such as an AVI format.

8. A method as claimed in claim 7, wherein the AVI format represents 25 Articulation, Verbatim or Interpretation (AVI).

9. A method as claimed in claim 7 or 8, wherein Articulation, substantially what the research participant said, preferably expressed in the words of the researcher, 30 Verbatim, substantially a reproduction of substantially all, or a representative part, of a respondent's comment, such as a direct quotation fro a research participant, and WO 2005/041058 PCT/AU2004/001451 39 Interpretation, substantially the researchers observations, interpretations and conclusions on what the research participants said.

10. A method of analysing data input into a qualitative research tool, the, 5 method comprising the step of analysing the data input in accordance with commentary, such as AVI.

11. A method as claimed in claim 10, wherein the step of analysing is conducted as the data is gathered. 10

12. A method as claimed in claim 10 or 11, further including the step of: marking-up on an originally imported document.

13. A method as claimed in claim 12, wherein the mark-up is conducted as 15 research is conducted.

14. A method as claimed in claim 12 or 13, wherein the marking-up enables data to be allocated to a selected heading or commentary, such as AVI. 20

15. A method of inputting data into a qualitative research tool, the method comprising the step of: defining relationships between data, based on unique indicia.

16. A method as claimed in claim 15, wherein the indicia represents a problem 25 statement, brand and/or picture.

17. A method of arranging data in a qualitative research tool, the method comprising the step of: providing an analysis frameworks for inputting, analysing andlor 30 interpreting research findings wherein the framework has a hierarchical structure. WO 2005/041058 PCT/AU2004/001451 40

18. A qualitative research tool, said tool including: processor means adapted to operate in accordance with a predetermined instruction set, said tool, in conjunction with said instruction set, being adapted to perform 5 the method as claimed in any one of claims 1 to 17.

19. A computer program product including: a computer usable medium having computer readable program code and computer readable system code embodied on said medium for facilitating 10 qualitative research analysis in conjunction with a data processing system, said computer program product including: computer readable code within said computer usable medium for performing the method as claimed in any one of claims 1 to 13. 15

20. A schema as herein disclosed.

21. A data model as herein disclosed.