Subject: | |
From: | |
Reply To: | |
Date: | Tue, 12 Apr 1994 11:28:46 EDT |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
----------------------------Original message----------------------------
I received this today from pacs-l and I thought that some of you
might have relevant comments for this person. I think he needs user
experience stuff as well as the cyberookie stuff. Obviously ;-)
you guys have a lot of user experience with the need for this kind
of information.
Since he's not on this list, please send mail to him directly.
virginia
---------------------------- Text of forwarded message -----------------------
. M1.UH.E
. Bytes omitted to save cyberspace
.
> From: Mike Dorrington <[log in to unmask]>
> Subject: setting up a gopher server
>
> My agency wishes to install a UNIX (IBM AIX) server at it's
> headquarter's office and is exploring options/costs. The
> server would be used as part of the Government Information
> Locator Service (GILS).
>
> GILS is being developed to implement recent federal mandates
> to make government information more accessible, including
> electronic dissemination. GILS would point interested parties
> to federal (and non federal) data/information. GILS data
> standards (Z.39.50) will emphasize "interoperability" and
> accessibility.
>
> We want to get on-line ASAP so a fancy, state-of-the-art
> system is out - for now. For the first year or two, we're not
> expecting heavy traffic or large data storage needs. However,
> we would like some upgrade "margin" , adding options as we
> learn and the number of our field (and private?) servers
> increase.
>
> The headquarter's server would be oriented toward uniquely
> Washington info (e.g. laws, regs, budget, directives, and
> public affairs) but would point to other agency (and
> private?) servers around the country.
>
> Should we use a gopher-based system initially, and add a WWW
> component later? I've also heard of "consolidated" gopher/WWW
> servers but the WWW option may be too much too soon.
>
> Ideas regarding internet hookup costs, hardware, software,
> cost information, and REFERENCES would be be appreciated.
> References should be not be too technical (i.e. primers)
> since I'm still a cyber-rookie.
|
|
|