From astroweb-request Sat Oct 1 17:39:26 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA11475; Sat, 1 Oct 94 17:39:26 EDT Return-Path: Message-Id: <9410012139.AA19291@CERBERUS.STSCI.EDU> X-Sender: adorf@cerberus.stsci.edu Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 1 Oct 1994 17:39:45 -0500 To: astroweb@NRAO.EDU (AstroWeb Consortium) From: adorf@stsci.edu (Hans-Martin Adorf) Subject: new WAIS sources Sender: astroweb-request@fits.CV.NRAO.EDU Hello, I have hunted for astronomical WAIS sources not yet included in our AstroWeb listings. Here are my 18 findings: Sources at stardust.jpl.nasa.gov -------------------------------- PDS_catalog.src PDS_labels.src PDS_standards.src PDS_templates.src Sources at wfpc3.la.asu.edu --------------------------- sci.astro.hubble.src Sources at anarky.stsci.edu --------------------------- sci-ulas-db.src astroweb.src (requires authorization) Sources at ecf.hq.eso.org ------------------------- hst-one-book.src stecf-directory-of-servers.src stecf-newsletter-index.src stecf-sw-library.src stecf-www.src Fionn Murtagh's sources at the ST-ECF (temporary?) -------------------------------------------------- hst-literature.src hst-observing-proposals-noPI.src hst-observing-proposals.src hst-publications.src proposal-abstracts-5.src wfpc-im-text.src Note that some of the WAIS sources at the ST-ECF are currently non-operational due to a temporary disk space problem. Should be fixed within a few days. Also the names of some of the sources at the ST-ECF need a revision. I wonder how all these sources are best incorporated into AstroWeb. Anyone volunteering? (I am tired after the hunting effort.) I could provide the WAIS source descriptions. Hans-Martin From astroweb-request Sat Oct 1 17:53:09 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA11500; Sat, 1 Oct 94 17:53:09 EDT Return-Path: Message-Id: <9410012153.AA19313@CERBERUS.STSCI.EDU> X-Sender: adorf@cerberus.stsci.edu Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 1 Oct 1994 17:53:30 -0500 To: astroweb@NRAO.EDU (AstroWeb Consortium) From: adorf@stsci.edu (Hans-Martin Adorf) Subject: yaws (yet another WAIS source) Sender: astroweb-request@fits.CV.NRAO.EDU @banzao.gsfc.nasa.gov --------------------- Magellan.src From dwells Sat Oct 1 18:42:49 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA11609; Sat, 1 Oct 94 18:42:49 EDT Return-Path: Date: Sat, 1 Oct 94 18:42:44 EDT From: dwells@fits.CV.NRAO.EDU (Don Wells) Message-Id: <9410012242.AA11600@fits.cv.nrao.edu> To: adorf@stsci.edu (Hans-Martin Adorf) Cc: astroweb@NRAO.EDU (AstroWeb Consortium) Subject: Re: new WAIS sources In-Reply-To: <9410012139.AA19291@CERBERUS.STSCI.EDU> References: <9410012139.AA19291@CERBERUS.STSCI.EDU> Sender: astroweb-request@fits.CV.NRAO.EDU Hans-Martin Adorf writes: > I wonder how all these sources are best incorporated into AstroWeb. I recommend using AstroWeb Resource Entry Form http://fits.cv.nrao.edu/www/astroweb/aref.html for the cases which are not already in AstroWeb. When I am doing this I usually have two copies of Mosaic running, one with the form and one to open on the resources. I cut text from the descriptions in the resource pages (in case of WAIS, "source" files) and paste it into the Resource Entry Form. The records will be added to the database within a few days (Anton almost always beats me to it). In fact, if you wanted to change an existing record, and didn't want to interact with the database, you could use the form and fill it with the text from the existing record plus your modifications. You could use Bob's tools to delete the old record if you wished (deleting is very easy). I recommend that you try the entry form. -Don From astroweb-request Mon Oct 3 23:37:35 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA15768; Mon, 3 Oct 94 23:37:35 EDT Return-Path: Message-Id: <9410040339.AA28593@cdsxb6.u-strasbg.fr> To: astroweb@fits.CV.NRAO.EDU Cc: heck@cdsxb6.u-strasbg.fr Subject: Varia Date: Tue, 04 Oct 94 04:39:13 +0100 From: Andre HECK Sender: astroweb-request@fits.CV.NRAO.EDU Dear Friends, 1. Have we a tool able to single out the URLs not necessarily dead, but obsolete, i.e. pointing towards new pages? 2. For those of you who did not see it at ADASS'94, a tie with the AstroWeb logo (Van Gogh's painting) is available from Ralph Martin's Co. (not the guy from the e-mail files, another one ...). Andre. ------------------------------------------------------------------------ From astroweb-request Tue Oct 4 08:47:08 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA17356; Tue, 4 Oct 94 08:47:08 EDT Return-Path: Date: Tue, 4 Oct 94 08:46:19 EDT From: Bob Jackson Message-Id: <9410041246.AA17892@MARIAN.STSCI.EDU> To: astroweb@NRAO.EDU In-Reply-To: <9410040339.AA28593@cdsxb6.u-strasbg.fr> (message from Andre HECK on Tue, 04 Oct 94 04:39:13 +0100) Subject: Re: Varia Reply-To: jackson@stsci.edu Sender: astroweb-request@fits.CV.NRAO.EDU w.r.t. 1. Have we a tool able to single out the URLs not necessarily dead, but obsolete, i.e. pointing towards new pages? I have seen instances in the DEAD and UNRELIABLE listings where the returned string contains the new address. I have hear of 'redirection' but have never set it up on my server. So, this tool may not be necessary From www_server Wed Oct 5 22:53:17 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA22665; Wed, 5 Oct 94 22:53:17 EDT Return-Path: Date: Wed, 5 Oct 94 22:53:13 EDT From: www_server@fits.CV.NRAO.EDU (httpd@fits.cv.nrao.edu) Message-Id: <9410060253.AA22656@fits.cv.nrao.edu> To: astroweb@NRAO.EDU, durand@dao.nrc.ca Subject: httpd server name correction Sender: astroweb-request@fits.CV.NRAO.EDU Message entered by: durand @ macdaniel.dao.nrc.ca [134.87.150.99] Please change all occurence of links using the following server name: cadc.dao.nrc.ca to the correct denomination: cadcwww.dao.nrc.ca. Right now, it is the same machine but we are planning a move in the next week or so. Thanks for the good work Daniel From astroweb-request Fri Oct 7 05:25:58 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA26082; Fri, 7 Oct 94 05:25:58 EDT Return-Path: X-Sender: hmadorf@ns3.hq.eso.org Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 7 Oct 1994 10:27:28 +0100 To: astroweb@NRAO.EDU From: InfoSeek Corporation (by way of adorf@eso.org (Hans-Martin Adorf)) Subject: Your message to info@infoseek.com Sender: astroweb-request@fits.CV.NRAO.EDU This is an automated reply to your message requesting more information about InfoSeek. NOTE: This message will be updated on Oct. 15 to reflect new pricing and information on how to get an account for the commercial service. The "info@infoseek.com" e-mail address *always* sends this introductory information. If you would like to request a specific document or get an account, your request should be sent to a *different* e-mail address as explained below. The "info" email address is normally *not* monitored by a human. If your request is not addressed by the information below, the following instructions will also tell you how to contact a real person. However, *please* use this as a last resort because we have had an incredibly high response to our service and we currently have very limited support resources. The answers to almost all questions are either in this document, or are available electronically and *instantly* through our request server. Also, we know you don't have a lot of time to read through all this, but we'd really appreciate it if you do. We've tried to keep it as short as we can and still cover everything you need to know. When we get support questions we haven't covered, we immediately fix the documentation. It will be *much* faster to read the information below carefully, rather than skimming it and then *waiting* for support!! InfoSeek is now making a limited number of free accounts available in order to give us a better understanding of the Internet market. Information on how to apply for an account is included below. It's easy and simple and there are no forms to fill out. The whole process takes about 60 seconds and your account will be immediately activated upon receipt of your request. This message contains: o Background information about InfoSeek o How to apply for a free account o What happens when the free trial is over o Minimum system requirements o List of supported browsers o How to get more information ======================================================================== Background information about InfoSeek ======================================================================== "It's too hard to find anything on the Internet." "Finding information takes too long, you have to know which vendors and which collections to search, you have to know the specific query language for the system, you have to be careful in formulating your query, you have to look through too many or too few hits, the hits aren't sorted in relevance order, there's too much pressure when you are being charged for connect time, it's too expensive if you don't find anything, and it's too expensive if you do." Can you relate to this? Finding information today is just plain too hard and too expensive. It's the reason we started InfoSeek. By making it very easy to find information and by requiring our information suppliers to provide their information at reasonable prices, more people will have rapid access to information. And that's a big win for everyone. ======================================== Mission InfoSeek Corporation's mission is to deliver products that make it possible for computer users to quickly find information stored anywhere in the world. Using a single, easy to use information tool, users connected to the Internet will be able to browse, search, and retrieve information from multiple local and remote collections. The problem Information today is widely available, but it's often expensive and difficult to find. All of today's information systems are limited in scope to only that data organized for access through a vendor-specific interface. We have "islands of information" where it is difficult to access anyone else's data in a uniform manner. For example, you must use the Dow Jones interface to search Dow Jones for a financial analyst report and the Dialog interface to search a database there. Compounding this segmentation is that even within a single vendor the tools are difficult to use. Users want a single, easy to use tool that provides uniform access to all data, whether that data is from local, remote, private, corporate, or commercial sources. That is what InfoSeek is all about. InfoSeek's approach In late 1994, InfoSeek will establish an Internet full-text search service that is compatible with existing Internet end-user tools and protocols. UNIX, PC, and Macintosh Mosaic users can use a single "point and click" user interface to browse, search, and retrieve information stored at InfoSeek or accessible from other Internet search servers. Queries can be expressed in plain English, e.g., "Who makes the fastest 400 dpi laser printer?" InfoSeek software hides the complexity of where the data is located and which protocols were used to retrieve the information. Within a few seconds, article titles are returned sorted in relevance order. Clicking on a title returns the original article with query terms highlighted. The search system we are using is extraordinarily accurate. On average, in the top 20 documents returned from a query, over 60% are relevant. In extensive independent laboratory tests of over 30 different full-text search systems, no other search system performed better than this and most were quite a bit worse. If you've been frustrated in the past with other search systems, you should be pleasantly surprised using InfoSeek. It is easy for novices to use, yet has capabilities that meet the needs of the most sophisticated professional searchers. In 1995, in addition to offering the search service, we will also be providing our search software and Internet server software to anyone who wants to make their information accessible over the Internet for either commercial or non-commercial use. This will expand the network of information sources available to all InfoSeek subscribers. InfoSeek has developed two novel approaches for finding information across distributed databases. First, users are not required to know "where" to search for the information. If the information is located on any participating computer(s) anywhere in the world, InfoSeek will be able to locate it within a few seconds. Second, InfoSeek can accurately rank the query "hits" from multiple servers into a single relevance ordered list, even if multiple heterogenous search engines are involved in the query. Solving these two problems was required in order to truly provide access to global information resources and, to our knowledge, no other company's search approach has solved these two problems. Background InfoSeek was started in January 1994 by Steve Kirsch, formerly founder and president of Frame Technology (makers of FrameMaker), as well as founder and president of Mouse Systems (makers of the Sun optical mouse). The development team has extensive experience in the design and implementation of wide-area document search and retrieval systems. InfoSeek, which is privately held, has raised over $2M in two rounds of financing. Investors include Menlo Ventures and founders and executives from Sun, 3Com, Frame, InterOp, Kodak, and Alex Brown. ======================================================================== How to apply for a free account ======================================================================== 100+ Computer Publications Now Searchable from Mosaic! InfoSeek is offering access to a trial version of the Computer Select articles database from over 100 computer periodicals for a limited time absolutely FREE to the first 20,000 Internet users who are willing to answer a few short surveys during our test period. The Ziff Computer Select trial database contains the full text of selected articles from such computer periodicals as The Seybold Report, MacUser, MacWeek, PC Week, and many more. Plus, it also contains selected computer-related abstracts from the New York Times, Wall St. Journal, San Jose Mercury News, etc. Over 79,000 articles covering more than a year's worth of data are included. Using plain English queries processed by a very powerful and accurate full-text search system, you will be able to obtain information on a broad variety of computer related topics, such as stories on companies, products, people, technologies, and trends. During the free trial period, the database will be limited to computer articles from November 1992 through November 1993. So although you cannot ask about events within the last 10 months, we encourage you to explore the database and become familiar with the search engine while it is free. The Ziff Computer Select test database has quite a bit of interesting data available to you at no charge! Here are some sample queries that can be typed in exactly as they appear: o A developer might want to look up algorithms or find out about development tools or technologies, e.g., What is JPEG? What is Kerberos? What is MIME? What is Spec 1170? Who makes transport-independent RPC? o A computer operations manager might want to look at articles/reviews/prices on equipment or software before making a purchase, e.g., Who makes the fastest Pentium PC? Who makes the fastest 486 computer? Who makes the best laser printer? Which digital tape drive has the best data reliability in the industry? Which Ethernet cards have the best performance? Who makes the best RAID system? What's the difference between the NEC 5FG and 5FGe? What are the considerations for selecting a UPS? What should I consider when buying a network server? o A product manager or business analyst might want to get information about other companies or technology trends, e.g., What were Apple's 4th quarter earnings? Where is Frame Technology located? Who is the president of RSA Data Security? What companies make CAD packages? Does anyone make an SGML viewer? What is the ticker symbol for HP? All of these queries, typed in exactly as they appear above, will produce a list of up to 20 of the most relevant documents within a few seconds. And, in all these examples, the first or second document in the list will contain exactly the information you are looking for. When you click on a title, the full document text will be quickly downloaded so you can read it or print it for your own use. Extensive on-line hypertext help is available which completely describes how to make the most effective use of the system including tips on how to limit your query to the key words that will give you the best results as well as how to use all the special advanced query operators. If you are using the **latest** 2.x release of Mosaic or Lynx on any platform (UNIX, PC, or Macintosh) or any of the other supported browsers listed below, we invite you to apply for a FREE account which will give you full access to the database. In return, we ask that you respond to a brief survey that will be sent to you during the test period. Please note that since this service is being provided to you absolutely free, InfoSeek reserves the right to terminate this offer at any time and to terminate any account at any time and for any reason. However, it is our intention at this time to run the trial until October 15, 1994 for all accounts. If you are a Mosaic or Lynx user and you are interested in participating in this trial, send an email to: request@infoseek.com The Subject line can be blank. However, the body of the message must contain one line of the form: password where the first argument is your preferred Internet e-mail address and the second argument is the password which you would like to use to protect your account. Do not include the angle brackets (they are there for readability). Also, please do not include any spaces in your password or e-mail address and do not include any other lines (such as signature lines) in your request. The e-mail address which you type in will be used both as your account ID as well as the address to use for sending the login instructions. It will also be used for communicating messages to you from time to time. Your e-mail address will be kept confidential. IMPORTANT: Please type your preferred e-mail address *carefully* or you won't get any instructions back! Try to use the "shortest" external e-mail address that still works since this will make it easier to deliver mail if you move and easier for you to log in. For example, fred@sun.com is preferred to fred@topgun.East.Eng.Sun.Com ***if*** both e-mail addresses work. Do NOT use *internal* e-mail addresses such as fred@topgun. Do NOT use your IP address; fred@192.9.201.3 is meaningless. Do NOT drop characters from your username. Do NOT use a 0 instead of a O (or vice-versa). Do NOT use .com if you are in an .edu or .net domain (or vice-versa). In short, TYPE YOUR E-MAIL ADDRESS CAREFULLY! Also, both the email address and password are ***case-sensitive*** so if you hate using the shift key every time you log in, just type everything in lowercase!!!! For example, if your Internet e-mail address is fred@mumble.com, and if you want to protect your account with the password "wombat", you would send email to request@infoseek.com containing a single line in the body of the message: password fred@mumble.com wombat Our automated responder will process your request and send a reply back to the e-mail address you have supplied within 10 seconds from when we receive it. The confirmation will have the username and password for your account as well as instructions on how to get to the server. You should then be able to log in. If you have any trouble logging in, please send e-mail to comments@infoseek.com. If you don't get a quick response to your password request, it may mean that either we are currently down (this is rare), or your e-mail gateway is slow. In either case, you will normally not need to repeat your request. For technical, copyright and support reasons, we ask that you not share your account with anyone. Plenty of accounts are available. Please refer other Mosaic (or WWW) users who are interested in getting an account to send e-mail to info@infoseek.com so that they will receive the latest introductory information. Another reason to refer people to info@infoseek.com is because account registration procedures may change from time to time, but this e-mail will alway contain the current instructions. Thanks! So if you are reading this because this e-mail was forwarded to you, please send e-mail to info@infoseek.com to get the latest version of this document! ======================================================================== What happens after the trial period is over ======================================================================== The free trial period will last until October 15. At that time, your account will be automatically closed. You will never be billed. After the trial period, you will need to explictly sign up if you want to use the commercial service which will begin on October 15. On October 15, the Computer Select database will be brought ***up-to-date*** and will be maintained so that it always has at least 1 years worth of ***current*** data, instead of 1 years worth of **historical** data. We'll be adding more databases to the service in the future so you'll be able to find things other than just ***computer*** articles. Pricing has not yet been determined yet. It will not be announced prior to October 15. Your suggestions (send email to comments@infoseek.com) are welcome! ======================================================================== Minimum system requirements ======================================================================== The minimum requirement for using InfoSeek is that you must have a real-time connection to the Internet. Ideally, you have a dedicated T-1 line or better, but you can also access InfoSeek through dialup connections (SLIP, PPP, or standard ASCII dialup). The minimum configuration to use InfoSeek is to run Lynx at either your local site (preferably) or by telnetting to a site where you can run Lynx. This will give you a line-oriented user-interface that, while usable, is not the easiest to use. You can run Lynx over standard ASCII dialup phone connections. The preferred method for accessing InfoSeek is by running a graphical WWW browser such as Mosaic. However, this requires either a direct Internet connection, or a PPP, SLIP, or CSLIP dialup connection. Even if you have a firewall between your system and the Internet, you can access InfoSeek without jeopardizing system security if your system administrator has installed one of the proxy forwarders available for Mosaic. This will be slower than running it directly on the Internet but it allows you to run Mosaic on your own workstation. You may also be able to run Mosaic on your firewall machine, and specify the name of an X display (your UNIX workstation, X terminal, PC, etc). Or you may be able to rlogin to your firewall machine and use lynx. Your system administrator may also be able to give your workstation an Internet IP address with direct Internet access. If done properly, this does not represent a security risk. Please contact your system administrator for details. Most commercial on-line services only provide a limited amount of connectivity to the Internet. For example, as far as we know (please let us know if we are mistaken!), you cannot at this time use the InfoSeek service from Prodigy, CompuServe, America Online, Dow Jones, or Apple e-World because these services do not yet provide a Mosaic-compatible browser (CompuServe is supposed to have PPP access in 1995). On the other hand, many "Internet" service providers such as CerfNet and Netcom allow you to use Lynx if you have a standard dialup account or Mosaic if you have a SLIP or PPP account. Delphi just recently announced a text-mode browser for the web, but it doesn't support forms or authentication. Since Delphi does not support Lynx and their WWW browser cannot be used with InfoSeek, InfoSeek will be providing a limited number of telnet logins to allow you to run Lynx. Use telnet to connect to infoseek.com and login as www. You can login as www-dumb if you terminal does not support highlighting (this will number the links). Once Lynx has started, navigate to the Query page, and log in using your InfoSeek username and password. ======================================================================== List of supported browsers ======================================================================== You MUST use Mosaic or a WWW-compatible browser that supports **both** forms and authentication in order to use the InfoSeek service. All the latest 2.x NCSA Mosaic versions support InfoSeek. Use the Help pulldown to see what version you have. The following browsers are known to work: NCSA Mac Mosaic 2.0 (alpha 2 and 6) NCSA Win Mosaic 2.0 (alpha 4,5,6, or 7) NCSA UNIX Mosaic 2.0 (2.1 thru 2.5). Lynx 2.1 thru 2.3 Spry AirMosaic Spyglass Mosaic OmniWeb 0.7.4.1 (Beta) for NextStep See the next section for how to use our request server to get information on how to ftp the latest versions of Lynx and NCSA Mosaic. The following browsers do *not* work and **cannot** be used with InfoSeek: Win Mosaic 2.0 (alpha 2) Win Mosaic 1.x.x Mac Mosaic 1.x.x MacWeb (all versions) Netcom's NetCruiser Note that Lynx is a character mode browser that can be used over standard ASCII dialup connections to Internet service providers and over telnet, while Mosaic is a graphical user interface browser and requires a direct Internet connection, or SLIP or PPP access. If you are not sure if your browswer supports authentication, try loading: http://www.infoseek.com/cgi-bin/query and see if you get a dialog box asking for a user name. ======================================================================== How to get more information ======================================================================== For more information about InfoSeek, you can use our automated request server. Send e-mail to: request@infoseek.com with the command: send titles in the body of the message. In return, you'll get back a complete list of document titles that you can subsequently request. A wide variety of documents are available through the request server such as: o information on how to get on or off our mailing list o information on how to close your account o information on how to get browsers such as Mosaic and Lynx o information on licensing Mosaic for commercial re-distribution o information for the press (screen shots in TIFF BinHex format, Q&A) o information on how to put your information on our server o information on how to get our software for your own server o the complete list of journals included in Computer Select o the complete list of request server commands o pricing (site licenses, educational pricing, etc.) o how to win $100 by solving a user mystery o and a lot more.... InfoSeek Corporation 2620 Augustine Dr #250 Santa Clara, CA 95054 FAX: (408) 986-1889 Phone: (408) 982-4450 <<-- Use as a last resort. E-mail to comments@infoseek.com is preferred. E-mail: info@infoseek.com (automated server; sends general information) request@infoseek.com (automated request server) comments@infoseek.com (for submitting questions, bugs, suggestions) WWW: http://www.infoseek.com/ End of info document. This document was last updated on October 3, 1994. From www_server Fri Oct 7 06:13:54 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA26919; Fri, 7 Oct 94 06:13:54 EDT Return-Path: Date: Fri, 7 Oct 94 06:13:41 EDT From: www_server@fits.CV.NRAO.EDU (httpd@fits.cv.nrao.edu) Message-Id: <9410071013.AA26910@fits.cv.nrao.edu> To: astroweb@NRAO.EDU, baruffolo@astrpd.pd.astro.it, web@www.pd.astro.it Subject: change of URL Sender: astroweb-request@fits.CV.NRAO.EDU Message entered by: Andrea Baruffolo @ 147.162.26.105 [147.162.26.105] We have moved our HTTP server from vega.pd.astro.it to www.pd.astro.it (a physically different machine). This means that the old URL: http://vega.pd.astro.it:8080/ should be changed to: http://www.pd.astro.it/ The old server will remain alive for a while redirecting all requests to the newer one, but it will be shut down in the future. Thank you for your attention. Andrea Baruffolo Astronomical Observatory Padova, Italy From astroweb-request Fri Oct 7 06:58:47 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA26955; Fri, 7 Oct 94 06:58:47 EDT Return-Path: X-Sender: hmadorf@ns3.hq.eso.org Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 7 Oct 1994 12:00:21 +0100 To: astroweb@NRAO.EDU From: Rudi Albrecht (by way of adorf@eso.org (Hans-Martin Adorf)) Subject: useful WWW information Sender: astroweb-request@fits.CV.NRAO.EDU Dear Mosaicers, While browsing the net I came across this collection of extremely useful hypermedia related stuff: http://cbl.leeds.ac.uk/nikos/doc/repository.html#soft Regards, Rudi From astroweb-request Fri Oct 7 15:38:14 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA27625; Fri, 7 Oct 94 15:38:14 EDT Return-Path: Date: Fri, 7 Oct 1994 13:41:16 -0600 From: brad@bear.ras.ucalgary.ca ( Brad Wallace ) Message-Id: <9410071941.AA19182@bear.ras.ucalgary.ca> To: astroweb@NRAO.EDU Subject: Web listing Sender: astroweb-request@fits.CV.NRAO.EDU G'day, In your astroweb pages you have a listing for the University of Calgary - Radio Astronomy Laboratory. While this link is still perfectly valid, other groups in the Physics and Astronomy Department have st up pages also. As such, I wonder if I could get you to remove the link to the Radio Astronomy lab, and replace it with the link http://bear.ras.ucalgary.ca/department.html which connects to information about the department of Physics and Astronomy at the U of Calgary, and branches from there. Many thanks. Brad Wallace From astroweb-request Fri Oct 7 16:29:30 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA27730; Fri, 7 Oct 94 16:29:30 EDT Return-Path: Date: Fri, 7 Oct 94 16:29:16 EDT From: Bob Jackson Message-Id: <9410072029.AA10640@MARIAN.STSCI.EDU> To: astroweb@NRAO.EDU Subject: statistics Reply-To: jackson@stsci.edu Sender: astroweb-request@fits.CV.NRAO.EDU I just did a crude look at my logs and... The STScI version of AstroWeb was accessed 8000 times and searched 1000 times during September 1994. From astroweb-request Sun Oct 9 05:54:09 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA05479; Sun, 9 Oct 94 05:54:09 EDT Return-Path: Message-Id: <9410090956.AA13856@SIMBAD.u-strasbg.fr> To: jackson@stsci.edu Cc: astroweb@fits.CV.NRAO.EDU Subject: Re: statistics In-Reply-To: Your message of Fri, 7 Oct 94 16:29:16 EDT . Date: Sun, 09 Oct 94 10:56:05 +0100 From: egret@SIMBAD.u-strasbg.fr X-Mts: smtp Sender: astroweb-request@fits.CV.NRAO.EDU Statistics of AstroWeb pages at CDS : since June 1st (130 days): there were 2075 calls to the AstroWeb page. Daniel From astroweb-request Mon Oct 10 15:10:39 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA08732; Mon, 10 Oct 94 15:10:39 EDT Return-Path: X-Sender: hmadorf@ns3.hq.eso.org Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 10 Oct 1994 13:16:19 +0100 To: astroweb@NRAO.EDU From: adorf@eso.org (Hans-Martin Adorf) Subject: AstroWeb advertising in ST-ECF Newsletter Sender: astroweb-request@fits.CV.NRAO.EDU Dear friends, I should like to run a short advertisement of the AstroWeb service in our Newsletter. Do you agree? Bob, could I reuse the material you presented at the ADASS '94 conference? -hma From astroweb-request Tue Oct 11 05:47:39 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA11073; Tue, 11 Oct 94 05:47:39 EDT Return-Path: X-Sender: hmadorf@ns3.hq.eso.org Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 11 Oct 1994 10:49:19 +0100 To: astroweb@NRAO.EDU From: Sake Hogeveen (by way of adorf@eso.org (Hans-Martin Adorf)) Subject: Utrecht URLs have changed Sender: astroweb-request@fits.CV.NRAO.EDU Dear Hans-Martin, The WWW server of the Astronomical Institute at Utrecht University has been moved to an other computer. With the move, the URLs of the various entries in the server have changed. The URLs have been modified such, that future changes of machine will not be noted by the outside world. In your page "Astronomical information on the Internet", I found the following references to our server: =========
Sterrenkundig Instituut Preprint Service (Utrecht)
The URL should now read: http://stkwww.fys.ruu.nl:8000/preprint.html =========
Utrecht University - Astronomical Institute ADS-X11, solar physics
This URL should now read: http://stkwww.fys.ruu.nl:8000/ Please remove the remarks about "ADS-X11, solar physics". You can enter as OWNER: hogeveen@fys.ruu.nl. =========
Aspects of publishing with TeX and LaTeX
This URL should now read: http://stkwww.fys.ruu.nl:8000/posters/hogeveen/recommend/astdoc.html ========= There is one special case:
XXIInd General Assembly of the International Astronomical Union
This entry should be removed entirely. This server was maintained not by the IAU itself, but by the Local Organizing Committee, which is no longer committed to maintain it, since the 22nd GA is over. ========= I will send a copy of this letter to Don Wells at NRAO. I hope this will help to keep your excellent service up to date. -- Sake J. Hogeveen, Astronomical Institute, Utrecht University, Princetonplein 5, P.O. Box 80000, NL-3508 TA Utrecht, The Netherlands. Telephone: +31 (0)30 535227/5200, Fax: +31 (0)30 535201, E-mail: hogeveen@fys.ruu.nl. From astroweb-request Tue Oct 11 05:49:51 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA11090; Tue, 11 Oct 94 05:49:51 EDT Return-Path: X-Sender: hmadorf@ns3.hq.eso.org Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 11 Oct 1994 10:51:15 +0100 To: Sake Hogeveen From: adorf@eso.org (Hans-Martin Adorf) Subject: Re: Utrecht URLs have changed Cc: astroweb@NRAO.EDU Sender: astroweb-request@fits.CV.NRAO.EDU Dear Sake, did you check whether the other servers also need modifications? The reason is that the ST-ECF is a bit outdated right now, and we are (with the help of Don Wells) in the process of installing an automatic update mechanism. -Hans-Martin From astroweb-request Wed Oct 12 01:19:50 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA13656; Wed, 12 Oct 94 01:19:50 EDT Return-Path: Message-Id: <9410120521.AA03456@cdsxb6.u-strasbg.fr> To: astroweb@fits.CV.NRAO.EDU Cc: heck@cdsxb6.u-strasbg.fr Subject: Announcement in CDS Bulletin Date: Wed, 12 Oct 94 06:21:43 +0100 From: Andre HECK Sender: astroweb-request@fits.CV.NRAO.EDU Here is the bibliographical reference of this announcement: Bull. Inform. Centre Donnees Astron. Strasbourg 45 (1994) 21-25 AH. ------------------------------------------------------------------------ From dwells Wed Oct 12 17:39:53 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA17567; Wed, 12 Oct 94 17:39:53 EDT Return-Path: Date: Wed, 12 Oct 94 17:39:50 EDT From: dwells (Don Wells) Message-Id: <9410122139.AA17561@fits.cv.nrao.edu> To: astroweb Subject: The ILIAD Knowledge Robot Sender: astroweb-request@fits.CV.NRAO.EDU Dear friends, For many weeks my WAIS server nrao-fits, which indexes FITS-related documents, has been bombarded with strange search queries coming from a machine at Johnson Space Center in Texas. At first I ignored the traffic, but finally I became annoyed enough that I picked up the telephone and called the network administrator at JSC. I found out that the origin of the queries is an HPCC project to build a "knowledge robot" based on Dewey Decimal classification of network resources (in this case WAIS servers): NASA Johnson Space Center's HPCC K-12 Project http://www.jsc.nasa.gov/stb/ILIAD/Mosaic/iliad.html It is conceivable that some variation on the ideas of this project might be relevant to our general problem of resource discovery in astronomy. -Don From astroweb-request Thu Oct 13 03:41:15 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA18048; Thu, 13 Oct 94 03:41:15 EDT Return-Path: X-Sender: hmadorf@ns3.hq.eso.org Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 13 Oct 1994 08:42:57 +0100 To: astroweb@NRAO.EDU From: adorf@eso.org (Hans-Martin Adorf) Subject: Re: The ILIAD Knowledge Robot Sender: astroweb-request@fits.CV.NRAO.EDU Dear Don, you pesumably know this URL: http://web.nexor.co.uk/mak/doc/robots/robots.html on WWW Robots, Wanderers and Spiders. The past few days I have been interested in finding more astronomical WAIS databases. The CEA maintains two (abstracts/publications and their WWW), NASA's PDS at least five. I also found the ADASS '93 proceedings and the ADASS '94 abstract sources. My collection of astronomical WAIS sources numbers > 60 now, of which about "only" 40 are listed in our AstroWeb database. -hma From astroweb-request Thu Oct 13 04:24:23 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA18083; Thu, 13 Oct 94 04:24:23 EDT Return-Path: X-Sender: hmadorf@ns3.hq.eso.org Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 13 Oct 1994 09:26:06 +0100 To: astroweb@NRAO.EDU From: adorf@eso.org (Hans-Martin Adorf) Subject: W3 Search Engines Sender: astroweb-request@fits.CV.NRAO.EDU The most usefule resource for locating WWW (and other) Internet resources I find http://cui_www.unige.ch/meta-index.html which gives direct acess to about 15 robot databases as well as other searchable material. Hans-Martin From astroweb-request Thu Oct 13 11:27:04 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA19801; Thu, 13 Oct 94 11:27:04 EDT Return-Path: Date: Thu, 13 Oct 94 11:26:57 EDT From: Bob Jackson Message-Id: <9410131526.AA13528@MARIAN.STSCI.EDU> To: astroweb@NRAO.EDU Subject: [dwells@fits.cv.nrao.edu: The ILIAD Knowledge Robot] Reply-To: jackson@stsci.edu Sender: astroweb-request@fits.CV.NRAO.EDU Unfortunately the ILIAD tool appears to only look at WAIS indices and then only at the contents of the .src file, which is not a good measure of the actual index contents. I think HARVEST is a better approach. From dwells Thu Oct 13 11:45:23 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA19825; Thu, 13 Oct 94 11:45:23 EDT Return-Path: Date: Thu, 13 Oct 94 11:45:20 EDT From: dwells (Don Wells) Message-Id: <9410131545.AA19819@fits.cv.nrao.edu> To: astroweb Subject: Re: [dwells@fits.cv.nrao.edu: The ILIAD Knowledge Robot] In-Reply-To: <9410131526.AA13528@MARIAN.STSCI.EDU> References: <9410131526.AA13528@MARIAN.STSCI.EDU> Sender: astroweb-request@fits.CV.NRAO.EDU Bob Jackson writes: > Unfortunately the ILIAD tool appears to only look > at WAIS indices and then only > at the contents of the .src file, > which is not a good measure of the actual > index contents. I talked to one of the developers. My understanding of their current technique is that they use descriptions of Dewey codes as search strings, and run them against a list of WAIS servers to rank the degree of match between the contents of the indicies of the servers (_not_ the src files) and the codes. Then a user query to their system can be matched against the Dewey codes in order to produce a list of appropriate servers to which the query can be submitted. This approach only applies to WAIS servers, of course. In principle, the Astronomy Thesaurus might provide a classifier coding system analogous to DDC. I have heard experienced people say that the thesaurus approach does not work, that indexing of full text is the only reliable approach. I have insufficient experience to judge. > I think HARVEST is a better approach. Does Harvest do WAIS servers? I thought it was only looking at HTML. -Don From astroweb-request Fri Oct 14 03:47:26 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA22080; Fri, 14 Oct 94 03:47:26 EDT Return-Path: X-Sender: hmadorf@ns3.hq.eso.org Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 14 Oct 1994 08:49:11 +0100 To: astroweb@NRAO.EDU From: durand@dao.nrc.ca (Daniel Durand) (by way of adorf@eso.org (Hans-Martin Adorf)) Subject: New WWW browser Sender: astroweb-request@fits.CV.NRAO.EDU Please look at the netscape WWW browser. You will find it under ftp://ftp.mcom.com/pub/netware... They have Mac, X and Windoze versions. It is incredibly faster than Mosaic (up to 20X more if you have big images) It is really a breakthrough. Let me know what you think.... Chers Daniel From astroweb-request Fri Oct 14 03:45:52 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA22066; Fri, 14 Oct 94 03:45:52 EDT Return-Path: X-Sender: hmadorf@ns3.hq.eso.org Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 14 Oct 1994 08:47:36 +0100 To: fmurtagh@eso.org (Fionn Murtagh), malbrech@eso.org (Miguel Albrecht) From: adorf@eso.org (Hans-Martin Adorf) Subject: e-print server Cc: astroweb@NRAO.EDU Sender: astroweb-request@fits.CV.NRAO.EDU Fionn, Miguel, did you already check out the LANL e-print server at http://xxx.lanl.gov It offers a really good forms based interface to LANL's e-print archive (which includes astrophysics) plus TeX macros and utilities. Hans-Martin From astroweb-request Fri Oct 14 04:12:25 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA22104; Fri, 14 Oct 94 04:12:25 EDT Return-Path: X-Sender: hmadorf@ns3.hq.eso.org Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 14 Oct 1994 09:14:08 +0100 To: astroweb@NRAO.EDU From: adorf@eso.org (Hans-Martin Adorf) Subject: WWW resource discovery Sender: astroweb-request@fits.CV.NRAO.EDU Check out http://home.mcom.com/home/internet-search.html From the intro: Internet Search If you're trying to find a particular page on the Internet, you can use one of the many available online Search Engines. These search engines allow you to search for information in many different ways -- some engines search titles or headers of documents on the net, others search the documents themselves, still others just search other indexes or directories. For every case, we'll cite a sample search thet provides some guidence about each engine's effectiveness. ... -hma From dwells Fri Oct 14 15:36:24 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA24558; Fri, 14 Oct 94 15:36:24 EDT Return-Path: Date: Fri, 14 Oct 94 15:36:05 EDT From: dwells@fits.CV.NRAO.EDU (Don Wells) Message-Id: <9410141936.AA24548@fits.cv.nrao.edu> To: durand@dao.nrc.ca (Daniel Durand) (by way of adorf@eso.org (Hans-Martin Adorf)) Cc: astroweb@NRAO.EDU Subject: Re: New WWW browser In-Reply-To: References: Sender: astroweb-request@fits.CV.NRAO.EDU Daniel Durand) (by way of adorf@eso.org (Hans-Martin Adorf) writes: > Please look at the netscape WWW browser. You will find it under > ftp://ftp.mcom.com/pub/netware... see http://mosaic.mcom.com/info/newsrelease.html http://mosaic.mcom.com/info/how-to-get-it.html The mcom server was overloaded, so I got my copy from U.Kansas. > Let me know what you think.... I am impressed. I am still trying to decide whether to commit myself to it as a replacement for old Mosaic. Now we know what Marc Andreesson has been doing since he left Illinois-NCSA! Netscape supports the mailto: URL. Email support is definitely better. Print support seems to be improved. -Don From astroweb-request Fri Oct 14 16:15:31 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA24676; Fri, 14 Oct 94 16:15:31 EDT Return-Path: From: jones@bradbury.nrl.navy.mil (Dave Jones) Message-Id: <9410142016.AA27643@bradbury.nrl.navy.mil> Subject: Contribution to the astroweb To: astroweb@fits.CV.NRAO.EDU Date: Fri, 14 Oct 1994 16:15:56 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 320 Sender: astroweb-request@fits.CV.NRAO.EDU The Space Science Division (SSD) of the Naval Research Lab has recently developed a homepage for distribution on the Web. Could you please include a link on your Astronomical information on the Internet page to the Space Science Division. The URL is http://bradbury.nrl.navy.mil/general/ssd.html. Thanks Dave Jones From astroweb-request Mon Oct 17 09:29:38 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA03043; Mon, 17 Oct 94 09:29:38 EDT Return-Path: Date: Mon, 17 Oct 94 09:29:31 EDT From: Bob Jackson Message-Id: <9410171329.AA10419@MARIAN.STSCI.EDU> To: jones@bradbury.nrl.navy.mil In-Reply-To: <9410142016.AA27643@bradbury.nrl.navy.mil> (jones@bradbury.nrl.navy.mil) Subject: Re: Contribution to the astroweb Reply-To: jackson@stsci.edu Cc: astroweb@NRAO.EDU Sender: astroweb-request@fits.CV.NRAO.EDU http://bradbury.nrl.navy.mil/general/ssd.html. was added to the AstroWeb database. From astroweb-request Mon Oct 17 09:43:04 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA03073; Mon, 17 Oct 94 09:43:04 EDT Return-Path: X-Sender: hmadorf@ns3.hq.eso.org Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 17 Oct 1994 14:44:52 +0100 To: astroweb@NRAO.EDU From: adorf@eso.org (Hans-Martin Adorf) Subject: new URL to ST-ECF's AstroWeb file Cc: bfrasmus@eso.org (Bo Rasmussen), Salim.Ansari@mail.esrin.esa.it (Salim Ansari) Sender: astroweb-request@fits.CV.NRAO.EDU Dear members of AstroWeb, please note that the location of the ST-ECF's astroweb file has changed. It's new URL is http://ecf.hq.eso.org/astroweb/yp_astro_resources.html (The old URL is still active simply pointing to the new file.) The astroweb file should now automatically be updated every day by fetching a file from NRAO. The new procedure was essentially put together by Don Wells, who deserves many thanks. Please change the URL, if you point to the ST-ECF's astroweb variant. Thanks. Hans-Martin From www_server Tue Oct 18 04:50:18 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA00560; Tue, 18 Oct 94 04:50:18 EDT Return-Path: Date: Tue, 18 Oct 94 04:50:10 EDT From: www_server@fits.CV.NRAO.EDU (httpd@fits.cv.nrao.edu) Message-Id: <9410180850.AA00551@fits.cv.nrao.edu> To: adorf@eso.org, astroweb@NRAO.EDU Subject: AstroWeb WAIS index Sender: astroweb-request@fits.CV.NRAO.EDU Message entered by: Hans-Martin Adorf @ st7.hq.eso.org [134.171.10.108] In the descriptive text a 'the' is missing. -hma From www_server Tue Oct 18 05:38:47 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA01942; Tue, 18 Oct 94 05:38:47 EDT Return-Path: Date: Tue, 18 Oct 94 05:38:39 EDT From: www_server@fits.CV.NRAO.EDU (httpd@fits.cv.nrao.edu) Message-Id: <9410180938.AA01933@fits.cv.nrao.edu> To: adorf@eso.org, astroweb@NRAO.EDU Subject: PSDD Sender: astroweb-request@fits.CV.NRAO.EDU Message entered by: Hans-Martin Adorf @ st7.hq.eso.org [134.171.10.108] the second entry has the correct database psdd From www_server Tue Oct 18 06:34:10 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA02175; Tue, 18 Oct 94 06:34:10 EDT Return-Path: Date: Tue, 18 Oct 94 06:33:57 EDT From: www_server@fits.CV.NRAO.EDU (httpd@fits.cv.nrao.edu) Message-Id: <9410181033.AA02166@fits.cv.nrao.edu> To: adorf@eso.org, astroweb@NRAO.EDU Subject: STSDAS help system Sender: astroweb-request@fits.CV.NRAO.EDU Message entered by: Hans-Martin Adorf @ st7.hq.eso.org [134.171.10.108] Anlaysis read Analysis From www_server Tue Oct 18 07:58:09 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA02287; Tue, 18 Oct 94 07:58:09 EDT Return-Path: Date: Tue, 18 Oct 94 07:58:00 EDT From: www_server@fits.CV.NRAO.EDU (httpd@fits.cv.nrao.edu) Message-Id: <9410181158.AA02278@fits.cv.nrao.edu> To: adorf@eso.org, astroweb@NRAO.EDU Subject: European Space Agency Sender: astroweb-request@fits.CV.NRAO.EDU Message entered by: H.-M. Adorf @ st7.hq.eso.org [134.171.10.108] The title of URL http://www.esrin.esa.it/ should be ESA/ESRIN. It is not the official hompage of ESA, but of ESA/ESRIN. -hma From astroweb-request Wed Oct 19 03:52:01 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA04038; Wed, 19 Oct 94 03:52:01 EDT Return-Path: X-Sender: hmadorf@ns3.hq.eso.org Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 19 Oct 1994 08:53:53 +0100 To: astroweb@NRAO.EDU From: adorf@eso.org (Hans-Martin Adorf) Subject: ESA homepage Sender: astroweb-request@fits.CV.NRAO.EDU Friends, I take back what I said about http://www.esrin.wsa.it/ not being the home page of ESA. I found an e-mail msg from Salim Ansari, stating that this is ESA's homepage. How official it is, I don't know. Hans-Martin From www_server Wed Oct 19 07:49:06 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA05698; Wed, 19 Oct 94 07:49:06 EDT Return-Path: Date: Wed, 19 Oct 94 07:48:58 EDT From: www_server@fits.CV.NRAO.EDU (httpd@fits.cv.nrao.edu) Message-Id: <9410191148.AA05687@fits.cv.nrao.edu> To: adorf@eso.org, astroweb@NRAO.EDU Subject: ional Solar Observatory / Sacramento Peak Sender: astroweb-request@fits.CV.NRAO.EDU Observatory Message entered by: Hans-Martin Adorf @ st7.hq.eso.org [134.171.10.108] correct URL is http://www.sunspot.noao.edu/ From astroweb-request Wed Oct 19 12:48:39 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA06392; Wed, 19 Oct 94 12:48:39 EDT Return-Path: X-Sender: hmadorf@ns3.hq.eso.org Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 19 Oct 1994 17:50:11 +0100 To: astroweb@NRAO.EDU From: dwells@fits.CV.NRAO.EDU (Don Wells) (by way of adorf@eso.org (Hans-Martin Adorf)) Subject: Re: Don, Sender: astroweb-request@fits.CV.NRAO.EDU I believe we need a category "catalog(ue)" for astronomical catalogues. I just ran across one and couldn't properly classify it. Also I suggest to have the category menu in the entry form alphabetically sorted. Hans-Martin From astroweb-request Wed Oct 19 12:49:24 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA06409; Wed, 19 Oct 94 12:49:24 EDT Return-Path: X-Sender: hmadorf@ns3.hq.eso.org Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 19 Oct 1994 17:51:03 +0100 To: astroweb@NRAO.EDU From: dwells@fits.CV.NRAO.EDU (Don Wells) (by way of adorf@eso.org (Hans-Martin Adorf)) Subject: new category Sender: astroweb-request@fits.CV.NRAO.EDU I believe we need a category "catalog(ue)" for astronomical catalogues. I just ran across one and couldn't properly classify it. Also I suggest to have the category menu in the entry form alphabetically sorted. Hans-Martin From dwells Wed Oct 19 14:17:32 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA06593; Wed, 19 Oct 94 14:17:32 EDT Return-Path: Date: Wed, 19 Oct 94 14:17:28 EDT From: dwells@fits.CV.NRAO.EDU (Don Wells) Message-Id: <9410191817.AA06584@fits.cv.nrao.edu> To: astroweb@NRAO.EDU Subject: Re: new category In-Reply-To: References: Sender: astroweb-request@fits.CV.NRAO.EDU Don Wells) (by way of adorf@eso.org (Hans-Martin Adorf) writes: > Also I suggest to have the category menu in the entry form alphabetically > sorted. DONE. -Don From astroweb-request Wed Oct 19 17:35:58 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA06971; Wed, 19 Oct 94 17:35:58 EDT Return-Path: Message-Id: <9410192137.AA10659@cdsxb6.u-strasbg.fr> To: astroweb@fits.CV.NRAO.EDU Cc: heck@cdsxb6.u-strasbg.fr Subject: E-mail recommendation Date: Wed, 19 Oct 94 22:37:29 +0100 From: Andre HECK Sender: astroweb-request@fits.CV.NRAO.EDU FYI, and although this had no direct relation with the use of the web, it has been recommended in Chicago that people try to rationalize their e-mailing practice, such as thinking it twice before sending out a message and trying to condense several small messages in only one while restricting themselves to only important matters. AH. ------------------------------------------------------------------------ From astroweb-request Thu Oct 20 03:50:34 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA07418; Thu, 20 Oct 94 03:50:34 EDT Return-Path: X-Sender: hmadorf@ns3.hq.eso.org Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 20 Oct 1994 08:52:27 +0100 To: astroweb@NRAO.EDU From: adorf@eso.org (Hans-Martin Adorf) Subject: AstroWeb bibliography Sender: astroweb-request@fits.CV.NRAO.EDU Dear friends, here is my collection of references so far: Jackson, R., Wells, D., Adorf, H.-M., Egret, D., Heck, A., Koekemoer, A., Murtagh, F.: 1994, "The AstroWeb Database", Bull. CDS 45, 21-25. Jackson, R., Wells, D., Adorf, H.-M., Egret, D., Heck, A., Koekemoer, A., Murtagh, F.: 1995, "AstroWeb - A database of links to astronomy resources - Announcement of a database", Astron. Astrophys. Suppl. Jackson, R.E., Adorf, H.-M., Egret, D., Heck, A., Koekemoer, A., Murtagh, F., Wells, D.: 1995, "AstroWeb - Internet resources for astronomers", in: Proc. Astronomical Data Analysis Software and Systems (ADASS) '94, Baltimore, MD, D. Shaw, H. Payne, and J. Hayes (eds.), Astronomical Society of the Pacific. Adorf, H.-M.: 1994, "AstroWeb - a database of astronomical Internet resources", ST-ECF Newsl. 22. Questions: 1. Are the above entries correct? Will the AAS paper appear still in 1994? 2. Are there entries missing? 3. Do we always publish in all our names, in which case the author list of the ST-ECF announcement needs to be modified Thanks Hans-Martin From astroweb-request Thu Oct 20 04:36:57 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA07458; Thu, 20 Oct 94 04:36:57 EDT Return-Path: X-Sender: hmadorf@ns3.hq.eso.org Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 20 Oct 1994 09:38:48 +0100 To: astroweb@NRAO.EDU From: adorf@eso.org (Hans-Martin Adorf) Subject: results of AstroWeb DB searches Sender: astroweb-request@fits.CV.NRAO.EDU Dear friends, I should like to suggest two modifications to the presentation of AstroWeb DB search results: 1. have the returned entries alphabetically sorted according to their headline 2. add the score as an indication of relevance to the query What do you think? Hans-Martin From astroweb-request Thu Oct 20 04:40:06 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA07475; Thu, 20 Oct 94 04:40:06 EDT Return-Path: X-Sender: hmadorf@ns3.hq.eso.org Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 20 Oct 1994 09:41:57 +0100 To: jackson@stsci.edu (Bob Jackson) From: adorf@eso.org (Hans-Martin Adorf) Subject: dead entries Cc: astroweb@NRAO.EDU Sender: astroweb-request@fits.CV.NRAO.EDU Bob, despite your welcome validation there are dead entries in our DB. Some of the descriptive texts have embedded URLs. E.g.
University of California, San Diego - Center for Astrophysics and Space Sciences ( UCSD - CASS )
The Center for Astrophysics and Space Sciences at UC San Diego is the birthplace of the multi-channel Digicon photon detectors. Four of these are used on two instruments, the UCSD Faint Object Spectrometer (FOS), and the Goddard High Resolution Spectrometer (GHRS), on the Hubble Space Telescope (HST). Available at this site is information relating to the activities, facilities, and personnel at CASS. The Faint Object Spectrograph group, its history, and related areas of research are described in detail.
All the cassfos01 URLs are dead as far as I can tell. I suppose that you are only checking the URLs of the headlines. Hans-Martin From astroweb-request Thu Oct 20 07:20:47 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA09043; Thu, 20 Oct 94 07:20:47 EDT Return-Path: Message-Id: <9410201122.AA19197@cdsxb6.u-strasbg.fr> To: astroweb@fits.CV.NRAO.EDU Cc: heck@cdsxb6.u-strasbg.fr Subject: Authorship Date: Thu, 20 Oct 94 12:22:37 +0100 From: Andre HECK Sender: astroweb-request@fits.CV.NRAO.EDU Yes, I believe all the names should lbe listed, especially when the paper is of general substance, which is the case for the paper in the ST-ECF Newsletter. AH. ------------------------------------------------------------------------ (Prof.) Andre HECK -+- * Phone (direct) +33-88.35.82.22 Observatoire Astronomique * Phone (Secretary) +33-88.35.82.18 11, rue de l'Universite -+- * Fax (direct/private) +33-88.49.12.55 F-67000 Strasbourg * -+- Fax (Secretary) +33-88.25.01.60 France -+- * * Numeris (private) +33-88.48.20.60 ------------------------------------------------------------------------ URL: http://cdsweb.u-strasbg.fr/~heck ------------------------------------------------------------------------ From astroweb-request Thu Oct 20 08:07:14 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA09134; Thu, 20 Oct 94 08:07:14 EDT Return-Path: Message-Id: <9410201206.AA06481@cv3.cv.nrao.edu> From: Boris Gaensicke Subject: New WWW-Server To: astroweb@NRAO.EDU Date: Thu, 20 Oct 1994 13:06:53 +0100 (MET) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 548 Sender: astroweb-request@fits.CV.NRAO.EDU Gentlemen, we recently started our own WWW server, providing information about our department (research activities, preprints, the history of the institute...). Could you please insert a link to our homepage at a appropriate place in the astronomical WWW resource list? Thank's a lot, Boris Gaensicke URL: http://www.uni-sw.gwdg.de/ Mail: wwwadmin@uni-sw.gwdg.de Address of the observatory: Universitaets-Sternwarte Goettingen Geismarlandstr. 11 37083 Goettingen Germany Fax: 49-(0)551-395043 Phone: 49-(0)551-395053 / 395042 From astroweb-request Thu Oct 20 09:13:17 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA09223; Thu, 20 Oct 94 09:13:17 EDT Return-Path: X-Sender: hmadorf@ns3.hq.eso.org Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 20 Oct 1994 14:14:57 +0100 To: Boris Gaensicke From: adorf@eso.org (Hans-Martin Adorf) Subject: Re: New WWW-Server Cc: astroweb@NRAO.EDU Sender: astroweb-request@fits.CV.NRAO.EDU >Gentlemen, > >we recently started our own WWW server, providing information about >our department (research activities, preprints, the history of the >institute...). Could you please insert a link to our homepage at a >appropriate place in the astronomical WWW resource list? > >Thank's a lot, > > Boris Gaensicke > > >URL: http://www.uni-sw.gwdg.de/ >Mail: wwwadmin@uni-sw.gwdg.de > >Address of the observatory: >Universitaets-Sternwarte Goettingen >Geismarlandstr. 11 >37083 Goettingen >Germany > >Fax: 49-(0)551-395043 >Phone: 49-(0)551-395053 / 395042 Done. Hans-Martin Adorf ------------------------------------------------------------------------------ Hans-Martin Adorf Tel: +49-89-32006-261 ST-ECF/ESO Fax: +49-89-32006-480 Karl-Schwarzschild-Str. 2 D-85748 Garching b. Muenchen E-mail: adorf@eso.org F.R. Germany WWW: http://ecf.hq.eso.org/staff/hmadorf.html ---------------------------------------------------------------------------- -- From astroweb-request Thu Oct 20 11:49:56 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA09561; Thu, 20 Oct 94 11:49:56 EDT Return-Path: X-Sender: hmadorf@ns3.hq.eso.org Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Thu, 20 Oct 1994 16:51:39 +0100 To: astroweb@NRAO.EDU From: adorf@eso.org (Hans-Martin Adorf) Subject: draft of AstroWeb fr ST-ECF Newsletter Sender: astroweb-request@fits.CV.NRAO.EDU Dear friends, here is the draft of my AstroWeb article for the next issue of the ST-ECF Newsletter. Please let me have your comments asap. Thanks. Hans-Martin --------------------------------------------- AstroWeb - Internet resources for astronomers Hans-Martin Adorf1, Daniel Egret2, Andr=E9 Heck2, Robert Jackson3, Anton Koekemoer4, Fionn Murtagh1, Don Wells5 1ST-ECF, 2CDS, 3STScI, 4MSSSO, 5NRAO Abstract: The AstroWeb database is the most complete collection of of astronomical Internet resources worldwide. It comprises well above 1000 pointers to observatories and societies, telescope schedules, meteorological information, conferences, publications, data archives, software and other information services. The AstroWeb page has become the most wanted item in WISE, the ST-ECF's WWW-based information system. The AstroWeb database The amount of astronomical information easily accessible on the Internet has grown explosively over the past year. Particularly the advent of the World Wide We= b (WWW, Adorf 1994) has facilitated access and transfer of textual and image data. It has been recognized for quite some time that the wealth of distributed information would certainly benefit from some organisational structure. Early in 1994 several people had individually started to collect interesting astronomical Internet resources, only to quickly realize that the only way to proceed was to merge the different, partially overlapping collections into a comprehesive database - the birth of the AstroWeb consortium (Jackson et al. 1994, 1995a, 1995b). Its currently seven members (identical to the authors) are located at five different institutions in Europe, the United States, and Australia. Their primary product, the AstroWeb database, comprises records for FTP, Gopher, Telnet, USENET Newsgroups, WAIS, and WWW resources, uniquely specifi= ed by their respective Uniform Resource Locators (URLs). Many resources are already augmented by a paragraph of descriptive text; some descriptions already cont= ain links to other entries. If known, the e-mail address of the resources's maintainer is stored in the record. As an added value, each record is classified by a consortium member according to one or more of ~25 categories, such as observatory, instrument, abstract, software or people. The AstroWeb collection complements, and to some extent supersedes the recen= t annotated compilation of Internet resources by Andernach, Hanisch & Murtagh (1994). Being of general interest and being the most complete collection available, the AstroWeb database pages have become the most popular items in WISE, the = ST- ECF's WWW-based information system, yielding about 70 downloads per day. Structure and organisation The current AstroWeb set-up consists of a master database maintained at the STScI. In a highly dynamic enviroment such as the WWW, it is important to regularly check the validity of the database entries. Three times a day a demon probes the primary URLs of all records (except Telnet URLs), and removes "dead" or "unreliable" entries from the database. =46rom the master database different renderings are automatically derived on= a daily basis. For instance, the ST-ECF presentation of the database (http://ecf.hq.eso.org/astroweb/yp_astro_resources.html) is terse, permitting quick transfer and reference (suitable for European networks with relatively low bandwidths). The STScI presentation (http://www.stsci.edu/net= - resources.html), on the other hand, includes the descriptive text, and is mo= re suitable for initial browsing of the database content. Categories and resource owners are usually not displayed, but hidden in HTML comments; these can be viewed in the HTML source, if necessary. At a size of well above 1000 entries it is mandatory that the AstroWeb datab= ase is searchable. To this end a WAIS index (see Adorf 1994b) is maintained at t= he STScI, which indexes the titles, descriptions and categories. HST related resources in AstroWeb As an example we briefly inspect the current content of the AstroWeb database with respect to HST, ST-ECF and STScI. Searching the database for 'HST or Hubble" retrieves more than 25 records, including pointers to STScI, ST-ECF, the Space Telescope electronic informat= ion system (STEIS), remote proposal submission (RPS), STSDAS, PSF modeling software, all three HST archives, HST public relation images, a newsgroup, t= he STScI's preprint database, and somewhat surprisingly a gravitational lensing conference. Similarly, searching the database for'stecf or ecf' finds more than 30 point= ers to ST-ECF related information, including WISE, the ST-ECF Newsletter, the HS= T archive, and all ST-ECF staff. =46inally, searching for 'STScI' reveals 35 records including pointers to ST= ScI received preprints, STScI authored preprints (searchable abstracts), PASP abstracts, and IAU circulars. Submission of new records The AstroWeb consortium welcomes new contributions. To this end it is providing a WWW entry form for entering new records (http://fits.cv.nrao.edu/www/astroweb/aref.html). Similarly there are entry forms for requesting modifications to existing records, for entering a perso= nal anchor, and for reviewing recently submitted records. Each entry or modification request is reviewed by a consortium member and, upon acceptance, added manually to the database in order to assure continued quality. =46uture developments Several future developments are conceivable, apart from continuing to collect more Internet resources. For instance, it would be very helpful, if the AstroWeb database were internally fully crossreferenced. Also some community involvement is currently being considered in order to complete and improve the resource descriptions. In any case the AstroWeb consortium welcomes suggestions by al= l database users (e-mail to astroweb@nrao.edu). References Adorf, H.-M.: 1994a, "Electronic access to HST information II - the World Wide Web", ST-ECF Newsl. 21, 31-34. Adorf, H.-M.: 1994b, "Electronic access to HST information III - WAIS", ST-ECF Newsl. 22. Andernach, H., Hanisch, R.J., Murtagh, F.D.: 1994, "Network resources for astronomers", Publ. Astron. Soc. Pacific, (in press). Jackson, R., Wells, D., Adorf, H.-M., Egret, D., Heck, A., Koekemoer, A., Murtagh, F.: 1994, "The AstroWeb Database", Bull. CDS 45, 21-25. Jackson, R., Wells, D., Adorf, H.-M., Egret, D., Heck, A., Koekemoer, A., Murtagh, F.: 1995a, "AstroWeb - A database of links to astronomy resources - Announcement= of a database", Astron. Astrophys. Suppl. (submitted). Jackson, R.E., Adorf, H.-M., Egret, D., Heck, A., Koekemoer, A., Murtagh, =46., Wells, D.: 1995b, "AstroWeb - Internet resources for astronomers", in: Proc. Astronomic= al Data Analysis Software and Systems (ADASS) '94, Baltimore, MD, D. Shaw, H. Payne, and J. Hayes (eds.), Astronomical Society of the Pacific, (in press). =46igure captions =46ig. 1: The ST-ECF's top-level WWW page (http://ecf.hq.eso.org/astroweb/yp_astro_resources.html) of the AstroWeb database, viewed with EINet's MacWeb browser on the Apple Macintosh. From astroweb-request Fri Oct 21 05:32:38 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA12379; Fri, 21 Oct 94 05:32:38 EDT Return-Path: X-Sender: hmadorf@ns3.hq.eso.org Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Fri, 21 Oct 1994 10:34:26 +0100 To: astroweb@NRAO.EDU From: adorf@eso.org (Hans-Martin Adorf) Subject: recent modifications of the AstroWeb database Sender: astroweb-request@fits.CV.NRAO.EDU Dear friends, for the first time I have modified the AstroWeb database. I entered my backlog of 40 or so records, mainly WAIS sources. Here are my experiences: In general, I found the AstroWeb update mechanism to be ok, but I see room for improvements. I chose to edit the whole database which, however, comes not in the agreed HTML format, but in abbreviated Tcl. My 40 or so new records which I had entered, following Don Wells' suggestion, using his entry form, however were in the agreed-upon HTML format. How to merge these two files? I decided not to cut and paste (again), in fear of introducing more errors. I conversed with Bob Jackson, who finally converted for me the new HTML records into the abbreviated Tcl format. I am sure he used a Tcl tool, and it would be nice to have it generally available. I merged the two files in Emacs - and had to submit it about a dozen times, since Bob's checker (good as it is) reports only one error at a time and then quits. I suggest that the checker goes as far as possible and produces an error report with multiple errors, if that is not too much effort for Bob. The database increased in size by 15 % (from 308 kByte by 48 kByte to 354 kByte). I see two important improvements to be made to the database: 1. check that the descriptive text of a resource always mentions the institute it comes from; we may ask the resource maintainers to do the necessary modifications. 2. fully crossreference the AstroWeb database (i.e. automatically insert anchors into the descriptions); I presume that this is not too difficult, given that Bob has all the basic Tcl parsing tools at hand. I offer to write the specifications and to cooperate, if that is an agreed-upon action item within the consortium Cheers Hans-Martin From astroweb-request Fri Oct 21 07:35:53 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA12651; Fri, 21 Oct 94 07:35:53 EDT Return-Path: Date: Fri, 21 Oct 94 07:35:47 EDT From: Bob Jackson Message-Id: <9410211135.AA00897@MARIAN.STSCI.EDU> To: adorf@eso.org Subject: comments on draft Reply-To: jackson@stsci.edu Cc: astroweb@NRAO.EDU Sender: astroweb-request@fits.CV.NRAO.EDU Look for >>>'s Bob --------------------------------------------- AstroWeb - Internet resources for astronomers Hans-Martin Adorf1, Daniel Egret2, Andr=E9 Heck2, Robert Jackson3, Anton Koekemoer4, Fionn Murtagh1, Don Wells5 1ST-ECF, 2CDS, 3STScI, 4MSSSO, 5NRAO >>> Please list me as: "CSC/STScI" >>> Abstract: The AstroWeb database is the most complete collection of of Abstract: The AstroWeb database is the most complete collection of >>> >>> astronomical Internet resources worldwide. It comprises well above astronomical Internet resources worldwide. It comprises well over >>> 1000 pointers to observatories and societies, telescope schedules, meteorological information, conferences, publications, data archives, software and other information services. The AstroWeb page has become >>> the most wanted item in WISE, the ST-ECF's WWW-based information the most accessed item in WISE, the ST-ECF's WWW-based information >>> system. The AstroWeb database The amount of astronomical information easily accessible on the Internet has grown >>> explosively over the past year. Particularly the advent of the World Wide We= b (WWW, Adorf 1994) has facilitated access and transfer of textual and image data. It explosively over the past year, largely driven by the World Wide We= b (WWW, Adorf 1994) which has greatly facilitated access to and transfer of textual and image data. It >>> has been recognized for quite some time that the wealth of distributed information >>> would certainly benefit from some organisational structure. would benefit from some organisational structure. >>> Early in 1994 several people had individually started to collect interesting astronomical Internet resources, only to quickly realize that the only way to proceed was to merge the different, partially overlapping collections into a >>> single >>> comprehesive database - the birth of the AstroWeb consortium (Jackson et al. 1994, 1995a, 1995b). Its currently seven members (identical to the authors) are located at five different institutions in Europe, the United States, and Australia. Their primary product, the AstroWeb database, comprises records for FTP, Gopher, Telnet, USENET Newsgroups, WAIS, and WWW resources, uniquely specifi= ed by their respective Uniform Resource Locators (URLs). Many resources are >>> already >>> >>> augmented by a paragraph of descriptive text; some descriptions already cont= augmented by a paragraph of descriptive text and some descriptions cont= >>> ain links to other entries. If known, the e-mail address of the resources's maintainer is stored in the record. As an added value, each record is classified by a consortium member according to one or more of ~25 categories, such as observatory, instrument, abstract, software or people. The AstroWeb collection complements, and to some extent supersedes the recen= t annotated compilation of Internet resources by Andernach, Hanisch & Murtagh (1994). Being of general interest and being the most complete collection available, the AstroWeb database pages have become the most popular items in WISE, the = ST- ECF's WWW-based information system, yielding about 70 downloads per day. Structure and organisation The current AstroWeb set-up consists of a master database maintained at the STScI. In a highly dynamic enviroment such as the WWW, it is important to regularly check the validity of the database entries. Three times a day a demon probes the primary >>> URLs of all records (except Telnet URLs), and removes "dead" or "unreliable" entries from the database. URLs of all records (except Telnet URLs), and labels "dead" or "unreliable" entries in the database. >>> =46rom the master database different renderings are automatically derived on= a daily basis. For instance, the ST-ECF presentation of the database (http://ecf.hq.eso.org/astroweb/yp_astro_resources.html) is terse, permitting quick transfer and reference (suitable for European networks with relatively low bandwidths). The STScI presentation (http://www.stsci.edu/net= - resources.html), on the other hand, includes the descriptive text, and is mo= re suitable for initial browsing of the database content. Categories and resource owners >>> are usually not displayed, but hidden in HTML comments; these can be viewed are usually not displayed, but hidden in HTML comments, which can be viewed >>> in the HTML source, if necessary. At a size of well above 1000 entries it is mandatory that the AstroWeb datab= ase is searchable. To this end a WAIS index (see Adorf 1994b) is maintained at t= he >>> STScI, which indexes the titles, descriptions and categories. STScI, which indexes all the information in the database, including the categories, URL's, and owner email addresses. >>> HST related resources in AstroWeb As an example we briefly inspect the current content of the AstroWeb database with respect to HST, ST-ECF and STScI. Searching the database for 'HST or Hubble" retrieves more than 25 records, including pointers to STScI, ST-ECF, the Space Telescope electronic informat= ion system (STEIS), remote proposal submission (RPS), STSDAS, PSF modeling software, all three HST archives, HST public relation images, a newsgroup, t= he STScI's preprint database, and somewhat surprisingly a gravitational lensing conference. Similarly, searching the database for'stecf or ecf' finds more than 30 point= ers to ST-ECF related information, including WISE, the ST-ECF Newsletter, the HS= T archive, and all ST-ECF staff. =46inally, searching for 'STScI' reveals 35 records including pointers to ST= ScI received preprints, STScI authored preprints (searchable abstracts), PASP abstracts, and IAU circulars. Submission of new records The AstroWeb consortium welcomes new contributions. To this end it is providing a WWW entry form for entering new records (http://fits.cv.nrao.edu/www/astroweb/aref.html). Similarly there are entry forms for requesting modifications to existing records, for entering a perso= nal anchor, and for reviewing recently submitted records. Each entry or modification request is reviewed by a consortium member and, upon acceptance, added manually to the database in order to assure continued quality. =46uture developments Several future developments are conceivable, apart from continuing to collect more Internet resources. For instance, it would be very helpful, if the AstroWeb database were internally fully crossreferenced. Also some community involvement is currently being considered in order to complete and improve the resource descriptions. In any case the AstroWeb consortium welcomes suggestions by al= l database users (e-mail to astroweb@nrao.edu). References Adorf, H.-M.: 1994a, "Electronic access to HST information II - the World Wide Web", ST-ECF Newsl. 21, 31-34. Adorf, H.-M.: 1994b, "Electronic access to HST information III - WAIS", ST-ECF Newsl. 22. Andernach, H., Hanisch, R.J., Murtagh, F.D.: 1994, "Network resources for astronomers", Publ. Astron. Soc. Pacific, (in press). Jackson, R., Wells, D., Adorf, H.-M., Egret, D., Heck, A., Koekemoer, A., Murtagh, F.: 1994, "The AstroWeb Database", Bull. CDS 45, 21-25. Jackson, R., Wells, D., Adorf, H.-M., Egret, D., Heck, A., Koekemoer, A., Murtagh, F.: 1995a, "AstroWeb - A database of links to astronomy resources - Announcement= of a database", Astron. Astrophys. Suppl. (submitted). Jackson, R.E., Adorf, H.-M., Egret, D., Heck, A., Koekemoer, A., Murtagh, =46., Wells, D.: 1995b, "AstroWeb - Internet resources for astronomers", in: Proc. Astronomic= al Data Analysis Software and Systems (ADASS) '94, Baltimore, MD, D. Shaw, H. Payne, and J. Hayes (eds.), Astronomical Society of the Pacific, (in press). =46igure captions =46ig. 1: The ST-ECF's top-level WWW page (http://ecf.hq.eso.org/astroweb/yp_astro_resources.html) of the AstroWeb database, viewed with EINet's MacWeb browser on the Apple Macintosh. From astroweb-request Fri Oct 21 14:41:22 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA13560; Fri, 21 Oct 94 14:41:22 EDT Return-Path: Date: Fri, 21 Oct 94 14:40:52 EDT From: Bob Jackson Message-Id: <9410211840.AA02554@MARIAN.STSCI.EDU> To: astroweb@NRAO.EDU Subject: Draft of ADASS paper - Comments/Suggestions/... ? Reply-To: jackson@stsci.edu Sender: astroweb-request@fits.CV.NRAO.EDU \documentstyle[11pt,paspconf]{article} \begin{document} \title{ Astroweb - Internet Resources for Astronomers } \author{ Robert E. Jackson } \affil{ Computer Sciences Corporation, Space Telescope Science Institute} \author{ Hans-Martin Adorf } \affil{ Space Telescope - European Coordinating Facility } \author{ Daniel Egret } \affil{ Strasbourg Astronomical Data Center } \author{ Andre Heck } \affil{Strasbourg Astronomical Observatory} \author{ Anton Koekemoer } \affil{ Mount Stromlo and Siding Spring Observatories } \author{ Fionn Murtagh } \affil{ Space Telescope - European Coordinating Facility } \author{ Don Wells } \affil{ National Radio Astronomy Observatory } \begin{abstract} AstroWeb is a WWW interface to a collection of Internet accessible resources aimed at the astronomical community. The collection currently contains more than 1000 World Wide Web, Gopher, Wide Area Information System, Telnet, and Anonymous FTP resources and it is still growing. AstroWeb provides the additional value-added services: Categorization of each resource; Descriptive paragraphs for some resources; Searchable index of all resource information; 3x daily search for 'dead' or 'unreliable' resources; \end{abstract} \keywords{Brevity,models} \section{What Is AstroWeb?} The goal of AstroWeb is to be the most complete, up to date, and useful listing of Internet accessible astronomical resources available anywhere. AstroWeb currently contains 1123 World Wide Web, Gopher, WAIS, Telnet, FTP, and Usenet News resource, and a total of 1235 Universal Resource Listings (URL's). As a value-added service, AstroWeb also provides: \begin{list}{}{} \item One or more standardized Categories for each resource \item Descriptive text for many resources \item Searchable index of all resource information \item Thrice daily search for ``dead'' or ``unreliable'' resources \item The most complete Astronomical resource listing \end{list} These value-added services set AstroWeb apart from other, more static lists of Internet resources. \section{Where Is AstroWeb?} AstroWeb is available at: \begin{list}{}{} \item \htmllink{STScI}{http://www.stsci.edu/net-resources.html} \item \htmllink{NRAO}{http://fits.cv.nrao.edu/www/astronomy.html} \item \htmllink{CDS}{http://cdsweb.u-strasbg.fr/astroweb.html} \item \htmllink{ST-ECF}{http://ecf.hq.eso.org/astro-resources.html} \item \htmllink{MSSSO}{http://meteor.anu.edu.au/astronomy.html} \end{list} Each version is based on the same resource database, but each site has a different structure or format. For example, ST-ECF only displays the title and acronym for each resource, while STScI displays the descriptive text as well. Each site updates and formats their version daily from the central listing at STScI. Some sites, in addition, will have ``mirror'' copies of the other sites versions. \section{When Was AstroWeb?} On January 24, 1994, Jackson sent EMail to Wells and Adorf suggesting that they collaborate instead of maintaining separate resource listings. A standard interface file format was defined and some software tools were written. Additional members joined the \htmllink{AstroWeb Consortium}{http://fits.cv.nrao.edu/www/astroweb.html} and on April 6, 1994, AstroWeb was announced to the public via \htmllink{NCSA Mosaic What's New}{http://www.ncsa.uiuc.edu/SDG/Software/Mosaic/Docs/whats-new.html} and several Usenet newsgroups. \section{Why Was AstroWeb Created?} Jackson, Wells, and Adorf noticed that they and others had created largely overlapping lists of Astronomical resources. New resources were being discovered every day and it seemed more productive to coordinate efforts and use a common master resource listing. From the early size and growth rate of the listing, it was also clear that standardized categories and search tools would be needed to allow the user to quickly find the desired resource. The volatile nature of URL's required that resources be frequently checked for ``aliveness'' in order to prevent the listing from accumulating ``pointers to nowhere''. Most importantly, it was a fun and useful thing to do. \section{How To Add Or Change AstroWeb?} To preserve the homogeneity and integrity of AstroWeb, the central listing at STScI can be edited only by AstroWeb Consortium members. However, we welcome comments, suggestions, new resources, corrections to existing resources, etc. from everyone. Consortium members can be reached via EMail at: \begin{list}{}{} \item \htmllink{astroweb@nrao.edu}{mailto://astroweb@nrao.edu} \end{list} \noindent There are also HTML forms available to: \begin{list}{}{} \item \htmllink{Add a Resource}{http://fits.cv.nrao.edu/www/astroweb/aref.html} \item \htmllink{Add a Personal Resource}{http://fits.cv.nrao.edu/www/astroweb/paref.html} \item \htmllink{Submit a Correction}{http://fits.cv.nrao.edu/www/astroweb/adcrf.html} \end{list} \begin{references} \reference Jackson, R., Wells, D., Adorf, H.-M., Egret, D., Heck, A., Koekemoer, A., Murtagh, F. 1994, "The AstroWeb Database", Bull. CDS 45, 21-25. \reference Jackson, R., Wells, D., Adorf, H.-M., Egret, D., Heck, A., Koekemoer, A., Murtagh, F. 1995, "AstroWeb - A database of links to astronomy resources - Announcement of a database", Astron. Astrophys. Suppl (in press) \reference Jackson, R.E., Adorf, H.-M., Egret, D., Heck, A., Koekemoer, A., Murtagh, F., Wells, D. 1995, "AstroWeb - Internet resources for astronomers", in: Proc. Astronomical Data Analysis Software and Systems (ADASS) '94, Baltimore, MD, D. Shaw, H. Payne, and J. Hayes (eds.), Astronomical Society of the Pacific \reference Adorf, H.-M. 1994, "AstroWeb - a database of astronomical Internet resources", ST-ECF Newsl. 22 \end{references} \end{document} From astroweb-request Sun Oct 23 03:43:47 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA16461; Sun, 23 Oct 94 03:43:47 EDT Return-Path: Date: Sun, 23 Oct 94 17:10:27 EST From: anton@mso.anu.edu.au (anton koekemoer) Message-Id: <9410230710.AA08859@merlin.anu.edu.au> To: astroweb@fits.CV.NRAO.EDU Subject: Re: recent modifications of the AstroWeb database Sender: astroweb-request@fits.CV.NRAO.EDU Dear Friends, Firstly, it's great to see Hans-Martin's ST-ECF version also now up-to-date; also, thanks very much Hans-Martin for sharing all the new resources you found (and thanks to those who helped him out). That was a truly monumental effort; the total number of entries increased by about 70 in the space of one day! I would suggest that the "ADD New Resource" option in Bob's astroweb Entry form is probably the preferred way for any of us to directly enter any new resources we find (while Don's entry form should be regarded as a buffer for additions by the general community; it is up to us to transfer those to the database by hand, also making modifications to them if necessary). However, while Bob's form works perfectly well for single entries, I would tend to agree with Hans-Martin that if one wants to add multiple entries there is probably a little room for improvement. Certainly my current preferred mode of operating is to accumulate new URLs and corrections over the space of a week or two, and when I have time I use "Edit Entire Database" and add them all at once. But this does involve hacking the {}'s, &'s etc, which is really only of therapeutic value. After having allowed my mind to digest this matter over the last few months (ie every time I add new resources) here are some suggestions supplementary to those of Hans-Martin's, if they do not involve too much effort for Bob to implement: 1. It would be useful to be able to enter an indefinite number of newly found resources using the "ADD" form, creating a single intermediate file containing all the new resources, and having the option of only updating the database itself when all entries have been added. The format of this intermediate file should probably be either the tcl format we use when editing the entire database, or else the original html format (or even allow this to be specified?- I suspect that we may have different preferences anyway. If in html than it could be internally translated to tcl when the database is updated). It would also be good to be able to edit this file at any stage (even if all the new resources have not yet been added) in order to fix any mistakes. Also, when this intermediate file is finally added to the database, I'd support the suggestion of a "log-file" of errors, and the ability to subsequently re-edit the file and re-submit it after fixing the errors. 2. This would also solve the problem of translating entries from Don's inp_incoming.html file into the tcl database format. One could use Bob's "ADD" form to edit the empty intermediate file immediately, specifying html format, and just paste the entries from inp_incoming.html into this file. Then update the database when all entries have been pasted in (and optionally fixed). 3. Allow one to specify the comment describing the changes made, in the same way as is currently done for "Edit Entire Database". Also, a suggestion for the "MODIFY Existing Resource" option - have it work much the same as "DELETE Existing Resource", except that it says "Modify>" next to each URL instead of "Delete>". Clicking on "Modify" then brings up a little editing window which lets you modify that particular resource. One way of updating the database might then be to first create a new database with that entry removed, and then use a function similar to the "Add New Resource" option to add the modified version (of course all this should be invisible to whoever has just clicked the "Update" button). And again, it may be useful to allow a number of modifications to be made, storing the deleted/modified resources in temporary buffer files, before doing the database update. I suspect that if the above options are implemented then I'd rarely need to use the "Edit Entire Database" option again. cheers, - anton. From astroweb-request Mon Oct 24 09:10:22 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA02257; Mon, 24 Oct 94 09:10:22 EDT Return-Path: Date: 19 Oct 1994 02:51:52 GMT From: neilb@evian.khoros.unm.edu (Neil Bowers) (by way of adorf@eso.org (Hans-Martin Adorf)) To: astroweb@NRAO.EDU Subject: weblint Organization: Khoral Research, Inc. Path: eso!Germany.EU.net!EU.net!howland.reston.ans.net!gatech!newsxfer.itd.umich.edu!jobone!lynx.unm.edu!evian.khoros.unm.edu!neilb Newsgroups: comp.infosystems.www.providers Lines: 34 Message-Id: <3821k8$71q@lynx.unm.edu> Nntp-Posting-Host: evian.khoros.unm.edu X-Newsreader: TIN [version 1.2 PL2] Sender: astroweb-request@fits.CV.NRAO.EDU Weblint is a perl script which checks html pages for the World-Wide Web. Files to be checked are passed on the command-line: % weblint -i *.html Warnings are generated a la lint -- (line #): . E.g.: home.html(9): unmatched (seems to match

on line 8) The following checks are currently performed: * basic structure * expects to see a TITLE in the HEAD element * do IMG elements have ALT text? * mis-matched tags (e.g.,

...

) and unclosed elements. * catches elements which should only appear once * flags obsolete tags * whines if you use `here' as anchor text :-) * checks for expected arguments (catches ... ) * (optional) are tags in upper-case (if you like that sort of thing). There is no man page yet, but the -U switch gives a short usage statement, and -T displays the current ToDo list (additions to which are welcome :-). Weblint is available via anonymous ftp from ftp.khoros.unm.edu, in /pub/perl/www/weblint-1.000.tar.gz I hope you find this useful. Comments, suggestions and bug reports are welcome, see my email address or home page, given below. Neil Bowers Khoral Research, Inc. http://www.khoros.unm.edu/staff/neilb From astroweb-request Mon Oct 24 09:12:35 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA02274; Mon, 24 Oct 94 09:12:35 EDT Resent-Date: Wed, 19 Oct 1994 09:53:17 GMT Resent-From: astroweb-request Resent-Message-Id: <9410241312.AA02274@fits.cv.nrao.edu> Return-Path: Date: Wed, 19 Oct 1994 09:53:17 GMT From: avishaiy@mcil.comm.mot.com (Avishai Yacobi) (by way of adorf@eso.org (Hans-Martin Adorf)) To: astroweb@NRAO.EDU Reply-To: avishaiy@mcil.comm.mot.com Subject: HTML tools Organization: Motorola Communications Israel, Ltd., Tel Aviv Newsgroups: comp.infosystems.www.providers Path: eso!Germany.EU.net!wizard.pn.com!sundog.tiac.net!europa.eng.gtefsd.com!howland.reston.ans.net!pipex!uunet!mdisea!mothost!lmpsbbs!news Message-Id: <1994Oct19.095317.11163@lmpsbbs.comm.mot.com> References: Nntp-Posting-Host: 145.9.18.102 Lines: 146 Resent-Sender: news@lmpsbbs.comm.mot.com (Net News) Sender: astroweb-request@fits.CV.NRAO.EDU "ian c rogers" writes: >I'm looking to do keyword searches on information in a small portion of >my server. There are many files in this section, in many directories, >but all beneath a single directory. >Are there packages available which solve just this function? I wrote a cgi-bin script that recursively searches an html tree and build an html page with the hits where each hit is a URL to the matched data. You will have to modify the $WWWhome to the root of your server portion and the $title to something you like. Here is an example of using this script: Click on Search MCIL WWW pages to invoke a regular expression search on all our local documents.

---------------------------------------------- Avishai Yacobi, Motorola Communications Israel Phone: (972-3)-565-9549 Fax: (972-3)-565-9507 email: avishaiy@mcil.comm.mot.com or cay002@email.mot.com or yacoby@bimacs.cs.biu.ac.IP ---- 8< ------- cut here ------------------- #!/tools/pd/bin/perl # Name: htmlgrep.pl # Author: Avishai Yacoby # Search the entire local WWW tree for regular expression. # return indexed list where each hit is a URL for the matched data. # The grep code was enhanced from Piet van Oostrum's rgrep # The simple cgi interface was taken from ??? whois.pl $WWWhome = "/disk1/ftp/pub/www"; $title = "Search MCIL WWW pages"; $debug = 0; $regexp = ""; sub send_index { print "Content-type: text/html\n\n"; print "\n", $title, "\n\n"; print "\n

", $title, "

\n"; print "Type a regular expression for search:

"; print ""; print "\n"; } sub grep { do { &'send_index; #' return; } unless defined @ARGV; $regexp = $ARGV[$[]; print "Content-type: text/html\n\n"; print "\n", $title, "\n\n"; print "\n

", $title, "

\n"; print "Search pattern: \"$regexp\".

"; print "To view the full text, click on the appropriate match.

"; &do_grep($WWWhome); print "\n"; } sub do_grep { local ($file) = @_; local (*F, $ln, $f, $g, @dirfiles); if (-f $file) { if (open (F, $file)) { if ( $file =~ /.*\.(gz|Z)$/ ) { close(F); open (F, "zcat < $file|"); } print "Reading $file\n" if $debug; &grep_file ($file); } else { print stderr "Cannot open $file\n"; } } elsif (-d $file) { print "Entering $file\n" if $debug; if (opendir (F, $file)) { @dirfiles = readdir (F); closedir (F); for $f (@dirfiles) { next if ($f eq '.' || $f eq '..'); $g = "$file/$f"; next if (-l $g); if (-f $g && $g =~ /^.*\.html(\.(gz|Z))?$/ || -d _) { &do_grep ($g); } } } else { print stderr "Can't open $file\n"; } } } sub grep_file { local ($file) = @_; $file=substr($file, length($WWWhome)); local ($name, $title, $found) = ("", "",0); while () { $ln++; # unless (defined $title) { if (/(.*)<\/title>/i) { $title = $1; } # } if (/<\s*a\s+name\s*=\s*"([^"]+)"\s*>/i) { #" $name = "#" . $1; print $name if $debug; } if (/$regexp/oi) { unless ($found) { $found =1; printf("\n<p><U>In document \"%s\" (%s):</U><p>", $title, $file); } chop if substr($_, -1, 1) ne "\n"; s/<[^<>]*>//g; s/$regexp/<b>$&<\/b>/oig; print "<li>"; print "line $ln: <a href=\"$file$name\">$_</a>\n"; } } } eval '&grep'; From astroweb-request Mon Oct 24 09:47:56 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA02325; Mon, 24 Oct 94 09:47:56 EDT Return-Path: <adorf@eso.org> Date: 18 Oct 1994 19:01:03 -0500 From: churchyh@doc.cc.utexas.edu (Henry Churchyard) (by way of adorf@eso.org (Hans-Martin Adorf)) To: astroweb@NRAO.EDU Subject: HTML checker in AWK (source) Organization: The University of Texas at Austin; Austin, Texas Xref: eso comp.infosystems.www.providers:6417 comp.infosystems.www.misc:6448 Path: eso!Germany.EU.net!EU.net!howland.reston.ans.net!cs.utexas.edu!geraldo.cc.utexas.edu!doc.cc.utexas.edu!not-for-mail Newsgroups: comp.infosystems.www.providers,comp.infosystems.www.misc Lines: 308 Message-Id: <381njv$t22@doc.cc.utexas.edu> Nntp-Posting-Host: doc.cc.utexas.edu Sender: astroweb-request@fits.CV.NRAO.EDU Here's an HTML-checking program in awk. It doesn't pretend to understand all of SGML, but it's simple and easy to use, can be run on any platform where awk is available, and gives _lots_ of information (including about some stylistically bad practices): #htmlchek.awk: Syntactically checks HTML files for a number of possible errors. # # Typical use: # # awk -f htmlchek.awk infile.html > outfile.check # # This program is written in the ``awk'' programming language (on Sun systems # and some others, non-archaic ``awk'' is called ``nawk''; also, a freely- # redistributable ``awk'' interpreter called ``gawk'' is available for most # platforms, and as source from the FSF GNU project). It checks for quite a # number of possible defects in the HTML (Hyper-Text Mark-up Language) SGML # files used on the World-Wide Web. # # Definite syntactic errors are signaled one per line, using the string # "ERROR!". Stylistically deprecated HTML coding is signaled by "Warning!". # (However, I don't bother checking for some common tricks such as using # headings in lists.) SGML constructs outside the scope of HTML proper are not # checked for, and can result in error messages. At the end of the output, # diagnostics are generated as to the tags used in the file and the options # used with each tag, along with possible additional global warnings (these # final diagnostics/warnings can be longer than 80 columns). Note that # checking the same HTML file twice with this program can result in a different # ordering of the final tag diagnostics, due to the indeterminacy of the awk # "for (x in array) {...}" looping construct. # # As with almost any parser or lint-type program that doesn't just give up # at the first error, the presence of one real error can generate a cascade of # subsequent bogus errors. The only remedy is to fix the first error (which is # the real one), and run the check again. In particular, if you get a "nesting # underflow" error (i.e. at some point the number of </...> tags, of all types, # that have been encountered is more than the number of all pairing non-</...> # tags so far), then most subsequent error messages are unlikely to be helpful. # # Copyright H. Churchyard 1994 -- freely redistributable. This code is # functional but not very well commented (and readability has not been improved # by pushing all lines which would overflow 80 columns flush left) -- sorry! # If you find an error in this program, e-mail me at churchh@uts.cc.utexas.edu # (but please don't ask me what the errors and warnings mean -- they should be # fairly self-evident, assuming a familiarity with the basic HTML language # documentation; one warning that may be obscure, "Jump from H0", means that # the first heading in the file is not at level <H1>; also, "underflow" means # that more tokens of </x> than <x> have been encountered). # # Version 1.0 10/15/94 -- Tested with gawk 2.15 and nawk on SunOS, gawk 2.14 # and nawk on DEC Alpha OSF/1, and gawk 2.11 on 16-bit MS-DOS. # BEGIN{#List of known HTML tagwords, divided into pairing tags (<X>...</X>) and #non-pairing tags (those where <X> occurs without a following </X>). #Pairing tags are further classified into list tags, and those tags which #do not self-nest. The status of some tags (e.g. <P>) may change with #the evolution of the HTML language. Edit these lists if necessary, but #carefully preserve the existing format (``propertyarray["TAG"]=1;''). # #Non-pairing: # unpair["!--"]=1;unpair["BASE"]=1;unpair["BR"]=1;unpair["DD"]=1; unpair["DT"]=1;unpair["HR"]=1;unpair["IMG"]=1;unpair["INPUT"]=1; unpair["ISINDEX"]=1;unpair["LI"]=1;unpair["LINK"]=1;unpair["NEXTID"]=1; unpair["OPTION"]=1;unpair["P"]=1;unpair["PLAINTEXT"]=1; # #Pairing: # pair["A"]=1;pair["ADDRESS"]=1;pair["B"]=1;pair["BLOCKQUOTE"]=1;pair["BODY"]=1; pair["CITE"]=1;pair["CODE"]=1;pair["DFN"]=1;pair["DIR"]=1;pair["DL"]=1; pair["EM"]=1;pair["FORM"]=1;pair["H1"]=1;pair["H2"]=1;pair["H3"]=1; pair["H4"]=1;pair["H5"]=1;pair["H6"]=1;pair["HEAD"]=1;pair["HTML"]=1; pair["I"]=1;pair["KBD"]=1;pair["KEY"]=1;pair["LISTING"]=1;pair["MENU"]=1; pair["OL"]=1;pair["PRE"]=1;pair["SAMP"]=1;pair["SELECT"]=1;pair["STRONG"]=1; pair["TEXTAREA"]=1;pair["TITLE"]=1;pair["TT"]=1;pair["U"]=1;pair["UL"]=1; pair["VAR"]=1;pair["XMP"]=1; # #Deprecated: # deprecated["PLAINTEXT"]=1;deprecated["XMP"]=1;deprecated["LISTING"]=1; deprecated["KEY"]=1;deprecated["COMMENT"]=1; # #Allowed in <head>...</head> element: # inhead["!--"]=1;inhead["BASE"]=1;inhead["ISINDEX"]=1;inhead["LINK"]=1; inhead["NEXTID"]=1;inhead["TITLE"]=1;inhead["HEAD"]=1; # #Lists (all <LI> must be first order daughter of these and vice versa): # list["DIR"]=1;list["MENU"]=1;list["OL"]=1;list["UL"]=1; # #List that does not involve <LI>: # nonlilist["DL"]; # #Pairing but non-self-nesting: # nonnest["A"]=1;nonnest["ADDRESS"]=1;nonnest["B"]=1;nonnest["BLOCKQUOTE"]=1; nonnest["CITE"]=1;nonnest["CODE"]=1;nonnest["DFN"]=1;nonnest["EM"]=1; nonnest["FORM"]=1;nonnest["H1"]=1;nonnest["H2"]=1;nonnest["H3"]=1; nonnest["H4"]=1;nonnest["H5"]=1;nonnest["H6"]=1;nonnest["HTML"]=1; nonnest["I"]=1;nonnest["KBD"]=1;nonnest["LISTING"]=1;nonnest["PRE"]=1; nonnest["SAMP"]=1;nonnest["SELECT"]=1;nonnest["STRONG"]=1;nonnest["TEXTAREA"]=1; nonnest["TITLE"]=1;nonnest["TT"]=1;nonnest["U"]=1;nonnest["VAR"]=1; nonnest["XMP"]=1; # #-=- -=- Don't edit below this line unless you know what you're doing -=- -=- # #nonnest["BODY"]=1;nonnest["HEAD"]=1; #Separate checks for these state=0;continuation=0;blank=0;nestvar=0;htmlwarn=0;maxlist=0;headone=0; headlevel=0;br=0} # # Main # {lastbeg=0;currsrch=1;if (("HTML" in lev)&&(lev["HTML"]>0)) {htmlwas=1}; while (match(substr($0,currsrch),/[<>]/)!=0) {currsrch=(currsrch+RSTART);#-1 if (substr($0,(currsrch-1),1)=="<") {if (state) {print "Multiple `<' without `>' ERROR! at line",NR}; lastbeg=currsrch;state=1} else {if (substr($0,(currsrch-1),1)==">") {if (state==0) {print "`>' without `<' ERROR! at line",NR} else {parsetag(currsrch-1); if ((lasttag=="!--")&&(lastcomt!="--")) {print "!-- comment not terminated by \042--\042 ERROR! at line",NR}; if (inquote) {print "Malformed tag option ERROR! at line",NR,"on tag",lasttag}; state=0;continuation=0;blank=0}} else {print "Internal error at line",NR,"ignore"}}}; if (((state==1)&&(blank==0))||((lastbeg==0)&&(continuation==1))) {parsetag(length($0)+1);continuation=1}; if ((!htmlwarn)&&(($1!="")&&($1!="<")&&($1!~"^>"))&&((!("HTML" in lev))||(lev["HTML"]==0))) {if (!htmlwas) {print "Non-whitespace found outside <HTML>...</HTML> Warning! at line",NR; htmlwarn=1}}; htmlwas=0; if ($0~/&/) # Don't actually check against the list of &xxx; codes. {gsub(/&[A-Za-z][a-z]*;/,"");gsub(/&#[0-9][0-9]*;/,""); if ($0~/&/) {print "Apparent non-complying ampersand code ERROR! at line",NR}}} # # # parsetag() communicates with main() through these global variables: # - lastbeg (zero if no `<' ocurred on line, otherwise points to character # immediately after the last `<' encountered). # - state (one if unresolved `<', zero otherwise). # - continuation (one if unresolved `<' from previous line, zero otherwise), # - blank (one if continuation and no tag-word encountered yet). # - inquote (one if inside option quotes <tag opt="....">). # function parsetag(inp) {if (!lastbeg) {lastbeg=1}; #print substr($0,lastbeg,(inp-lastbeg));#XXdebugging# numf=split(substr($0,lastbeg,(inp-lastbeg)),arr); if (numf==0) {if (substr($0,(lastbeg-1))~/<[ \t]*$/) {continuation=1;blank=1;state=1;return} else {if (substr($0,1,inp)~/^[ \t]*>/) {if (continuation&&blank) {print "Multiline Blank <> ERROR! at line",NR}; continuation=0;blank=0;state=0;return} else {if (!continuation) {print "Blank <> ERROR! at line",NR; continuation=0;blank=0;state=0;return}}}} else {if ((!continuation)||(continuation&&blank)) {arr[1]=upcase(arr[1]);if (arr[1]~/^!--/) {raw=arr[1];arr[1]="!--"} else {raw=""}; lasttag=arr[1]; if (arr[1]~/^\//) #</TAG> found {sub(/^\//,"",arr[1]);--lev[arr[1]]; if (lev[arr[1]]<0) {print "Underflow ERROR! at line",NR, "on tag /" arr[1]}; if (arr[1] in pair) {if (nestvar<=0) {print "Nesting underflow ERROR! at line",NR,"on tag /" arr[1]} else {if (nestarr[nestvar]!=arr[1]) {print "Nesting ERROR! at line",NR,": /" nestarr[nestvar],"expected, /" arr[1],"found"}}; if ((nestarr[nestvar] in list)&&(!isli[nestvar])) {print "Empty list (without <LI>) ERROR! at line",NR,"on tag /" arr[1]}; --nestvar} else {revusarr[arr[1]]=1}; if ((arr[1] in list)||(arr[1] in nonlilist)) {--listdep}} else {if ((arr[1]=="HEAD")||(arr[1]=="BODY")) #<TAG> found {hbwarn=0;if ((!("HTML" in lev))||(lev["HTML"]==0)) {print "HEAD or BODY outside of <HTML>...</HTML> ERROR! at line",NR}; if ((("HEAD" in lev)&&(lev["HEAD"]>0))||(("BODY" in lev)&&(lev["BODY"]>0))) {print "HEAD or BODY nested inside HEAD or BODY element ERROR! at line",NR}} else {if ((!hbwarn)&&(lasttag!="!--")) {if ((!(("BODY" in lev)&&(lev["BODY"]>0)))&&(!(("HEAD" in lev)&&(lev["HEAD"]>0)))) {if (("HTML" in lev)&&(lev["HTML"]!=0)) {print "Tag outside of HEAD or BODY element Warning! at line",NR,"on tag",arr[1]; hbwarn=1}}}}; ++lev[arr[1]]; if ((arr[1]!="LI")&&(nestarr[nestvar] in list)&&(!isli[nestvar])) {print "Tag in list occurred before first <LI> ERROR! at line",NR,"on tag",arr[1]}; if (arr[1] in pair) {++nestvar;nestarr[nestvar]=arr[1];isli[nestvar]=0}; if ((arr[1] in list)||(arr[1] in nonlilist)) {++listdep;if (listdep>maxlist) {maxlist=listdep}}; if (arr[1]=="LI") {isli[nestvar]=1; if (!(nestarr[nestvar] in list)) {print "<LI> outside of list ERROR! at line",NR}}; if (("HEAD" in lev)&&(lev["HEAD"]>0)) {if (!(arr[1] in inhead)) {print "Disallowed tag in <head>...</head> ERROR! at line",NR,"on tag",arr[1]}}; if (arr[1]~/^H[1-6]$/) {newheadlev=substr(arr[1],2,1); if (newheadlev>(headlevel+1)) {print "Warning! Jump from header level H" headlevel, "to level H" newheadlev,"at line",NR}; headlevel=newheadlev; if (headlevel==1) {if (headone==1) {print "Multiple <H1> headings Warning! at line",NR}; headone=1}}; if (arr[1]=="HTML") {htmlwarn=0;hbwarn=0;htmlwas=1;headone=0}; if ((arr[1] in nonnest)&&(lev[arr[1]]>1)) {print "Self-nesting of unselfnestable tag ERROR! at line",NR,"on tag",arr[1]}}; blank=0;startf=2;usarr[arr[1]]=1;inquote=0} else {startf=1}; if (lasttag!="!--") #Remainder of stuff in <...> after tag word {for (i=startf;i<=numf;++i) {if (!inquote) #((arr[i]~/^[^=\042]+=\042[^=\042]*\042$/)||(arr[i]~/^[^=\042]+(=(\042)?[^=\042]*)?$/)) {if ((arr[i]~/^[^=\042]*(=\042[^=\042]*\042)?$/)||(arr[i]~/^[^=\042]*=(\042)?[^=\042]*$/)) {split(arr[i],arr2,"="); if (arr2[1]=="") {print "Null tag option ERROR! at line",NR,"on tag",lasttag} else {arr2[1]=upcase(arr2[1]); optarr[lasttag,arr2[1]]=1}; if (gsub(/\042/,"",arr[i])==1) {inquote=1}} else {print "Malformed tag option ERROR! at line",NR,"on tag",lasttag}} else {if (arr[i]~/\042/) {inquote=0; if (arr[i]!~/^[^\042]*\042$/) {print "Malformed tag option ERROR! at line",NR,"on tag",lasttag}}}}} else {if ((numf==1)&&(!continuation)) {sub(/!--/,"",raw);arr[1]=raw}; if (arr[numf]~/--$/) {lastcomt="--"} else {lastcomt=""}}; return}} # # Uppercasing routine; in GAWK can replace upcase() with built-in function # toupper() for a speed boost. # BEGIN{ upc["a"]="A";upc["b"]="B";upc["c"]="C";upc["d"]="D";upc["e"]="E";upc["f"]="F"; upc["g"]="G";upc["h"]="H";upc["i"]="I";upc["j"]="J";upc["k"]="K";upc["l"]="L"; upc["m"]="M";upc["n"]="N";upc["o"]="O";upc["p"]="P";upc["q"]="Q";upc["r"]="R"; upc["s"]="S";upc["t"]="T";upc["u"]="U";upc["v"]="V";upc["w"]="W";upc["x"]="X"; upc["y"]="Y";upc["z"]="Z"; } # function upcase(upcins,k) {if (upcins~/[a-z]/) {for (k in upc) {if (upcins~k) {gsub(k,upc[k],upcins)}}}; return upcins} # # End-of-file routine. Information is passed here through arrays: # - usarr[x]: The tag <x> was used. # - revusarr[x]: The reverse tag </x> was used. # - lev[x]: Current degree of self-nesting of paired tag <x>...</x>. # - optarr[x,y]: The option y was used with tag <x>. #and also through the variables maxlist and continuation. # END{if (continuation) {print "Was awaiting a `>' ERROR! at END"}; for (x in usarr) {if (x in pair) if (lev[x]>0) {print "Pending unresolved <x> without </x> ERROR! of level",lev[x],"at END on tag",x}; if (lev[x]<0) {print "Residual underflow of level",lev[x],"at END on tag",x}}; if (!("HTML" in usarr)) {print "<HTML> not used in document Warning! at END"}; if (!("HEAD" in usarr)) {print "<HEAD> not used in document Warning! at END"}; if (!("BODY" in usarr)) {print "<BODY> not used in document Warning! at END"}; for (x in usarr) {options="";head=("^" x SUBSEP); for (z in optarr) {if (z~head) {split(z,optx,SUBSEP); options=(options " " optx[2])}}; if (!br) {print "";br=1}; printf "%s %s %s","Tag",x,"occurred"; if (options) {printf "%s%s",", with options",options}; if (!((x in pair)||(x in unpair))) {printf "; Warning! tag is unknown"}; if (x in deprecated) {printf "; Warning! tag is obsolescent and deprecated"}; if ((x in unpair)&&(x in revusarr)) {printf ("; Warning! " x " not a paired tag, yet </" x "> encountered")}; if ((!(x in pair))&&(x in revusarr)&&(lev[x]!=0)) {printf ("; Balance of <" x "> minus </" x "> nonzero ERROR! of level " lev[x] " at END")}; printf "\n"}; if (maxlist) {print "Maximum depth of list embedding was",maxlist}} #-=- -=- -=- -=- -=- -=- -=- -=- -=- -=- -=- -=- -=- -=- -=- -=- ##EOF -- _ ___ _ ____ (< __|~`---, <( Henry Churchyard | | | | )> \ _ * | >) University of Texas | __| | | (< `~ \ / <( . . . . )> Austin`-' TX >) churchyh@ccwf.cc.utexas.edu . . From astroweb-request Tue Oct 25 03:59:40 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA03441; Tue, 25 Oct 94 03:59:40 EDT Return-Path: <adorf@eso.org> X-Sender: hmadorf@ns3.hq.eso.org Message-Id: <aad26ba738021004e1d6@[134.171.10.154]> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 25 Oct 1994 09:01:28 +0100 To: astroweb@NRAO.EDU From: adorf@eso.org (Hans-Martin Adorf) Subject: Free Internet Access in Italy Cc: ralbrech@eso.org (Rudi Albrecht) Sender: astroweb-request@fits.CV.NRAO.EDU Free Internet Access in Italy by Adam C. Engst <ace@tidbits.com> Mario Marinelli <mario@basker.sublink.org> tells us that, in what may be a first, the Italian city of Bologna now provides free Internet access to all its citizens. http://www.infn.it/pub/CNAF/Bologna.html CINECA, a semi-public organization owned in part by the City of Bologna, has leased a 128K high speed link to the Internet and provides Internet access in several ways, including basic Unix shell accounts, a BBS (probably SoftArc's FirstClass) that will provide news and email, and also, for a fee of $20 per month, SLIP or PPP accounts for more advanced users who want their own Internet nodes. The project, called NetTuno ("Nettuno" is the Italian name for the Roman god of the sea and the symbol of Bologna), has been joined by the cities of Rome and Turin as well. If other Italian cities follow suit, it could lead to a significant upswell in Internet use from Italy. The initiative apparently started as a result of the responses to a series of newspaper articles about global networking and its impact for growth in business opportunities, but perhaps more interesting, in response to articles discussing the development and implementation of a new model of participatory democracy. You can get more information about the project via email from <baskerville@cineca.it> or via the Web (assuming you read Italian) at: http://www.cineca.it/nettuno/nettuno.htm [Incidentally, I found the above information on Bologna via The Virtual Tourist, an especially interesting Web service located at the URL below. -Adam] http://wings.buffalo.edu/world/ From astroweb-request Wed Oct 26 04:45:37 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA06722; Wed, 26 Oct 94 04:45:37 EDT Return-Path: <adorf@eso.org> X-Sender: hmadorf@ns3.hq.eso.org Message-Id: <aad3c42802021004eb01@[134.171.10.154]> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 26 Oct 1994 09:47:38 +0100 To: astroweb@NRAO.EDU From: adorf@eso.org (Hans-Martin Adorf) Subject: search and classification Sender: astroweb-request@fits.CV.NRAO.EDU Dear friends, I noticed a pecularity of our WAIS index which I should like to communicate. I was searching the AstroWeb database for ESO and found 143 (!) records, many of which have no relation to ESO other than they have been submitted by me, and I happen to be sitting at a machine xxx.hq.eso.org. While in general I like the idea that the target URLs are being indexed - that assures completeness of one's search - I am disfavouring the inclusion of the submitter's host machine. I do not know whether it is possible to discard that information prior/during indexing, but I hope so. Also when I inspected my new pages, which have resource records grouped according to the assigned hidden categories, I noticed quite a number of misclassifications, which were not present in my old handcrafted page. I believe that these misclassification will negatively influence the reception of the AstroWeb database in the community, and I think that it should be the top-priority item to (a) revise the classification scheme, (b) subdivide the database into equal chunks among ourselves and check the classification (which might include accessing the recorded URL) Cheers Hans-Martin From astroweb-request Wed Oct 26 06:01:12 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA08034; Wed, 26 Oct 94 06:01:12 EDT Return-Path: <adorf@eso.org> X-Sender: hmadorf@ns3.hq.eso.org Message-Id: <aad3d9d1030210046ddc@[134.171.10.154]> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 26 Oct 1994 11:03:12 +0100 To: astroweb@NRAO.EDU From: ESO Garching Librarian <esolib@eso.org> (by way of adorf@eso.org (Hans-Martin Adorf)) Subject: The Hot Hot List Sender: astroweb-request@fits.CV.NRAO.EDU I couldn't resist from including it into our "Goodies" Library page. Regards, ...Uta ------- Forwarded Message From: Liz Bryson <bryson@CFHT.HAWAII.EDU> Subject: Re: hot hot list Comments: To: sla-pam@ukcc.uky.edu To: Multiple recipients of list SLA-PAM <SLA-PAM%UKCC.BITNET@uga.cc.uga.edu> Try this if you haven't already: http://www.ccsf.caltech.edu/~roy/others.html ------- End of Forwarded Message From astroweb-request Wed Oct 26 07:27:04 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA08160; Wed, 26 Oct 94 07:27:04 EDT Return-Path: <jackson@stsci.edu> Date: Wed, 26 Oct 94 07:26:58 EDT From: Bob Jackson <jackson@stsci.edu> Message-Id: <9410261126.AA26702@MARIAN.STSCI.EDU> To: adorf@eso.org In-Reply-To: <aad3c42802021004eb01@[134.171.10.154]> (adorf@eso.org) Subject: Re: search and classification Reply-To: jackson@stsci.edu Cc: astroweb@NRAO.EDU Sender: astroweb-request@fits.CV.NRAO.EDU I suspect that I can eliminate the spurious hits on 'eso' by eliminating all html comments in the DESCRIPTION fields. >>> Does anyone object to eliminating HTML comments from the >>> descriptions? Bob From astroweb-request Wed Oct 26 08:06:09 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA08206; Wed, 26 Oct 94 08:06:09 EDT Return-Path: <jackson@stsci.edu> Date: Wed, 26 Oct 94 08:06:03 EDT From: Bob Jackson <jackson@stsci.edu> Message-Id: <9410261206.AA26839@MARIAN.STSCI.EDU> To: astroweb@NRAO.EDU Subject: format converter Reply-To: jackson@stsci.edu Sender: astroweb-request@fits.CV.NRAO.EDU http://anarky.stsci.edu/astroweb/munge-html is a Tcl script which takes the HTML version of the database and creates the Tcl'ish version of it, suitable for converting Don's record format into Bob's Edit Entire Database format. Suggested usage: 1. Open http://lor.stsci.edu/astroweb/astroweb-cvs.html 2. Enter name, password, select 'Edit Entire Database', 3. Save As (HTML) <whatever> 4. Take records in Don's format and munge-html <input-file> <output-file> 5. Open <whatever> in your editor 6. Insert <output-file> in between any existing records 7. Save <whatever> 8. Open Local <whatever> From astroweb-request Wed Oct 26 09:26:12 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA08383; Wed, 26 Oct 94 09:26:12 EDT Return-Path: <adorf@eso.org> X-Sender: hmadorf@ns3.hq.eso.org Message-Id: <aad409a307021004aa21@[134.171.10.154]> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 26 Oct 1994 14:28:13 +0100 To: jackson@stsci.edu From: adorf@eso.org (Hans-Martin Adorf) Subject: Re: search and classification Cc: astroweb@NRAO.EDU Sender: astroweb-request@fits.CV.NRAO.EDU >I suspect that I can eliminate the spurious hits on 'eso' by >eliminating all html comments in the DESCRIPTION fields. > >>>> Does anyone object to eliminating HTML comments from the >>>> descriptions? It depends on what you mean by eliminating. I would like to see the submitter's information staying, but not indexed. -hma From astroweb-request Wed Oct 26 11:28:13 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA08636; Wed, 26 Oct 94 11:28:13 EDT Return-Path: <adorf@eso.org> X-Sender: hmadorf@ns3.hq.eso.org Message-Id: <aad4263b0202100461fa@[134.171.10.154]> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 26 Oct 1994 16:30:10 +0100 To: astroweb@NRAO.EDU From: adorf@eso.org (Hans-Martin Adorf) Subject: draft of AstroWeb article for *ESO Messenger* Sender: astroweb-request@fits.CV.NRAO.EDU % Converted from RTF format using rtf2LaTeX % Comments and bugs to Erwin Wechtl % Woertg. 2/18 % A-2500 Baden % \documentstyle{article} \pagestyle{myheadings} \newlength{\defaultparindent} \setlength{\defaultparindent}{\parindent} % definition of reference% \newenvironment{reference}{% \normalsize % \setlength{\parindent}{-27pt}% \begin{list}{ }{% \setlength{\leftmargin}{28pt}\setlength{\rightmargin}{0pt}% \setlength{\topsep}{0pt}\setlength{\partopsep}{0pt}} \item }{% \end{list}} % definition of indented Paragraph% \newenvironment{indented Paragraph}{% \setlength{\parindent}{28pt}}{} % definition of comment% \newenvironment{comment}{}{} % definition of affiliation% \newenvironment{affiliation}{% \begin{center}}{% \end{center}} % definition of acknowledgement% \newenvironment{acknowledgement}{% \normalsize }{} % Normal will be ignored % heading 1 will be translated as section % heading 2 will be translated as subsection %*****************************************************************% \begin{document} \title{The AstroWeb database of Internet resources} \author{} \maketitle \begin{center} {\normalsize Hans-Martin Adorf}% {\normalsize $^{1}$}% {\normalsize , Daniel Egret}% {\normalsize $^{2}$}% {\normalsize , Andr\'{e} Heck}% {\normalsize $^{3}$}% {\normalsize , Robert Jackson}% {\normalsize $^{4}$}% {\normalsize , Anton Koekemoer}% {\normalsize $^{5}$}% {\normalsize , Fionn Murtagh}% {\normalsize $^{1}$}% {\normalsize , Don Wells}% {\normalsize $^{6}$}% \\ {\normalsize $^{1}$}ST-ECF, % {\normalsize $^{2}$}CDS, % {\normalsize $^{3}$}Strasbourg Astronomical Observatory, % {\normalsize $^{4}$}CSC/STScI, % {\normalsize $^{5}$}MSSSO, % {\normalsize $^{6}$}NRAO \end{center} \section{Introduction} The Internet has succeeded --- and with it the World Wide Web. This mould of hypertext information pages with embedded pictures and hyperlinks to other local or remote information pages --- as well as to other Internet services --- has greatly facilitated public participation of the Shoemaker-Levy-9 comet crash (West 1994, Murtagh \& Fendt 1994). The World Wide Web, or WWW for short, is also increasingly being used for scientific communication and information dissemination in all natural sciences, and astronomy is one of the most active communities in this respect. With the success of the Internet, a mechanism better than individual ``hotlists'' for organising useful collections of astronomical Internet resources is clearly needed. This is where the ``AstroWeb'' database (Adorf % {\it et al. }1994, Jackson % {\it et al.} 1994, 1995a, b) enters. It aims at being the most complete and useful on-line collection of Uniform Resource Locators (URLs) for astronomical Internet resources, pointing to entities as diverse as societies, observatories, databases, preprint servers, telescopes, telescope schedules, weather information or individual astronomers. As such the AstroWeb database complements the recent annotated compilation of astronomical Internet resources (Andernach, Hanisch \& Murtagh 1994). \section{Organisation} \setlength{\parskip}{0pt}The AstroWeb database, which is being maintained by the ``AstroWeb Consortium'', currently comprises more than 1100 records of FTP, Gopher, Telnet, News, WAIS and WWW resources. Each record minimally consists of a headline and an associated URL. Many records are augmented by a paragraph of descriptive text. If known, the e-mail address of the resource's maintainer is stored along with the record. As added value, the AstroWeb consortium has classified each record according into one or more of about 25 categories, such as observatory, radio, optical, infrared, telescope, database or software. The AstroWeb database is actually a distributed system of databases maintained at five different sites (CDS, MSSSO, NRAO, ST-ECF, and STScI ) on three continents. The master copy is currently kept at the Space Telescope Science Institute, Baltimore. There the aliveness of all URLs (except of Telnet records) is verified three times a day, and ``unreliable'' or ``dead'' URLs are flagged. Once a day each site automatically fetches a copy from the master, and computes a local rendition of the AstroWeb database. Each site offers the AstroWeb database in a different style of presentation. The ST-ECF rendition, for instance, is terse and suitable for quick reference, whereas the STScI or NRAO renditions are more verbose and particularly suitable for browsing. Some sites even offer more than one rendition for the convenience of the users. \section{Accessing the AstroWeb database} \setlength{\parskip}{0pt}The natural place for offering the AstroWeb database is the WWW. The ST-ECF rendition can be accessed either through hyperlinks originating from the ESO web (http://www.hq.eso.org/eso-homepage.html), or from the ST-ECF web (http://ecf.hq.eso.org/), or directly via the ``yellow pages'' URL http://ecf.hq.eso.org/astroweb/yp\_astro\_resources.html (Fig. 1), from where links to the other AstroWeb renderings are provided. The AstroWeb database is an excellent starting point for browsing the astronomical Internet branch (Figs. 2 and 3), as well as for finding other resources of potential interest to astronomers. At a size of well over 1000 records, it is mandatory that the database is also % {\it searchable}. To this end one may use the simple text matching facility built into most, if not all, WWW clients. A more powerful search mechanism, however, is offered by the AstroWeb WAIS index, which can be queried using natural (English) language from all AstroWeb sites. Since complete records are indexed, queries may include categories and URLs, which are usually hidden in HTML-comments. The results are returned as WWW-pages with ready-to-use hyperlinks to interesting resources found. \section{Submission of new records} \setlength{\parskip}{0pt}The AstroWeb Consortium, consisting of the authors above, % {\it welcomes} submissions of new records from the astronomical community; WWW forms have been put in place to facilitate this process. Submissions are reviewed by Consortium members and entered manually to ensure a minimum quality of the database. The list of recent submissions, not yet entered into the main database, may be viewed. The Consortium also encourages corrections to existing records (e.g. via e-mail to astroweb@noao.edu). AstroWeb Consortium members can globally edit the database, in order to better respond to change requests. \section{Possible future steps} \setlength{\parskip}{0pt}After a rapid growth, the AstroWeb is currently being consolidated. It is hoped that, with the help of the astronomical community, the degree of completeness and quality of the AstroWeb database can be further improved. Certainly, database internal cross-referencing within the descriptive paragraphs is far from complete. Here the situation can presumably be remedied with an appropriate software tool. In the future the AstroWeb database might be used as a starting base for indexing all astronomical WWW pages out on the Internet. This would involve a ``robot'' repeatedly fetching all relevant HTML pages, similarly to how Archie indexes all files in all registered anonymous FTP servers. Such a project is by no means out of question. In fact, general indices spanning the whole WWW already exist, but none thus far is specific to astronomy. \section{References} \setlength{\parskip}{0pt}% \begin{reference} Adorf, H.-M., Egret, D., Heck, A., Jackson, R., Koekemoer, A., Murtagh, F., Wells, D.: 1994, ``AstroWeb --- Internet resources for astronomers'', % {\it ST-ECF Newsl. }% {\bf 22}, (in press). Andernach, H., Hanisch, R.J., Murtagh, F.D.: 1994, ``Network resources for astronomers'', % {\it Publ. Astron. Soc. Pacific, }(in press). Jackson, R., Wells, D., Adorf, H.-M., Egret, D., Heck, A., Koekemoer, A., Murtagh, F.: 1994, ``The AstroWeb Database'', % {\it Bull. CDS }% {\bf 45}, 21---25. Jackson, R., Wells, D., Adorf, H.-M., Egret, D., Heck, A., Koekemoer, A., Murtagh, F.: 1995a, ``AstroWeb --- A database of links to astronomy resources --- Announcement of a database'', % {\it Astron. Astrophys. Suppl., }(in press). Jackson, R.E., Adorf, H.-M., Egret, D., Heck, A., Koekemoer, A., Murtagh, F., Wells, D.: 1995b, ``AstroWeb --- Internet resources for astronomers'', in: Proc. % {\it Astronomical Data Analysis Software and Systems (ADASS) '94,} Baltimore, MD, D. Shaw, H. Payne, and J. Hayes (eds.), Astronomical Society of the Pacific, (in press). Murtagh, F., Fendt, M.: 1994, ``The SL-9/ESO Web Encounter'', ESO Messenger % {\bf 77}, 47. West, R.: 1994, ``Comet Shoemaker-Levy 9 Collides with Jupiter'', ESO Messenger % {\bf 77}, 28---31.% \end{reference} \setlength{\parindent}{\defaultparindent}% \begin{reference} \end{reference} \section{Figures} \setlength{\parskip}{0pt}Fig. 1: View of the top-level page of the AstroWeb database at the ST-ECF. Hyperlinks to forms for entering new records, and for error corrections are provided. Fig. 2: The list of ``telescope schedules'' accessible from the AstroWeb information pages. Fig. 3: Portion of the ``abstracts'' resource listing in the AstroWeb database. \end{document} From www_server Wed Oct 26 17:46:32 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA09557; Wed, 26 Oct 94 17:46:32 EDT Return-Path: <www_server@fits.CV.NRAO.EDU> Date: Wed, 26 Oct 94 17:46:28 EDT From: www_server@fits.CV.NRAO.EDU (httpd@fits.cv.nrao.edu) Message-Id: <9410262146.AA09548@fits.cv.nrao.edu> To: astroweb@NRAO.EDU Sender: astroweb-request@fits.CV.NRAO.EDU Message entered by: @ watt.ee.washington.edu [128.95.42.254] acsacascacs From www_server Wed Oct 26 22:19:44 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA09844; Wed, 26 Oct 94 22:19:44 EDT Return-Path: <www_server@fits.CV.NRAO.EDU> Date: Wed, 26 Oct 94 22:19:39 EDT From: www_server@fits.CV.NRAO.EDU (httpd@fits.cv.nrao.edu) Message-Id: <9410270219.AA09828@fits.cv.nrao.edu> To: astroweb@NRAO.EDU, asvdasdv@fits.CV.NRAO.EDU Subject: savdsadvsvad Sender: astroweb-request@fits.CV.NRAO.EDU Message entered by: @ watt.ee.washington.edu [128.95.42.254] sadgvasvdsavdd From www_server Wed Oct 26 22:28:37 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA09893; Wed, 26 Oct 94 22:28:37 EDT Return-Path: <www_server@fits.CV.NRAO.EDU> Date: Wed, 26 Oct 94 22:28:32 EDT From: www_server@fits.CV.NRAO.EDU (httpd@fits.cv.nrao.edu) Message-Id: <9410270228.AA09884@fits.cv.nrao.edu> To: astroweb@NRAO.EDU Sender: astroweb-request@fits.CV.NRAO.EDU Message entered by: @ watt.ee.washington.edu [128.95.42.254] sdvsdvsdvsvdsdv From www_server Wed Oct 26 22:34:49 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA09947; Wed, 26 Oct 94 22:34:49 EDT Return-Path: <www_server@fits.CV.NRAO.EDU> Date: Wed, 26 Oct 94 22:34:44 EDT From: www_server@fits.CV.NRAO.EDU (httpd@fits.cv.nrao.edu) Message-Id: <9410270234.AA09938@fits.cv.nrao.edu> To: astroweb@NRAO.EDU Sender: astroweb-request@fits.CV.NRAO.EDU Message entered by: @ watt.ee.washington.edu [128.95.42.254] acsacascacsbdfb` dfbascascc From www_server Thu Oct 27 09:40:05 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA11878; Thu, 27 Oct 94 09:40:05 EDT Return-Path: <www_server@fits.CV.NRAO.EDU> Date: Thu, 27 Oct 94 09:39:58 EDT From: www_server@fits.CV.NRAO.EDU (httpd@fits.cv.nrao.edu) Message-Id: <9410271339.AA11869@fits.cv.nrao.edu> To: astroweb@NRAO.EDU, csillag@astro.phys.ethz.ch Subject: change of the record name Sender: astroweb-request@fits.CV.NRAO.EDU Message entered by: Csillaghy @ mimas.ethz.ch [129.132.63.5] I would like to have the name of our current record, which is "ETH Solar Radio Spectrometer" changed to "Zurich Solar Radio Spectrometer", as we are more known with that name. I thank you in advance, Yours Sincerely, -- Andre Csillaghy From dwells Thu Oct 27 14:26:26 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA12460; Thu, 27 Oct 94 14:26:26 EDT Return-Path: <dwells@fits.CV.NRAO.EDU> Date: Thu, 27 Oct 94 14:26:22 EDT From: dwells@fits.CV.NRAO.EDU (Don Wells) Message-Id: <9410271826.AA12451@fits.cv.nrao.edu> To: astroweb@NRAO.EDU Subject: Re: search and classification In-Reply-To: <aad3c42802021004eb01@[134.171.10.154]> References: <aad3c42802021004eb01@[134.171.10.154]> Sender: astroweb-request@fits.CV.NRAO.EDU Hans-Martin Adorf writes: > .. I was searching the AstroWeb database for ESO and found 143 > (!) records.. happen to be.. at.. machine > xxx.hq.eso.org. Sigh... this feature of the WAIS indexing is both a blessing and a curse. I am reluctant to recommend disabling it, but your particular example (ESO) definitely demonstrates the curse aspect. > .., I noticed quite a number of > misclassifications.. Yes. The quality of classification codes in the AstroWeb database has declined as the size of the database has grown. > I believe that these misclassification will negatively influence the > reception of the AstroWeb database in the community.. That is a real possiblity. > should be.. top-priority item to > (a) revise the classification scheme, The existing category codes were not planned, but rather are mostly classifications which various Consortium members had made before January 94; I invented most of the codes as I merged the five old databases. A starting point might be to construct a Web page containing a paragraph of text for each code to specify the range of cases that the code will include. At the present time, the only thing that we have to document the codes is the menu in the entry form. > (b) subdivide the database into equal chunks among ourselves and check the > classification (which might include accessing the recorded URL) That may be necessary. There are 7 of us, so an equal partition would be something like 160 records to check. I suggest partitioning the yp_topzone file. I am willing to do 160 records, but I would like to see agreement on classification guidelines and the text describing each code before I start on my piece of the database. I hope that we can also agree on issues like whether there should be both FTP and HTTP records for the same institution (I say 'no', HTTP should take precedence). Likewise, should the WAIS search engine for a database be listed separately from record for the database itself? These are style and policy questions, questions which we have mostly avoided trying to answer because we know that there are a range of opinions in the Consortium. -*- Improving the classifications is going to be truly hard work in the AstroWeb project. Maybe we should recruit some discipline experts to aid us. For example, we could advertise for applications to be the 'solar' specialist, or the 'planetary' specialist, two possibilities which are not currently represented in our group. Also, I believe that we could recruit one or more astronomy librarians to join with us in order to maintain the library-related categories if we just asked them. -Don From astroweb-request Fri Oct 28 01:39:04 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA13632; Fri, 28 Oct 94 01:39:04 EDT Return-Path: <heck@cdsxb6.u-strasbg.fr> Message-Id: <9410280541.AA00354@cdsxb6.u-strasbg.fr> To: astroweb@fits.CV.NRAO.EDU Cc: heck@cdsxb6.u-strasbg.fr Subject: Classification problems Date: Fri, 28 Oct 94 06:41:14 +0100 From: Andre HECK <heck@cdsxb6.u-strasbg.fr> Sender: astroweb-request@fits.CV.NRAO.EDU You may go back to one of my messages at the very beginning of AstroWeb where I indicated that sorting out entries in categories would lead to significant problems. This was based on my 17y experience with my own databases. Now you realize it. So my recommendation is: drop them and save time both in arguing about the principle and the classifications themselves. The only way I found practical to sort entries was by countries and alphabetically on the full name within countries, with the addition of a few cross-pointers. Refer to StarWorlds/StarGuides. I never got a single complaint on the way my entries were sorted out. AH. ------------------------------------------------------------------------ From astroweb-request Sat Oct 29 13:19:16 1994 Received: by fits.cv.nrao.edu (4.1/DDN-DLB/1.5) id AA18697; Sat, 29 Oct 94 13:19:16 EDT Return-Path: <heck@cdsxb6.u-strasbg.fr> Message-Id: <9410291721.AA06179@cdsxb6.u-strasbg.fr> To: astroweb@fits.CV.NRAO.EDU Cc: heck@cdsxb6.u-strasbg.fr, mh@image.univ-lyon1.fr Subject: Change in Lyon Observatory URL Date: Sat, 29 Oct 94 18:21:25 +0100 From: Andre HECK <heck@cdsxb6.u-strasbg.fr> Sender: astroweb-request@fits.CV.NRAO.EDU Please note that the anchor for Lyon Observatory: file://image.univ-lyon1.fr/pub should be replaced by: http://www-obs.univ-lyon1.fr AH. ------------------------------------------------------------------------