Project: talenddataquality
Issue TDQ-7504: Match Analysis Editor
h3. New analysis Create a new kind of analysis called "match analysis" under the "column set category". h4. User stories *As a* data quality user, *I want* to easily create a profile analysis *so that* I can find duplicate records (just like the tMatchGroup component does). *TODO* write other User stories + acceptance criteria The analysis setting tab is described by the "Match Editor" mockup. h4. Select Data Set the "Create connection" button opens a connection wizard (the first page is the metadata page usually used in wizard, the second page asks the user to choose between a database and a file, the following pages are related to the previous choice). At the end of the creation wizard, the user is asked to select the data (as it would be done in the "select data" wizard described just below). The "Select Data" button opens the columns selection window. When the user clicks ok, a sample of the data is retrieved and displayed in the data table. Notice that the data table has *6* additional columns (all columns related to the matching: GID, GRP_SIZE... and the BLOCK_KEY column) which are empty at the beginning. (Attribute scores is the MATCHING_DISTANCES of the component actually). h4. Adding blocking keys The "Select blocking key" button is a push button. When the button is pushed, the user will be able to add rows into the "blocking key" table by selecting the columns in the "data" table. When the user clicks once on a column in the data table, this column is added to the blocking key table. The selected column header becomes red color. When the user clicks again on the same column in the data table, this column is removed from the blocking key table and the color of the header in the data table is the default. When the user clicks on the button again, then the selection ends. h4. Adding match keys The "Select matching key" button is a push button. When the button is pushed, the user will be able to add rows into the "matching key" table by selecting the columns in the "data" table. When the user clicks once on a column in the data table, this column is added to the matching key table (in all match rules tabs when there several match rule tabs - the first one when no match rule exist yet). The selected column header becomes green color. When the user clicks again on the same column in the data table, this column is removed from all the matching rules in the match key table and the color of the header in the data table is set back to the default color. When the user clicks on the button again, then the selection ends. h4. Removing blocking keys A right-click on a row in the blocking key table will display a "Remove element" menu. This menu will remove the selected key(S) from the blocking table. The "DEL" key from the keyboard must also be enabled to remove columns. h4. Removing matching keys A right-click on a row in the matching key table will display a "Remove element" menu. This menu will remove the selected key(S) from the match rule of the match key table. The "DEL" key from the keyboard must also be enabled to remove columns. h4. Execution prerequisites Selecting a blocking key is optional. The user may not select any blocking key but at least one match key is required. A pop-up should display when the user tries to save or run the analysis without any match key defined. h3. Running charts h4. block chart The "Visualize" button will refresh the charts according to the settings and the data sample. It will also compute the generated key and update it in the data table. h4. match chart The "Visualize" button will refresh the charts according to the settings and the data sample. It will compute the groups and update the corresponding fields in the data table. The chart must be interactive as the one in the tMatchgroup component configuration wizard. h2. Result tab The analysis run button will execute the matching rules against the whole dataset and switch to the result tab. h3. Import, exporting match definitions. The import/export buttons will import and existing match definition from the repository or create a new match rule definition in the repository. The import button overwrite the local match rule. The export button creates a new match rule (hence a wizard as usual to create an item). This wizard is the same as the one for the "new match rule" (if we do it. Maybe, that's not needed).
Story points: 13