--- title: Blog (27) description: Orbis software and services support mission critical Enterprise Content Management Software, Solutions, Services, and Analytical Software Solutions. (27) --- ## [Principles matter - A successful CMS implementation for publishers](https://blog.orbistechnologies.com/bid/44565/Principles-matter-A-successful-CMS-implementation-for-publishers) Posted by [Lisa Bos](https://blog.orbistechnologies.com/author/lisa-bos) on Mar 25, 2011 2:42:00 PM - [Tweet](https://twitter.com/share) ![XML content management for publishers](https://blog.orbistechnologies.com/hs-fs/file-13544508-gif/images/principlesmatter.gif)The success of a CMS implementation is ultimately determined by thousands of individual choices made every day by team members - developers, PMs, analysts, and so on. Many of these choices are based on design principles with which business managers might strongly disagree but of which they are often unaware. Occasionally one of these decisions has inordinate impact - a complexity of design that results in a complexity of implementation, testing, and maintenance that is radically inappropriate relative to the value of the feature in question. Managers who aren't deeply engaged with their teams tend to over-simplify such discussions by saying things like, "So-and-so engineer always makes things more complicated than they need to be." It's true some engineers are hard to manage (and that some managers start almost every new project with unrealistic expectations, and that some users won't give up complicated requirements). But I believe this difference in philosophy is also in play, and a PM or other manager would do well to understand and talk about how a team's varying philosophies impact its members' choices, and where change might be in order. An interesting article on this topic by Eliot Kimber is [here](http://drmacros-xml-rants.blogspot.com/2010/08/worse-is-better-or-is-it.html). Such discussions might seem esoteric, but they absolutely are not. 0 Comments [Click here to read/write comments](https://blog.orbistechnologies.com/bid/44565/Principles-matter-A-successful-CMS-implementation-for-publishers#comments-listing) Topics: [publishing](https://blog.orbistechnologies.com/topic/publishing), [CMS](https://blog.orbistechnologies.com/topic/cms), [publishing industry](https://blog.orbistechnologies.com/topic/publishing-industry), [XML CMS](https://blog.orbistechnologies.com/topic/xml-cms), [project management](https://blog.orbistechnologies.com/topic/project-management) ## [Learn XML Schemas and DTDs in 5 minutes](https://blog.orbistechnologies.com/bid/44173/Learn-XML-Schemas-and-DTDs-in-5-minutes) Posted by [Christopher Hill](https://blog.orbistechnologies.com/author/christopher-hill) on Mar 22, 2011 12:56:00 PM - [Tweet](https://twitter.com/share) In my[ previous blog post ](https://blog.reallysi.com/bid/43431/Learn-XML-in-5-Minutes)I introduced XML in 5 minutes. As a follow up, here's another 5 minute lesson to understand what an XML Schema or DTD is and what it might mean to end users of XML-based systems. In the previous post we created an XML document to describe a book. Recall that it used tags around the actual content to describe the content.      Alice's Adventures In Wonderland      Lewis Carroll      This book tells the story of an English girl, Alice, who drops down a rabbit hole and meets a colorful cast of characters in a fantastical world called Wonderland. We also learned how representing content in this way allows us to dramatically reduce the effort required to support multichannel publishing. It also helps a great deal with automation and moving content between systems or organizations as it eliminates some of the issues of file formatting. What would happen to our stylesheet if someone decided to use different tags to label their content?      Alice's Adventures in Wonderland      Lewis Carroll      This book tells the story of an English girl, Alice, who drops down a rabbit hole and meets a colorful cast of characters in a fantastical world called Wonderland. What we called author in one document we called writer in another. This inconsistency might be small now, but if we didn't restrict what people named things in our XML we would have to support a potentially endless list of tags. In the[ previous article ](https://blog.reallysi.com/bid/43431/Learn-XML-in-5-Minutes)we wrote rules for how to make our books look good on a page. If we can't predict what tags (labels) people are going to use - such as author - then it becomes nearly impossible to reliably write rules. So even though XML helps us get a consistent base format for content, we need more help to get predictability and consistency. Enter the concept of a DTD or Schema. DTDs and Schemas are ways that systems can impose rules on the XML itself. You can describe what tags can be used, where they can be used, and put restrictions on the content of those tags. There are two different standards for describing these restrictions: Document Type Definition (DTD) and XML Schemas. We won't get into the syntax or pros and cons of the two approaches. For our 5 minute lesson we can just assume they both are ways to enforce consistent labeling of our tags in our XML documents. Here in English is how we might communicate the requirements for our flavor of XML: 1. Put everything inside a book tag. You can only have one of these. 2. The first thing you put in a book is a title tag containing the title text. You cannot leave this out. 3. The second thing you put in a book is an author tag containing the author name. You must have at least one author. If there are more, you can repeatedly add more tagged authors. 4. After all the tagged authors, you can add a summary tag. This is optional - leave it out if you want. But you can have at most 1 summary. This is essentially what a DTD or XML Schema does, although they do this in a language friendlier to computers. ![DTDs/XML Schemas allow you to specify the rules for the structure of your XML documents](https://blog.orbistechnologies.com/hs-fs/file-13544126-png/images/dtd-schema-validity-resized-600.png) *You can think of XML Schemas or DTDs as a means to create a template that all valid documents must follow* * * These rules can now be applied to the two examples above. The first example follows the rules, so we would say that the first XML document is *valid*. That means it conforms to the rules. The second document, when tested with the above rules, would be *invalid*. The presence of tagged content labeled "writer" is not allowed by the rules.  In the XML world, XML Schemas or DTDs are used in a lot of scenarios, including: - XML editors know what is allowed by the rules and prevent writers from making mistakes - XML programs test incoming content and indicate when the rules are being broken, preventing formatting errors - XML stylesheets can be much more easily written as they only process valid content and don't have to worry about rulebreakers - If I want to merge my book content with yours, we can look at the rules and decide what adjustments will need to be made to bring our rules together - Industries can agree on the rules for types of content. So we might create a set of rules to represent newspaper articles, adopt it as an industry standard, enabling anyone to easily exchange newspaper articles without having to modify the content. So when you hear someone rambling on about an XML Schema or DTD, they are really just talking about the rules governing how the particular XML document is to be structured. That's XML Schemas and DTDs in 5 minutes. In the coming weeks watch the blog for more quick lessons on XML-related technologies. 1 Comment [Click here to read/write comments](https://blog.orbistechnologies.com/bid/44173/Learn-XML-Schemas-and-DTDs-in-5-minutes#comments-listing) Topics: [publishing](https://blog.orbistechnologies.com/topic/publishing), [XML](https://blog.orbistechnologies.com/topic/xml), [XML Schema](https://blog.orbistechnologies.com/topic/xml-schema), [DTD](https://blog.orbistechnologies.com/topic/dtd), [5-minute-series](https://blog.orbistechnologies.com/topic/5-minute-series) ## [Learn XML in 5 Minutes!](https://blog.orbistechnologies.com/bid/43431/Learn-XML-in-5-Minutes) Posted by [Christopher Hill](https://blog.orbistechnologies.com/author/christopher-hill) on Mar 15, 2011 8:24:00 PM - [Tweet](https://twitter.com/share) As product manager for an XML-based CMS, often I find myself answering the question "What is XML?" Not necessarily a simple thing to answer in passing - entire books and courses are dedicated to the subject - but in about 5 minutes most content creators can at least understand at a basic level what XML is all about. Here is my 5 minute XML class to give a first pass at answering this question. At the end most people should have a rough idea of what XML is and can start thinking about its potential.     Take a look at the following text:        Alice's Adventures In Wonderland *by Lewis Carroll* This book tells the story of an English girl, Alice, who drops down a rabbit hole and meets a colorful cast of characters in a fantastical world called Wonderland.        Reading it, you probably can infer that the underlined text is a book title. The italicized text appears to be the author of the book (if you dropped the word "by"). Then there is additional text. If you are familiar with the book, you can tell that the text is not part of the book itself, but appears to be a short summary. We know all of this because of certain conventions we have been taught as well as contextual clues provided by the words themselves.        Let's look at the same text again:       Lewis Carroll **Alice's Adventures In Wonderland** *This book tells the story of an English girl, Alice, who drops down a rabbit hole and meets a colorful cast of characters in a fantastical world called Wonderland.* * * Even though the text looks quite different, we probably could still successfully interpret the author's intent. Now, imagine you have to train a robot to understand these two cases. What rules might you create to "teach" the robot how to decide how to successfully parse these two text examples and understand what parts of the text are titles, author names, and summaries? Even for these two limited cases, the list of rules is going to be quite involved, and will include rules based on formatting, language, and convention. And a robot will have to know that somewhere in the text are the three pieces of content, otherwise it probably has little chance of determining the nature of what it is looking at (Darwin the Jeopardy-playing supercomputer excluded). * * Even if all that was true, errors are likely to creep in. Do your rules allow the robot to understand that "by" is really a formatting cue indicating the following text is an author name? What about the meaning of an underline? Bold? Italics? Each example uses the same formatting cues but in different ways.  * * When you write a document in a word processor or a desktop publishing program you mostly focus on how that text looks. Imagine after all that careful work making the text look right for your printer, you decide your content should appear on a Web site. Suddenly all that formatting needs to be re-worked to take advantage of the conventions of the Web. Now if you want to deliver to an electronic reader or a mobile phone your formatting may again need to be revisited.  * * This is an expensive proposition when you start imagining all of the possible delivery channels that may require formatting changes. For many channels, all that formatting work needs to be scrapped and done again.  * * The answer to this is XML: the extensible markup language. A short way to summarize the promise of XML is that it allows authors to indicate **what the content is** rather than **how the content looks**. XML does this using tags, essentially text-based labels that indicate what a particular piece of data might be. Here is the same example as XML. Even though you may not know anything about XML, you can make sense of this content. * * Alice's Adventures In Wonderland Lewis Carroll This book tells the story of an English girl, Alice, who drops down a rabbit hole and meets a colorful cast of characters in a fantastical world called Wonderland. * * Yes, angle brackets seem a little cold, but notice how they are labels making the meaning of the various pieces of text completely unambiguous. Notice how each tag (i.e. ) has a match (i.e. ). These pairs create a container. Everything appearing between matching tags is considered contained by them. * * Now, imagine you want to deliver the content to a printed page, web site or mobile device. It is much easier now to write a set of rules that indicate how each should be formatted. * * *Rule for :* start a new page *Rule for :* one the first line, output the text as underlined,16 point Helvetica *Rule for <author>:*   start a new line, output the text in italic, 12 point Helvetica *Rule for <summary>: * double-space, start a new line, output the text in 12 point Helvetica * * These rules could be called a *stylesheet*. In reality, stylesheets are written in a more machine-friendly format that are beyond the scope of a 5 minute XML course, but this example should suffice to give you an idea of what a stylesheet's role in creating presentable XML content is.  * * If I had hundreds, thousands or millions of book content items I could use this single stylesheet to output them all and be guaranteed consistency.  * * If I decide I want to switch to a new look for my content, maybe using Garamond instead of Helvetica, then I just need to modify the stylesheet. Notice how the original book content exists completely independently of the formatting. And notice that changing the look of something doesn't require any editing of the original content. * * Suppose I want to deliver my content to multiple channels. Each channel has its own conventions, limitations, and capabilities. People expect different formatting on a mobile phone than on their desktop computer. A web site typically looks different than the printed page. We used to underline book titles in print - but underline means something else on the web so often a different format is used. Helvetica may not even be an available font for many channels.  * * Fortunately, XML makes supporting each unique channel straightforward. Instead of endlessly modifying my content, I simply develop new rules (a new stylesheet, or a variation of an existing stylesheet) for a new channel. The authoring process is unaffected. Existing content does not need to be re-edited to support the new channel. Instead, the new rules are applied to the content generating channel-appropriate output. And as the number of channels expand, XML serves as a content anchor point so that you can adapt content rapidly and in an automated way to the unique requirements of each channel. ![XML as an anchor for multichannel publishing](https://blog.orbistechnologies.com/hs-fs/file-13545052-png/images/xml_single_source-resized-600.png) * * If all of your content were clearly labeled by what it is, it is not nearly as daunting to support new output formats for new opportunities. Instead to a massive conversion of all your formatted content from one format to another, you just have to develop a new set of rules and you are ready to go. * * That's XML in 5 minutes. At least as it impacts content creation and delivery. In the coming weeks I'll be posting additional quick lessons on XML-related technologies. 8 Comments [Click here to read/write comments](https://blog.orbistechnologies.com/bid/43431/Learn-XML-in-5-Minutes#comments-listing) Topics: [ebooks](https://blog.orbistechnologies.com/topic/ebooks), [publishing](https://blog.orbistechnologies.com/topic/publishing), [XML](https://blog.orbistechnologies.com/topic/xml), [5-minute-series](https://blog.orbistechnologies.com/topic/5-minute-series) ## [SharePoint: When did free begin to cost so much?](https://blog.orbistechnologies.com/bid/42928/SharePoint-When-did-free-begin-to-cost-so-much) Posted by [Barry Bealer](https://blog.orbistechnologies.com/author/barry-bealer) on Mar 11, 2011 9:58:00 AM - [Tweet](https://twitter.com/share) ![when did free cost somuch](https://blog.orbistechnologies.com/hs-fs/file-13544242-gif/images/free1.gif)I ran across an interesting blog post by Stephen Arnold who is a longtime industry analyst and consultant that spells out the hidden costs of a SharePoint implementation.  The post is [here](http://arnoldit.com/wordpress/2009/10/18/sharepoint-six-servers-with-massive-cost-burden/).  While free always looks better than paying for software, I think Stephen hits the spot with his assessment.  A free software framework such as SharePoint is great if you plan to keep requirements very simplistic.  As we all know from our own experiences with implementing content management, that is easier said than done.  If you have more complex requirements, maybe a packaged solution such as [RSuite](http://www.rsuitecms.com) makes sense.  Your company's approach to projects, culture to build versus buy, and several other factors need to be considered before selecting a technology and embarking on a content management project.  Whatever approach you take, just be cognizant of hidden costs as Arnold pointed out.  Free software does not always mean it will be cheap to implement and maintain in the long run. 0 Comments [Click here to read/write comments](https://blog.orbistechnologies.com/bid/42928/SharePoint-When-did-free-begin-to-cost-so-much#comments-listing) Topics: [content management](https://blog.orbistechnologies.com/topic/content-management), [Sharepoint](https://blog.orbistechnologies.com/topic/sharepoint) ## [Are publishers working too hard to create PDF and eBooks?](https://blog.orbistechnologies.com/bid/42677/Are-publishers-working-too-hard-to-create-PDF-and-eBooks) Posted by [Marianne Calihanna](https://blog.orbistechnologies.com/author/marianne-calihanna) on Mar 9, 2011 4:42:00 PM - [Tweet](https://twitter.com/share) [![Visit us at Publishing Business and Expo](https://blog.orbistechnologies.com/hs-fs/file-13544560-gif/images/pub_biz_ad.gif)](https://blog.reallysi.com/pub-biz-expo_2011/?utm_campaign=PBE2011-RSI_email&utm_source=email) We recently hosted a great webinar titled, "The Digital Integration: Your Content Anywhere, In Any Format, Anytime." We learned that a large number of publishers are still struggling with how XML fits into their organization. While we view XML as the primordial soup in the publishing world, the reality is that a large number of publishing organizations do not have an XML early (or XML at all) workflow. We can help. [Schedule a meeting](https://blog.reallysi.com/pub-biz-expo_2011/?utm_campaign=PBE2011-RSI_email&utm_source=email) with us at the nation’s largest event for book and magazine publishing executives: [Publishing Business Conference and Expo](http://www.publishingbusiness.com/) and let us show you how some of the leading publishers are using [RSuite ](http://www.reallysi.com/solutions/solutions_rsuite.html)and [RSuite Cloud](http://www.reallysi.com/solutions/solutions_rsuitecloud.html) to stay ahead of the digital revolution. **Hint: **XML is involved but you don't have to tell any of your authors or editors! 0 Comments [Click here to read/write comments](https://blog.orbistechnologies.com/bid/42677/Are-publishers-working-too-hard-to-create-PDF-and-eBooks#comments-listing) Topics: [content management](https://blog.orbistechnologies.com/topic/content-management), [publishing](https://blog.orbistechnologies.com/topic/publishing), [XML](https://blog.orbistechnologies.com/topic/xml), [conference](https://blog.orbistechnologies.com/topic/conference), [Publishing Business Conference and Expo](https://blog.orbistechnologies.com/topic/publishing-business-conference-and-expo) ## [Centralizing metadata, content and assets: Paradise Lost and Regained](https://blog.orbistechnologies.com/bid/41180/Centralizing-metadata-content-and-assets-Paradise-Lost-and-Regained) Posted by [Christopher Hill](https://blog.orbistechnologies.com/author/christopher-hill) on Feb 23, 2011 5:46:00 PM - [Tweet](https://twitter.com/share) I've been working in content management for more than ten years, and thinking back over that time I realized that the dream of a true, standards-based, central repository for all of an organization's assets I naïvely espoused in the late 90s still hasn't become a reality except in the most narrow of applications. When I used to write and teach XML classes I was sure that open markup standards were going to revolutionize the way we created and managed assets. Around 2003 I started to become a bit disillusioned with my vision for content utopia. By 2008 I had all but thrown in the towel. Despite herculean efforts content kept worming its way into proprietary, tactical-level production systems and often was never seen nor heard from again, a victim of legacy of "fire and forget" publishing approaches common prior to the rise of the Internet.   Fortunately, just as I had resigned myself to living in a world of content silos, new strategic ways of managing content started to emerge that rekindled my ideals. The idea is more modest than my grandiose vision of pure standards I once embraced, but offers a new, more practical approach that can survive in the real world.   Rather than insist that every asset be centralized in a consistent, preferably open, format practicality may dictate that we instead work to build a centralized asset repository that shares common representations for all assets. The actual bits and bytes making up the asset (Word documents, InDesign files, photos, videos, etc.) can still be developed and stored in traditional systems where applicable, but a new system takes on the responsibility of cataloging relevant features and details about the asset in a centralized repository. So instead of insisting that every asset be physically managed in a central repository, we instead insist on the much more modest - and realistic - demand that all assets make relevant, common data and metadata available in a consistent format through a centralized system. This distinction means that rather than try to replace the tactical systems we use to create, manage or distribute content we instead develop a parallel, complementary content management strategy that reflects data in these systems and presents a common, consistent view of the asset regardless of type.    So an image file may exist as a TIFF or PSD formatted file in a production system or on some hard drive somewhere, but the centralized repository maintains a record for this image with all of its relevant metadata and a standard image format readily accessible to any system (i.e. PNG, JPG in thumbnail and applicable preview formats). For a lot of applications, centralized lighter-weight representations of content is enough to create new products without returning to . For example, if I want to rapidly re-use images or stories on a new microsite, I don't have to resort to tracking down all of the content in its silos, but instead rely on these common representations to collect the assets together and send them into my Web CMS for the new microsite. Formats, conversions, and so forth can either be provided to the central system through traditional manual conversion or, preferably, through automated mechanisms built in to existing content workflows.   This sort of approach was attempted using search technologies at one time, but lacked an important ability to offer the depth of content management required to not just find the asset but also to be able to use and transform it. It gave us the ability to view the content but not any tools to do anything once we saw it. Search remains important, but a real central repository needs to actually have usable representations of content that can be managed, transformed and distributed as assets on their own. This requires a full content management system.   So my new vision of a centralized asset repository is not the end-all be-all "do everything" system that becomes impossible to design and build, it's a "do-some-things" central system that maintains some consistent, common format that can be readily transformed and transmitted and becomes an organization's strategic content reserve. It can answer questions like "what assets do we have about Egypt?" quickly, and serve as a baseline for those assets so that after finding them they can be used in our various tactical systems.   To build such a thing, consistent representations are needed. When looking for data standards we of course start with XML. When only a binary will do, ensuring that pointers are accurately maintained to the original assets and appropriate renditions of the binaries are created for things like the user interface of the central repository is an obviously useful model. Even if re-work is required the assets are already under active management.    The RSuite Content Management System happens to be a great foundation for building shared, managed centralize repositories of content. The system is flexible, built on an XML standard database with a metadata model that can not only leverage existing metadata but also be extended in arbitrary ways to adapt to evolving requirements. It is built on open standards and is a good corporate citizen, ready to interoperate with existing systems. The native XML database and pointer management features ensure that consistent representations are available. This approach creates a solid foundation for a strategic, centralized asset repository.    Part of my role as Product Manager for Really Strategies will be to focus on the ways that our existing clients have adopted XML-based content management. I'll be reporting in with our client success stories at building these content repositories here on the blog.    Does your organization have a vision for managing content strategically? It’d be great hearing how others are working to address this challenge. 0 Comments [Click here to read/write comments](https://blog.orbistechnologies.com/bid/41180/Centralizing-metadata-content-and-assets-Paradise-Lost-and-Regained#comments-listing) Topics: [content management for publishers](https://blog.orbistechnologies.com/topic/content-management-for-publishers), [publishing](https://blog.orbistechnologies.com/topic/publishing), [CMS](https://blog.orbistechnologies.com/topic/cms), [best practices](https://blog.orbistechnologies.com/topic/best-practices), [XML](https://blog.orbistechnologies.com/topic/xml), [metadata](https://blog.orbistechnologies.com/topic/metadata) ## [Metadata lessons from Google Books](https://blog.orbistechnologies.com/bid/40326/Metadata-lessons-from-Google-Books) Posted by [Lisa Bos](https://blog.orbistechnologies.com/author/lisa-bos) on Feb 15, 2011 9:24:00 AM - [Tweet](https://twitter.com/share) This [Salon interview with Geoffrey Nunberg about Google Books' unfortunate use of metadata ](http://www.salon.com/technology/google/index.html?story=/books/laura_miller/2010/09/09/google_books)is fascinating as an illustration of why a publisher implementing a CMS should focus as much (maybe more) on metadata as on anything else. Bad metadata leads to all sorts of problems, and unfortunately it's a self-reinforcing problem - bad leads to worse as users repeat mistakes, act on inaccurate search results, and ultimately come to distrust the system. By "focus on metadata" I mean publishers implementing CMS should take care in: - modeling metadata - the creation of controlled lists and taxonomies - the design of automated and manual tools for assigning metadata - the development of automated validation tools to ensure quality - the development of search that leverages metadata - user interface design to make metadata easily visible in various contexts (browse, edit, search results, ...) to encourage consistent usage and metadata correction/entry whenever it's convenient to the user Here's [Nunberg's original article in the Chronicle of Higher Education from August 2009 ](http://chronicle.com/article/Googles-Book-Search-A/48245/)and [a related blog post](http://languagelog.ldc.upenn.edu/nll/?p=1701). This topic is obviously fascinating at face value as well - as it relates to the usefulness of Google Books for different usages by different users with different expectations. The comments to Nunberg's article/blog posts illustrate effectively that smart, well-intentioned people strongly disagree on the value of metadata or of particular types of metadata as compared to the benefits of "simply" making content available through fulltext search. This basic disagreement often shows up during design projects for [RSuite CMS](http://www.reallysi.com/solutions/solutions_rsuite.html) implementation. Leaders within a publisher need to reach agreement about which metadata will truly be of value internally and to readers and about which types of usage are most important to support. They also need to determine the cost/benefit ratio (metadata is often relatively expensive to do right). If they can't reach such agreements, then it's also unlikely they will consistently and usefully build and leverage tools for metadata in the first place - thus leading to a self-fulfilling prophecy on the part of the fulltext-instead-of-metadata advocates. Of course, there's also a role here for the technology vendor like Really Strategies - we need to make it as easy as possible for publishers to take the steps on the bulleted list at the top of this post, so that the human effort required to make metadata really valuable is also really efficient. 0 Comments [Click here to read/write comments](https://blog.orbistechnologies.com/bid/40326/Metadata-lessons-from-Google-Books#comments-listing) Topics: [content management](https://blog.orbistechnologies.com/topic/content-management), [publishing](https://blog.orbistechnologies.com/topic/publishing), [metadata](https://blog.orbistechnologies.com/topic/metadata), [Google Books](https://blog.orbistechnologies.com/topic/google-books) ## [Top 5 Reasons CMS Projects Fail at Publishers](https://blog.orbistechnologies.com/bid/39137/Top-5-Reasons-CMS-Projects-Fail-at-Publishers) Posted by [Barry Bealer](https://blog.orbistechnologies.com/author/barry-bealer) on Feb 7, 2011 12:01:00 PM - [Tweet](https://twitter.com/share) ![RSuite - Content management for publishers](https://blog.orbistechnologies.com/hs-fs/file-13544532-jpg/images/project_sign.jpg?width=159&height=105&name=project_sign.jpg)All of us have been involved at one point or another in our careers with that “death project” that just seems to lack any real conclusion and no one seems to know how or why it is in the state of limbo.  Vendors who serve the publishing industry have many reasons why a project is in jeopardy or has failed altogether including lack of proper resources, no project management discipline,  etc.   From a vendor’s perspective there are some telltale signs that were evident from the very beginning of the project but everyone overlooked them in the excitement of project kickoff.  Following are my top 5 reasons (from a vendor perspective) on why CMS projects fail at publishers: 1. **Solution/Technology was not the right fit **– Almost no one will admit to selecting the wrong solution or technology.  We all know that buying technology is sometimes a mystery.  Some vendors are really good at selling a vision only to have the publisher realize in the middle of the project that reaching that vision is going to cost three times more than they budgeted.  In other cases publishers already have a preferred technology or product and force that product on all groups.  On more than one occasion we were told point blank by a larger publisher that we love your [RSuite](https://blog.orbistechnologies.com/cms-powered-by-marklogic-server/) technology but corporate is forcing us to use [Documentum](http://www.emc.com) because we bought a site license.  Economically that makes sense. But functionally this may be trying to shoehorn a technology that was built to manage documents into a publishing environment that requires content management.  Different requirements, different solution required.  It is that simple.  It is no surpise when we hear back from the publisher 9 months later that the project failed or the system is not being used because the system does not meet expectations.**** 2. **Buying a vision that is unattainable **– Publishers get excited by vendor demos.  And they should!  What they are seeing in a demo is something they generally don’t have in place.  Some vendors are outstanding at selling a vision by demonstrating slick end-user applications.  The problem with this is that a publisher needs to ask the question “how much is it going to cost me to reach that vision?”  Seeing a technology vendor show really cool functionality does not mean there is a good business or production model behind it.  It is good to see demonstrations that push the envelope, but understand what it will take to implement such a vision (time, money, and business model changes).  I have seen several publishers purchase certain technology to build really cool end user applications only to have the technology sitting around because the vision was not attainable to begin with because it just cost way more than they could ever budget.  Investing in a vision is fine, just be able to break that vision down into logical, cost-effective projects.  Be realistic about what you would *like to accomplish* and what you *can actually accomplish*.**** 3. **Poor project budgeting **– Along with vague requirements goes poor budgeting.  If you went to a home builder and said "I want a two story house built, give me a quote." How much confidence would you have in the quote you would receive back when the requirements for the house were so vague?  Well, from a vendor’s perspective, we get this level of vague requirements for a CMS on a regular basis and are expected to provide a budget to implement the software.  It is generally couched with “we are only looking for a ballpark.”  OK, great, but if you are looking for a ballpark price that you would have a low level of confidence in, why are you putting that ballpark price into your next fiscal years’ budget?  Immediately you are putting the project at risk.  Again, vague requirements will lead to ballpark estimates that can be misconstrued in budgets. There can be pressure on the vendor to implement a solution based on an unrealistic budget.  Because the system does not operate according to some vague vision there is a real risk of project failure and unhappy customers.  See the chain of events?**** 4. **Inherent conflict between IT and editorial**  – My colleague, [Lisa Bos](http://www.reallysi.com/about/biolb.html), wrote several years back in one of our website newsletters that software development and editorial processes are in direct conflict with one another.  Think about it.  Software developers are used to an environment where they work up to the very last minute making changes on the fly and moving the system to production with an acceptable level of bugs.  The software is never 100%, but it is operational.  On the other hand, the editorial team has a defined process to complete edits on a deadline with the goal of 100% accuracy.  This inherent conflict between these operational approaches comes out during a CMS project implementation.  Understanding the cultural differences between the two organizations is important.**** 5. **No definition of CMS project success** – Why do publishers implement CMSs?  There are many reasons of course, but how often are the goals of the CMS project discussed: during the budget cycle, RFP stage, kickoff only, never?  If you hold a CMS project kickoff meeting and ask the group the definition of success when the system is operational and no one in the room knows the answer, you have a problem.  How can a CMS project be successful if the project team does not know the measurement of success?  Installing a CMS is not a success criteria.  Managing XML better is not a measurable goal.   Re-using *X*% of content in new derivative products, or reducing time-to-market by *X* days are real, measurable success criteria.  One exercise I like to do at the project kickoff meeting is to make the team draft a press release announcing the completion of the project.  After the team gets over the silliness of the initial request, most teams have fun with the exercise and actually contribute to the writing of the press release.  This simple exercise allows the team to verbally communicate among peers what their interpretation of success is for the project.  If you cannot articulate the definition of project success for the CMS project from the outset, you may be in trouble of ever meeting expectations of management.  Know the success criteria, communicate the success criteria, and celebrate the success with your team. There are many reasons that CMS projects fail, but over the past decade these five are top of mind.  You will not be able to avoid all of them, but recognizing an issue early on and addressing it will benefit you in the long run and make everyone happier because of the ultimate success your team will achieve. 0 Comments [Click here to read/write comments](https://blog.orbistechnologies.com/bid/39137/Top-5-Reasons-CMS-Projects-Fail-at-Publishers#comments-listing) Topics: [content management for publishers](https://blog.orbistechnologies.com/topic/content-management-for-publishers), [content management](https://blog.orbistechnologies.com/topic/content-management), [CMS](https://blog.orbistechnologies.com/topic/cms), [project management](https://blog.orbistechnologies.com/topic/project-management), [best practices](https://blog.orbistechnologies.com/topic/best-practices), [CMS project](https://blog.orbistechnologies.com/topic/cms-project), [Content Mangement Project Team](https://blog.orbistechnologies.com/topic/content-mangement-project-team), [CMS Teams](https://blog.orbistechnologies.com/topic/cms-teams) ## [Really Strategies Announces RSuite Cloud](https://blog.orbistechnologies.com/bid/38769/Really-Strategies-Announces-RSuite-Cloud) Posted by [Barry Bealer](https://blog.orbistechnologies.com/author/barry-bealer) on Feb 1, 2011 1:10:00 PM - [Tweet](https://twitter.com/share) ### "Push-Button Publishing System” for Print, Web, and eBook Production in 70 Languages ![rsuite cloud 200w](https://blog.orbistechnologies.com/hs-fs/file-2504604638-gif/images/rsuite_cloud_200w.gif)We are pleased to announce the availability of [RSuite Cloud](https://blog.orbistechnologies.com/rsuite-cloud-demo-request/) - a complete end-to-end hosted editorial and production system for book publishers.  If you are looking to shorten your book production time to market, want to publish to multiple channels (print, HTML, eBook) at once, and publish in 70 different languages, I suggest you take a look for yourself.  Online demo [here](http://www.reallysi.com/solutions/online_demo_rsuitecloud.html). Here is what one of our clients said about RSuite Cloud: “We saw the time to produce PDF proofs drop from a week to just a few minutes. This improvement in productivity allowed us to dramatically shorten our production cycle and even recognize revenue in 2010 for a book that was originally scheduled for 2011," stated Stephen Driver, vice president of production services, Rowman & Littlefield Publishing Group. “We are excited about our ability to scale with this solution and the new scheduling flexibility that we could never have dreamed of in our old environment." 0 Comments [Click here to read/write comments](https://blog.orbistechnologies.com/bid/38769/Really-Strategies-Announces-RSuite-Cloud#comments-listing) Topics: [content management for publishers](https://blog.orbistechnologies.com/topic/content-management-for-publishers), [content management](https://blog.orbistechnologies.com/topic/content-management), [ebooks](https://blog.orbistechnologies.com/topic/ebooks), [CMS](https://blog.orbistechnologies.com/topic/cms), [CMS project](https://blog.orbistechnologies.com/topic/cms-project), [XML](https://blog.orbistechnologies.com/topic/xml) ## [Content Management Survey for DITA North America Conference](https://blog.orbistechnologies.com/bid/38182/Content-Management-Survey-for-DITA-North-America-Conference) Posted by [Marianne Calihanna](https://blog.orbistechnologies.com/author/marianne-calihanna) on Jan 26, 2011 4:13:00 PM - [Tweet](https://twitter.com/share) ![laptops globe](https://blog.orbistechnologies.com/hs-fs/file-13544341-gif/images/laptops-globe.gif)**Why business units can’t or don’t commit to a Content Management System (CMS)?** Our friends at the independent consulting firm, [TechProse](http://www.techprose.com/), are conducting a [survey ](http://www.surveymonkey.com/s/WQGVZC8)for a presentation at the spring DITA North America Conference. All professionals who are involved with content management are invited to participate. As a survey participant, you can receive the results via email. The results could be helpful if you're planning a content management initiative and need to put the R in your ROI! [Click here](http://www.surveymonkey.com/s/WQGVZC8) to take the survey. 0 Comments [Click here to read/write comments](https://blog.orbistechnologies.com/bid/38182/Content-Management-Survey-for-DITA-North-America-Conference#comments-listing) Topics: [content management](https://blog.orbistechnologies.com/topic/content-management), [DITA](https://blog.orbistechnologies.com/topic/dita), [XML](https://blog.orbistechnologies.com/topic/xml) [Previous](https://blog.orbistechnologies.com/page/26) [All posts](https://blog.orbistechnologies.com/all) [Next](https://blog.orbistechnologies.com/page/28) ## Comment below ### Subscribe by Email ![RSS_Feed_Button](https://blog.orbistechnologies.com/hs-fs/hubfs/RSS_Feed_Button.jpg?width=40&name=RSS_Feed_Button.jpg)[Click here to subscribe to our RSS feed!](http://feeds.feedburner.com/orbistechnologies/blog) ### Most Popular Posts ### Browse by Tag - [#AskAnEngineer (1)](https://blog.orbistechnologies.com/topic/askanengineer) - [#BPTW (1)](https://blog.orbistechnologies.com/topic/bptw) - [#DBW13 (1)](https://blog.orbistechnologies.com/topic/dbw13) - [#DBW16 (1)](https://blog.orbistechnologies.com/topic/dbw16) - [#FBF13 (1)](https://blog.orbistechnologies.com/topic/fbf13) - [#FBF17 (1)](https://blog.orbistechnologies.com/topic/fbf17) - [#FBF18 (1)](https://blog.orbistechnologies.com/topic/fbf18) - [#ImplementingRSuite (1)](https://blog.orbistechnologies.com/topic/implementingrsuite) - [#Keynote (1)](https://blog.orbistechnologies.com/topic/keynote) - [#LBF17 (1)](https://blog.orbistechnologies.com/topic/lbf17) - [#MarkLogicSummit (1)](https://blog.orbistechnologies.com/topic/marklogicsummit) - [#merger (1)](https://blog.orbistechnologies.com/topic/merger) - [#MLW17 (1)](https://blog.orbistechnologies.com/topic/mlw17) - [#MLW18 (1)](https://blog.orbistechnologies.com/topic/mlw18) - [#PlanVsReality (1)](https://blog.orbistechnologies.com/topic/planvsreality) - [#ProductRoadmap (2)](https://blog.orbistechnologies.com/topic/productroadmap) - [#Progress (2)](https://blog.orbistechnologies.com/topic/progress) - [#RSuiteCustomers (1)](https://blog.orbistechnologies.com/topic/rsuitecustomers) - [#RSuiteUC (3)](https://blog.orbistechnologies.com/topic/rsuiteuc) - [#RSuiteUC15 (7)](https://blog.orbistechnologies.com/topic/rsuiteuc15) - [#RSuiteUC16 (10)](https://blog.orbistechnologies.com/topic/rsuiteuc16) - [#RSuiteUC16Sponsors (1)](https://blog.orbistechnologies.com/topic/rsuiteuc16sponsors) - [#smart (1)](https://blog.orbistechnologies.com/topic/smart) - [#Sponsors (1)](https://blog.orbistechnologies.com/topic/sponsors) - [#stc15 (2)](https://blog.orbistechnologies.com/topic/stc15) - [2013 CMS/DITA North America (1)](https://blog.orbistechnologies.com/topic/2013-cmsdita-north-america) - [4.1 (1)](https://blog.orbistechnologies.com/topic/41) - [5-minute-series (3)](https://blog.orbistechnologies.com/topic/5-minute-series) - [AAP (2)](https://blog.orbistechnologies.com/topic/aap) - [AARDVARK (2)](https://blog.orbistechnologies.com/topic/aardvark) - [achievements (2)](https://blog.orbistechnologies.com/topic/achievements) - [Adobe (1)](https://blog.orbistechnologies.com/topic/adobe) - [AEP (1)](https://blog.orbistechnologies.com/topic/aep) - [Agenda Announcement (1)](https://blog.orbistechnologies.com/topic/agenda-announcement) - [Alan Houser (1)](https://blog.orbistechnologies.com/topic/alan-houser) - [ALPSP (1)](https://blog.orbistechnologies.com/topic/alpsp) - [Amazon.com (2)](https://blog.orbistechnologies.com/topic/amazoncom) - [American Collective Stand S31 (1)](https://blog.orbistechnologies.com/topic/american-collective-stand-s31) - [Announcement (2)](https://blog.orbistechnologies.com/topic/announcement) - [Anthony Allen (1)](https://blog.orbistechnologies.com/topic/anthony-allen) - [April 3 (1)](https://blog.orbistechnologies.com/topic/april-3) - [Army (1)](https://blog.orbistechnologies.com/topic/army) - [Association of American Publishers (2)](https://blog.orbistechnologies.com/topic/association-of-american-publishers) - [Association of Educational Publishers (1)](https://blog.orbistechnologies.com/topic/association-of-educational-publishers) - [ASTD (1)](https://blog.orbistechnologies.com/topic/astd) - [Audible (1)](https://blog.orbistechnologies.com/topic/audible) - [Authoringtools (1)](https://blog.orbistechnologies.com/topic/authoringtools) - [Automation (2)](https://blog.orbistechnologies.com/topic/automation) - [Barry Bealer (8)](https://blog.orbistechnologies.com/topic/barry-bealer) - [beginning (1)](https://blog.orbistechnologies.com/topic/beginning) - [behind the scenes (1)](https://blog.orbistechnologies.com/topic/behind-the-scenes) - [Best Enterprise CMS (1)](https://blog.orbistechnologies.com/topic/best-enterprise-cms) - [Best Places to Work (1)](https://blog.orbistechnologies.com/topic/best-places-to-work) - [best practices (9)](https://blog.orbistechnologies.com/topic/best-practices) - [Best practices for RSuite workflow (1)](https://blog.orbistechnologies.com/topic/best-practices-for-rsuite-workflow) - [Bill Kasdorf (1)](https://blog.orbistechnologies.com/topic/bill-kasdorf) - [BITS (1)](https://blog.orbistechnologies.com/topic/bits) - [bogus reviews (1)](https://blog.orbistechnologies.com/topic/bogus-reviews) - [book publishers (4)](https://blog.orbistechnologies.com/topic/book-publishers) - [book publishing (10)](https://blog.orbistechnologies.com/topic/book-publishing) - [book reviews (1)](https://blog.orbistechnologies.com/topic/book-reviews) - [books (2)](https://blog.orbistechnologies.com/topic/books) - [Booth 26 (1)](https://blog.orbistechnologies.com/topic/booth-26) - [Booth T18 (1)](https://blog.orbistechnologies.com/topic/booth-t18) - [Booth V535 (1)](https://blog.orbistechnologies.com/topic/booth-v535) - [Brian Howard (1)](https://blog.orbistechnologies.com/topic/brian-howard) - [browser (2)](https://blog.orbistechnologies.com/topic/browser) - [Browser Strategy Series (5)](https://blog.orbistechnologies.com/topic/browser-strategy-series) - [Build Your Bottom Line With Strategic Content Mana (2)](https://blog.orbistechnologies.com/topic/build-your-bottom-line-with-strategic-content-mana) - [CCMS (1)](https://blog.orbistechnologies.com/topic/ccms) - [central repository (1)](https://blog.orbistechnologies.com/topic/central-repository) - [Challenges of Digital Online Publishing Management (1)](https://blog.orbistechnologies.com/topic/challenges-of-digital-online-publishing-management) - [Christopher Hill (1)](https://blog.orbistechnologies.com/topic/christopher-hill) - [Chrome (5)](https://blog.orbistechnologies.com/topic/chrome) - [CK Editor (1)](https://blog.orbistechnologies.com/topic/ck-editor) - [CMMI (1)](https://blog.orbistechnologies.com/topic/cmmi) - [CMS (30)](https://blog.orbistechnologies.com/topic/cms) - [CMS Critic (1)](https://blog.orbistechnologies.com/topic/cms-critic) - [CMS for publishers (31)](https://blog.orbistechnologies.com/topic/cms-for-publishers) - [CMS project (10)](https://blog.orbistechnologies.com/topic/cms-project) - [CMS Strategies (2)](https://blog.orbistechnologies.com/topic/cms-strategies) - [CMS Teams (4)](https://blog.orbistechnologies.com/topic/cms-teams) - [Component Content Management Systems (1)](https://blog.orbistechnologies.com/topic/component-content-management-systems) - [conference (5)](https://blog.orbistechnologies.com/topic/conference) - [content (2)](https://blog.orbistechnologies.com/topic/content) - [content conversion (2)](https://blog.orbistechnologies.com/topic/content-conversion) - [Content in Context (2)](https://blog.orbistechnologies.com/topic/content-in-context) - [content management (36)](https://blog.orbistechnologies.com/topic/content-management) - [content management for publishers (56)](https://blog.orbistechnologies.com/topic/content-management-for-publishers) - [Content Management Solution (1)](https://blog.orbistechnologies.com/topic/content-management-solution) - [Content Management System (1)](https://blog.orbistechnologies.com/topic/content-management-system) - [Content Mangement Project Team (5)](https://blog.orbistechnologies.com/topic/content-mangement-project-team) - [content transformations (2)](https://blog.orbistechnologies.com/topic/content-transformations) - [contract award (3)](https://blog.orbistechnologies.com/topic/contract-award) - [control (1)](https://blog.orbistechnologies.com/topic/control) - [cookbook publishing (1)](https://blog.orbistechnologies.com/topic/cookbook-publishing) - [Critics Choice CMS Awards (1)](https://blog.orbistechnologies.com/topic/critics-choice-cms-awards) - [Customer engagement (1)](https://blog.orbistechnologies.com/topic/customer-engagement) - [customer webinar (1)](https://blog.orbistechnologies.com/topic/customer-webinar) - [DAM (1)](https://blog.orbistechnologies.com/topic/dam) - [DAMS (2)](https://blog.orbistechnologies.com/topic/dams) - [David Gorbet (1)](https://blog.orbistechnologies.com/topic/david-gorbet) - [David Saracco (2)](https://blog.orbistechnologies.com/topic/david-saracco) - [Deloitte Fast 50 (1)](https://blog.orbistechnologies.com/topic/deloitte-fast-50) - [Demo (2)](https://blog.orbistechnologies.com/topic/demo) - [design (1)](https://blog.orbistechnologies.com/topic/design) - [Digital Asset Management (4)](https://blog.orbistechnologies.com/topic/digital-asset-management) - [Digital Book World (3)](https://blog.orbistechnologies.com/topic/digital-book-world) - [digital content industry (1)](https://blog.orbistechnologies.com/topic/digital-content-industry) - [digital publishing (14)](https://blog.orbistechnologies.com/topic/digital-publishing) - [digital publishing strategy (6)](https://blog.orbistechnologies.com/topic/digital-publishing-strategy) - [digital revenue (1)](https://blog.orbistechnologies.com/topic/digital-revenue) - [digital revenue metrics (1)](https://blog.orbistechnologies.com/topic/digital-revenue-metrics) - [Digital Zone (1)](https://blog.orbistechnologies.com/topic/digital-zone) - [DITA (9)](https://blog.orbistechnologies.com/topic/dita) - [DITA for Publishers (4)](https://blog.orbistechnologies.com/topic/dita-for-publishers) - [documentation (1)](https://blog.orbistechnologies.com/topic/documentation) - [DocZone (11)](https://blog.orbistechnologies.com/topic/doczone) - [DocZone Book Publisher (6)](https://blog.orbistechnologies.com/topic/doczone-book-publisher) - [DocZone DITA (2)](https://blog.orbistechnologies.com/topic/doczone-dita) - [DTD (2)](https://blog.orbistechnologies.com/topic/dtd) - [Dynamic Management Dashboard Features (1)](https://blog.orbistechnologies.com/topic/dynamic-management-dashboard-features) - [e-first (1)](https://blog.orbistechnologies.com/topic/e-first) - [ebook (1)](https://blog.orbistechnologies.com/topic/ebook) - [ebook production (1)](https://blog.orbistechnologies.com/topic/ebook-production) - [ebooks (21)](https://blog.orbistechnologies.com/topic/ebooks) - [EC100 (1)](https://blog.orbistechnologies.com/topic/ec100) - [EContent (2)](https://blog.orbistechnologies.com/topic/econtent) - [EContent 100 (3)](https://blog.orbistechnologies.com/topic/econtent-100) - [Education (1)](https://blog.orbistechnologies.com/topic/education) - [Educational Publishers (2)](https://blog.orbistechnologies.com/topic/educational-publishers) - [educational publishing (3)](https://blog.orbistechnologies.com/topic/educational-publishing) - [Eliot Kimber (2)](https://blog.orbistechnologies.com/topic/eliot-kimber) - [Emerging Innovator (1)](https://blog.orbistechnologies.com/topic/emerging-innovator) - [emerging technologies (1)](https://blog.orbistechnologies.com/topic/emerging-technologies) - [Engineering (1)](https://blog.orbistechnologies.com/topic/engineering) - [Enterprise CMS (2)](https://blog.orbistechnologies.com/topic/enterprise-cms) - [Enterprise Software (2)](https://blog.orbistechnologies.com/topic/enterprise-software) - [Epson America (1)](https://blog.orbistechnologies.com/topic/epson-america) - [epub (1)](https://blog.orbistechnologies.com/topic/epub) - [ePub3 (1)](https://blog.orbistechnologies.com/topic/epub3) - [events (5)](https://blog.orbistechnologies.com/topic/events) - [Executive Management Award (2)](https://blog.orbistechnologies.com/topic/executive-management-award) - [Expands to South America (1)](https://blog.orbistechnologies.com/topic/expands-to-south-america) - [Fast 50 (1)](https://blog.orbistechnologies.com/topic/fast-50) - [FBM18 (1)](https://blog.orbistechnologies.com/topic/fbm18) - [features (1)](https://blog.orbistechnologies.com/topic/features) - [Firefox (5)](https://blog.orbistechnologies.com/topic/firefox) - [Flipboard (1)](https://blog.orbistechnologies.com/topic/flipboard) - [FontoXML (1)](https://blog.orbistechnologies.com/topic/fontoxml) - [FrameMaker (1)](https://blog.orbistechnologies.com/topic/framemaker) - [Frankfurt Book Fair (4)](https://blog.orbistechnologies.com/topic/frankfurt-book-fair) - [Free webinar (1)](https://blog.orbistechnologies.com/topic/free-webinar) - [Future 50 (1)](https://blog.orbistechnologies.com/topic/future-50) - [Future 50 Award (2)](https://blog.orbistechnologies.com/topic/future-50-award) - [global (4)](https://blog.orbistechnologies.com/topic/global) - [Google Books (1)](https://blog.orbistechnologies.com/topic/google-books) - [GXP360 (1)](https://blog.orbistechnologies.com/topic/gxp360) - [Hall 8.0 (1)](https://blog.orbistechnologies.com/topic/hall-80) - [HarperCollins (4)](https://blog.orbistechnologies.com/topic/harpercollins) - [HarperCollins Publishers (3)](https://blog.orbistechnologies.com/topic/harpercollins-publishers) - [Henry Stewart (2)](https://blog.orbistechnologies.com/topic/henry-stewart) - [Henry Stewart DAM NY (2)](https://blog.orbistechnologies.com/topic/henry-stewart-dam-ny) - [How to (1)](https://blog.orbistechnologies.com/topic/how-to) - [Human Kinetics (2)](https://blog.orbistechnologies.com/topic/human-kinetics) - [Hunger Games (1)](https://blog.orbistechnologies.com/topic/hunger-games) - [IET TV (1)](https://blog.orbistechnologies.com/topic/iet-tv) - [improved productivity (1)](https://blog.orbistechnologies.com/topic/improved-productivity) - [Inc. 500|5000 (1)](https://blog.orbistechnologies.com/topic/inc-5005000) - [inhouse publishing (1)](https://blog.orbistechnologies.com/topic/inhouse-publishing) - [Internet Explorer (5)](https://blog.orbistechnologies.com/topic/internet-explorer) - [JATS (1)](https://blog.orbistechnologies.com/topic/jats) - [Java Architect (1)](https://blog.orbistechnologies.com/topic/java-architect) - [Job Opening (1)](https://blog.orbistechnologies.com/topic/job-opening) - [John Shaw (1)](https://blog.orbistechnologies.com/topic/john-shaw) - [journal (1)](https://blog.orbistechnologies.com/topic/journal) - [journal publishers (2)](https://blog.orbistechnologies.com/topic/journal-publishers) - [journals (2)](https://blog.orbistechnologies.com/topic/journals) - [June (1)](https://blog.orbistechnologies.com/topic/june) - [Keith Lawrenz (1)](https://blog.orbistechnologies.com/topic/keith-lawrenz) - [Klopotek (1)](https://blog.orbistechnologies.com/topic/klopotek) - [LBF (1)](https://blog.orbistechnologies.com/topic/lbf) - [Legacy CMS (1)](https://blog.orbistechnologies.com/topic/legacy-cms) - [Lessors For Trade Publishers From STM Publishers (1)](https://blog.orbistechnologies.com/topic/lessors-for-trade-publishers-from-stm-publishers) - [Lisa Bos (7)](https://blog.orbistechnologies.com/topic/lisa-bos) - [London (1)](https://blog.orbistechnologies.com/topic/london) - [London Book Fair (3)](https://blog.orbistechnologies.com/topic/london-book-fair) - [LUXID (1)](https://blog.orbistechnologies.com/topic/luxid) - [magazines (2)](https://blog.orbistechnologies.com/topic/magazines) - [management (1)](https://blog.orbistechnologies.com/topic/management) - [marketing (1)](https://blog.orbistechnologies.com/topic/marketing) - [MarkLogic (17)](https://blog.orbistechnologies.com/topic/marklogic) - [MarkLogic 7 (1)](https://blog.orbistechnologies.com/topic/marklogic-7) - [MarkLogic World (3)](https://blog.orbistechnologies.com/topic/marklogic-world) - [MarkLogic World 2013 (1)](https://blog.orbistechnologies.com/topic/marklogic-world-2013) - [MarkLogic World San Francisco (1)](https://blog.orbistechnologies.com/topic/marklogic-world-san-francisco) - [May 5 (1)](https://blog.orbistechnologies.com/topic/may-5) - [metadata (12)](https://blog.orbistechnologies.com/topic/metadata) - [Michael McGinniss (1)](https://blog.orbistechnologies.com/topic/michael-mcginniss) - [Mike McGinniss (2)](https://blog.orbistechnologies.com/topic/mike-mcginniss) ### Posts by Month - [July 2019 (3)](https://blog.orbistechnologies.com/archive/2019/07) - [June 2019 (1)](https://blog.orbistechnologies.com/archive/2019/06) - [February 2019 (1)](https://blog.orbistechnologies.com/archive/2019/02) - [January 2019 (2)](https://blog.orbistechnologies.com/archive/2019/01) - [November 2018 (2)](https://blog.orbistechnologies.com/archive/2018/11) - [October 2018 (1)](https://blog.orbistechnologies.com/archive/2018/10) - [September 2018 (1)](https://blog.orbistechnologies.com/archive/2018/09) - [August 2018 (1)](https://blog.orbistechnologies.com/archive/2018/08) - [July 2018 (1)](https://blog.orbistechnologies.com/archive/2018/07) - [June 2018 (2)](https://blog.orbistechnologies.com/archive/2018/06) - [May 2018 (1)](https://blog.orbistechnologies.com/archive/2018/05) - [March 2018 (1)](https://blog.orbistechnologies.com/archive/2018/03) - [December 2017 (1)](https://blog.orbistechnologies.com/archive/2017/12) - [October 2017 (1)](https://blog.orbistechnologies.com/archive/2017/10) - [September 2017 (3)](https://blog.orbistechnologies.com/archive/2017/09) - [August 2017 (1)](https://blog.orbistechnologies.com/archive/2017/08) - [July 2017 (1)](https://blog.orbistechnologies.com/archive/2017/07) - [June 2017 (1)](https://blog.orbistechnologies.com/archive/2017/06) - [May 2017 (1)](https://blog.orbistechnologies.com/archive/2017/05) - [April 2017 (1)](https://blog.orbistechnologies.com/archive/2017/04) - [March 2017 (3)](https://blog.orbistechnologies.com/archive/2017/03) - [February 2017 (1)](https://blog.orbistechnologies.com/archive/2017/02) - [January 2017 (2)](https://blog.orbistechnologies.com/archive/2017/01) - [October 2016 (2)](https://blog.orbistechnologies.com/archive/2016/10) - [September 2016 (2)](https://blog.orbistechnologies.com/archive/2016/09) - [August 2016 (4)](https://blog.orbistechnologies.com/archive/2016/08) - [July 2016 (2)](https://blog.orbistechnologies.com/archive/2016/07) - [June 2016 (1)](https://blog.orbistechnologies.com/archive/2016/06) - [May 2016 (1)](https://blog.orbistechnologies.com/archive/2016/05) - [March 2016 (2)](https://blog.orbistechnologies.com/archive/2016/03) - [February 2016 (1)](https://blog.orbistechnologies.com/archive/2016/02) - [December 2015 (1)](https://blog.orbistechnologies.com/archive/2015/12) - [July 2015 (2)](https://blog.orbistechnologies.com/archive/2015/07) - [June 2015 (4)](https://blog.orbistechnologies.com/archive/2015/06) - [May 2015 (1)](https://blog.orbistechnologies.com/archive/2015/05) - [April 2015 (5)](https://blog.orbistechnologies.com/archive/2015/04) - [March 2015 (1)](https://blog.orbistechnologies.com/archive/2015/03) - [February 2015 (3)](https://blog.orbistechnologies.com/archive/2015/02) - [January 2015 (1)](https://blog.orbistechnologies.com/archive/2015/01) - [December 2014 (2)](https://blog.orbistechnologies.com/archive/2014/12) - [October 2014 (2)](https://blog.orbistechnologies.com/archive/2014/10) - [September 2014 (1)](https://blog.orbistechnologies.com/archive/2014/09) - [August 2014 (3)](https://blog.orbistechnologies.com/archive/2014/08) - [July 2014 (4)](https://blog.orbistechnologies.com/archive/2014/07) - [June 2014 (4)](https://blog.orbistechnologies.com/archive/2014/06) - [May 2014 (6)](https://blog.orbistechnologies.com/archive/2014/05) - [April 2014 (4)](https://blog.orbistechnologies.com/archive/2014/04) - [March 2014 (4)](https://blog.orbistechnologies.com/archive/2014/03) - [February 2014 (2)](https://blog.orbistechnologies.com/archive/2014/02) - [January 2014 (4)](https://blog.orbistechnologies.com/archive/2014/01) - [December 2013 (3)](https://blog.orbistechnologies.com/archive/2013/12) - [November 2013 (4)](https://blog.orbistechnologies.com/archive/2013/11) - [October 2013 (5)](https://blog.orbistechnologies.com/archive/2013/10) - [September 2013 (4)](https://blog.orbistechnologies.com/archive/2013/09) - [August 2013 (2)](https://blog.orbistechnologies.com/archive/2013/08) - [July 2013 (3)](https://blog.orbistechnologies.com/archive/2013/07) - [June 2013 (2)](https://blog.orbistechnologies.com/archive/2013/06) - [May 2013 (4)](https://blog.orbistechnologies.com/archive/2013/05) - [April 2013 (5)](https://blog.orbistechnologies.com/archive/2013/04) - [March 2013 (2)](https://blog.orbistechnologies.com/archive/2013/03) - [February 2013 (5)](https://blog.orbistechnologies.com/archive/2013/02) - [January 2013 (7)](https://blog.orbistechnologies.com/archive/2013/01) - [December 2012 (4)](https://blog.orbistechnologies.com/archive/2012/12) - [November 2012 (5)](https://blog.orbistechnologies.com/archive/2012/11) - [October 2012 (9)](https://blog.orbistechnologies.com/archive/2012/10) - [September 2012 (7)](https://blog.orbistechnologies.com/archive/2012/09) - [August 2012 (8)](https://blog.orbistechnologies.com/archive/2012/08) - [July 2012 (3)](https://blog.orbistechnologies.com/archive/2012/07) - [June 2012 (4)](https://blog.orbistechnologies.com/archive/2012/06) - [May 2012 (4)](https://blog.orbistechnologies.com/archive/2012/05) - [April 2012 (14)](https://blog.orbistechnologies.com/archive/2012/04) - [March 2012 (3)](https://blog.orbistechnologies.com/archive/2012/03) - [February 2012 (5)](https://blog.orbistechnologies.com/archive/2012/02) - [January 2012 (8)](https://blog.orbistechnologies.com/archive/2012/01) - [December 2011 (4)](https://blog.orbistechnologies.com/archive/2011/12) - [November 2011 (5)](https://blog.orbistechnologies.com/archive/2011/11) - [October 2011 (5)](https://blog.orbistechnologies.com/archive/2011/10) - [September 2011 (4)](https://blog.orbistechnologies.com/archive/2011/09) - [August 2011 (4)](https://blog.orbistechnologies.com/archive/2011/08) - [July 2011 (3)](https://blog.orbistechnologies.com/archive/2011/07) - [June 2011 (3)](https://blog.orbistechnologies.com/archive/2011/06) - [May 2011 (4)](https://blog.orbistechnologies.com/archive/2011/05) - [April 2011 (4)](https://blog.orbistechnologies.com/archive/2011/04) - [March 2011 (7)](https://blog.orbistechnologies.com/archive/2011/03) - [February 2011 (4)](https://blog.orbistechnologies.com/archive/2011/02) - [January 2011 (4)](https://blog.orbistechnologies.com/archive/2011/01) ### Follow Me <http://www.youtube.com/rsicontentsolutions> © 2017 Orbis Technologies, Inc. [![Share on LinkedIn](https://static.hubspot.com/final/img/common/icons/social/linkedin-24x24.png)](https://www.linkedin.com/company/orbis-technologies-inc-) [![Share on Twitter](https://static.hubspot.com/final/img/common/icons/social/twitter-24x24.png)](https://twitter.com/orbistech)