[url removed, login to view] provides links to stock groups, we have scripts that download this data and place it in a mysql database. Stocks belong to groups and groups belong to sectors. We have decided to farm out the last part of a script that updates the database. This script is called [url removed, login to view], and it keeps track of changes to sectors, groups and stocks (changes between yahoo and our current DB state). But it lacks a complete management of Stock Membership changes. Bear in mind a stock can change not only its symbol, company name, url locations, but could also leave and reenter a group as well as be moved from one group to another. Symbol changes are being tracked and updated. 4 letter symbols could have a fifth letter added, and then removed, and any symbol (1-5 letters) can have a .ob or .pk added or removed anytime, and many times. These changes are being handled. But when that happens the Group membership table "GroupStocks" would need to be updated to reflect the change. This DB holds information from multiple sources, these sources are differentiated by sectorroot_id, but stocks are unique and can belong to none, one or more sectorroot_id. If a Stock name changes, all sectorroot_ids in GroupStocks must be updated. in sumary: The GroupStocks table has the group memberships, and the Log table logs the changes for historical purposes, so these two tables need to be updated. These are the changes I anticipate: -Symbols could have been renamed. -Symbols could move from one group to another. -Symbols could get dropped from a group. -Symbols could get added to a group. -If a symbol changes its name, the change needs to be reflected in the GroupStocks table. Please see [url removed, login to view] in the attached zip for all project requirements.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).