Normalize existing HTML output to simple table

An existing web-based report needs to have some very minor formatting changes made, with the overall goal of changing the output to a single, simple, unstructured HTML table. This will allow us to easily copy the data into Excel spreadsheets. **Background:** We recently acquired a website, and are in the process of issuing our first series of payments to our publishers. There are some changes which need to be made to the report which will be used to generate this information Friday. **Time Constraints:** These changes need to be **completed by 9am (Eastern) Friday** at latest, in order to facilitate said payments. **I will be out of the office after 3pm (Eastern) Wednesday** through early Friday, so *all* questions need to be asked between 9am and 3pm (Eastern) Wednesday. If you are *not* available to work with these time constraints, please *do not bid*. You do not need to be available during the entire six hours, just enough time so that we can engage in a normal conversation to clarify any unclear portions of this specification. You'll also have to sign the NDA during this period. You'll then have 42 hours in which to perform the actual work. ## Deliverables **To complete this project, you need to do each of the following:** **1.** You will be given root password for three servers. Create a normal user account for yourself, ensure that the files in question are accessible by the new account, and then **use that new account** (not root) for the rest of your work. You will be given a URL which displays a report with a table of existing data. It is *critical* that you **do not push** the buttons marked "generate" or "commit", or you will cause much data loss for us. All of your work can be done on the *existing* data. **2.** The table *should* allow left/right scrolling, as the new report *will* (and should) exceed most browser widths. This may very well be as simple as *removing* the table's "width=100%" attribute. **3.** The column "Payment Method" currently outputs two different pieces of data per row, e.g., "regdmail moneyorder". This should be split into two separate columns, called, "Sending Method" and "Instrument". Thus, in the above example, the Sending Method will be "regdmail" and the Instrument will be "moneyorder". **4.** If the "Sending Method" is blank or null, it should display, "web". If the "Instrument" is blank or null, it should display, "paypal". **5.** The "Notes" column currently outputs a nested table with two columns (per row). The inner (nested) table structure can be removed, and its two columns should simply be two columns of the primary table. These should be labeled, "Carryover" and "Edit", i.e., replacing the "Notes" label and column. **6.** A new column called "PayPal Address" should be appended to the right of the above "Edit" column. The following procedure is offered to you strictly so that *you* can find the PHP code and SQL query which fetches this data; once you determine the correct way of getting the address, simply display it in the new column. If blank or null, display nothing. Copy (to your clipboard) the first name of the third publisher shown in this report. Click on the upper left graphic, marked "Admin Home". Paste that name into the "Account search:" field and click "Go". To the right of the word, "Lists", you will see a blue button with an envelope, and then a second blue button depicting an arrow pointing to a person. Click that latter button. On the left side of the screen, you will see a link entitled, "Account Settings"; click on that. Scroll down, and you will see a field marked, "PayPal Email:"; note that this is *different* than the email address near the top of the page. **7.** Remove the "Payment Address" column, and move *all* associated data to new columns to the very right of the table, in the same order as currently presented, except that the country column should *follow* the zip code column, rather than precede it. For example, if the current Payment Address consists of Address1, Address2, City/Town, State/Province, Country, Zip, then you would append six new columns to the right of the table, each which displays only *one* piece of data per column. The names of the columns in this example would be, "Address1", "Address2", "City/Town", "State/Province", "Zip", "Country". If there are other fields that are being displayed which I can't see, simply add more columns as appropriate. The important thing is to display the exact same *amount* of data, but split into separate columns. You should remove all instances of "<br>". **8.** The report is currently sorted by publisher first name. This sort order should be changed to the following: instrument + sending method + country + zip code + city + account id. If this point ends up being incredibly complex, it's not crucial, and could be compromised as needed. **9.** There are three parallel webservers, (which are managed with a web load balancer), and the identical change needs to be **uploaded to all three**. Furthermore, on *each* server, *any* file which is modified needs have its *original* version (i.e., prior to modification) copied using cp -p (to preserve all meta-information) to the corresponding location ../archive/*filename*.php.*YYMMDD* , using the original file's file modification timestamp. In short, we don't (yet) have a code version management system, and we **need to be able to "roll back" changes** in case of a problem. | ![PGP][1] | You must have a PGP (or compatible) program. All data will be transmitted in a PGP-encrypted form, and we expect you to do the same. Coders will be expected to provide their PGP public key. Strong preference will be given to Coders who provide this key _in their bid_. | | ![NDA][2] | You will be expected to sign our non-disclosure agreement (NDA) (*and follow it!*) upon winning this project; we will be transmitting our sensitive corporate data, as will you. You need to sign the NDA using PGP, as this is now legally binding, as per the US Federal Electronic Signatures in Global and National (ESIGN) Commerce Act of 2000. If you are not prepared to do this, please do not bid. | We will retain full legal rights to the code and/or data upon completion. All code and/or data is and becomes *our* intellectual property! You will *not* have any rights to the code and/or data in any fashion. **Thank you for your consideration and for bidding through RentACoder!** * * *Copyright © 2005, Buyer [notecom][3]. **All Rights Reserved.** Reproduction without permission is strictly prohibited. * * *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). ## Platform Linux, MySQL, PHP (CGI). Possibly Perl, but not very likely.