http://blog.publish2.com/2012/02/19/old-dogs-new-tricks-and-crappy-editorial-systems/ Thu, 16 May 2013 03:34:04 +0000 hourly 1 http://wordpress.org/?v=3.1.2 http://blog.publish2.com/2012/02/19/old-dogs-new-tricks-and-crappy-editorial-systems/comment-page-1/#comment-3039 Legacy Newspaper Editorial Systems Really Are Killing the Industry - Publish2 Blog Thu, 16 May 2013 03:34:04 +0000 http://blog.publish2.com/?p=1887#comment-3039 [...] It’s not at all surprising that legacy print editorial systems in the “cloud” are failing, systemically, at every major news organization that has rolled them out. It’s not what they were designed to do. [...] [...] It’s not at all surprising that legacy print editorial systems in the “cloud” are failing, systemically, at every major news organization that has rolled them out. It’s not what they were designed to do. [...]

]]> http://blog.publish2.com/2012/02/19/old-dogs-new-tricks-and-crappy-editorial-systems/comment-page-1/#comment-3016 Scott Karp Wed, 22 Feb 2012 18:35:00 +0000 http://blog.publish2.com/?p=1887#comment-3016 John, the workflow that you have, i.e. create content in the print CMS, then send to the web, is not what I'm talking about here.  That workflow has been around for years.  I'm talking about true digital-first workflows, where content is posted to the web first, then flowed back into the print CMS, without copying/pasting or other time-wasting inefficiencies.  And I'm talking about connecting many newsrooms with disparate systems and workflows into an efficient and scalable internal content network (where your legacy vendor has had some notable failures -- Google their new product name and you'll find some examples).  And I'm talking about seamlessly integrating content from outside the newsroom from a range of new sources to create new digital products. John, the workflow that you have, i.e. create content in the print CMS, then send to the web, is not what I’m talking about here.  That workflow has been around for years.  I’m talking about true digital-first workflows, where content is posted to the web first, then flowed back into the print CMS, without copying/pasting or other time-wasting inefficiencies.  And I’m talking about connecting many newsrooms with disparate systems and workflows into an efficient and scalable internal content network (where your legacy vendor has had some notable failures — Google their new product name and you’ll find some examples).  And I’m talking about seamlessly integrating content from outside the newsroom from a range of new sources to create new digital products.

]]> http://blog.publish2.com/2012/02/19/old-dogs-new-tricks-and-crappy-editorial-systems/comment-page-1/#comment-3015 John Webster Wed, 22 Feb 2012 17:18:00 +0000 http://blog.publish2.com/?p=1887#comment-3015 Nonsense. No supporting specifics. Bears no resemblance to the reality with which I'm personally familiar. And whose hidden, competing agenda does this oh-so-trendy rhetoric support? I'm a newspaper systems expert, working daily with one of the industry's best publishing system vendors. My newspaper's system uses advanced XML protocols to integrate with our progressive, open-source web CMS. This "legacy" system is extremely stable  with excellent support and regular updates. Nonsense. No supporting specifics. Bears no resemblance to the reality with which I’m personally familiar. And whose hidden, competing agenda does this oh-so-trendy rhetoric support? I’m a newspaper systems expert, working daily with one of the industry’s best publishing system vendors. My newspaper’s system uses advanced XML protocols to integrate with our progressive, open-source web CMS. This “legacy” system is extremely stable  with excellent support and regular updates.

]]> http://blog.publish2.com/2012/02/19/old-dogs-new-tricks-and-crappy-editorial-systems/comment-page-1/#comment-3014 John Hill Wed, 22 Feb 2012 00:22:00 +0000 http://blog.publish2.com/?p=1887#comment-3014 I totally agree that things are broken and I keep hoping some vendor will come out with a solution that makes sense in terms of truly building with digital-first workflow in mind. That said, I must point something out, though. I'm a big fan of John Paton and what he's advocated for this industry, but Paton's JRC also recently opted to go with Saxotech's systems for their publications (<a href="http://www.newsandtech.com/dateline/article_c45b7156-1cec-11e0-8ebc-001cc4c03286.html" rel="nofollow">http://www.newsandtech.com/dateline/article_c45b7156-1cec-11e0-8ebc-001cc4c03286.html</a>). We use Saxo Editorial and used to use the Online product. I know they're migrating toward the cloud, but let's face it: it's an expensive old school "legacy" solution. It is "big iron." Just sayin'. I totally agree that things are broken and I keep hoping some vendor will come out with a solution that makes sense in terms of truly building with digital-first workflow in mind. That said, I must point something out, though. I’m a big fan of John Paton and what he’s advocated for this industry, but Paton’s JRC also recently opted to go with Saxotech’s systems for their publications (http://www.newsandtech.com/dateline/article_c45b7156-1cec-11e0-8ebc-001cc4c03286.html). We use Saxo Editorial and used to use the Online product. I know they’re migrating toward the cloud, but let’s face it: it’s an expensive old school “legacy” solution. It is “big iron.” Just sayin’.

]]> http://blog.publish2.com/2012/02/19/old-dogs-new-tricks-and-crappy-editorial-systems/comment-page-1/#comment-3013 Matt Terenzio Mon, 20 Feb 2012 14:15:00 +0000 http://blog.publish2.com/?p=1887#comment-3013 That's right on the mark, Scott. If the process has changed, then the software to create it needs to be radically different. In fact, start by not assuming their is a single cohesive end product at all. Perhaps it is more like re-directing existing rivers and streams of information flow that is how a journalist often works in the future. But you can go pretty far using tools out there, and will need to incorporate third party tools.  It's impossible to do all the innovation within one piece of software. And yes, if you just spent a million bucks last year on an out-dated system, it's unlikely that you will admit it's not the right tool this year. Hopefully, next year. ; ) That’s right on the mark, Scott. If the process has changed, then the software to create it needs to be radically different. In fact, start by not assuming their is a single cohesive end product at all. Perhaps it is more like re-directing existing rivers and streams of information flow that is how a journalist often works in the future. But you can go pretty far using tools out there, and will need to incorporate third party tools.  It’s impossible to do all the innovation within one piece of software. And yes, if you just spent a million bucks last year on an out-dated system, it’s unlikely that you will admit it’s not the right tool this year. Hopefully, next year. ; )

]]>