In this first round of breakout sessions, I decided to atttend “Content Applications Being Developed at the LDS Church” with Mike Bowers. I selected this session because The Church of Jesus Christ of Latter-Day Saints is the steward of generations worth of content, in an increasingly wide variety of formats. And, legacy content — yes, indeed — they got plenty. As a result, they have some interesting content challenges that span the entire lifecycle of content.
LDS is using MarkLogic Server as their platform for developing interactive web sites, content applications, single source repositories, and basic content management systems. Bowers said they’ve only had the system for just under a year, but they are using it in some pretty innovative ways. But, not without some confusion by the users. Is it a content management system? Is it a development environment? Is it a file system? Is it a search engine? Is it an app server? What is it, exactly? These are typical questions of folks who stuggle to find a category in which to put MarkLogic Server.
[Find answers to these questions here.]
LDS, Bowers said, has created a Java application using MarkLogic as a database to maintain their Handbook for Temporal Affairs (PolicyPoint). LDS users drop Word documents (section of a larger document) into a file folder, then a document appears in the larger document, the handbook. For those familiar with technical communication, think of the Adobe FrameMaker book model. In this example, each Word document is like a chapter or section in a FrameMaker book, but once it’s processed, it’s displayed as a virtual document. It allows the church to present the right sections of the document to the right people, in the right format, at the right time. And, it does it all without semantically-enabled structured content. It relies on the power of MarkLogic to hone in on relevant unstructured content.
The church website, LDS.org, will soon be replaced by a next-generation internet application. It will integrate social media-related techniques including: folksonomy-based content tagging, content personalization, polling, quizes, feedback/comments, etc. They’re even adding the ability for younger congregants to upload and manage user-generated content: video files, music, and games. And, they’ll be able to manage their own profiles, like they do on most social networking sites.
Using the MarkLogic Web Architecture, the church estimates that it will be able to support 10,000 concurrent users with a repsonse time of 2 second per page.
Bowers said that they were just now getting their feet wet with MarkLogic and that they’re figuring out how to use it, what works best, and they’re finding new and exciting content challenges to solve. He said he’d be happy to return next year to provide an update on their progress.
Unfortunately, he had too many examples to discuss in the time he had to present. He rushed through some examples at the end, providing some high-level descriptions:
“We really like MarkLogic Server because it allows us to quickly get up and running and create applications fast,” Bowers added, commenting that his co-workers, who have no experience with XQuery, are empowered to solve challenges without much specialized knowledge.
He said the church is also exploring how understanding how natural document structure can improve search relevance. They’re using XLink for Google-like searches.
“Everyone at LDS wants a piece of MarkLogic,” Bowers said.
Overall, it was an interesting session that helped attendees understand the issues an organization may experience when moving to MarkLogic. Its reliance on XQuery and its ability to handle both unstructured and structured content makes it a confusing proposition for some IT pros, who are used to the way things worked in the relational database and document-centric worlds most knowledge workers come from.
But, as LDS has discovered, change can be good — even if you don’t fully understand the impacts of the changes.