InformationArchitect

LouisRosenfeld? and PeterMorville? define information architecture as follows:

1. The combination of organization, labeling, navigation schemes and retrieval mechanisms within an information space.
2. The structural design of an information space to facilitate task completion and intuitive access to Content.
3. The art and science of structuring and classifying web sites, intranets and all other organizational information repositories to help people find and manage information.
4. An emerging discipline and CommunityOfPractice focused on bringing principles of design and architecture to the digital and paper-based landscape.

The InformationArchitect is responsible for strategies to Chunk and Tag, for ContentTemplate structures, forms for ContentElement entry, Metadata collection, Reuse, Syndication and Aggregation feeds, and database models or schemas.

How all the information is represented in the content of the CMS is an architecture problem. This art of classifying information is sometimes called taxonomy, the division of things into classes and class-members. Class-members may themselves constitute a Class with their own Class-members.

An InformationArchitect often has a background in LibraryScience, where the task was to organize, index, and abstract the books in a library or documents in a bibliographic InformationRetrieval? system.

The method included Classification and cataloging of a work under an agreed upon Categorization scheme, such as SubjectHeading?, creation of an Abstract or Description, plus tagging with the usual Metadata - Author, Title, Date of Publication, etc., now all standardized in the DublinCore.

LibraryScience goals or objectives were to allow users to find/locate books which had been collocated on a shelf or shelves of related books, so they could choose/select the best book for their needs, and then obtain access to the book by checking it out.

The difficult problem of displaying and navigating the arbitrary relations between physical books by placing them next to one another on shelves evaporated when information became digital and accessible over the Internet.

Despite dealing now with information bits rather than physical atoms ( NicholasNegroponte? ) we still have the five basic objectives defined by the International Federation of Library Associations and Institutions (IFLA)

• find/locate
• collocate/classify
• choice/select
• obtain/access
• navigate.

Now arbitrary relations between documents, even at the level of the ContentElement, are possible, but the near infinite flexibility poses the great challenge to the InformationArchitect, what UserInterface will be useful, usable, and used?

RT - Collocation?, ControlledVocabulary, LibraryScience, Thesaurus, EnterpriseInformationArchitecture


Up to CmsGlossary.