Information architecture (IA) is the structural design of shared information environments; the art and science of organizing and labelling websites, intranets, online communities and software to support usability and findability; and an emerging community of practice focused on bringing principles of design and architecture to the digital landscape. Typically, it involves an information model or concept of information that is used and applied to activities which require explicit details of complex information systems. These activities include library systems and database development.
Category: Content management & strategy (Page 96 of 479)
This category includes editorial and news blog posts related to content management and content strategy. For older, long form reports, papers, and research on these topics see our Resources page.
Content management is a broad topic that refers to the management of unstructured or semi-structured content as a standalone system or a component of another system. Varieties of content management systems (CMS) include: web content management (WCM), enterprise content management (ECM), component content management (CCM), and digital asset management (DAM) systems. Content management systems are also now widely marketed as Digital Experience Management (DEM or DXM, DXP), and Customer Experience Management (CEM or CXM) systems or platforms, and may include additional marketing technology functions.
Content strategy topics include information architecture, content and information models, content globalization, and localization.
For some historical perspective see:
https://gilbane.com/gilbane-report-vol-8-num-8-what-is-content-management/
Enterprise content integration (ECI) is a middleware software technology, often used within large organizations, that connects together various types of computer systems that manage documents and digital content. ECI systems often work in tandem with other technologies such as enterprise content management, document management, groupware, and records management. It takes a decentralized approach in order to manage content from various resources.
Also see enterprise information integration.
Digital experience (DX) emerged from work in the 1990s on “experience management” which included customers, employees, suppliers, and other stakeholders. Customer experience (CX) became the primary focus of experience management in the 2000s fueled by the growth of web commerce and other digital marketing channels. Technology suppliers and analysts serving marketing organizations began targeting CX in their products and services with features and their own marketing and branding efforts. In particular many “web content management (WCM) systems” became “customer experience management” (CXM), web experience management” or “web engagement management” systems (both using the WEM acronym). Most of these same products and services were also applicable and already in use for managing other stakeholder experiences, and became “digital experience” (DX) systems or platforms (DXPs), with CX being one component.
A positive digital experience requires much more than a pretty and fast web page or mobile app. There are other marketing technologies, internal back-end systems, supply chains, and operational workflows, digital or not, that need to be integrated with to ensure a smooth and informed experience. See Digital Experience is all about integration and agility.
The 2014 edition of the Gilbane Conference in Boston focused on Content Management, and Digital Experience: manage, measure, mobilize, monetize, and was designed for marketers, content managers, technologists, and executives responsible for building strategies and implementations for compelling multichannel digital experiences for customers, employees, and partners.
Chaired by: Frank Gilbane ∙ Organized by: Information Today Inc
Conference website: http://gilbaneconference.com/2014/
Program: http://gilbaneconference.com/2014/program.aspx
Speakers: http://gilbaneconference.com/2014/SpeakerList.aspx
Presentations: http://gilbaneconference.com/2014/Presentations.aspx
For posts about this conference see: https://gilbane.com/category/gilbane-conference/gilbane-conference-2014/
For additional information on our events see Gilbane Conferences.
The idea behind ‘information objects’ was that discrete pieces of information, along with metadata, were what should be the raw data for computing. Computing with information objects rather than bits or bytes or fixed-length records was the evolutionary step in information processing that would make the next big difference.
See Document Management & Information Objects
The term metadata refers to “data about data”, but both uses of “data” in practice are loose, in that they can refer to structured, unstructured, or semi-structured data, and can be descriptive or prescriptive. Metadata can also refer to physical objects.
Metadata is especially useful for creating, managing, publishing, categorizing, searching, and enhancing digital information. See the Wikipedia page on the Dublin Core for a good description.
https://en.wikipedia.org/wiki/Dublin_Core
The concept of an ‘information model’ goes back at least to the 1970s with the growth of digital information and database software to manage structured data. In the 1980s information models became a key tool for organizing and managing documents and unstructured data, and in the 1990s emerged as a critical requirement for complex content management applications. A ‘content model’ is an information model for unstructured data, or a combination of unstructured data types and structured data.
“An Information Model provides the framework for organizing your content so that it can be delivered and reused in a variety of innovative ways. Once you have created an Information Model for your content repository, you will be able to label information in ways that will enhance search and retrieval, making it possible for authors and users to find the information resources they need quickly and easily… The Information Model is the ultimate content-management tool.” (The Gilbane Report, Vol 10, Num 1, 2002 , What is an Information Model & Why do You Need One?).
“An information model provides formalism to the description of a problem domain without constraining how that description is mapped to an actual implementation in software. There may be many mappings of the information model. Such mappings are called data models, irrespective of whether they are object models (e.g. using UML), entity relationship models or XML schemas.” (Wikipedia).
Also see Integration DEFinition for information modeling (IDEF1X)
Content strategy refers to the planning, development, and management of content—written or in other media. The term has been particularly common in web development since the late 1990s. It is a recognized field in user experience design, and it also draws from adjacent disciplines such as information architecture, content management, business analysis, digital marketing, and technical communication.
https://en.wikipedia.org/wiki/Content_strategy
Also see: https://gilbane.com/category/content-management-strategy/
The term has also been adopted by the content marketing movement.
Subscribe to the Gilbane Advisor
