Data Clean-Up Tool

Our small consulting firm often helps customers implement CMMS systems. The quality of legacy equipment and spare part data is often poor and we have to try and clean-up. Today? we use spreadsheets for review and sign-off purposes, but think a more structured approach would yield better results and differentiate us from our competitors. ? I need a tool that presents XML data? in a treeview in one window and offers the attributes of the selected node? for editing in an adjacent window. Prefer WPF with VB. ## Deliverables Layout/concept: Please examine XAML attached. Note, this xaml is a mock-up to show layout and? relative sizes? you can change anything you need to including the controls. XML: Sample of XML attached. Typical file will have 300-400 nodes in three levels. Max file will have 1000 nodes in 5 levels max. Header_1 and Header_2 are always attribtues of the root node. The application will display the xml nodes in a tree control on the left with the atributes of the currently selected node on the right (SEE XAML). The? HEADER value? of the treeitem? is the attribute _NAME in all cases.? There is no drag and drop required. The user is not allowed to change the structure of the tree. All attributes of the selected node will appear in the right hand pane in a tabular format. The right hand pane should scroll up/down to accomodate lists of attributes longer than the window. The first column will be the attribute which will not be editable. The second column will be the value of that attribute. Attributes will not always be the same for all nodes in a file. Attributes that do not begin with an underscore character have values that are read only. That is they will be shown in the right hand pane but cannot be edited by the user. See attributes EQNUM and STATUS in the XML file for example. I would prefer that the attribute value text boxes word wrap to stay in the width of the right hand pane. However, if this is problimatic then allow the right hand pane to be scrolled left/right as well as up/down. On node attrbutes that begin with an underscore, the last two characters of the attribite name should resovle to an integer value. This is the fixed? length of the text? permitted for the value. If they do not resolve to an integer value, the default length is? 255 characters. Note that the values in the XML file may be longer than the indicated? value so that they will be truncated when displayed. (These values are often coming from a legacy system with no data validation). The changes or edits should not be saved to the XML file until the user selects the? SAVE button. All nodes except the root node will always have the attribute STATUS. When the user edits a node the STATUS attribute will be updated to "CHANGED" The? EXIT button will exit the application. It should warn for unsaved changes but permit the user to abandon changes or not.