Tables includes into DBPrism CMS owner.
Content assets are stored into two tables:
- pages, stores content meta-data such as page name, modification date, parent
information which defines a hierarchical structure and so on.
- content, stores the document assets with version information, every page stored
into the CMS makes a new row in this table and is connected to your page meta-data
through the foreign key.
Also the tables below is used by the CMS:
- related, stores information from-to of the CMS pages, these links provides mesh
structure of the information.
- Templates, has links to pages used as templates by the FrontEnd application
at the creation time of new pages.
Moreover(TM) News dynamic service uses two tables to store news downloaded from
Moreover's web site, these tables are populated every 24 hours through a CMS job.
- news_categories, stores categories of the news defined by Moreover.
- news_articles, stores articles downloaded from Moreover web site.
DBPrism project stores FAQs into tables, when an user asks for the /docs/faq.html
page a dynamic service queries these tables using Oracle's XML query and
transform it into document-v10.dtd format through a stylesheet stored into the
CMS repository.
- faq_sections, stores FAQ's section.
- faq_topics, stores question and answers connected to an specific section using
the foreign key.
|