Externally focused metadata is an essential element of a truly robust enterprise data model. A metadata repository can serve as a fundamental resource for enterprise applications of all kinds. Information architects can play a wide role in designing and developing the kind of metadata required to serve such a broad purpose.
In content metadata and hierarchies, you will often find a goldmine of implicit and explicit data that you can leverage to creatively contextualize content. After a brief introduction on taxonomy and metadata, this article focuses on finding and utilizing such relationships in hierarchies.
In part 4 of the continuing series on controlled vocabularies and faceted classification, the authors present a glossary of terms to help cut through through the verbiage often found in this field. And this glossary is more than just a list of terms. The glossary is itself a controlled vocabulary.
In part 3 of the continuing series on controlled vocabularies and faceted classification, the authors explain synonym rings and authority files and how their use can bridge the gap between natural language and complex controlled vocabularies (taxonomies and thesauri).
You have probably heard IAs discussing the benefits of their latest taxonomy project and how you should be implementing one. But how, you might wonder, can you get started? In the next installment about Controlled Vocabularies, our authors go into detail about one methodology.
Finding the right words to communicate the message of your website can be one of the most difficult parts of developing it. Our authors guide you through the concepts behind a well-designed controlled vocabulary and discuss the pros and cons of its development.
Information architects are fascinated with faceted classification and its application to information architecture problems. Our three authors present a series of in-depth articles covering faceted classification and controlled vocabularies and their practical application.
One of the dirty little secrets about being an information architect is that most of us only bat .500 at best. We labor and agonize over making recommendations and designing information architectures that are supposed to change the world, but many of our designs never see the light of day. Rather than moan about why my designs were not implemented, I want to share my story.