Our library has a pretty well-placed link on the university home page, so I
can't complain there.

The library website is the home page on the computers within our library
and commons buildings, so students can get right to their research.

I see no reason you should have the site under lock and key unless you
don't require users to login to access databases and other vendor-based
resources. Many libraries I've seen have a setup where they allow the
public to access the item records or indices for most resources, but then
require authentication for full-text viewing.

We share a server with our main institutional CMS, but we don't like the
CMS, so we're the only department that is allowed to do our own thing web
design and development-wise. We pushed for Drupal, but can't go that route
due to security issues (or so they say). So I'm literally hand-coding our
entire library website until they see that Drupal (or something similar) is
the answer to all their problems! I certainly agree that many institutions
don't understand the complexity of the modern library website, as I think
Nina alluded to above.



On Thu, Dec 19, 2013 at 1:47 PM, Lisa Rabey <[log in to unmask]> wrote:

> On Thu, Dec 19, 2013 at 1:27 PM, Miles Fidelman
> <[log in to unmask]> wrote:
> > Then again, how many university libraries can't be found by
> > library.<institution>.edu
> >
> I asked the network people at one of my institutions why it was
> and not, and was told the
> was orignally slated for the library school, then it
> was used for internal use only for computer naming schemea for the
> universities library system, not for web services.
> I don't agree should be a standard, but do agree
> whatever web services topography is deployed it should be consistant
> with that institutions layout.
> -Lisa
> Lisa M. Rabey | @pnkrcklibrarian
> ------------------------------------------------------------------------------------
> An Unreliable Narrator:
> Cunning Tales from a Systems Librarian: