UNM used Cascade Server. That CMS is expensive, but at least it's terrible.
I built a site for OU in libguides CMS; I like springshare and once you
understand how to use the system to get around the limitations in any CMS,
I think it worked pretty well. I've done some Drupal work and have no love
for it. Here at HAM-TMC we use WordPress, which has worked out pretty well.
In general it's a reasonably robust system for many purposes and regular
developers and power-users can do what they need to do by working outside
the gui and editing source code directly. I haven't been using it here very
long, but it's been pretty solid from what I've seen so far. At OU I also
experimented with MODX . . . I really liked that CMS (it's really more of a
framework, but it accomplished some of what you need from a CMS), but we
came to the conclusion that it would have been too difficult for some of
our regular web editors to work with. If I had all my druthers, MODX would
probably be my first choice of the systems I've worked with . . . but
that's in an environment where content editors were less of a consideration.

Best regards,
*Jason Bengtson, MLIS, MA*

Innovation Architect
The Texas Medical Center Library
1133 John Freeman Blvd
Houston, TX   77030
http://library.tmc.edu/
www.jasonbengtson.com

On Thu, Apr 2, 2015 at 11:27 PM, Sanchez, Edward L. <
[log in to unmask]> wrote:

> Jeffrey,
> Many thanks for the frank comments.  I'm going to forward your email to
> the project manager and ask for a follow up with you on the Loyola Law
> leads.
> Best regards,
> Ed
>
> -----Original Message-----
> From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of
> Jeffrey Sabol
> Sent: Thursday, April 2, 2015 8:43 PM
> To: [log in to unmask]
> Subject: Re: [CODE4LIB] CMS selection
>
> My previous place of employment, Loyola Law School (
> http://www.lls.edu/resources/library/), switched to Terminal 4 about 4
> years ago, it was selected by the HR department for the entire campus.  The
> Library had a lot of problems tailoring it to the needs of the Library, and
> in my opinion pretty much any library that is forced into predesigned
> templates will never really have a user friendly website.  One of the
> bigger problems is the huge header menu that was forced on every
> department.  Shortly before I left, the Law School hired a full time Drupal
> developer to create a Drupal intranet and additional webpages that were not
> able to be made in Terminal 4 (If I remember correctly php and javascript
> were not supported).  This was 4 years ago and I am sure a lot of things
> have changed so I encourage you to check out their website and if you are
> seriously considering Terminal 4 I can put you in touch with several people
> that still work there.
> Thanks,
> Jeffrey Sabol
> Systems Librarian
> Marymount California University
>
> On Thu, Apr 2, 2015 at 8:03 AM, Sanchez, Edward L. <
> [log in to unmask]> wrote:
>
> > Colleagues,
> > I am on a campus-wide team charged with evaluating and selecting a new
> > CMS system to replace our centralized Apache/PHP/Includes-based web
> > server infrastructure.
> >
> > Our Libraries and University Archives have relied on the existing
> > centralized system and would like to contribute to the selection of a
> > new CMS-based platform that will position our library well into the
> future.
> >
> > Currently the list is down to four vendors:
> >
> > Hippo
> > OmniUpdate
> > Terminal 4
> > Jahia
> >
> > If any of you have experience with any of these systems you wouldn't
> > mind sharing please contact me off list.
> >
> > Your feedback would be appreciated.
> >
> > Best regards,
> >
> > Ed
> >
> > Edward Sanchez
> > Head, Library Information Technology
> > Marquette University
> > 1355 West Wisconsin Avenue
> > Milwaukee, WI 53201
> > [log in to unmask]
> > W: 414-288-6043
> > M: 414-839-9569
> >
>