VB App Full Product Copy Feature

Update our existing ObjectPublisher Offline Editor (OLE) Visual Basic database editing application to support a Product ??" Full Copy feature. Currently the application supports separate Product and Item Copy actions. What we want is to add an optional deep copy of a product instance which copies the Product and all of it’s child instances. The current shallow Copy Product action only copies a Product, and child Graphic, Additional Information, and Attributes. Child Product Items and their children (e.g. Product Item Attributes, Prices, Customer SKU Number, etc.) are not included in this copy. ## Deliverables **Project Name:** ObjectPublisher Offline Editor (OLE) Full Product Copy **Project Deadline:** 1 4 days from Bid Acceptance **Project Summary:** Update existing ObjectPublisher Offline Editor (OLE) Visual Basic database editing application to support a Product ??" Full Copy feature. Currently the application supports separate Product and Item Copy actions. What we want is to add an optional deep copy of a product instance which copies the Product and all of it’s child instances. The current shallow Copy Product action only copies a Product, and child Graphic, Additional Information, and Attributes. Child Product Items and their children (e.g. Product Item Attributes, Prices, Customer SKU Number, etc.) are not included in this copy. This option should be provided to users on selection of the current Copy Product action wherever it may be exposed (i.e. Menu Button, mouse-click menu, etc.). Specifically, on selection of Copy Product, the user should be presented with a dialog box prompting them to choose 1) Shallow ??" Product Only (default) or 2) Full ??" Product and Items. Selection of Shallow should result in the current Copy Product action. Selection of Full should result in copying the product and all child class instances. Please note that this task will be the first in a long list of updates for this application. Specifically we are looking for an experienced developer who can take over primary responsibility for the maintenance and enhancement of this production application. Specifically, developers who bid on this project/task should only do so if they are willing to initiate a long term relationship with our company. Additionally, it is critical that the developer * be organized and disciplined for regular communication/support from/to our project management team * provide reliable work estimates * consistently communicate status (every few days) * prepare detailed release notes * check and respond to email daily (i.e. be available) * test enhancements sufficiently prior to release * participate in and extend design architecture (e.g. offer design alternatives) Total experience is highly desired but not as important and definitely not a replacement for the previous list of developer requirements. Specifically it is more important that the developer be reliable and efficient in meeting project requirements than in absolute experience in Visual Basic programming. Additional skills which are desirable but not required include * Java * Apache * Tomcat * Hibernate * JSP * PHP * Ajax **OLE Development Environment:** VB6 SP6, and Visual C++ 6 **OLE Application Description:** OLE is a Visual Basic application which provides a GUI interface to a local Microsoft Access relational database. Users populate this database by logging in and downloading data from our Product Information Management (PIMS) server as separate class files (i.e. Product, Graphic, ProductItems, etc. ) in tab-delimited text file format (dtf). These text files are structured similar to the relational tables in the OLE local Access database. The download process retrieves, parses, and then imports the files into the local OLE database structure for offline user editing. Users can then post their updates to the server as often as desired. This process involves preparation and posting of the modified data in the standard dtf structure to the server, and processing of the server response for errors, etc. Additionally, OLE will do request a CheckSum value from the server for comparison with local data to provide a rough check on data consistency. Additional features within OLE include * Excel Import/Export * Tab-Delimited Text File Import/Export * Graphic Import * Basic and Extended Attribute Models * Change Reports * Drag/Drop Editing * Auto-Synch with Server **Standard PIMS Class File Structure:** Central to working with OLE is a comprehensive understanding of the standard dtf file structure used for export and import to the ObjectPublisher Web Service PIMS database. Documentation on this structure can be reviewed in the Managing Your Product Data sub-menu at [[login to view URL]][1]. **ObjectPublisher Web Services API:** All communication with ObjectPublisher Web Services is done via simple http(s) api calls. This includes use validation, downloading customer-specific application parameters (i.e. controls OLE behavior for customer), downloading product/item data, uploading product data to servers, running change reports, etc. Relevant documentation on this api can be reviewed in the following links. **Security Manager API:** ftp://[login to view URL] **On-Demand Publishing API:** ftp://[login to view URL] **Sample Release Notes:** A sample well written release note documentation can be reviewed at [Sample Release Notes][2]