Back to top



What it means for some EServer collections to be "database-driven".

 the TC Library database-driven website
 the Journals database-driven website

In traditional web publishing, the writer/web designer would create individual files (usually in HTML), then copy those to the webserver. To update information involved editing the HTML file and then copying the newer version, replacing the older one.

Database-driven websites are organized quite differently. They have template files, using a server-side include language such as Lasso or PHP, which constitute a skeleton for page information, then call the actual contents of the page from a database such as FileMaker Pro or MySQL.

Using this sort of a system, one EServer collection (the EServer Technical Communication Library) uses eleven HTML template files in conjunction with a database to generate more than 136,000 pages in total. All of which follow carefully-planned, standards-compliant template designs.

Because of this, any individual entry can be quickly or easily updated. By means of search and replace, the editors could update a large number of records, as needed. And by changing a single template file, the editors could update the look and feel of thousands of pages which would otherwise be quite a complicated process.