Rating: 
Summary: Buzzword loaded yet superficial
Review: Metadata Solutions--Using Metamodels, Repositories, XML, and Enterprise Portals to Generate Information on Demand targets a wide audience, from CIO/CTOs through business users through project managers through developers, vendors, and consultants. The book has six parts.Part I focuses on information. It begins by introducing data management, and briefly presenting data warehousing, object-oriented models, and directories as the integration technologies of the 1990s. A few 2-page case studies illustrate data warehousing, directories, and Web-based data management. Next it lays the groundwork for introducing metadata as the solution. Unfortunately, although some chapters mention packaged vendor solutions and ``tools, tools, and more tools'' (chapter 6), the lack of concrete examples keeps the discussion abstract. Part II introduces metadata. These chapters present a methodology that begins with requirements, stakeholders and perspectives, and produces metamodels and a metadata architecture. Before introducing the architecture, the author also presents several options for storing metadata. This part also includes a discussion that contrasts vendor and custom metamodels. However, the lack of vendor model examples leaves the discussion unconvincing. Part III discusses meta-metadata, shifting focus from the outside of a metadata solution to its implementation. The first chapter introduces meta-metadata and meta-metamodels. The following chapters present repositories, the Web, file managers and file systems, database systems, and class libraries as metadata-based technologies. This part concludes with a discussion of standards for metamodels, metadata exchange, and architectures and frameworks. The discussion covers efforts by the Meta Data Coalition, the Object Management Group, and the World Wide Web Consortium, among others. Part IV continues the implementation discussion, but focuses on non-metadata aspects. As such it covers the non-technical environment, the technical environment, and technical support. Finally, it discusses several implementation options from the perspective of the metadata store, and sketches a brief answer to the ``Buy versus Build'' question. Case studies illustrate non-metadata factors and an XML-based solution. Again, although sometimes the discussion involves packaged products or tools, the author doesn't provide concrete examples. Part V presents six sample metadata solutions. Generally case studies provide excellent vehicles to illustrate how reality impacts solutions presented on paper. Unfortunately, the case studies in this part are cursory and lack detail. As such, they do a poor job of showing how each metadata solution makes different tradeoffs to deal with its specific requirements. If you expect carefully dissected and thoughtfully presented case studies like in Software Architecture in Practice (by Bass, Clemens, and Kazman) you will be disappointed! Finally, part V focuses on the phase of the lifecycle following implementation: metadata solution maintenance. As such, it covers beneficiaries, the metadata quality, and how metadata fits within a business strategy. However, this part leaves unanswered an important question that has crystallized throughout the book: what types of problems are unsuitable for metadata solutions? The absence of this analysis may wrongfully lead uninitiated readers to regard metadata as a solution to problems it cannot solve. From a presentation perspective, the book has a distracting number of problems. The writing style uses passive voice and fairly long sentences. In addition, unlike most technical books, the text doesn't contain references. Instead, the author has chosen to supply a few additional readings for several topics at the end of the book. Moreover, most forward and backward references appear as footnotes. Finally, footnoting the ``5 Questions'' as copyrighted and trademarked each and every time they're mentioned comes off as a monotonous, repetitive, and tiring sales pitch. If you're looking for MBA-level information about metadata solutions, this book will give you a better idea of the area. However, if you're looking for detailed technical information about designing custom solutions or evaluating COTS systems, this book won't fit the bill. All in all, Metadata Solutions remains an MBA-level book written by an MBA.
Rating: 
Summary: Metadata is not always the solution
Review: Our large Fortune 100 organization is spending lots of time developing metadata. Because our existing data is redundant conflicting and sometimes just wrong, many feel that the presence of metadata will solve the problem. After one year we have lots of metadata, but still need much more
How do we make sure that this metadata will solve our information problems? I think this book got me to think in a different way and point me in the right direction It is nice to have metadata to explain why some of our data is wrong, it is even nicer to explain what the right data means. but when that is not possible, this book will help. I give it 5 stars because it is the first book with possibilities that I read in a long time. All of the others just don't seem to give me enough informatino
Rating:
Summary: THe facts about fixing metadata problems
Review: Overall a wandering essay. Not for the novice to data management. I recommend you take a look at David Marco's "Building and Managing the Meta Data Repository: A Full Lifecycle Guide" which I found to be much more useful and pointed. That said, if you are suffering from insomnia definitely buy this book, too!
Rating:
Summary: Didn't like it.
Review: Overall a wandering essay. Not for the novice to data management. I recommend you take a look at David Marco's "Building and Managing the Meta Data Repository: A Full Lifecycle Guide" which I found to be much more useful and pointed. That said, if you are suffering from insomnia definitely buy this book, too!
Rating: 
Summary: where's the tools and urls?
Review: Pros: discusses the real pitfalls in trying to keep repositories up to date.
Cons:
1. This whole meta metadata terminology suffers from technojargonitis...simple words that justify return on investment are needed
2. Where's the working tools or urls to sites that you might find tools? A book that neither includes a CD nor references to internet sites for further research seems out of date.
Rating: 
Summary: Defines Metadata Well
Review: Tannenbaum clearly knows the data storage and mining industry. She has produced a book that brings together a comprehensive view of metadata and of its parent, meta-metadata. It is rather easy to find a book on the details of XML, for example. Or on SQL and its various commercial and open source implementations. And on database design. But all these can be regarded as lower level details. What if you have several data warehouses, each with its own DBMS catalog, and the warehouses are not from the same vendor? Plus, there are manifold, quite separate application tools that read/write to these. You want to develop a coherent integrated view of the data, hopefully by using metadata descriptors. The type of texts mentioned above are of little help here. The vendor specific books typically orient you to their product alone. Tannenbaum has striven to fill this market gap. She explains what metadata is, and what a metamodel is. All done at a high level that frees you from the syntax of XML or SQL. Though she does use UML in many diagrams, you do not need to know UML to understand them. My only quibble is that perhaps some more detailed examples would have been instructive. The high level discussions are good. But some readers might miss the significances of some remarks. More explicit pedagogic examples might drive home the points.
Rating:
Summary: Disappointed
Review: the title of the book is very attractive, however I was so disappointed after i read the book.
Rating:
Summary: Essential for portal architects
Review: This book is not only essential for architects involved with portal design, but also the supporting cast of data architects, business analysts and process modelers. If the "XML" or "portal" keywords in the title led you top this book and you are not exactly sure what a "metadata solution is", the following definition from the book succinctly describes it and the theme of the book itself: Metadata solution An organized and integrated set of related metadata, logically connected but physically separate, with common access points and methods." The author covers the topic thoroughly, starting with an exhaustive discussion of information and its value to business that spans the first six chapters. Some excellent case studies are included to reinforce concepts. Part II consists of five chapters that take information up one level of abstraction and introduce metadata. Topics in this section start with requirements, and move to modeling. It's worth noting here that the OMG Open Information Model notation is heavily used in this section of the book. This should not be a problem because the notation is easy to follow and is widely known and used, reducing any learning curve to zero for experienced architects and modelers. Part III's three chapters delve into the underlying infrastructure technologies and tools. I especially liked the chapter on repositories, as well as the one that provided a balanced view of standards. Part IV is where the pace picks up with four chapters devoted to factors you need to consider before designing the solution. The case studies that are included in some of these chapters are important reading because they portray the issues and challenges that are associated with the factors. The last chapter in this section leads you through the design selection process.
I especially like Section V, which is a catalog of solutions that thoroughly examine each aspect of the solution. It starts off with a chapter that describes a typical disaster, followed by viable solutions presented in a format that can be easily recast into design patterns. I also like Section VI, which covers post-implementation administration and maintenance. The three chapters in this section cover topics that are often overlooked until a solution is ready to go into production or (in too many cases) after it has been released into production. Key points about this book: (1) It is unique in that it addresses the data abstraction requirements of portals, and does so comprehensively. (2) Provides an end-to-end view of metadata from concept to final solution using real life examples and sound techniques. This is a refreshing change from many books that address metadata, but are so abstract themselves that it is difficult to transform the concepts into a working solution. (3) Addresses post implementation issues, which is something I have never come across in a book on metadata. This is an important work and is essential reading for key players in a portal design and implementation project. Five stars and my highest recommendation.
Rating:
Summary: Essential for portal architects
Review: This book is not only essential for architects involved with portal design, but also the supporting cast of data architects, business analysts and process modelers. If the "XML" or "portal" keywords in the title led you top this book and you are not exactly sure what a "metadata solution is", the following definition from the book succinctly describes it and the theme of the book itself: Metadata solution An organized and integrated set of related metadata, logically connected but physically separate, with common access points and methods." The author covers the topic thoroughly, starting with an exhaustive discussion of information and its value to business that spans the first six chapters. Some excellent case studies are included to reinforce concepts. Part II consists of five chapters that take information up one level of abstraction and introduce metadata. Topics in this section start with requirements, and move to modeling. It's worth noting here that the OMG Open Information Model notation is heavily used in this section of the book. This should not be a problem because the notation is easy to follow and is widely known and used, reducing any learning curve to zero for experienced architects and modelers. Part III's three chapters delve into the underlying infrastructure technologies and tools. I especially liked the chapter on repositories, as well as the one that provided a balanced view of standards. Part IV is where the pace picks up with four chapters devoted to factors you need to consider before designing the solution. The case studies that are included in some of these chapters are important reading because they portray the issues and challenges that are associated with the factors. The last chapter in this section leads you through the design selection process.
I especially like Section V, which is a catalog of solutions that thoroughly examine each aspect of the solution. It starts off with a chapter that describes a typical disaster, followed by viable solutions presented in a format that can be easily recast into design patterns. I also like Section VI, which covers post-implementation administration and maintenance. The three chapters in this section cover topics that are often overlooked until a solution is ready to go into production or (in too many cases) after it has been released into production. Key points about this book: (1) It is unique in that it addresses the data abstraction requirements of portals, and does so comprehensively. (2) Provides an end-to-end view of metadata from concept to final solution using real life examples and sound techniques. This is a refreshing change from many books that address metadata, but are so abstract themselves that it is difficult to transform the concepts into a working solution. (3) Addresses post implementation issues, which is something I have never come across in a book on metadata. This is an important work and is essential reading for key players in a portal design and implementation project. Five stars and my highest recommendation.
Rating:
Summary: Who cares about a CD?
Review: This book, without a CD, has more practical metadata information than any other one I've read. THere is a section, Part V, which shows actual solution implementations. In fact, each chapter represents a specific type of implementation including centralized repositories, information directories, centralized and distributed metadata stores (these by the way are not the same as repositories), metadata exchange (XML is the example used), portal-based information access. I suspect that all of these practical solutions represent actual implementations. In some cases, the submitters are mentioned. Many of the chapters however were written by consultants from Adrienne Tannenbaum's firm. If you are looking for something to plug into your CD-ROM, then don't get this book. But if you are looking for something that will help you get a job done, then I strongly recommend it.
| 
