ࡱ > # T > ? @ A B C D E F r F Z L P l n ( * , . 0 4 8 : < . 0 V v : < f h j l ƒ Ȓ V | V ~ Ɨ ң \ ^ $ & 0 4 mH j UmH 5mH mH OJ QJ 55OJ QJ j U W X Z $ # Design of the LHCb Web LHCb Technical Note Issue: Version 1 Revision: 1 Reference: LHCb COMP 98-xxx Created: 6 May 1998 Last modified: Wednesday, 06 May 1998 Prepared By: LHCb Computing Group Eric van Herwijnen Abstract Document Status Sheet Table SEQ Table \* ARABIC 1 Document Status Sheet 1. Document Title: [Project Name Qualification] User Requirements Document 2. Document Reference Number: [Document Reference Number] 3. Issue 4. Revision 5. Date 6. Reason for change Table of Contents TOC \o "1-3" 1. Introduction PAGEREF _Toc419021800 \h 1 1.1. Type of information to be communicated PAGEREF _Toc419021801 \h 1 1.2. Needs for notification PAGEREF _Toc419021802 \h 1 1.3. Confidentiality PAGEREF _Toc419021803 \h 2 1.4. Tools for accessing information PAGEREF _Toc419021804 \h 2 1.5. Current status PAGEREF _Toc419021805 \h 3 2. Paper documents PAGEREF _Toc419021806 \h 4 2.1. Tools and technology PAGEREF _Toc419021807 \h 4 2.2. Procedures PAGEREF _Toc419021808 \h 5 2.2.1. What system to use PAGEREF _Toc419021809 \h 5 2.2.2. Material for publications PAGEREF _Toc419021810 \h 5 2.2.3. Public notes PAGEREF _Toc419021811 \h 5 2.2.4. Publications PAGEREF _Toc419021812 \h 6 2.2.5. Lectures and Public presentations PAGEREF _Toc419021813 \h 6 2.2.6. Proceedings of conferences PAGEREF _Toc419021814 \h 7 2.2.7. Computer documentation, userguides, release notes PAGEREF _Toc419021815 \h 7 2.2.8. LHCC documents PAGEREF _Toc419021816 \h 7 2.2.9. Private notes PAGEREF _Toc419021817 \h 7 2.3. What to improve PAGEREF _Toc419021818 \h 7 3. Web pages PAGEREF _Toc419021819 \h 9 3.1. Tools/technology PAGEREF _Toc419021820 \h 9 3.2. Procedures PAGEREF _Toc419021821 \h 9 3.2.1. Web design PAGEREF _Toc419021822 \h 9 3.2.2. Implementation PAGEREF _Toc419021823 \h 19 3.2.3. Cookies PAGEREF _Toc419021824 \h 32 3.2.4. Adding/updating pages PAGEREF _Toc419021825 \h 33 3.2.5. BWHO/ColdFusion maintenance PAGEREF _Toc419021826 \h 35 3.2.6. Adding/deleting a new Institute (member of the collaboration) to the database PAGEREF _Toc419021827 \h 38 3.2.7. Adding/deleting a new free participating Institute PAGEREF _Toc419021828 \h 39 3.2.8. Changing the status of an Institute PAGEREF _Toc419021829 \h 39 3.2.9. Adding/deleting a mailing list PAGEREF _Toc419021830 \h 40 3.2.10. Configuration of the search engine PAGEREF _Toc419021831 \h 44 3.2.11. Java programs used by the server PAGEREF _Toc419021832 \h 53 3.2.12. System Administration PAGEREF _Toc419021833 \h 54 3.2.13. Testing of new technology PAGEREF _Toc419021834 \h 54 3.2.14. Private web pages PAGEREF _Toc419021835 \h 55 3.3. What to improve PAGEREF _Toc419021836 \h 55 4. Email PAGEREF _Toc419021837 \h 56 4.1. Tools/technology PAGEREF _Toc419021838 \h 56 4.2. Procedures PAGEREF _Toc419021839 \h 56 4.3. What to improve PAGEREF _Toc419021840 \h 57 5. Discussion groups and news PAGEREF _Toc419021841 \h 58 5.1. Tools/technology PAGEREF _Toc419021842 \h 58 5.2. Procedures PAGEREF _Toc419021843 \h 58 5.3. Improvements PAGEREF _Toc419021844 \h 58 6. Proposed direction PAGEREF _Toc419021845 \h 59 6.1. Definition of the "LHCb Information Management" project PAGEREF _Toc419021846 \h 59 6.2. TDR production policy PAGEREF _Toc419021847 \h 59 6.3. The Web service PAGEREF _Toc419021848 \h 59 6.4. Security PAGEREF _Toc419021849 \h 60 6.5. PIE PAGEREF _Toc419021850 \h 60 6.6. Document archive PAGEREF _Toc419021851 \h 60 6.7. Support and maintenance items PAGEREF _Toc419021852 \h 60 List of Figures List of Tables TOC \c "Table" Introduction The communication inside a collaboration should provide tools for various functions, and allow an easy use of them. This note is an attempt to summarize the user requirements (chapter 1 of this document), to review the current situation (chapter 2-5), and to make a plan for future developments in this area (chapter 6). The material in chapter 2-5 is also a reference guide to current technology and procedures. Type of information to be communicated There are several types of information to be distributed, which correspond to various wishes for delivery: Announcements of meetings, typically with an agenda. Valid up to the meeting. Should reach all those interested by the meeting, but not every time everybody. Should be readable on all platforms. Applies to all sorts of events, not only meetings. Minutes of meetings. Valid forever, may not need to be distributed, but just made available e.g. on the Web, and announced. Classified by type of meeting. Technical documents, notes, figures, blue prints. Not distributed, but should be easy to print. However, they need to be classified so that retrieval is easy. Discussion list. Informal exchange of idea, for sub-groups. General News items. People news. Needs for notification Notification is the part of an information system which informs the user that he has new information, for him (mail) or interesting him (news). Notification can be done at login time (number/list of unseen documents), but could also be done in real time. If a maximum delay for informing the user is guaranteed, this can then be used for reminder of meeting, last minute changes in agenda and so on. But with high traffic, notification can be a nuisance, so its level should be under the users control. Information can be pertinent only for a given subset of the collaboration, for example Sub-detector related messages. This is mainly for notification, as it is also useful to be able to get access to the whole information in the collaboration. Registering and de-registering to a category of information should be easy. Notification could implies the existence of a tag that specifies whether the information has or not been seen by a user. This is a 2 dimensional array, which can be big! Confidentiality It is clear that some documents should be restricted to members of the collaboration. But not all, as some 'commercial' plots or documents should be world accessible. Protection by a generic password is not very solid, as it is known by all those who worked once in the collaboration, including those working part-time like technical staff in the home labs. And it is very difficult to change without a lot of complaints, or a prior broadcast of the new password, which makes then the change partly useless. Tools for accessing information We should use a commercial tool for displaying information. The information can be sent to the local host (unknown delay to arrive, but easy to access after), or directly accessed on a central server, with the problems of bad/slow/unavailable network. There are three existing systems, some advantages and disadvantages of which are listed below. Web server and browser. No notification. Difficult to maintain a list of unseen messages, as the user name is not (usually) known by the Web server. Document posting requires a special procedure. User authentication usually by a 'generic' password. Protection depends on the Web server. Can access old messages, in any class. Old/obsolete messages archived by a Webmaster. Central server. Mail messages. Notification OK. Seen/Unseen flag exists in some mail programs (e.g. Netscape). Document posting by a server of mailing list. Maintenance User authentication by the user login. Can not access old message, nor non subscribed lists. Old messages removed by the user when he wants. Unknown time for delivery. News messages on a dedicated news server. Notification OK. Unseen tag by a local file on the reader. Document posting by the news protocol. User authentication by a 'generic' password. Can access old message, in any class. Old messages archived by their expiration date, either specified when posting or handler by the news server. Central server. But can be easily replicated, at the expense of more 'risks' on confidentiality. As an example, the client side of these three systems are integrated in Netscape, so the look and the possibilities to display graphic are quite similar. Current status The current LHCb system is based essentially on MAIL, with a part on the Web. The subscription to the lists is done by editing BWHO, which requires a password than one tends to forget. The way to post information (address of the correct mailing list) is not widely known, and the selection of the correct distribution list far from being adequate. Private mailing lists are then built and used. It is also not easy to see if a message was sent to YOU as single person, or to you as member of a distribution list. Last, multipart messages are not properly propagated on the mailing list, but this can clearly be fixed. Several attempts have been made to obtain all the functions in one tool. The newswatcher to inform on new Web pages, a private news server, and a news-like interface on a dedicated Web server. Information in LHCb is delivered using: Paper documents. Web pages. Email. Discussion groups and News. We believe this situation will continue to exist in the foreseeable future. Paper documents Tools and technology Currently we use: Word 97 for office documents short reports and technical notes on PC and Mac. FrontPage 97/98 for making minutes of meetings and other short documents that have to be posted on the Web. PowerPoint for presentations on PC and Mac. FrameMaker 5.0 and 5.5 for medium to long reports and technical notes not requiring too much mathematical formulas, on PC. LaTeX (2.9e) for technical notes with mathematical formulas, and if no PC or Mac is available. For Windows NT 4, we use MikTeX 1.09. We have templates for LHCb technical notes for Word and FrameMaker. Adobe Illustrator 7.0 for editing PostScript figures. Adobe Photoshop 3.0 for editing photos, scanned images and other bitmaps. Corel Draw 6.0 for editing PostScript figures. Advantages of the current practice: Everyone chooses the tool they seem happiest with. Templates for Word and FrameMaker guarantee a standard look of LHCb technical notes. Disadvantages: Word contains bugs, does a poor job of formatting mathematical formulas and is not available on UNIX. FrameMaker does a slightly better job of formatting mathematical formuals but is difficult to use, requires training and is more expensive than Word. TeX has an archaic user interface, no WYSIWYG yet is loved by physicists. The lack of a TeX template for LHCb technical notes causes different styles of documents. No automatic conversion tools exist for getting in and out of TeX. We have found that a combination of Adobe Illustrator and Corel Draw is required to be able to fix all problems that occur with PostScript files. Procedures What system to use For TeX. On CERNSP, TeX is installed and publicly available. For Windows NT users, TeX is not available on NICE. We recommend MikTeX, the distribution file can be found on the LHCb Web site, go to HYPERLINK http://lhcb.cern.ch/documents/miktex/miktex.zip http://lhcb.cern.ch/documents/miktex/miktex.zip . MikTeX must be installed as user administrator. For Mac there is no recommended TeX system. There are no templates. For Word. Word 97 is the recommended system. A template may be found on the ALNTS1 "Programs" disk in the directory Office97/Templates/ALEPH-LHCB/lhcbnote.dot. This template may also be found on the Web at HYPERLINK "http://lhcb.cern.ch/documents/html/templates.htm"http://lhcb.cern.ch/documents/html/templates.htm. For Mac there is no template. Mac Word can be read by Word 97, but not in the other direction. For FrameMaker. FrameMaker 5.5 is the recommended system. It must be installed via a CD Rom with a license code that can be obtained from Mario Ruggier, IPT group. A template may be found on the Web at HYPERLINK "http://lhcb.cern.ch/documents/html/templates.htm"http://lhcb.cern.ch/documents/html/templates.htm. Material for publications Official figures are available on the Web in various places: Detector figures. Go to HYPERLINK "http://lhcb.cern.ch/html/progress/detect_fig.htm"http://lhcb.cern.ch/html/progress/detect_fig.htm. Geometry figures. Go to HYPERLINK "http://lhcb.cern.ch/technicalcoordination/geometry/html/body.htm"http://lhcb.cern.ch/technicalcoordination/geometry/html/body.htm Experimental area: Infrastructure -> Experimental Area ( HYPERLINK http://nicewww.cern.ch/~lacarrer/lhc-b/lhcbtop1.htm http://nicewww.cern.ch/~lacarrer/lhc-b/lhcbtop1.htm EPS files from the Technical Proposal: http://lhcb.cern.ch/tp/ Public notes Public notes are documents which have an unrestricted circulation and may be read by the public. The content of these notes is endorsed by the LHCb collaboration. These documents have to be read and approved by the subgroup convener and the spokesman. When the note is written, a number is obtained from the LHCb secretariat (Nathalie Grub), in the form "LHCb yy-xyz KEYWORD"(where yy is the year, and xyz is a number. KEYWORD is TRIG, TRIG-MUON, TRAC, DAQ, MAGNET, COMP, RICH, EXPT, PHYS, HCAL or ECAL ). Nathalie takes a PostScript file and saves a copy on the LHCb Web server, in the directory HYPERLINK http://lhcb.cern.ch/documents/notes/postscript/yynotes/yy-xyz/name.ps http://lhcb.cern.ch/documents/notes/postscript/yynotes/yy-xyz/name.ps, where yy is the year, yy-xyz is the reference number, name.ps is the name of the postscript file. The source of the article (text and postscript images) is also archived in the directory HYPERLINK http://lhcb.cern.ch/documents/notes/system/noteyy-xyz/ http://lhcb.cern.ch/documents/notes/system/noteyy-xyz/, where system is tex, word, or framemaker and yy-xyz is the reference number. An entry for the document (including all its authors) is added to the BWHO database. Nathalie then sends an email to the list HYPERLINK mailto:allbwho@lhcb.cern.ch allbwho@lhcb.cern.ch to inform all people interested in LHCb of the existence of a new public note. Publications I do not know what the procedure is for publication in a peer reviewed journal. I assume that the document must first be an approved LHC technical note, then the CERN guidelines for publications must be followed. The BWHO database should contain details of publication date, journal etc. Lectures and Public presentations These documents are archived on the Web on an ad-hoc basis. For slides of plenary collaboration meetings, the following procedure is applied: The transparencies are collected by T. Nakada at the meeting and handed over to Nathalie. If the speaker needs to get his slides back immediately, a photocopy is made. The slides are scanned in by H. Mettler, Web Office. Mettler uses FrontPage to put the scanned slides directly on our Web, as gif files and html files with links to them. The page HYPERLINK http://lhcb.cern.ch/documents/presentations/transparencies/html/body.htm http://lhcb.cern.ch/documents/presentations/transparencies/html/body.htm is updated to include a link to the agenda of the plenary meeting, e.g. HYPERLINK http://lhcb.cern.ch/forthcomingevents/html/mar98.htm http://lhcb.cern.ch/forthcomingevents/html/mar98.htm. The items on the agenda are linked to directories which have the name of the speaker, e.g. the first item on the agenda mar98.htm is linked to HYPERLINK http://lhcb.cern.ch/transparancies98/mar98/Nakada/Nakada.html http://lhcb.cern.ch/transparancies98/mar98/Nakada/Nakada.html If Mettler forgets, the directory HYPERLINK http://lhcb.cern.ch/transparencies/smallnavbuttons http://lhcb.cern.ch/transparencies/smallnavbuttons needs to be copied into the subdirectory with the slides (e.g. mar98). Proceedings of conferences Contributions to conferences should be placed on the Web by Nathalie, updating the file HYPERLINK http://lhcb.cern.ch/private/conferencetalks/html/body.htm http://lhcb.cern.ch/private/conferencetalks/html/body.htm and placing at least the PostScript in the directory http://lhcb.cern.ch/private/conferencetalks/postscript/. Computer documentation, userguides, release notes Computer documentation (the SICB userguide and the PCSF userguide) are the only examples I know of that are currently available from the Web. Release notes do not yet exist. LHCC documents These are the Letter Of Intent (LOI), the Technical Proposal (TP) and forthcoming (Technical Design Reports) TDR's. They are added to BWHO, and their text and images source files are archived on the Web. The LOI is archived at HYPERLINK http://www.cern.ch/LHC-B/LOI/ http://www.cern.ch/LHC-B/LOI/ and the TP at HYPERLINK http://lhcb.cern.ch/tp/ http://lhcb.cern.ch/tp/. Private notes There is no procedure yet for making and storing private notes, such as minutes of meetings, working documents etc. What to improve We need to make a list of what to document. A procedure needs to be defined for TDR's. Items to consider are: Choice of a single text formatter. A consistent style of LHCb documents for the LHCC. The necessity of an editorial board. Use of the Web to distribute the latest version of contributions. How to avoid problems printing PostScript. If we continue to use TeX for Technical Notes, then we need to make a LaTeX template to ensure a consistent style of LHCb technical notes. We should request a standard NICE NT installation of TeX. Considering the problems we have with PostScript, we should explore the use of an additional format for document archival. Do we need a quality control procedure for non-public documents? We need a procedure for release notes. Design a directory/subweb structure for archiving various document types on the Web. Create a single place for storing recommended figures for publications and presentations. Define/describe the procedure for publication in peer reviewed journals. Web pages Tools/technology We are currently running the Microsoft Internet Information Server 3.0 on Windows NT 4 server, service pack 3.0. The Microsoft Index Server is used for the search engine. We have installed the FrontPage 97 extensions; we use FrontPage 97/98 for updating the pages on the Web. We are running the Java server 1.0. We use Symantec Caf with JDK 1.1 for Java applets, applications and servlets. We use the sliding menu applet from OpenCube technologies. We use ColdFusion 2.0 for Internet Database Connectivity. We use Access 97 for the BWHO database. Procedures Web design Operation of the Web server The LHCb Web server was configured according to the following principles: By having its own Web server, LHCb has optimal flexibility and full control over its information. By choosing commodity software that does not require specialized knowledge or training, LHCb should not depend on a particular person for maintaining its Web server. The server runs Microsoft Windows NT 4 server, service pack 3. Service pack 3 needs to be installed after Windows NT 4 server. It can be found on a Microsoft Developer's Network Disk from A. Pacheco, or from the Microsoft Web site. The system administrator password is the same as for all LHCb PCs, and is known by J.P. Droulez. The Microsoft Internet Information Server is part of Windows NT 4.0. The configuration parameters of the Web and ftp server are shown in the following figures. Make sure that a user lhcb (an ordinary user) is defined on the Webserver (it is with this userid that protected pages are accessed). The other users that are not created by the system are not important. The Microsoft Index Server is installed for the Web search engine. The Index Server is part of the NT 4 Option Pack, available for free from the Microsoft Web site. Microsoft FrontPage was selected to maintain the LCHb Web. The FrontPage 97 extensions have been installed on the server. These are some reasons why FrontPage was chosen: Frontpage allows multiple people to maintain the LHCb Web in a well organized way. All pages in the Web are automatically indexed. Frontpage is integrated with the Microsoft Index Server, and thus supports a professional search engine without any additional installation effort. Frontpage is the best wysiwyg Web editor currently on the market, with easy facilities for Word import, table creation, frames, and image manipulation. Through the use of variables, we can update information in a central place, without the need for modifying individual pages (e.g. phone and fax numbers). Management of the Web is easy with FrontPage. For example, moving many files into a different subdirectory is easy FrontPage makes sure that all the hypertext links are automatically updated. We get an automatic date stamp (with the date of last modification), and can give each page an individual hitcounter (note that it is not so easy to make a reliable hit counter; most CGI-perl scripts can be easily abused). Frontpage manages discussion groups. Using Frontpage, we can obtain a professional quality Web without a single line of programming and a minimum of maintenance. Frontpage works across the Internet, allowing the Web to be maintained from outside CERN. Requirements for the LHCb Web When designing the Web, the following requirements were applied: Ergonomic. The hypertext link structure should minimize the path to a page and maximize the ease with which it is found. It should be attractive to LHCb collaboration members, interested physicists and members of the general public, and attempt to keep the surfer inside the LHCb Web. To achieve this, a navigation file (containing all the major areas) is presented in the left hand frame. This presents an overview of the web site without the need to follow a link to find out what is below it. It should be flexible. To accommodate the varying requirements of different users, there are three home pages: one with Java and images and frames, one with only frames, and one with no frames. A cookie is set to remember the preference of the user. It should be easy to add a new page to the Web in a way that the LHCb look and feel is maintained. It should be complete. It should be up-to-date. Each page should have a signature (email address of the person who last edited the page), a date stamp (the date when the page was last modified) and optionally a hitcounter. The page should be contained in a centered, 600 pixel wide table without visible borders. Links to pages outside the LHCb Web should have target=_top so that when the link is followed, the target page occupies the whole screen. When a link is followed that has no target, the target page is placed inside the same frame as the page where the link started. Each page should have a white background colour. This is because by default, browsers display a page with a grey background that is more difficult to read. FrontPage 97 and 98 by default generate pages with white backgrounds. Design of the LHCb Web Frontpage supports the notion of a subweb. We have exploited this feature to introduce a two-tier hierarchy in the LHCb Web, with the root web containing general material. This structure was agreed on by a few ad-hoc meetings between the T. Nakada, T. Ruf, A. Schopper, E. van Herwijnen, the secretariat and input from individual people to E. van Herwijnen. Each sub (detector) group has its own subweb, for example the Computing subweb, the DAQ subweb, the Physics subweb etc. In principle any group (even if it doesn't correspond to a subdetector) with a well defined purpose can have its own subweb, such as the collaboration board. Subwebs are created on demand as required. Every subweb has a discussion group and a mailing list in BWHO. Note that a Web-structure is independent of this hierarchical structure. For example, there are subwebs corresponding to Computing, DAQ, Datahandling, Trigger and Software. This allows each activity to have its own discussion group, mailing list, area for storing documents etc. On the other hand, using hypertext links, it is easy to create a structure where the all encompassing activity is Datahandling, which comprises Computing, DAQ and Trigger, and where Software is a subactivity of the Computing activity. Although this Web-structure is not yet fully defined for our Web, it is not incompatible with the present hierarchical structure. The content of the root web and the various subwebs is: Root web: Home page. Three versions exist: with images, java and frames, without java and images but with frames, without java, images or frames. The files are: default.htm, newleft.htm, top.htm, noimagesleft.htm, noimagestop.htm, html/text.htm, noframes.htm. Secretariat plus people pages. Help pages. Search pages. Jobs page. A discussion group. Structure pages Progress pages. BWHO People query, insert, update and delete Document query, insert, update and delete Calorimeters Discussion group Collaborationboard Discussion group Computing Discussion group DCS: detector slow controls, safety, links to LHC machine, run control, expert systems. Event Display Information Management Convenors Discussion group List of convenors DAQ Discussion group Minutes of DAQ meetings, other documents, links Datahandling Documents Technical Proposal LOI Presentations (B-physics, Conference talks) Transparencies LHCb notes Material for publications (Figures, Templates, TeX for PC ) User guides (SICB, Using PCSF) Experimentalarea Forthcomingevents Next event Future events Past events Generalmanagement Convenors Collaboration Board Technical Coordination Infrastructure LHC Interface (LHC/IP 8 parameters, Beam Pipe) Detector Geometry Magnet Test Beam List (email) Magnet Muon Discussion group News Physics Discussion group Documents Private Constitution Draft documents Conferences, Speakers Proceedings Rich Discussion group Documents Software Discussion group Simulation Reconstruction Software maintenance Technicalcoordination Detector geometry Technicalproposal Files Documents, minutes of meetings Tracking Discussion group Documents Transparencies98 Transparencies of meetings held in 1998 Transparencies Transparencies of meetings in previous years Trigger Discussion group Documents Vertexdetector Discussion group Documents Implementation Organization of files inside subwebs (adding a subweb) Inside each subweb, the following subdirectory filestructure may be found. For new subwebs, a similar structure should be put in place: /html. For html files only. /images. For images. If required, a further substructure indicating the format (/images/gif or /imagves/jpg) can be added. _fragments, _vti _bin etc. All directories starting with an underscore (_) are internal to FrontPage. They should not be touched. Files inside them are ignored by the search engine, and are not indexed. /postscript, /tex, /word, /powerpoint, /frame for files of a certain type. We have the policy to archive all material in its original source format, and for each format a subdirectory should exist. If a further subdivision is required inside a subweb (e.g. the /infrastructure/testbeam and /computing/informationmanagement) a corresponding subdirectory with its own set of subdirectories 1-4 should be created. Subweb variables For each subweb, two variables phone and fax should be created. Go into Tools, Web settings: Click on the parameters tab, then add the variables phone and fax with the correct values. Inside the FrontPage editor, these may now be referred to via Insert, Webbot Components (choose Substitution). Security The pages in the root web and various other webs are open to the public. The permissions of the root web are defined as follows: The pages in the public web can be viewed by anyone with a connection to WWW. Subwebs contain information that is exclusively for LHCb members, such as LHCb notes and transparencies of collaboration meetings. To view the pages in the private web requires the use of a special userid and password. This userid (lhcb) and password is different from the one that is used to maintain the pages with Frontpage. It is a drawback of FrontPage that permissions can only be set on the level of a subweb, not on the level of a directory or a file. When a new subweb is made, its permissions should be set uniquely as follows: Only administrators and the user lhcb are allowed to browse these pages: Adding a discussion group to a subweb Open the previously created subweb with the FrontPage explorer. Go into File, New, FrontPage Web. Select Discussion Web Wizard, and make sure to check the box Add to the current Web: This wizard will ask you some questions that you should answer as shown in the following screens: Now you need to edit the files that FrontPage made for you, and move them into hidden directories. If a directory _fragments does not yet exist, create it. Inside it, create a subdirectory _nameofgroup (where nameofgroup is the name of your discussion group). Do this from the Frontpage explorer by File, New, Folder. Move the files nameofgroup_cfrm.htm, nameofgroup_frm.htm, nameofgroup_post.htm, nameofgroup_srch.htm, nameofgroup_toc.htm, nameofgroup_tocf.htm, nameofgroup_welc.htm into the directory _fragments/_nameofgroup. They were originally created by Frontpage in the root of your web. Once you have moved them there, they must be edited to look like the other LHCb discussion group pages. You also need to edit the files /_nameofgroup/toc.htm, /_nameofgroup/tocproto.htm, and /_private/_nameofgroup_aftr.htm, /_private/_nameofgroup_ahdr.htm, /_private/_nameofgroup_foot.htm, /_private/_nameofgroup_head.htm. Here is what you need to do (in order): /_private/_nameofgroup_aftr.htmAdd the following HTML markup: ./_private/_nameofgroup_ahdr.htmPut the whole page in a table 600 pixels wide, invisible borders. Change the heading from level 1 to level 2. Change the text Post to Start a new article. Reduce the font size. Change the targets of the hypertext links: Home goes to _top, contents, search, start and reply go to body; the others go to a blank target. Add a blue horizontal line (/images/buttons/hline.gif, set its width to 600 pixels, 1 pixel thick. Add the following HTML ad the end of the file:
/_private/_nameofgroup_foot.htmMake it an empty file./_private/_nameofgroup_head.htmPut the whole page in a table 600 pixels wide, invisible borders. Change the heading from level 1 to level 2 Change the text Post to Start a new article. Reduce the font size. Change the targets of the hypertext links: Home goes to _top, contents, search, start and reply go to body; the others go to a blank target. Add a blue horizontal line (/images/buttons/hline.gif, set its width to 600 pixels, 1 pixel thick./_fragments/nameofgroup_cfrm.htmPut the page in a table table 600 pixels wide, invisible borders. /_fragments/nameofgroup_frm.htmPut the page in a table table 600 pixels wide, invisible borders. Remove the line (to avoid reloading of page)./_fragments/nameofgroup_post.htmPut the page in a table table 600 pixels wide, invisible borders./_fragments/nameofgroup_srch.htmPut the page in a table table 600 pixels wide, invisible borders./_fragments/nameofgroup_toc.htmRemove the line ./_fragments/nameofgroup_tocf.htmRemove the line /_fragments/nameofgroup_welc.htmPut the page in a table table 600 pixels wide, invisible borders. Add some text like Please use it whenever you have to make a general communication to all people interested in the LHCb experiment. After posting up your article, you have the option to send the article as an email to all people that have inscribed themselves to this list via BWHO./_nameofgroup/toc.htmPut the contents section in a table table 600 pixels wide, invisible borders./_nameofgroup/tocproto.htmPut the page in a table table 600 pixels wide, invisible borders. Edit this file regularly make sure the links of the articles have as target body.Cookies
In accordance with all modern web sites that try to make interactive and userfriendly sites cookies are used to keep track of user preferences. On our site, they are used in the following places:
On the home page (nocchie), to keep track of whether a user wants java, images and frames (=0), images and frames but no java (=1, the default), or nothing at all (=2). The cookie has an expiry date of 30 days, and if it exists it is not re-written. This cookie is read and written by a java servlet on the server.
By BWHO for updating the users own record. When sending email to a list from the Web, this cookie is used to determine the email address of the user filling out the form (so we can keep track of who sent an email, and to prevent people from the general public to use this facility anonymously). The BWHO_username and BWHO_password cookies are written by a ColdFusion template. For reasons of bugs, we can not read and write the email cookie with ColdFusion, but I had to do it in JavaScript. I am aware that I used some JavaScript that is not available in old browsers, there is a fix but I havent yet had the time to clean this up.
Adding/updating pages
Who is allowed to make changes?
Any member of the LHCb collaboration who has a good reason to do so may make changes to existing pages, or add new pages to the LHCb Web. This Web site was designed to maximize efficient information retrieval. New pages, or any modifications to existing pages should be made following the simple guidelines described below. You will require a password which you can obtain from any person who is authorized to make changes. If you don't know such a person, contact me.
The LHCb Web pages are maintained with FrontPage. The FrontPage 97 extensions are installed on the server, which means that FrontPage 1 (Macintosh), FrontPage 97 or FrontPage 98 may all be used to maintain our pages. In the next few weeks, we intend to install FrontPage 98 extensions on the Web server. From this date only FrontPage 98 can be used to maintain the pages.
It is very important to use Frontpage for all modifications, because Frontpage will automatically undo any changes that were made without using Frontpage! Also, by using Frontpage, each page is automatically indexed and searchable using the search page.
Quality control of pages?
Installing FrontPage on NICE NT
From now on, it is recommended to use the FrontPage 98 client (although we still only have the FrontPage 97 extensions installed on our wever). This is available on NICE NT under ALEPH/LHCb Software:
Once installed, use FrontPage as usual.
Page design guidelines
To minimize the download time, pages should be kept as small as possible. This means that the number of graphics on each page should be minimized. Our page guidelines are very simple:
The background colour of the page should be white.
The text of the page should be contained in a 600 pixel wide table with invisible borders.
The title of the page should be self-contained with the word LHCb appearing in it somewhere. The page will then show up when people use a search engine to look for information related to the experiment. It will also distinguish the page when people are looking for unrelated information.
The page should start with a centered heading of level 2. Other headings should be of level less than or equal to 2, left adjusted. Hypertext links to files outside the LHCb Web should have target="_top" (other links should leave this field blank):
At the bottom should appear in 10 pt roman italic:
a datestamp containing the date the page was last updated;
the signature of the author of the page with an email link
a hitcounter (optional). A file containing an example of such a line can be found at: http://lhcb.cern.ch/_fragments/contentsbottom.htm. You can open this file in Frontpage, then copy and paste it into your page. Be sure to double click on the word 'Hit Counter' and update the path of the file custom.gif (import it into your subweb if necessary; it can be found at http://lhcb.cern.ch/images/gif/custom.gif).
How to make changes if you don't have FrontPage
If you do not have access to a PC or a Mac, send me an email with the URL or ftp address of your page. You can also ftp the file directly to the Web server, but in this case you should let me know where I should put the file.
BWHO/ColdFusion maintenance
There are two databases installed for ColdFusion: BWHO Read and BWHO Read/Write.
Requests allowed:
Debugging:
Mail:
CFX tags empty. Mappings:
The dbml executable should reside in the /inetpub/scripts directory.
Adding/deleting a new Institute (member of the collaboration) to the database
Changes to the Access database.
Open Access, open D:\CFusion\DATABASE\bwho, open the table Institutes_and_Places
Start typing at the end of the table, note the value of the place_key is automatically updated. Add values as for the other entries. Remember this number (e.g. XX). Save the table.
Open the table fax. Define an alias with a fax number. This alias should be used in the table above (Institutes_and_Places) but also in the Persons table when a new person from this institute is added.
Changes to HTML files. Modify the line:
by adding OR XX at the end of the string, where XX is the place_key obtained in the previous step. This modification needs to be applied to:
D:\InetPub\wwwroot\_fragments\_communications\communications_cfrm
D:\InetPub\wwwroot\calorimeters\_fragments\_calorimeters\calorimeters_cfrm
D:\InetPub\wwwroot\collaborationboard\_fragments\_collaborationboard\collaborationboard_cfrm
D:\InetPub\wwwroot\computing\_fragments\_computing\computing_cfrm
D:\InetPub\wwwroot\daq\_fragments\_daq\daq_cfrm
D:\InetPub\wwwroot\muon\_fragments\_muon\muon_cfrm
D:\InetPub\wwwroot\physics\_fragments\_physics\physics_cfrm
D:\InetPub\wwwroot\rich\_fragments\_rich\rich_cfrm
D:\InetPub\wwwroot\tracking\_fragments\_tracking\tracking_cfrm
D:\InetPub\wwwroot\trigger\_fragments\_trigger\trigger_cfrm
D:\InetPub\wwwroot\vertexdetector\_fragments\_vertexdetector\vertexdetector_cfrm
D:\InetPub\wwwroot\list\html\body.htm
Changes to ColdFusion templates.
Sendmail.dbm, Sendmail1.dbm, Sendmail3.dbm: change
|
To send this article as email to all people that have subscribed to the LHCb mailing list (or check any other list mentioned below), click on the "Send email article" button.
Changes to BWHO templates (instikeyzzz is the variable defined to above): Sendmail3.dbm, add a section:Entire collaboration | Computing | Calorimeter | Collaboration board | Conveners | DAQ | Muon | |||||||||
CERN group | RICH | Software | Everyone in database | Trigger | Tracking | Physics | Vertex Detector | ||||||||
Changes to Java applications. None. Configuration of the search engine The Microsoft Index server is installed and used in more or less its default configuration. We use two query forms: For query of all files: d:\inetpub\wwwroot\samples\search\_fragments\querybody.htm. This file calls the search servlet to have access to password protected files, and to filter out any directories starting with an underscore.The corresponding idq file is: d:\inetpub\scripts\samples\search\query.idq. It should be customized as follows: # # This is the query file for the query.htm query form. # [Query] # The CiCatalog variable must point to where the catalog (index) files # are stored on your system. You will probably have to change this # value. If this value is not specified, a default value is read from # the registry from: # HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ContentIndex\IsapiDefaultCatalogDirectory # CiCatalog=D:\IndexServer\ <= COMMENTED OUT - default registry value used # These are the columns that are referenced in the .htx files # when formatting output for each hit. CiColumns=filename,size,rank,characterization,vpath,DocTitle,write # Do a recursive search (ie all directories under CiScope). # The opposite is SHALLOW CiFlags=DEEP # The CiRestriction is the query. Here, it's just pass in from the # form in the .htm file. CiRestriction=%CiRestriction% # Don't allow more than 300 total hits in the result set. It can be # expensive for the server to allow this value to get too large. CiMaxRecordsInResultSet=300 # Display CiMaxRecordsPerPage hits on each page of output CiMaxRecordsPerPage=%CiMaxRecordsPerPage% # CiScope is the directory (virtual or real) under which results are # returned. If a file matches the query but is not in a directory beneath # CiScope, it is not returned in the result set. # A scope of / means all hits matching the query are returned. CiScope=%CiScope% # This is the .htx file to use for formatting the results of the query. CiTemplate=/scripts/samples/search/%TemplateName%.htx # This is the list of property names to use in sorting the results. # Append [a] or [d] to the property name to specify ascending or # descending. Separate keys in multi-key sorts with commas. # For example, to sort on file write date ascending, then file size # descending, use CiSort=write[a],filesize[d] CiSort=%CiSort% # Setting CiForceUseCi to true means that the index is assumed to be # up to date, so queries that might otherwise force a walk of the # directory structure (find files older than X), will instead use # the index and run more quickly. Of course, that means that the results # might miss files that match the query. CiForceUseCi=true # # Setting CiLocale allows the web master to override the locale sent from # the browser. Supported locals include (from ISO 639:1988 language codes # and ISO 3166 country codes): # # BG Bulgarian # ZH Chinese # ZH-CN Chinese/china # ZH-TW Chinese/taiwan # HR Croatian # CS Czech # DA Danish # NL Dutch # EN English # EN-GB English-United kingdom # EN-US English-United States # FI Finnish # FR French # FR-CA French-Canadian # FR-FR French-France # DE German # EL Greek # IS Icelandic # IT Italian # JA Japanese # KO Korean # NO Norwegian # PL Polish # PT Portuguese # PT-BR Portuguese-Brazil # RO Romanian # RU Russian # SK Slovak # SL Slovenian # ES Spanish # ES-ES Spanish-Spain # SV Swedish # TR Turkish # # The locale effects the formatting of dates, times, and numbers. Currency # is formatted according to the locale of the web server. Locale is also # used to select the word breaker, and the stop word list. # # The web master may want to allow the browser to send the locale when # attempting to query for text in variety of languages. For example, # given a single HTML page, one query couold be for German text (CiLocale=De) # and another could be for Spanish text (CiLocale=Es). If CiLocale is # not found in the IDQ file the locale send by the web browser is used. If # no locale is send from the browser, the locale of the web server is used. # # The web browser sends its locale via the HTTP_ACCEPT_LANGUAGE parameter # #CiLocale=En-US <== specified by the web master #CiLocale=%CiLocale% <== send from the HTML page #CiLocale= <== value used from the web browser The following query.htx file is used to format the results: <%if CiMatchedRecordCount eq 0%> |
Index ServerSearch Results |
New query | <%if CiContainsFirstRecord eq 0%><%endif%> <%if CiContainsLastRecord eq 0%> | <%endif%> |
<%if CiMatchedRecordCount ne 0%>
New query | <%if CiContainsFirstRecord eq 0%><%endif%> <%if CiContainsLastRecord eq 0%> | <%endif%> |
<%if CiOutOfDate ne 0%>
The index is out of date.
<%endif%>
<%if CiQueryIncomplete ne 0%>
The query is too expensive to complete.
<%endif%>
<%if CiQueryTimedOut ne 0%>
The query took too long to complete.
<%endif%>
<%if CiTotalNumberPages gt 0%>
Page <%CiCurrentPageNumber%> of <%CiTotalNumberPages%>
<%endif%> For query of the last modified files, d:\inetpub\wwwroot\samples\search\_fragments\bdfiletime.htm. The search servlet is called by this form to have access to the abstracts of password protected files. The idq file, d:\inetpub\scripts\samples\search\filetime.idq should be customized as follows: # # This is the query file for the filesize.htm query form. # [Query] # The CiCatalog variable must point to where the catalog (index) files # are stored on your system. You will probably have to change this # value. CiCatalog=D:\IndexServer\ # These are the columns that are referenced in the .htx files # when formatting output for each hit. CiColumns=filename,size,rank,characterization,vpath,DocTitle,write # Do a recursive search (ie all directories under CiScope). # The opposite is SHALLOW CiFlags=DEEP # Allow either a filesize restriction, a free-text restriction, or both CiRestriction=%if TextRestriction ne ""%( %TextRestriction% ) and %endif% @write > %if FMMod eq "since"%%FMModDate%%else%%FMMod%%endif% # Don't allow more than 300 total hits in the result set. It can be # expensive for the serer to allow this value to get too large. CiMaxRecordsInResultSet=300 # This is the maximum number of records per page of output. It is limited # by CiMaxRecordsInResultSet CiMaxRecordsPerPage=%CiMaxRecordsPerPage% # CiScope is the directory (virtual or real) under which results are # returned. If a file matches the query but is not in a directory beneath # CiScope, it is not returned in the result set. # A scope of / means all hits matching the query are returned. CiScope=%CiScope% # Choose either the sorted or unsorted version of the .htx file. # Sorting by rank can use sequential execution for greater efficiency. CiTemplate=/scripts/samples/search/%if SortProperty ne "None"%%if SortProperty ne "Rank"%S%endif%%endif%format%CiTemplateChoice%.htx CiSort=%if SortProperty ne "None"%%SortProperty%%SortOrder%%endif% # Setting CiForceUseCi to true means that the index is assumed to be # up to date, so queries that might otherwise force a walk of the # directory structure (find files older than X), will instead use # the index and run more quickly. Of course, that means that the results # might miss files that match the query. CiForceUseCi=true Java programs used by the server All Java applications are stored in D:\JavaAppForServer. They are well documented with readme files in each subdirectory. All applications come up when the system is booted and the administrator logs on. Mail server (runs on startup). Reads incoming mail to the addresses HYPERLINK mailto:webmaster@lhcb.cern.ch webmaster@lhcb.cern.ch, HYPERLINK mailto:postmaster@lhcb.cern.ch postmaster@lhcb.cern.ch, allbwho@lhcb.cern.ch, calorimeters@lhcb.cern.ch, cerngroup@lhcb.cern.ch, collaborationboard@lhcb.cern.ch, HYPERLINK mailto:communications@lhcb.cern.ch communications@lhcb.cern.ch, computing@lhcb.cern.ch, HYPERLINK mailto:convenors@lhcb.cern.ch convenors@lhcb.cern.ch, HYPERLINK mailto:daq@lhcb.cern.ch daq@lhcb.cern.ch, HYPERLINK mailto:lhcb@lhcb.cern.ch lhcb@lhcb.cern.ch, muon@lhcb.cern.ch, physics@lhcb.cern.ch, rich@lhcb.cern.ch, HYPERLINK mailto:software@lhcb.cern.ch software@lhcb.cern.ch, HYPERLINK mailto:tracking@lhcb.cern.ch tracking@lhcb.cern.ch, trigger@lhcb.cern.ch, HYPERLINK mailto:vertexdetector@lhcb.cern.ch vertexdetector@lhcb.cern.ch. Mail to the first two addresses generates a reply with a help message, this is stored in D:\JavaAppForServer\lhcbmail\mailhelp.txt. This code is a bit tricky, you need to avoid ping-pong situations. We only protect against mail from HYPERLINK mailto:postmaster@mail.cern.ch postmaster@mail.cern.ch, it gets forwarded to me. When an address in BWHO doesnt work, HYPERLINK mailto:postmaster@mail.cern.ch postmaster@mail.cern.ch returns the message to the server. To start it, run the runlhcbmail.exe file. Search engine - a servlet to display also the abstract of password protected files. To run it, run the runserver.exe file. Tricky code again, contains a password. Not a security problem as the class file is not stored in the Web data directory and thus unaccessible from the Web. Note that if subwebs have different passwords, this code will no longer work. Prepare a list of the last modified files for the Nando News watcher (runs every hour). A servlet to read and write a cookie to decide which home page to send. These servlets are stored in the D:\JavaAppForServer\search\ directory. When the cookie code (stored in D:\JavaAppForServer\noimages) is modified, the class files need to be copied to the search directory and the server stopped and restarted. An application to analyse the logfiles and to generate access statistics. This application is run once per night. An applet to produce scrolling menus on the home page (slidem). All the Opencube applets are stored in the directory D:\JavaAppForServer\Opencube. Slidem is the only one we use at the moment. They are well documented. System Administration Run mail server on startup, and the java server. These are run from the administrator account, who should be logged on. Backup procedure. Run every night, or run D:\Backsup.exe. Note: only the D:\inetpub\wwwroot\ directory (and subdirectories) are backed up. Disk defragmentation. Not installed yet. Bug in the Index server requires occasional reboot of the server when search results give rubbish. Testing of new technology The server HYPERLINK http://pclhcb02.cern.ch/ http://pclhcb02.cern.ch/ is a test Web server. Whenever a major new design is implemented, it is first tested here. New technology is also tested on this machine first. Interested colleagues can review and comment on novelties before they are put into production. Private web pages Members of the collaboration that wish to make available their LHCb related work through the Web are strongly encouraged to use the LHCb Web server in favour of their private or other servers, because of indexing and archiving. We do recognize however that there can be good reasons for using other Web servers. What to improve Design of Web. Ergonomics. Add home page without frames. Migrate server to FrontPage 98, and move all clients to FrontPage 98. FrontPage 98 training. Teach people how to make consistent pages and to integrate them with the Web server. For LHCb documents, people should use the LHCb server rather than their own server. Make it clear when something should be put on the Web. Integrate BWHO with CERN's Human Resources (HR) database, PIE project. Offload maintenance of Web server to secretariat, train subgroup conveners. Email Tools/technology We use: Any standard SMTP mail client to send email to one of the mailing lists on the Web server. Via a page on the Web, the Cold Fusion SMTP mail client running on the Web server. Procedures Via the Web: To send an email, go to the LHCb Web page, and click on 'Home-Email'. Fill in the form, select the list that the email should be sent to and send the form. Before the form can be sent, the user will be prompted for his/her BWHO userid and password. This protection was added to prevent abuse of the mailing lists by non LHCb members. If an LHCb member abuses the system, his/her identity will be known from the logfiles. The From field is optional on the Web page, and may be set to an arbitrary person; however, it is pre-filled in with the email address found in the BWHO database from the userid/password logon sequence. Due to a bug in ColdFusion, there is a restriction on the size of the message that can be sent out in this way. For very long messages, the mail should be sent directly to the server (see below). Email sent like this can be archived to the discussion list that the email was sent to. The sender of the email is free to decide whether the email should be archived or not. The user lhcbnews, with email address HYPERLINK mailto:lhcbnews@axaonl.cern.ch lhcbnews@axaonl.cern.ch is subscribed to all mailing lists. This user creates a news item with the content of the email, which can be subscribed to from the Web. From anywhere else: Email can be sent to any of the following addresses @lhcb.cern.ch: allbwho (everyone in the bwho database), calorimeters, cerngroup, collaborationboard, communications (kept for backwards compatibility, the same as lhcb), computing, convenors, daq, lhcb (everyone in the collaboration), muon, physics, rich, software, tracking, trigger, vertexdetector. Cross posting may be achieved by adding a list to the cc: field. Anyone may send an email to the lhcb server. Emails are archived by the Webmaster, except if the email contains rubbish. What to improve What should be sent out via email? Discussion groups and news Tools/technology We use: FrontPage discussion groups, interface to the ColdFusion mail client. A Unix news group on axaonl.cern.ch Procedures Every mailing list has its own discussion group. Items can be posted up by using the Web interface. After posting up an article, it can be optionally sent as an email to a mailing list from BWHO. An article that is sent as an email is also posted up on the news group at axaonl.cern.ch. Improvements Proposed direction Definition of the "LHCb Information Management" project As you can see from this document, CERN has already made a considerable investment in the LHCb information management infrastructure. Therefore, if any of this work is to be redone, and for any new work to be done, including the items listed below, we should first discuss: If it is not easier to improve the current solution. If it is worth the effort to put something new in place. Who is going to do the work to put in place the new solution. Who will do the maintenance of the new system. I suggest that the LHCb Information Management project comprises the following areas: Definition of a policy for forthcoming important reports by the collaboration (TDR's). The Web server. As described in the previous chapters, the LHCb Web server fulfills the functions of an HTML page server, a document archive, a mail server, a news-group server and the collaboration database. It was suggested to the collaboration by me to unite these functions on a single machine to minimize the maintenance, to give a consistent user interface, and to maximize our independence of other services for these critical functions. Procedures connected to Information management. Recommendation of Information management tools. TDR production policy Selection/recommendation of system. Training requirements. Support. The Web service Under this point, the following issues should be discussed: Migration to FrontPage 98. Design of pages - review of structure of the Web. Should we move the Web server to the ALNTS1 server? FrontPage training requirements? Performance issues. The Microsoft server is the slowest in benchmarks. Should we consider moving to Apache or Netscape? When? Security Protection of pages on the Web with the userid lhcb may not be sufficient. How should the BWHO userid evolve? Do we need a secure session management session as offered by the Netscape Web server? PIE When should we move to PIE (in any case we can't before August)? How will PIE coexist with BWHO? Phase-out plan for BWHO? Document archive Archival of LHCb notes and other documents. Interface with other CERN projects, e.g. library preprint server. Support and maintenance items Who can take over this work from me? Annex A. Discussion by O. Callot on why we need a news server Mailing lists have a STRONG disadvantage: Access to information produced before you registered to the list, or to lists you have not registered to, is IMPOSSIBLE. MAIL should then be coupled with a permanent repository, storing all messages posted in the list, with tools to select them as a mail reader would do. Also, creating new mailing lists is not easy, and the procedure for registering to or canceling from mailing lists is not fully mastered by all the collaborators. And some people do not like to have all the activity of meeting announcement,. in the middle of their private mails. A better solution is a private news server. A generic password allows to restrict access to members of the collaboration. Posting, reading old news or news on other 'lists' is easy. Creating new lists also. Notification, by scanning the interesting lists every 5-10 mins is feasible. Note that an LHCb news server exist, try on axaonl.cern.ch with the "lhcb" user and usual password. Of course this does not provide a very solid functionality for long term archives, i.e. if all messages are kept, a new user will see thousand of messages, and it will be difficult to find its way. The only good long term repository seems then to be the Web. However, adding a document to the Web should be easy, essentially automatic for all the traffic on the mailing lists. Tools to retrieve a message with some search string should be available, an Alta-Vista like search engine would be superb... An implementation using LEP tools is available at HYPERLINK http://axaonl.cern.ch/VAXNEWS http://axaonl.cern.ch/VAXNEWS using username "lhcb/xxxx" (xxxx being a string which identifies you) and the usual LHCb password. Posting is more the problem. The Web protocol does not allow an easy posting of document, a few lines of plain text is the maximum one can reasonably do. Mail can specify the category by using different mail addresses (as now), but can not specify other parameters like expiration date. One can imagine to force the text sent to the mail distributor to start by some technical lines, like list name and expiration, but this is not very practical. News is the best solution for posting, even if the specification of an expiration date is not possible in some newsreader like Netscape. STYLEREF "Document: Project Name" \* MERGEFORMAT Design of the LHCb Web KEYWORDS \* MERGEFORMAT STYLEREF "Document: Project Name Qualification" \* MERGEFORMAT STYLEREF "Document: Reference" \* MERGEFORMAT Reference: LHCb COMP 98-xxx STYLEREF "Document: Type" \* MERGEFORMAT LHCb Technical Note STYLEREF "Document: Revision Number" \* MERGEFORMAT Revision: 1 STYLEREF "Document: Issue" \* MERGEFORMAT Issue: Version 1 STYLEREF "Document: Last Modified Date" \* MERGEFORMAT Last modified: Wednesday, 06 May 1998 STYLEREF "Document: Project Name" \* MERGEFORMAT Design of the LHCb Web KEYWORDS \* MERGEFORMAT STYLEREF "Document: Project Name Qualification" \* MERGEFORMAT STYLEREF "Document: Reference" \* MERGEFORMAT Reference: LHCb COMP 98-xxx STYLEREF "Document: Type" \* MERGEFORMAT LHCb Technical Note STYLEREF "Document: Revision Number" \* MERGEFORMAT Revision: 1 STYLEREF "Document: Issue" \* MERGEFORMAT Issue: Version 1 STYLEREF "Document: Last Modified Date" \* MERGEFORMAT Last modified: Wednesday, 06 May 1998 page page ! . / = > N O i j k l m & ' ( ) * P Q k l m n o j UmH jq UmH j UmH jw UmH j UmH j} UmH j UmH j UmH mH j UmH 5mH mH @ , ? L j 8 G $I @&