Re: [CODE4LIB] CMS selection

[Gregory Markus]

I had a conversation with the developers from Oslo Public Library who have
chosen Koha for their new CMS. Not sure if it can handle your needs but you
can read their blog about the process here

and a little interview with one of their developers here
.

Curious to hear what you all decide to go with!

-greg

On Mon, Apr 6, 2015 at 12:58 PM, Ben Wallberg  wrote:

> We use Hippo at the University of Maryland Libraries, please see my blog
> post ³Why Hippo CMS² [1] on why it was selected.  That post is now a year
> old and I would say that despite some challenges we are still satisfied
> with our selection.  I¹m happy to talk with anyone who would like more
> information.
>
>
> [1] https://dssumd.wordpress.com/2014/01/27/why-hippo-cms/
>
> Ben
>
> --
> Ben Wallberg, Manager
> Software Systems Development and Research
> Digital Systems and Stewardship
> University of Maryland Libraries
> wallb...@umd.edu
> 301-314-6010
> http://lib.umd.edu/dss
>
>
> On 4/2/15, 11:03 AM, "Sanchez, Edward L." 
> 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
> >edward.sanc...@mu.edu
> >W: 414-288-6043
> >M: 414-839-9569
>



-- 

*Gregory Markus*

Project Assistant

EuropeanaTech Community Manager

*Netherlands Institute for Sound and Vision*
*Media Parkboulevard 1, 1217 WE  Hilversum | Postbus 1060, 1200 BB
Hilversum | *
*beeldengeluid.nl* 
*T* 0612350556

*Aanwezig:* - ma, di, wo, do, vr

Re: [CODE4LIB] CMS selection

[Ben Wallberg]

We use Hippo at the University of Maryland Libraries, please see my blog
post ³Why Hippo CMS² [1] on why it was selected.  That post is now a year
old and I would say that despite some challenges we are still satisfied
with our selection.  I¹m happy to talk with anyone who would like more
information.


[1] https://dssumd.wordpress.com/2014/01/27/why-hippo-cms/

Ben

-- 
Ben Wallberg, Manager
Software Systems Development and Research
Digital Systems and Stewardship
University of Maryland Libraries
wallb...@umd.edu
301-314-6010
http://lib.umd.edu/dss


On 4/2/15, 11:03 AM, "Sanchez, Edward L." 
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
>edward.sanc...@mu.edu
>W: 414-288-6043
>M: 414-839-9569

Re: [CODE4LIB] CMS selection

[Will Martin]

My current institution, the University of North Dakota, adopted 
OmniUpdate as a campus-wide CMS four years ago.  On balance, I have not 
been happy with it.  It has not been something to work with, but 
something to work around.


In particular, it has made it impossible for me to have a proper 
testing/development set up.  Although OmniUpdate does have a built-in 
split between a staging and a production server, it suffers from a 
crucial flaw in that PHP is not executed on the staging server.  If you 
are working with PHP, as I primarily do, then the only way to find out 
whether your PHP is functioning correctly is to publish it to the 
production server.  This is bad practice.  Testing things without 
potentially breaking the live site requires making duplicate copies of 
the files to be edited, and yields a workflow like this:


1) Make the change to the testing file on the staging server.
2) Publish the testing file to the production server.
3) Refresh the page to find out if it worked as expected.
4) Correct any errors and repeat steps 1-3 until satisfied.
5) Copy the code from the testing file on the staging server to the real 
file on the staging server.

6) Publish the real file from staging to production.
7) Go double check to make sure it's working.

As workflows go, I find it annoyingly cumbersome.  At one point it was 
taking me something like 9 clicks to publish a file, every time I wanted 
to test something.  That has improved with the most recent version, but 
the fundamental problem of PHP not executing on the staging server is 
still there.


OmniUpdate's assumption that "content = files" also annoys me.  In most 
CMSs, if you are a content producer, you go to the page you're working 
on, edit it, save it, and publish it when done.  You never have to think 
about how the information is stored, because all of that is handled by 
the CMS, which tucks it away in a database.  In OmniUpdate, a large 
portion of the interface is devoted to creating, editing, and managing 
files and folders.  You can't avoid dealing with them.  Compared to the 
editing experience in most other CMSs, it seems a strained and pointless 
attempt to extend the conventions of desktop word processors onto the 
web.


I do not have top level access to OmniUpdate, and I can't tell you much 
about how it works from a system management perspective.  For example, 
I've never had to edit the XSL transforms that are used to combine the 
content (stored in XML files) with templates to produce a finished page. 
 If you would like, I can refer you to colleagues from the university 
web team who work more closely with OmniUpdate at those levels.  If you 
would like to do so, please email me off-list.


Will Martin


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
edward.sanc...@mu.edu
W: 414-288-6043
M: 414-839-9569

Re: [CODE4LIB] CMS selection

[Jason Bengtson]

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. <
edward.sanc...@marquette.edu> 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:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
> Jeffrey Sabol
> Sent: Thursday, April 2, 2015 8:43 PM
> To: CODE4LIB@LISTSERV.ND.EDU
> 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. <
> edward.sanc...@marquette.edu> 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
> > edward.sanc...@mu.edu
> > W: 414-288-6043
> > M: 414-839-9569
> >
>

Re: [CODE4LIB] CMS selection

[Sanchez, Edward L.]

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:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Jeffrey 
Sabol
Sent: Thursday, April 2, 2015 8:43 PM
To: CODE4LIB@LISTSERV.ND.EDU
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. < 
edward.sanc...@marquette.edu> 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
> edward.sanc...@mu.edu
> W: 414-288-6043
> M: 414-839-9569
>

Re: [CODE4LIB] CMS selection

[Jeffrey Sabol]

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. <
edward.sanc...@marquette.edu> 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
> edward.sanc...@mu.edu
> W: 414-288-6043
> M: 414-839-9569
>

[CODE4LIB] CMS selection

[Sanchez, Edward L.]

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
edward.sanc...@mu.edu
W: 414-288-6043
M: 414-839-9569