[WEB4LIB] Lobbying for a dedicated web server

[Karen Harker]

I would expect human resources and support issues to be raised.  Adding
another box to their collection means something else they have to run
regular and ad-hoc maintenance.  Security may still be another issue, as
it is yet another potential hole to keep account of.  Consider the
additional work if you plan on adding more "goodies" which will also
need to be maintained and watched-over. 

I would suggest you appeal to a higher level than the IT staff. This
way you can address information management & security issues as well as
promote the advantages you expect to gain. The IT staff probably don't
give a hoot as to the enhanced services you can provide if it means
having to do more work.  But if you can convince your campus
administration that the added services will add real value to the
faculty, staff, and students, they may be more likely to support your
initiative. 

You may also try to show what other university libraries have done,
particularly from competing or slightly higher-ranking institutions. Our
Web development unit tried a while back to lobby for our own Web server,
but between resistance from our campus info management and library info
management groups, we were unsuccessful.  However, we are able to use
certain tools such as MS SQL Server and Cold Fusion, to enable a dynamic
Web site.  So you may need to compromise and accept additional
functionality on the current server.

My thoughts...


>>> Andrew Darby <adarby at ithaca.edu> 9/3/2004 12:18:39 PM >>>
Hello, all.  I'm at a smallish academic library, and currently we have
a
little folder on the university's web server, without access to
goodies/basic human necessities like PHP and MySQL.  As such, we are
about to lobby for our own web server, presumably to be hosted by
campus 
in their climate controlled room.

My question, then, is:  What sort of resistance should I expect?  What
sorts of concerns are likely to be voiced (and what are reasonable
countering arguments)?

Perhaps I am wrong, but if the IT folks

1. do the initial setup of a LAMP (Linux/Apache/MySQL/PHP)
environment,
with the security to their liking

and 2. integrate this box into their backup routine (i believe they do
a
middle of the night chron job)

there should be little or no overhead on their part.  By gum, it would
be one less thing for them to worry about! My recollection from a
previous incarnation, is that Apache servers are pretty stable, and
don't require much (if any) maintenance . . .

And as a bonus, in the unlikely event we do something stupid and crash
the server, the campus at large is insulated.  (We currently have full
access to the library folder on the existing server.)

Any thoughts, suggestions, etc.?

Thanks,

Andrew Darby






Karen R. Harker, MLS
UT Southwestern Medical Library
5323 Harry Hines Blvd.
Dallas, TX  75390-9049
214-648-8946
http://www.utsouthwestern.edu/library/