In the database relations section you'll note that we have an old archive in Q&A. We will be providing you with this database, plus a link to a site that offers a program (sesame database manager) that will convert this into a modern database that can be then exported as CSV. We want this imported into MYSQL and accessible to our Admin -> Case History -> Search (before august 31st 2007) function. 

We also want a way to backup this database daily. 
It will go unused at night.

The database relations section has been developped by someone with no experience in mysql. As such, understand first what we're trying to accomplish, before you move on to creating the databases. It is quite possible that some of the relations specified won't function accordingly. And it is more than likely that a better solution can be devised by your team. Please confer with us extensively about all vague understandings.
We are also interested in suggestions concerning privacy policies and terms of service. 

Here a few problems that we've attempted to solve, and some that we couldn't even begin to solve.

- Each booking/case has multiple lawyers.
- Each lawyer has multiple secretaries.
- Each booking/case has multiple witnesses.
- Each order can be for specific witnesses.
- If a witness has been ordered by another lawyer. It is important that this be known to the next lawyer wishing to order that witness, since they are getting a copy and it is cheaper.
- During a cross-examination, a lawyer orders an original for their witnesses, and a copy goes to the opposing lawyers.
- There are bookings that are continuations, hence take up multiple dates with identical information. To save time, we need a way to copy this data from one date to another.
- User information colliding with lawyer/reporter information.
- Recent activity display

We want a software company that fully understands the hierarchy of information and what we do.

We are also looking for a company that is willing to make adjustments as we require them in the future.

Design details remain open to discussion, and will be mutually agreed upon before hand. What we believe is required is an horizontal menu bar, in order to allow for more room on the screen to display columns. 
We will gladly max out the 1024 resolution. Font size can be reduced if necessary, but if there comes a time when too many columns have been requested and do not fit on the page, please consult with us.
Color scheme and logo information will be provided at a later date, once the template is defined. We want a relatively clean design with room at the bottom for a footer displaying our contact information; room for our logo in the header. Otherwise as little information and clutter as possible.

Please feel free to make inquiries of any kind. We will go to great lengths to ensure cohesive communication. 

Note: A few very minor modifications may be made before work on the project is begun - nothing beyond changing a field displayed, nothing that should change the quote provided...we will renegotiate if anything substantial changes.