- Whether to mention a pregnancy in a job interview
- A possible meeting protocol
- What are an end-user's responsibilities?
- Another take on opening PCs, or not
- Getting some process going
- Selling a more open environment to management
- Running an effective meeting
- Licensing rules for virtual machines
- The ROI of metrics
- Legal challenges to virtual machines
January 25, 2008 | Comments: (0)
End-user-supplied metadata - problem or solution?
Dear Bob ...
Do you know of any cases where a large enterprise has used a Wiki for their metadata, allowing most people (after registering) with access to the intranet update the metadata?
The problem we are having is that IT does not want to own (seems they did not budget or schedule for it) the metadata, so now we have an entry for every database, schema, table, column, term and concept, but most of the entries simply contain the name, data type and when it was created. This was created using automated scripts from the various databases, and is not helping me as a downstream developer.
Most of the knowledge has been given out, but in so many PowerPoint slides and e-mails that no one person knows it all. Since the problem is that IT doesn't have the staff to fill in the metadata I figured we, the users could.
- Volunteer
Dear Volunteer
I don't know of any cases for metadata. My initial reaction is that there would be a significant loss of control. I think of metadata the way I think of the chart of accounts - something to be carefully planned and centrally managed.
But maybe I'm just getting old.
In any undertaking, when a business chooses an alternative, it's balancing risks. Compared to the risk of undocumented metadata, it's entirely possible the risk of having too many incorrect entries might be lower.
Or, it might not: Remember the wise words of Mark Twain, who said, "It ain't what we don't know that gets us into trouble. It's what we do know that ain't so."
- Bob
Powered by ScribeFire.
Posted by Bob Lewis on January 25, 2008 08:50 PM
RATE THIS ARTICLE:
-

- COMMENTS
The problem with metadata -- it looks like you're using it in the sense of a global data dictionary -- is that its value is generally in reuse, not short-term.
As Volunteer said, it's not helping him as a downstream developer. The project sponsor typically doesn't care what helps the downstream developer on someone else's project sometime next year. Which is why creation and maintenance of this data never gets any budgetary love.
This is clearly a case where you have to suboptimize the project for the greater good of the company. And to do that, you can't rely on the project manager. There have to be incentives from an extra-project level or it won't happen.
So let's see, in order for this to happen you need:
* recognition of the value of the metadata
* high level buy-in to that value
* a view that extends beyond the current project
* appropriate incentives to support the long view
* to maintain all these factors continuously for several years
In case I've been to subtle here, I'll say it more directly. I don't think large corporations -- the ones with the most to gain from doing this right -- are typically organized in a way that it will happen. I know I've never seen it.
Posted by: Drew Kime at January 28, 2008 08:29 AMWhen dealing with unstructured data, the user community owns the metadata. They work with IT to develop it so they can organize their business data/documents. I have not worked with Wiki technology, but we use metadata to organize items in our document management systems. The metadata provides "structure" to meet a specific business need (e.g. displaying a folder structure of documents based on the metadata). Therefore, users define, and IT provides a method where owners can add to the existing values. As users add items to the repository, the system enforces metadata assignment for all required metadata categories.
Posted by: Rick Tuttle at January 30, 2008 11:59 AMThere are Metadata Repository products which can be used for the purpose. You can load the repository with Metadata ( both Technical and Business, integrated) of your Organization Manually or Automate the process ( called Scanners). Once Metadata is in the Repository, you can use it for lot of purposes, including Wiki like facility to user community.
You can do Impact Analysis, Provide Data Lineage and different kind of reports. Metadata repositories do support Web interfaces as well.
|
Three books. Three ways to change the world, your life, or at least Bob Lewis' bank account. Leading IT: The Toughest Job in the World distills the world of IT leadership into eight learnable skills and gives you concrete, practical techniques for each one of them. Bare Bones Project Management: What you can't not do makes project management manageable, even for first-time project managers with no formal training in the discipline. ManagementSpeak: What managers say/What they mean … well, it won't help your career, and won't make you a better manager. Mostly, it will make you chuckle, guffaw, and maybe even chortle. Make friends - it's the perfect gift for anyone who has ever suffered through one of those meetings. Order your copies today! |
TOP STORIES
Hyperconnected users growingSteve Jobs to keynote WWDC
CSC settles kickbacks case
MS previews SMB software
What does HP-EDS really mean?
Mac Office 2008 SP1 released
HP buys EDS for $13.9 billion
Corporate IT spending slows
MS targets smartphone market
Sun to clarify JavaFX plan
ADDITIONAL RESOURCES

- Virtualization: A Step by Step Approach to Success
- Dialing up Agility with Business Transformation
- 5 Things You Need to Know About Storage Virtualization

- Is your smaller organization ready for High Availability?
- Is system maintenance doing more harm than good?
- Virtual Test Lab Automation: Manage development infrastructure





