Showing posts with label Topic Maps. Show all posts
Showing posts with label Topic Maps. Show all posts

Thursday, January 14, 2010

Delivering Integrated Information from Data Silos Using MODS

Lyn Robinson of the Burton Group wrote an excellent paper describing a "Methodology for Overcoming Data Silos" (MODS).; a "groundbreaking project structure" for bridging silos and delivering integrated information from decentralized, disparate information systems.

Interesting concept. A lot of thought, time and money has gone into breaking down information silo's over the past few years. Robinson recognizes that this is frequently unsuccessful or, at best temporary, but that the need for integrated information remains very important - even mission critical. So instead of re-engineering the underlying information systems into a single integrated replacement, MODS proposes to implement an information bridge that fills the need for integrated information from across these silos.

So how does it work? "Each MODS project results in the definition of a few relevant and important enterprise data types, as well as a registry that tracks and reconciles the instances of those data types in the disparate silos throughout the enterprise. This registry functions somewhat like the old card catalogs for books in a library. Using a MODS registry, businesspeople can discover where to find particular types as well as instances of relevant data within the disparate silos scattered all over the enterprise." And, it's supposed to be cheap (well, cheap in comparison to development projects).

Wow. Cataloging data - maybe a librarian should be called in! Robinson describes a typical MODS pattern as "establishing a registry or system of record for a particular set of closely related enterprise data types. The scope of these data types should be determined by a conceptual data model, which defines the needs the business has for information regarding a particular business topic. The best MODS projects are narrow in scope, so the more specific the business topic, the better". Here are the steps in the pattern:

  1. Model the relevant data.
  2. Clean and Understand the Relevant Data
  3. Classify
  4. Convey
  5. Control
As I read this approach, I got to thinking, this is a possible application best served by a TopicMap. After all, TopicMaps were originally developed for indexes or catalogs. It seems like a natural fit. TopicMaps can implement many of the features MODS calls for: data typing, data relationships and styled queries. And I also began to think about social networking features like folksonomies and how these might apply to MODS.

A lot of my personal focus is related to content management and publishing. As I consider this, Content Silos are just as prevalent in publishing companies as other information type silos are in other organizations. So MODS may well have a place in content management.

So, in the next several blog posts I'm going to explore TopicsMaps and perhaps Folksonomies as technology solutions for implementing a MODS project for content in publishing.

Stay tuned...

Sunday, March 11, 2007

Open Publish Conference

I got to speak at the Open Publish conference in Baltimore (http://www.open-conferences.com/baltimore/) on Friday, 3/9/2007 amongst many of the content management and publishing luminaries. It was humbling. While the conference was small, it was very interactive and the audience was firing questions both during and after the talk. Kept me on my toes!

My particular talk was on topic maps, and on using topic maps as an information architecture to improve hypertext linking. The premise is that users frequently click on links embedded in web pages that take them somewhere they didn't want to go and that with better knowledge captured on the "aboutness" of the link, we (as content providers) can give the user more information and options about the links they are following (anyone interested can get the presentation slides from the conference directly or contact me and I'll email them).

My presentation was either fabulous or boring (depending on whether you're asking me or an attendee). But what I came away with were a bunch of questions about how to glean a topic set from extant content. I've spoken on the subject of topic maps on several occasions and many of the questions follow this same theme -- "How do we collect and organize the topics of the content in a meaningful way?"

I always have some lame answer -- "that's a job for the subject matter experts." While this is true -- the current state of the art is somewhat limited in our ability to parse content and determine subject matter, it really begs the question. Often (in my experience) there is something with which to begin this process. Usually, our content has already been touched in this way, from something as simple as the application of keywords to creation and maintenance of an outside topical index and the positioning of a particular content object within that. And often there are tables of content that can be used to further glean the "aboutness" of the content. What we (developers) need to consider is how to create a toolkit that both captures as much of this meta data as possible and imputes a relationship structure to it that in the least can serve as the foundation for a subject matter expert's work, and in the larger sense can provide a fully automated creation of a functional, integrated taxonomy.

At this conference, I was asked if I knew of any translation program that would convert the output of an index creation/management program (CINDEX) into a topic map -- a good example of what I'm talking about here.

I'm going to explore this further. We (Retrieval Systems) have a bunch of content processing tools, including some tools to work with the CINDEX data formats. Perhaps we can develop a reasonable toolkit for this kind of conversion.