For the DAMA 1998 National Conference, Canberra, 23 October 1998

This document is URL: (Draft of 27 August 1998).

The Internet for Information Professionals

Back to basics

Tom Worthington

Tom Worthington

Immediate Past President of the Australian Computer Society



It is argued that it is time to strip the hype from hypertext and put some reality back into virtual reality. Basic practices for information professionals (particularly information technology professionals) using the Internet are outlined. The paper discusses the need for information professionals to master these basics, before they tack on the glittery bits of on-line communication. Examples include distributing documents in readable formats, using meta-data and structuring information using traditional data analysis techniques.


Information Technology (IT) professionals may know how to build a data network or program a computer, but that doesn't mean they necessarily know how to use them to communicate to people. A new form of literacy is needed to make the maximum use of this new medium.

This was intended to be a series of articles, on how professionals can use the Internet. It was written for IT professionals, that is people working with computers and telecommunications. I started writing this in March 1997. After a while I realised that a series of articles was a little over-ambitious and that the principles may be of interest to other Internet information professionals (such as librarians and records managers). Therefore I have decided to finish the material (as much as any electronic document is ever finished) and deliver it for DAMA 98.

In my policy work for the Department of Defence and the Australian Computer Society (ACS) the Internet is my primary tool of trade. With the Internet I research material, send out drafts for comment, collect input and publish final results, as well as keep in touch with people.

The skills I use to do this have been built up from years of practice, as well as from courses in marketing, graphic design and IT. Many of the people I work with appear to have trouble with this new medium and ask "how do you cope with all the information?", "how do you get approval to put draft policy documents on-line?". In this paper I want to set down the tips and techniques which have been useful in keeping up. Also I want to make a plea for all information professionals to apply their professionalism to on-line communication.

There are many limitations with the Internet. It could be improved in many ways and there are many tasks it is not suitable for. However, the Internet is well worth using for what it is good for: routine, not very secure communication. Waiting for something better is not an option with IT, as there will always be something better. Professionals need to learn their skills with the technology which is available now.

When you first get an e-mail address, post a news item, or upload a web document, you are joining a community. As an information professional you are an elite member of that community. You have an obligation to demonstrate competence in the use of communication, which one of the 'tools of trade' of any professional. The community and your peers will hold you accountable for you actions in cyberspace as much as in any other place.

Electronic Mail

The basic tool of the Internet is electronic mail. While the web might be glamorous, plain old text based e-mail is the first and most important tool to master.

E-mail on the Internet is much the same as you might have used in your work place. The difference is the scale and familiarity: there are many more people to communicate with (or not communicate with) and you don't necessarily know who they are, or what they expect.

How to read e-mail

To write good e-mail messages you first need to know how to read them. Initially you will be excited by the novelty of receiving messages from around the world. This will change within a few days to worry about coping with the volume of material and trying to filter useful content from the rubbish.

I am a moderately heavy e-mail user and receive about 100 messages a day. How does anyone cope with reading this many messages? The answer is simple: I don't read more than about one tenth of them. You will get more mail than you can read and need adopt techniques to sort and sift the mail. Here are the ones I use:

Pre-sort with multiple addresses

As soon as the e-mail gets to be a burden, consider obtaining separate e-mail addresses for different types of e-mail. I have one e-mail address for my work and one for ACS business and personal e-mail.

Separate addresses allows the people who write to you to sort your mail for you. If you have a special function or project which is likely to generate a lot of mail, then create a special address for it. You can then let that mail build up until you need to read it (or have it forwarded to someone else and not read it at all).

Read in batches

Don't read each message as it arrives, let the mail build up and read it in batches. How often you read the mail depends on how much you get and how important the particular e-mail address is to you. I read my work mail about every fifteen minutes while at my desk and my ACS mail once or twice a day.

In this way you can exploit one of e-mail's great advantages over the telephone: you don't have to be interrupted continuously by it.

Sort by subject

When you have a batch of e-mail to read, don't just read it one item at a time in the order it arrived. You can use the features of your e-mail software to sort items to make them easier to handle.

I usually sort items by subject. Good e-mail authors will use a descriptive subject line on their messages. Usually e-mail will be sent to several people, who will then reply to the list. Good authors will use the original subject when replying, so if you sort by subject you will get the thread of conversation, ready for easy reading.

If your e-mail package can't sort mail, then get a new one which can. Otherwise you are going to waste a very large amount of your time.

After you have sorted by subject, look down the list and see if there are any very interesting topics. Open the first item of the most interesting topic. If this isn't really interesting then close it and have a quick look at the authors of the other items on this topic. If there isn't anyone interesting, then don't bother opening any other items, just delete them all and go on to the next subject.

When you do find an item of interest, quickly read through other messages in on that subject. Don't send any replies or take any action, until you have looked through all the items. Most likely what you were going to say or do has already been said or done by one of the other authors already.

Use folders

Don't leave mail in your in-tray after you have read it. If it isn't worth keeping, then delete it. If you need to keep it put it in an appropriate folder. Otherwise your in-tray will become unmanageable in a few days.

Apply filters

Occasionally you will get continual mail you don't want or don't want to look at immediately. The first step if you don't want the mail is to ask the sender not to sent it. However, this may not work and you will get repeated unwanted messages. You can then set a filter on you mail system to remove items from that address or topic from your in-tray. You might have these put straight in the bin, forwarded to someone else, or put in a special folder which you can look at occasionally.

Get less e-mail while 'away'

There are many clever technical ways to read your e-mail while travelling. For several years I have explored the limits of where mail can be read; in hot air balloons, on warships, snow skis and in trains (Worthington, 1994). But you do need a break occasionally. First reduce the volume of mail:

You might want to break the rules about letting mail build up, while away and just handle the essential items. You can forward mail to yourself at another address (useful for when people send work items to your personal address). You can also send yourself e-mail as a way to file electronic documents.

Before going away test that the measures you have put in place actually work. Check the automated reply function is working and is smart enough to only reply to each sender once, not to every message received. Preferably it should not to reply to messages from mailing lists at all.

Check you have actually unsubscribed from mailing lists. A badly behaved auto-reply function could annoy thousands of people, by sending everyone on every list unwanted replies in your name.

Be a critical reader

When reading e-mail retain a sceptical attitude to the message. Remember it may not be from who it appears to be from or they may not be honest. If you get what appears to be an offer that is too good to be true, it probably is.

Look carefully at the address the message claims to be from: is it plausible? Did the sender include non-email contact details you can use for verification? Does the e-mail address match the name and contact details?

Messages which have subject lines like: "Read this!" and "Check this out!" are usually unsolicited advertising material and should be discarded. You may want to tell the sender not to send any more, but first check the address the mail was sent to. If the mail wasn't sent directly to you, but to a mail list, or "exploder" you are on, don't reply. The sender doesn't have your address, just that of the list. Ask the maintainer of the list to do something about it.

Remember that while e-mail messages can be faked, they are formal written communications and can be used as evidence in court. If you receive a message indicating an improper or unlawful activity, you should refer it to the appropriate authorities for investigation.

How to write mail messages

The first and most important skill in writing mail messages is knowing when not to write. Writing a good mail message is a time consuming task: don't start unless the topic is worth spending the time on. A badly written message will do neither you nor the recipient any good and may do a lot of harm. Remember that your casual off-the-cuff message is a written legal document and may be used in evidence against you, perhaps by someone other than the intended recipient.

Don't write messages which will not be read

Most messages are replies to other messages. Remember that you aren't the only one who gets more mail than they can read. Before adding to the problem consider that the recipient most likely will not read the message you are going to send.

Before you write, check if someone else has already said it, or consider if they are likely to. Do you have something useful to contribute, or are you just trying to show off? Do you need to write to a large group, or would a reply to a few individuals do? Do you need to write now, or can it wait? Are you angry or upset and likely to say something you will regret? If so then don't write now, or at least don't send the message now.

Set up your e-mail system

Make sure that your e-mail system is set up to add the appropriate information to messages and test it works. Each message should automatically include your return address, name and a signature block on messages. Check you correct e-mail address is sent and test it by sending someone a message and having them reply.

Set up your name in your e-mail system: The system might have a default setting, like "insert user-name here". Having this sent on the bottom of every message will not enhance your reputation as a professional.

Set the signature block to be included on the bottom of each message: This should include your name, organisation, affiliations, e-mail and postal address, phone and fax number (where appropriate). Don't make the signature more than about four lines long. Very long signatures don't make you look important, just foolish.

Don't rely on the "business card" facility in your mail system: Some mail systems include a facility to send an electronic "business card" with each message. Unless you know your recipients have this facility, don't rely on it. The business card is sent in a format easy for computers to read, but not easy for people.

Set the line length: Some e-mail packages can only cope with about 76 characters on one line of text. Unless you know your recipients can receive longer lines of text okay, set your system to word wrap at 76.

Write messages to be read

Consider you message from the point of view of the reader. Compose a subject line which is a summary of the message and indicates what you want the reader to do. Don't send subjects like "important information" or "please read this", as your message will likely be treated as junk mail.

Use the correct e-mail address to send you mail from. If it is official correspondence from an organisation, use the official e-mail system to send it. Don't use your organisation's e-mail system for personal correspondence, unless this is authorised.

Use a descriptive summary

Include a summary of the message and what action you want the reader to take in the first few lines of the message. Unlike paper correspondence, you should have the conclusion at the start of the message, not the end. Remember that the reader will see only the first 10 to 20 lines of the message on screen. If those lines are not interesting they will delete the message without reading further.

Check the spelling

Check the spelling of the message before sending it. Numerous spelling errors will result in the content of your message being discounted, regardless of its worth. If your e-mail package doesn't include a spell checker, you can copy the text to your word processor for checking.

Use small attachments sparingly, in common formats

A lot of time is wasted by people sending mail messages with large word processing documents attached. Many of these are in formats incompatible with the recipient's system. Most would be better sent just as text e-mail. Many include letterheads with graphics and images of autographs, which add nothing to the information content of the message, but waste network bandwidth and storage space.

If you have a document to send which includes formatting and diagrams essential to the topic, then attach it to the message. However, attachments can cause problems and should be avoided where possible. Describe the attachment in the message and explain why you are sending it. Use common formats for attachments (RTF for word processing documents). Check you actually did attach the attachment, before sending the message.

If a document is an early draft, or doesn't rely on any formatting, then send it as plain text in the body of a message, not as a attachment. If some of your recipients are unlikely to be able to receive attachments, then send the text as well as the attachment. If the document is very large, then just send a summary and offer to provide it on request. If it is public, then put it on the web and include the URL in the mail message. If your organisation has a secure web site, put the large documents there and tell authorised readers it is there with mail.

Some mail packages allow two versions of the message to be sent: one in plain text and the other in HTML. Unless you know your recipients can read HTML in the body of mail messages, just send plain text. Otherwise, your readers get a poorly formatted text message with a whole lot of HTML code appended.

Web addresses in mail messages

A good way to communicate is to send a short e-mail message and provide details on the web. However, you need to include a complete, correct web address. Use a complete Universal Resource Locator (URL) in mail messages, such as

Many e-mail systems can automatically detect web addresses and allow the recipient to open the document just be clicking on it (if your mail system doesn't do this, it would be worth considering an upgrade). In paper correspondence it is usual to leave "http://" off a web address. Don't do this in e-mail, as the software may then not recognise this as a valid address.

Don't type a URL into a mail message. It is very easy to mis-type an address. Open your web browser, bring up the web page on the screen and then copy the URL from the browser to the message. Check for extraneous characters next to the URL, which might be confused for part of the address (such as a period after it). It is very frustrating for your readers to get a URL which doesn't work and embarrassing for you to have to issue an apology and correction.

Quote just enough of messages in replies

Most of the messages you write will be replies to other messages. You need to quote enough of the message being replied to, to make sense of your answer, but no more. The recipient needs some context as they may not have received the original message, may not remember it or know which it is. However, they don't want the whole of their message quoted back at them.

Use the "reply" function on your e-mail system to generate a reply message to the sender. This should prefix the originator's subject with "re:", quote the time and date of the message, add addressees and quote all the text of the original message. If you mail system doesn't have this function, upgrade to one which has. Some mail systems quote the original message at the end of the reply and don't let you easily edit it. If you have one of these systems, it is time to get a new e-mail product.

Don't send back the whole of a message with a reply, this is calculated to annoy. Cut the original message down to the essential points you want to address.

Address each point in the original message, in the order given. If there is a general point you want to make, then make that first. If you were asked to comment on a document, then give suggested alternative wording, rather then just general comments.

Check what other comments have already been made on this subject. Is what you are going to say already been said? You might want to summarise several responses from others and add something extra, rather than send several replies.

Know who you are writing to and reply to the minimum number

Before you send a reply, check who it is going to: do you need to reply to everyone on the list? Do you know who these people are? Is this a public mailing list which you want to be quoted on? Are these people from outside your organisation? Is the sender's address genuine or is the message fraudulent?

Do not reply in haste or anger

I make it a practice to wait until the next day before sending most mail messages. Before despatch I review each item and frequently make changes or delete replies. If your e-mail system does not allow you to hold items for later despatch, then upgrade to one which does. This can save much embarrassment.

Occasionally you will want to write an angry and impassioned mail message. Write it, but don't send it until you have calmed down. It is almost never a good idea to send an angry message. Remember that these are formal written communications and you can face civil and criminal court proceedings as a result of an e-mail message.

Keep the messages you send

If it is worth writing a message, it is worth keeping. Create folders for topics and keep a copy of mail sent in the appropriate folder. Don't leave mail in the out-tray as it will quickly become unmanageable.

Mail messages can make or break you

This may all sound like hard work for doing something as easy and casual as sending a mail message. However, consider that e-mail will be the way many (perhaps most) people know you. You are not sending e-mail for entertainment, but for serious business as a professional. Your professional reputation can be enhanced with good e-mail communication or destroyed by poor communication.

Usenet News and mailing lists

Electronic mail lets you send a message to a person or a particular list of people. But you can use other Internet tools to discuss a topic with whoever has registered interest. For this article I will call these tools "Internet Groupware" (IG): Usenet News ("news"), automated mailing lists and web based discussion groups.

There are proprietary products which provide sophisticated "groupware" for a small group of people in one organisation. Internet Groupware is has fewer features, but is already in use by millions of people around the world. Its cheap, easy and is good enough for many routine tasks. But it takes some practice to use effectively and to avoid making a fool of yourself in front of thousands of people.

One often overlooked point is that you can use the same Internet tools for private discussions, in the workplace or for informing your clients, as well as for public discussions. You might not need buy an expensive proprietary groupware product, which uses up system facilities and takes extra time for staff to learn. You might save on letters, faxes and meetings with your clients by providing them with a simple on-line forum, using the Internet connection they already have.

Talking the Topic

Whatever the technology the purpose is the same: to communicate with a group of people interested in a topic. With e-mail you explicitly select the group of people to communicate with by addressing a message to them. With groupware you "post" an item to a topic and whoever has registered for the topic receives the information. You do not know exactly who will get the information.

You must be even more careful when reading or writing items than with ordinary e-mail. Before posting an item, ask yourself: is it relevant to the topic? who is this going to?, is this a public group?, will my boss object?, who will own the posting?, will I get hate mail?

If you follow the guidelines you should be okay. I have posted thousands of items over about seven years and only get one or two nasty replies a year. About twice a year I have to apologise for an inappropriate posting and I once posted something my employer objected to. For these small negatives I have received an immense amount of valuable information in response to items posted. Also I have provided valuable publicity for the ACS, my employer and myself. I receive several "thank you" replies a week and several requests for follow-up information each day. Some responses are for items I posted years before, but still in archives around the world and of interest to someone.

When you find you have sent something out which people object to:

Groupware Facilities

Whatever the technology you are using the following facilities are provided: Some extra facilities you might get: The interface for mailing lists is via messages sent to a special address. Usenet news requires specialised software. Web forums use web forms as the interface.

Mailing lists don't require any extra software or effort to collect postings (they arrive in your mail). However, sending commands to the mail server via e-mail is clumsy and your mail box can quickly fill up with unwanted postings. But I find lists very useful for daily announcements and discussion.

It is easier to register for new topics using the Usenet news and the items don't clog your mailbox. But you have to remember to check regularly for new items. I use news groups for announcements, more than for serious discussion.

Web forums provide additional facilities, but there are no standards yet. You may have to enter a user-id and password to access the forum, making it cumbersome. So far I haven't found web based forums much use for anything.

All three technologies can be interconnected, with the one topic available as a list, a news group and web forum at the same time.

What to use it for

I use news and mailing lists to: The simplest use of groupware is to distribute routine information on a topic. This frees the sender from having to keep a distribution list of who to send the information to. People can register and un-register as they need. You can join a join a list to collect information. First just see what information "goes past" and perhaps have a look in the archive for relevant information. Then post a question asking for information. Make sure the request is relevant to the topic, is on a specific subject, does not sound not too mercenary and offers the participants something in return.

The worst posting are those off the topic, asking for something with no reward: "Can anyone from the give me some material for my university assignment on Canadian pay TV?".

I regularly use groupware to prepare policy material for the ACS and my employer. To do this I first research the issue. Then I prepare a Request for Information (RFI). This says what I want to know, why I want to know it, what I have already found out, when I want it and what those who help will get in return.

The usual rewards I offer in return for assistance are to promote the contributor's views and to provide a summary of what was found. Many people are willing to contribute their ideas for free. Some want acknowledgement in the final document and some want the opportunity to contribute anonymously. Many appreciate receiving a copy of the final document.

Offering something in return is very important. Why should someone else do your work for you for free? I receive requests for assistance from academics conducting research on IT. I used to provide assistance freely, but never seemed to hear anything back from them. Then I started asking them to provide me a copy of their report. I still didn't get anything. Now I ask if they have published reports before, if this new research will be made public and if so on what date? With undergraduate students I ask them to give me a copy of their preliminary literature search, to demonstrate they are serious about the work.

Before discussing something on-line, check you are in a discussion topic and you are welcome. Some topics are just for announcements, some are for specific groups and there is another associated place to discuss the issues. I once posted a message to a group discussing women in science, was politely told the group was for female scientists only, apologised and left rapidly.

ACS use of groupware

The ACS has two news groups: for general announcements and discussion and for announcing books available for review in the Australian Computer Journal. These are un-moderated lists.

The ACS also has a number of electronic mailing lists for use by members, staff and committees. The ACS National Council meets twice a year to decide major policy matters. In between we discuss issues on a closed mailing list. While not a formal part of the decision making process, it has proved very useful for information, discussion and consultation. I expect that it will take the ACS another year to be fully comfortable with this way of working and it will then be the primary means of running the organisation.

Use It Now

By using existing groupware you can make yourself and your organisation better known, more informed and better run. Use the existing tools for what they are good for now. Don't wait for some grand groupware of the future. You will still have to learn the basic techniques to use an advanced product and you will find many people you need to collaborate with don't have more than the basic tools anyway. The world is not going to convert to the one proprietary product that you spent so much money on: they already have the Internet.

The Web

The web is the only bit of the Internet most people know of. However, you should first master electronic mail and newsgroups before preparing web documents. Many of the same concepts of reading and writing apply.

The web builds on e-mail and newsgroups adding document storage, more sophisticated formatting, hypertext linking and a universal user interface for computer applications.

With the web you will have to face problems of volume of information, permanency and complexity, greater than those of e-mail. There is an array of software which the vendors will claim will remove all your problems. However, these tools may just get you into more trouble more quickly. Applying simple information management techniques to avoid a problem is better than applying tools to fix the problem.

How to read web documents

There are millions of documents on the web. The problem is finding the information you want and verifying its accuracy.

When someone gives you a Universal Resource Locator (URL) address for a web page, examine the details. First, is it complete? Many addresses given verbally or in a printed document don't work. Addresses can be incomplete or incorrectly transcribed. While you still have the source of the address available (for example a person), check the address is syntactically correct.

If the address looks syntactically correct, is it plausible? Most URLs include the country, type of organisation and the organisation acronym. Is the country appropriate? It should be "AU" for an Australian organisation. Is the domain type relevant? It should be "GOV" for a government organisation, or "COM" for commercial. Does the organisation acronym match the organisation? For example suggests this is the home page of the ACS (".acs.") and it is a non-commercial organisation (".org.") in Australian (".au").

Open the document in your browser and look at the top and the bottom of the page. These should indicate who the page is from and their contact details. Are these details consistent with what the address indicates?

Who prepared the document. Who sponsored it? When was it last updated? Is there a link from a web page you trust?

If there are any inconsistencies, open the source code for the comment and examine the comments and meta-data tags in the head section. The meta-data and comments (if present) should match the visible details of the document.

Sometimes legitimate pages are at odd locations. For example at some time the Canberra Tourism, ACT Government, SBS and AIIA home pages were under my account at ACSlink. This was officially sanctioned and reflected both in the visible content and the comments.

Web search engines are very useful for finding documents. There are specialised engines for particualr topics (MADDEN, 1996). The average user will just type in as many words as they can think of. You should be able to do a bit better, applying professional skills in information retrival, using boolean search syntax. Some search engines allow meta-data searches for more precise control.

To save on bandwidth, turn off graphics in your web browser. If there is a page which doesn't make sense, then turn on graphics just for that page. Also you might want to tell the owner of the page that their design needs to be improved, as there are some people who don't have the option of graphics (such as the blind).

How to write simple web pages

To prepare a web page:

The hardest part in the process is to obtain the content. Converting to web format and putting the pages on-line is easy. The steps many people forget are to tell others where to find the web page and to then maintain it.

Unless you are going to publish thousands of documents or are a tech-head there is no point in running your own web server: get someone else to do it. If you have direct acces to the web server, you use an FTP utility to upload your documents. The alternative is to email them to the webmaster.

The future: Real time, On-line, All the Time?

At the time this was being finalised (August 1998), I had just purchased a new computer capable of using video, sound and performing encryption. I want to experiment with delivering presentations and interacting with colleagues via the 'net, using audio, low resolution video and digital presentations. Also it should be possible to start using digital certificates for signing e-mail messages and web pages. I hope to be able to report the results of this work at the DAMA'98 conference.

Internet Videoconferencing

In theory, a dial-up Internet connection should be adequate for discussion or a remote presentation. This could use the narrow-bandwidth options of the ITU-T "H-Series" videoconferencing standards (ITU-T, 1997). These standards provide for low bandwidth audio, video, shared white-board and remote application display and are implemented in a number of low cost Internet based products.

Transmitting efficient, high quality, digital "slides" should remove the need for high resolution video and thus make video conferencing a practical tool for everyday use. Video would only be used to show a postage stamp image of the remote presenter, while slides would be sent separately using remote application display.

Digital Certificates

Proposals for the implementation of a public key authentication framework have the promise of providing a way to send information securely over the Internet and to authenticate documents on the web (SA, 1996). But how practical are these proposals?

Australia Post are now offering a KeyPOST service, issuing digital certificates through PostShops (Keypost , 1998). On Tuesday 18 August I applied for a personal certificate ($20) to see how practical the process is. Exactly what happens next, or when, is not clear.


The Internet is a new medium and so needs a new form of literacy. Information professionals have an obligation to demonstrate competence an leadership in the use of this technology. There are many limitations with the Internet as it is now, however, it is well worth using for what it is good for: routine, not very secure communication. Professionals need to learn their skills with the technology which is available now.

About the Author

Mr Worthington is Special Adviser for Internet/Intranet Policy, with the Australian Department of Defence and Immediate Past President of the Australian Computer Society. Information Age magazine lists Mr. Worthington as one of the 10 most influential IT&T people in Australia in 1998. His work since 1994 has been on the policy and practice of implementation of the Internet, including appearances before three Senate hearings. He established the first web home pages for the ACT Government, the Special Broadcasting Service, Australian Information Industry Association and the National Press Club.



Thanks to Mike Lean, QUT, for reviewing the document and for extensive suggestions.

See also