Information architecture for the interactive environment
View Patent ↗A system and method for providing management such as creation, manipulation, storage, control, and retrieval of digital content for a company on a global basis. Digital content is created and stored in, for example, the eXtensible Markup Language (XML) format using the relationship between component mapping information and content information comprising webpage components. The XML data is developed by defining page components, mapping the components on a page and indexing the page for future retrieval of the page. The data is then stored in a single database, as segments related to the page, for call-up by a user. The information architecture of the present invention provides for a separation of data from the presentation itself. Thus, the information architecture data content, not being tied to the presentation, may, for example, enable the database to support various foreign languages, formats and medias.
1. A computer-implemented method for managing digital content for a company website on a global basis, including the steps of:
receiving, at a content management application, a request to create updated content for a content page within said company website, wherein said updated content comprises components;
creating said components according to said request;
storing each of said components within a markup language file in a database globally accessible by a reviewer, wherein said components are decoupled from said content page;
routing said components to said reviewer, wherein each of said components is individually routed;
creating an updated content page when each of said components has been authorized, wherein said updated content page does not include said components and comprises content mapping data which includes instructions for mapping said components to said updated content page;
receiving, from a computer of a user, a request to view said updated content page;
retrieving a category tag click count for at least one of said components corresponding to said user;
analyzing said category tag click count to determine a level of interest for establishing user preferences;
retrieving said components according to said user preferences, wherein each of said components includes a category tag corresponding to said user preferences; and
positioning said retrieved components on said updated content page according to said content mapping data.
2. The method of claim 1 , wherein said markup language file is in the eXtensible Markup Language (XML) format.
3. The method of claim 1 , further comprising translating said markup language file from a eXtensible Markup Language (XML) format to an HTML format for presentation on said company website.
4. The method of claim 1 , wherein storing said components as said markup language file includes storing said markup language file in an extensible database that is platform and software independent.
5. The method of claim 1 , wherein storing said components as said markup language file includes storing said markup language file, wherein said markup language file is an XML file, in an extensible database that is platform and software independent.
6. The method of claim 1 , further comprising translating said markup language file from a first markup language format to a second markup language format for presentation on said company website.
7. The method of claim 1 , wherein said components comprise at least one of content components, cross-sell components, and navigation components.
8. A computer-readable storage medium containing a set of instructions for a general-purpose computer comprising:
receiving, at a content management application, a request to create updated content for a content page within said company website, wherein said updated content comprises components;
creating said components according to said request;
storing each of said components within a markup language file in a database globally accessible by a reviewer, wherein said components are decoupled from said content page;
routing said components to said reviewer, wherein each of said components is individually routed;
creating an updated content page when each of said components has been authorized, wherein said updated content page does not include said components and comprises content mapping data which includes instructions for mapping said components to said updated content page;
receiving, from a computer of a user, a request to view said updated content page;
retrieving a category tag click count for at least one of said components corresponding to said user;
analyzing said category tag click count to determine a level of interest for establishing user preferences;
retrieving said components according to said user preferences, wherein each of said components includes a category tag corresponding to said user preferences; and
positioning said retrieved components on said updated content page according to said content mapping data.