- Use of the package includes the right to print a single copy for personal use.. - Ownership of the copyright, trademark and all other rights, title and interest in the Package, as well as any copies, derivative works (if any are permitted) or merged portions made from the Package shall at all times remain with us or licensors to us. - You may not make copies of the files provided in the Package. - No part of this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means – electronic, mechanical, recording, or otherwise – without the prior written consent of the publisher.. - Example Document Standard 7,8,9. - Create a Document Standard. - Step 2 Implement the Intranet Publishing. - Training on the tools, the template, and the. - document standard Step 6. - document standard. - Gain an understanding of the current technologies in use within the organization so they can be integrated into the overall plan.. - Section 1.1: Identify Business Objectives, and Information for large-scale distribution. - Section 1.2: Determine Existing Technology Deployment. - This is useful information when we move into the later steps of the process. - Current status with respect to the Internet. - Section 1.3: Locate and Identify Legacy Documents. - Define the Intranet Publishing Paradigm 2. - Define the Intranet Team. - Determine who is going to fill the positions on the team, and adjust the MBOs, or job descriptions of the people contributing to the Intranet to include their new responsibilities.. - Create a mission statement for the Intranet and give it a name.. - Section 2.1: Intranet Publishing Paradigm. - The Intranet provides a, because it allows all of the information consumers within an organization to get to information as soon as it is published. - Will return documents to the Information Creator with revision comments.. - Checks the document to make sure it fits within the document standard. - Takes documents from the Technical Auditor and publishes them to the staging server.. - Moves the content from the staging server to the production Intranet Server.. - Section 2.2: Information Publishing Flow. - is someone with excellent knowledge of the document standard (defined later) and the publishing technology. - This person approves or sends the document back for further revisions based on technical merit.. - If the document passes both audits it can be published. - If the document is ok it is moved to the production site. - Section 2.3: Define the Intranet Team. - Determine who is going to fill the positions on the team and adjust the MBOs or job descriptions of. - the people contributing to the Intranet to include their new responsibilities.. - Section 2.4: Create a mission statement for the Intranet and give it a name.. - Section 3.1.a: Internet Security Structure. - Internet Web Server. - Extranet Web Server. - Intranet Web Server. - In consideration of the tools and resources required, security plays an important role in your Intranet design. - Depending on the scope of your project you may need to include some of the elements detailed in Figure 4.. - Section 3.1.b: A Full Service Intranet. - Web Server. - An Intranet today is far more than just an internal web server with some static web pages.. - Section 3.1.b.i: Infrastructure Servers. - Section 3.1.b.ii: Collaboration Servers. - Section 3.1.b.iii: Content and Information Servers. - Section 3.1.c: Site Management Tools &. - Section 3.1.d: Programming tools. - Section 3.1.e: Authoring Tools. - Section 3.2: Determine your Intranet Application Development architecture. - Section 3.2.a: Simple CGI Program. - Web Server Browser. - This sends the data the user entered to the web server.. - The web server receives the data and passes it to the program specified in the ACTION attribute of the <FORM>. - The CGI program creates a new HTML document on the fly and sends it to the client.. - Browser Web Server CGI Program. - Section 3.2.b: Three-Tier Web Application Development. - Web Server Database Server. - The program in this case creates a command and issues it to the database server.. - The data returned from the command is then sent back to the CGI application running on the web server.. - The CGI program creates a new HTML document on the fly with the data returned from the database server and sends it to the client.. - Database Server. - Section 3.2.c: Four-Tier Web Application Development. - In this case the program invokes a transaction on the transaction server.. - The data returned from the command is then sent back to the transaction, this cycle will continue until the transaction fails or completes.. - When the transaction completes successfully or unsuccessfully it passes the result to the web server.. - The CGI program running on the web server then creates a new HTML document on the fly with the data returned from the transaction server and sends it to the client.. - Step 4: Create a Document Standard and Navigation Standard Step 4: Create a Document Standard and Navigation Standard. - Section 4.1: The Document. - Date the document was published.. - Use of Meta Tags, or on the page. - Section 4.1.a: Technology Choices. - Section 4.2: Site Navigation Plan and Directory Structure. - Using the Document Standard create a Document Template and tie it into your authoring software.. - Step 6: Training on the tools, the template, and the document standard Step 6: Training on the tools, the template, and the document standard. - Train all of the content creators, content auditors, technical auditors, and publishers/site maintainers on the tools to increase their productivity.. - With a successful training program you have a number of authors that can publish good effective content using the document template and the document standard.. - Section 7.1.a: Alpha Release. - For the Alpha Release you should choose an area of high interest, or high return on investment, that can be created using as many of the tools you chose in employing your document standard, navigation standard, and you document template.. - This group may only contain members of the immediate project team. - For this reason we suggest the Alpha Users not be members of the immediate project team.. - This release will tell you whether everything is going to work the way you planned it or whether you are going to have to go back to the drawing board.. - Section 7.1.b: Beta Release. - You also want to get more of the content creators involved, as well as content auditors, technical auditors, and publishers.. - Section 7.1.c: Preview or Limited Release. - Section 7.1.d: Full Release. - In this release everyone should be an information consumer and should be told about the great things that exist on the Intranet for them.. - Aiding in the expansion of the site. - Example Document Standard for Content Creators. - Information relating to activities of the company such as sponsored organizations, events, etc.. - contents of the directory. - Keyword elements describing the contents of the page, for use with a search engine. - Each page should clearly display marked navigation buttons, with links to the following locations:. - Example Document Standard for Publishers. - IT involvement will be limited to configuration and maintenance of the server and generation and maintenance of top-level document hierarchy.. - whose responsibilities include managing the document hierarchy, and the server, and insuring the documents meet XYZ Corp web content guidelines.. - The webmaster designates space on the internal web server for the group and generates a login account on the server for the web coordinator. - Download released document hierarchy to web server.. - Provide backup service for information placed on the server.
Xem thử không khả dụng, vui lòng xem tại trang nguồn hoặc xem
Tóm tắt