Content Management Service

Print this Page	1.1 Portfolio 23. Content Management Service	Close this Page

1.1.23. Content Management Service (CMS):

1. Every application service provided with dynamic business documents need the contents of those documents to be managed using a CMS. CMS is a common QMS portfolio that is configured to be part of most application services. The management of document content is part of a quality management service.

2. ECM means Enterprise Content Management.

4.5.01 CMS:

1. Content Management Services are a problem in that some documents want to be a file and some want to be DB records. After many years of using both files and records, the solution is total interchange from one style to the other.

2. Most people have been conditioned by Word that sets their expectations based on past experience. In practice, to author a web page can be quite a challenge using Word that has little concept of topic structure, links and menus. Just ask a person to use Word to replicate a web sites public pages - most people will find it impossible.

3. Two classes of documents can be identified: (1) documents that are relatively static and do not need evidence history and (2) documents that change and evidence of changes add value.

(1) Files are used to store static documents without history.

(2) Records are used to store dynamic documents with evidence history.

4. Files can be changed into records and records can be changed into files - total interchange will support both solutions. Every document can be viewed in a text area and any text area may be saved as a file or a set of statement-topic records.

2. Static File Service:

1. Fourth Generation Language (4GL) documents saved as files have been used for many decades and have proven to be very effective. In particular, global changes across hundreds of documents can be made in a single operation. Searching thousands of documents to find instances of a string and easy and very effective.

2. File systems are static with virtually no evidence history of who did what and when. An installed app such as WordPad++ is needed to process each file. People must remember to safe files and must remember not to delete files - work will be lost from time to time.

3. Dynamic Record Service:

1. Documents such as policies that need line by line evidence of changes are saved as records: statement in topic. A major benefit is that anybody with online access can edit any such document - its great for documents subject to change. Authoring a document as a series of statements in a topic is not what people expect - its not yet comfortable, even if its adequate.

2. A second window needs to be open at the same time to see a view of the document as it is being authored. Statements and topics can be moved, but this is not self-evident - its not yet comfortable. No data can be lost, data is automatically saved as it is entered, accidental changes can easily be reversed.

4. Interchange Service:

1. Documents are viewed as a web page and may be edited as a web page - a big text area. Wiki pages can be edited at the paragraph level and so all documents should have optional edit capabilities - at the topic level. Levels of editing may include privileges to move topics and delete topics. After making changes to a text area, the changes must be manually saved - changes not saved could be lost.

2. When a text area is saved, it may be saved as a static file or a dynamic set of statement-topic records. Adequate information must be shown in a text area to identify topics and statement types.

5. Evolution:

1. After more than 20 years of many different web page strategies, this current public web page strategy evolved. Simplicity became a founding principal because public web pages need to be viewed using any kind of device without any restrictions. Very simple HTML with inline CSS and no JavaScript is portable, can be emailed, can be printed and can be saved as a PDF. Containers and encryption serve no purpose and so they have been phased out.

2. Editors are available to a few authorised people using known computers on identified networks. (1) Full page text editor may be used for spell checking with Chrome. (2) Clone topic, paragraph or line with line editor may be used for dynamic updates in page layout mode. (3) New page can be named as a clone of an existing page. (4) Buttons exist to insert or update document control topics.

3. Every public web page has a unique subject name with the first few characters identify an inernational standard. Web pages are fragmented and managed by international standard - each internationl standard has its own manager.

6. Business Continuity:

1. Business rules are replicated in real-time to many data centers. Web pages are generated by Eliza as needed from business rules. Obsolete backup procedures are not used because recovery-restart procedures will always fail to some degree.

2. In the event that a data center is not available, business continues with public web pages provided from another data center. With more than ten replicated data centers, it is hard to imagine how any data could be lost.

3. No data is deleted and a historical copy of every public web page change is retained by date and time. It is very easy to recover a previous edition of a public web page as it was on a specific date and time.

4. Yes the amount od data stored as business rules is considerable, but that is the cost of a documentation service that cannot stop and cannot be stopped.

7. Security:

1. Public web page contents are published as normal HTML documents that are in the public domain and will be copied. Public web pages are an educational free service for the benefit of humanity - a way of saying thank you for the privileges we enjoy.

2. Every public web page is generated by Eliza from raw 4GL business rules that are stored in folders that cannot be accessed from the Internet. HTML cannot be defaced or hacked, because its transient and only exists once for one specific person. The only attack vector is the URL and Eliza simply shows a default web page when the URL is not perfectly formed. Business rules cannot be accessed from the Internet and Eliza cannot be hacked. No programming is involved and no database is involved, so criminals have no vulnerability to attack.

3. A handful of approved people using known computers on known networks are granted editing rights. The advanced security methods involved are not subject to phishing, advanced persistent threats or any other attack.

Vendor Product Services:

* Microsoft Sharepoint.

* Atlassian Confluence.

* Box.

* docSTAR Eclipse.

* Alfresco.

* BMC Documentum.

* Microsoft OneDrive.

* Objective ECM.

* Oracle Document and Process Cloud.

* Oracle WebCenter.

* Perceptive Software ImageNow.

* Siav Archiflow.

* Adobe Digital Enterprise Platform.

* Answerbase.

* ASG ViewDirect.

* Xerox Docshare.

* Ever Team.

* Fabasoft Folio.

* Hewlett Packard Enterprise Content Manager.

* Hyland OnBase.

* IBM ECM.

* IBM FileNet.

* Laserfiche Rio.

* NewGen OmiDocs.

* Nexeo.

* OpenText ECM.

* Orienge Conterra ECM.

* Saperion.

* Software Innovation Public 360.

* Spring CM.

* SunGuard EXP Macess.

* Systemware ECM.

* Xythos on Demand.

Document Control:

1. Document Title: Content Management Service.

2. Reference: 161123.

3. Keywords: CMS, Documents, public web pages.

4. Description: Every public web page is a document to the content management service.

5. Privacy: Shared with all approved people.

6. Issued: 11 Nov 2016.

7. Edition: 1.2.