URGENT Drupal Programmer required to set up cck fields, content types, relations and views/custom code unique module - repost

I require a Drupal expert to set up the base of a site. I don’t mind if he/she does it through a custom module or uses views, CCK, and node/field reference. In short, the website will be a categorized collection of current printed specials for the means of price comparison. There will be several retailers. Each retailer will have several catalogues. These will be dated so that you can easily see which are current and which are not. Each catalogue will have several pages, and on each and every page, there will be several specials. These all need to be interlinked. The admin will scan the current print specials, and manually upload each one. The Workflow required is the following (I am going to describe it with reference to cck, views and node reference, but like I said if the freelancer feels it better to do it through a custom module, then so be it). There will be 4 content types 1. Retailer (this I imagine being a content type, of which the content types below will reference. Or it can be a taxonomy term, as it will be used as means of a filter, but then it must still be able to contain the information in point 1.a) 2. Catalogue 3. Catalogue pages 4. Specials 1. Retailer a. This node will be static and each retailer will have one. On this node, all information regarding the retailer will be present. This will include name, locations (to be mapped and displayed on a Google map. The GPS co-ordinates of each location must be stored on the database), and their catalogues (see below). These catalogues must include current catalogue, as well as previous catalogues. b. I had initially thought to load the retailers as users (so that content types 2-4 would be created by that specific user), but in terms of display, using it as a node/taxonomy term may be better. 2. Catalogue a. This is the main catalogue item. This item will reference the retailer, and will “hold” all the pages of the catalogue. b. Here you will enter the dates that the catalogue is valid for. 3. Catalogue pages a. This will be all the pages of each catalogue (1 node per page). b. Each page must reference the catalogue. 4. Specials. a. These are the actual specials that appear on each page. b. Each special must reference the page it appears on c. These specials will be categorized (via free tagging) through a taxonomy system. d. Each special must also be mapped on the image (page) it appears on (so that a view can be created of the pages linking the specials). e. Several textual fields will appear here. This will all need to be set up, as well as several views. 1. A view to display current and past specials on the retailer’s page (as well as Google maps). 2. A slideshow of a catalogues pages (with image mapping allowing a user to click on a specific special to see detailed info). 3. Special page (text info, links back to catalogue it appears in.) A system must also be in place to state if this is the best deal for this item, or it another retailer has it on special for a better price. There must also be a display of similar items. 4. Price filters (slider). You will not need to design a full theme, you can in fact work on the Drupal base theme, all styling elements must be stored separately in a unique folder (so that the theme can easily be changed without effecting styling of the above). A detailed training doc (PDF) must be included demonstrating the workflow of uploading a catalo to the website. An ESSENTIAL part of the project is that it must be as simple and quick as possible to load a catalogue and require as few clicks as possible. Please send through your questions. As this is only the setting up on the functionality, with minimal design (and no uploads of catalogues except a test to confirm all works), the budget is extremely limited. You will also need to complete the project in a very short span of time.