LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  April 2015

CODE4LIB April 2015

Subject:

Re: CMS selection

From:

Will Martin <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Fri, 3 Apr 2015 14:00:20 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (85 lines)

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
> [log in to unmask]
> W: 414-288-6043
> M: 414-839-9569

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager