Output
The reason we invest in capturing and indexing content and documents and managing them is so that when required we can search for and retrieve and reuse and publish the content and documents.
The requirements we identified in our check list in stage one were as follows.
| Function | Description | |
| 3 | Output | |
| 3.1 | Search | Facilities to search all metadata; search full text content; save searches; present search results |
| 3.2 | Display | Facilities to display all content/documents/records captured and managed on the system irrespective of whether the application used to create them is present or not. |
| 3.3 | Presentation | Facilities to present metadata and records to applications outside the solution in a form suitable for electronic publication |
| 3.4 | Facilities to print all types of content, documents and records which are printable in same way as they are displayed on screen | |
| 3.5 | Facsimile | Facilities to output content/documents to facsimile format and transmit it to defined facsimile numbers. |
| 3.6 | Facilities to attach content objects/ documents held in the solution to e-mail messages and send them to specified e-mail accounts | |
| 3.7 | Portal | Facilities to search and display content/documents held on the solution from within a named portal. |
| 3.8 | Multi channel content delivery/ publishing | Facilities to publish specified content to specified delivery channels using defined style sheets etc |
| 3.8.1 | Print publishing | Facilities to publish specified content to print media using defined style sheets etc. |
| 3.8.2 | CD/DVD publishing | Facilities to publish specified content on CD/DVD media using defined style sheets and software |
| 3.8.3 | Delivery to mobile phones | Facilities to render content in format suitable for display on mobile phone screens using defined style sheets and software |
| 3.8.4 | Delivery to PDAs | Facilities to render content in format suitable for display on PDA screens using defined style sheets and software |
| 3.8.5 | Internet/intranet/extranet Web site publishing | Facilities to render and publish specified content to specified Web sites using defined style sheets and web publishing software |
| 3.8.5.1 | Web site development | Facilities to define and develop web sites using web content management software |
| 3.8.5.2 | Develop web applications | Facilities to develop web applications using Web content management software |
| 3.8.5.3 | Develop web pages | Facilities to develop specific web pages for use on a web site using Web content management software |
| 3.8.5.4 | Check links | Facilities to check and maintain the integrity of all links made on a web site. |
| 3.8.5.5 | Content approval | Facilities to route content through an agreed approval process using web content management and business process management software. |
| 3.8.5.6 | Support multiple Web site deployments | Facilities to publish content to multiple web sites and synchronise process. |
| 3.8.5.7 | Content personalisation | Facilities to customise content delivered to a searcher based on profile gathered of searcher |
Requirements (3.1 to 3.3) are covered in TNA core requirement (A.3). You may need to specify additional facilities to meet your active document and content search, display and presentation requirements.
Requirements (3.1 to 3.7) cover basic search, retrieve, display and output requirements.
Requirement (3.8) covers content delivery/publishing requirements that will require the content to be held separately from the delivery process and involves defining by the use of style sheets how the content should be rendered and presented to suit the specific requirements of different delivery/publishing mechanisms.
