| home | news | images | videos | goodies | hubble shop | about hubble | science | kids & teachers | press | projects | jobs |
![]()
The study of this matrix led to the following conclusions:
We ended up with the design for the front page seen in Figure 1. For us this is the compromise between efficiency, searchability, science, visual appeal, ‘action’ and overview that we think caters for the needs of most target groups and the most important users. For Spacetelescope.org there were three main areas of focus in the planning phase. Firstly to plan the functionality of the web site, then to plan the sitemap — ie, the structure (files and directories) and finally to plan file formats and sizes for images and videos — ie, the structure of the metadata. Anyone implementing a web site using the Simplicity scheme that
is described below will need to go through the same three planning
steps and to commit one or two days to set up and adapt the Perl
scripts to specific needs.
Requirements for Simplicity – the web scheme Secondly the technology behind the site juggles huge data files — images and videos — (from 10s to 1000s of MB) in archives containing thousands of items each represented in up to 15-20 different formats (eg, thumbnails, wallpaper, originals etc. for the images), without impeding function or maintenance. Thirdly the maintenance of the web system is extremely easy. Design changes are made in just one place so that the web master is not forced to manually update hundreds of pages. Structural changes such as the addition of new archives are also possible with relatively small changes to the scripts. Finally, the website is relatively ‘CPU light’ and
can, on standard server hardware, handle many concurrent visitors.
Dreamweaver MX is used to edit the html-scripts. Dreamweaver
is a simple and visual commercial editor that enables the easy
editing of web pages, and also provides a template scheme. The
templates define editable areas of a web page, making it possible
to keep a consistent design on all web pages. Any changes made
to a template will cascade to all web pages that are based on
it, and so design changes need only to be made in one place. To
further ease the maintenance load, so-called nested templates
are used, which are templates based in turn on another template.
This makes it possible to define the global design of the website
in one template and create templates for the different sections
based on this global template to hold the individual section design
items and menus.
Instead of using off-the-shelf database solutions that have problems dealing with huge files, a large maintenance overhead and a potentially slow response time, the choice for Simplicity fell on lightweight Perl scripts as the ‘engine’ to create the dynamic web content. In Simplicity the Perl scripts search and show excerpts of the archive metadata that are stored in Excel files (in reality comma-delimited text files). These files hold all the data for each news item, image and video and are edited with Microsoft Excel (or any column-based editor). The metadata include the object ID (for instance the image filename), title and caption. Excel, although not traditional for this type of work, has maintenance-friendly features such as spell checking and is familiar and easy to use. The Perl scripts can format the data/metadata content of the archives in many different ways and also make refined searches possible. Other features are also built into the Perl scripts:
Search functions are provided through a freely available search
engine called “ht://Dig” that indexes all web pages
on a regular basis, and can be customized to fit into the overall
design. Furthermore a freely available link-checker can be implemented
into the scheme to make sure that all links on the web site are
valid. In science communication there is an extreme need for flexibility, and this implies the fully autonomous control of a web scheme and its technical maintenance and flexibility to quickly adapt to new ideas. Most CMS do not provide this. In addition most CMS do not provide the lightning fast response needed. On the down side Simplicity is not a foolproof scheme. No web system is ever 100% foolproof, but our scheme is probably more open to error, especially when used by non-technical staff. Simplicity is also not a multi-user system, in the sense that only one person at a time can edit the page design, or update the individual metadata files. In a normal outreach office none of these issues should present major worries as it is usually staffed with technical personnel and there is no need for workflow control, approval control and version tracking. As a happy side effect, the construction of Simplicity (including the implementation of Spacetelescope.org with all its data and metadata) only required three man-months of work, compared to an estimated two or three times longer for off-the-shelf CMS (with less functionality). Some of this time was naturally invested in an integral knowledge of the scheme which in the long run will contribute towards a reduced total cost of ownership. The total implementation costs were about 13 kEuro. Simplicity’s low-tech solution has already proven its performance capability. Spacetelescope.org is running on a single Apache web server and was able to cope with 2.3 million hits per day (50-60 requests/sec peak load) and the delivery of up to 180 GB of data per day during the first weeks of operation. References
|
|
|
|
|
|
| ![]() Copyright-free material (more info).
|