An advertising manifest is a form used by publications, such as newspapers, showing which ads are scheduled to be run in a particular issue. The software I am requesting bids on will be a web-enabled database application tracking advertisers and the ads that they run. There will be different reports to be generated for printing. This system has to be able to handle multiple publications per ad entry. Some ads will run only once; some will run a set number of times; some will run until cancelled.
Publication: A newspaper or special edition for which advertising must be tracked separately; “Daily Bugle?? or “Home and Garden Show Tab??
Customer: An advertiser
Insertion Order: The transaction by which an advertisement is scheduled. Elements of an insertion order include customer, size of ad, first date of insertion, and what publication(s) it is for.
Columns: The horizontal measure of an advertisement. In a six-column newspaper, an ad that is three columns wide goes halfway across the page.
Depth: The vertical measure of an advertisement. Measured in inches.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Installation package that will install the software (in ready-to-run condition) on the platform(s) specified in this bid request.
3) Exclusive and complete copyrights to all work purchased. (No GPL, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site).
I envision the application using four tables, as laid out below. This is by no means an inflexible list; you're free to change this as necessary to meet the bid requirements.
* Inches per page
* Pub day of week (whether the publication comes out on Wednesday, Thursday, Friday, etc)
* Contact Person
* Customer (links to Customer table)
* First date of insertion
* Times to insert (0 for until cancelled?)
* Price of ad
* Comments (needs to be a pretty good sized free-text entry field, 4k would be plenty of space)
* Publications (that it is scheduled to run in, can be multiple)
* Salesperson (that sold the ad, links to Sales table. Can be null)
* Commission (numeric field)
* Rate (a decimal value between 0 and 1)
When the sales agent keys in the insertion order, they will provide the following information:
* Columns across
* Inches deep
* First date of insertion (pull down menu)
* Number of times ad will run
* Choose which publications it will run in
* Cost of the ad
* Which ad salesperson sold the ad
* Amount of commission (the default should be the cost of the ad times the commission rate, but the user has an opportunity to change the default)
There should also be input screens for the customer, publication and sales tables.
The main report is the Advertising Manifest. The inputs for the report should be the publication and the publication date. This report should list all ads scheduled for that publication, in descending order of size. The information needed is the customer name, columns, depth, and size (the product of columns and depth).
There should be information at the bottom of each page (like a footer) that includes the publication name, pub date, and how many pages of advertising there are throughout the entire publication. To arrive at this, add up the size of all ads in the publication.
For example, if there are 1007 column inches of advertising in the publication, then the program would report 12.59 pages of advertising.
Other useful reports would be commission reports (give a date range and it lists all ads per salesperson, commission on each ad and total commission per salesperson) and advertiser reports (give a date range and it generates a list of each advertiser and the total column inches they ran during that time).
All reports should be formatted to print on [url removed, login to view] paper.
It is a good idea to put in some security, since it is web based. But there is not a need for individual user security here; convenience and speed have a higher premium. Ideally, there will be a username/password that will be stored in a cookie so that the user doesn’t have to key it in every time.
If requested, I will provide an account on the server on which the software will ultimately run, accessible via ftp and ssh.