How to create QC web pages
	home dfos administration documentation procedures concepts external: QC

This is the internal QC home page. An external page is also available.

How to maintain external QC web pages

Purpose

• the QC process 
• the pipelines
• the data structure, handling and processing.

• Paranal SciOps
• your QC colleagues
• you yourself (memory!)
• the scientific community.

These pages are also meant to be the central memory of all aspects about instrument data quality. Over the years this repository is meant to grow continuously and become the prime reference source about instrument QC and data.

The maintenance of the instrument-specific QC web pages belongs to the core functions of the QC scientist.

The pages require permanent attention and some care regarding styling and information management. 

General rules and recommendations

• All html files must have extension .html.
• Absolute links to eso-internal URLs should be avoided, relative links are recommended. E.g., rather than linking to http:/www.eso.org/images/eso-logo.gif, you better link to /images/eso-logo.gif. This offers independence from www server naming conventions, and the option to develop sets of pages on your local machine.

The ESO webmaster recommends to use the content management system CQ5. However, some of the QC web pages have been developed long before this system became available, and there was no support available for the migration. Hence these pages are still edited and maintained with 'old' templates.

For that case, the ESO webmaster recommends to use the interactive, graphical tool dreamweaver run on a PC.

It is preferrable to look into the existing QC web pages and select them as template.

Specific rules

Below this level, there is one folder per instrument (called VIMOS, ISAAC, UVES etc.). The next level always has folders pipeline, DataManagement, and qc. Older instruments have ServiceMode which is not used anymore but kept for memory. These folders host the HTML files. There may also be folders like tools, txt and img.

• pipeline has in-depth information about data types, data structure, calibration and reduction strategies and recipes etc. The pipeline information should be very much user-oriented, i.e. non-technical, high level. It should primarily answer questions like "why are things done that way". 
• qc is maybe the core of our pages. This folder should host: 
• a documentation of what is QC checked and trended, 
• an explanation how this is done.

It is extremely important to present this information in a user-friendly way, even if this means hiding information. A good QC documentation can become a prime reference e.g. for PSO, for users preparing their applications or working with their data. And it may become the prime reference for yourself (or for your QC colleagues) since it's virtually impossible to keep all QC aspects in mind over the years.

It is a good idea to keep new QC pages as close as possible to this structure since otherwise users browsing between different instruments may easily become lost. 

Alias. The alias http://www.eso.org/qc (or QC) can be used instead of http://www.eso.org/observing/dfo/quality.

Top level index page. The top level page http://www.eso.org/qc/index.html must not be modified without permission of the page owner.

TOC. It's a good idea to have a page toc.html ('table of contents') for the more complex and evolved web structures. This page should be linked to the instrument QC home page.

Implementation. The development of the web pages is done on your PC. Find more here.

Permissions. Permissions for the existing pages are set to read/write access for the whole w3dfo group which actually is the QC group. So be careful about modifications of pages not authored by you! Those pages with virtual includes need execution permission.