Browse Prior Art Database

Method to Customize Online Documentation Based on Hardware Capability of Computer Systems.

IP.com Disclosure Number: IPCOM000015997D
Original Publication Date: 2002-Jul-12
Included in the Prior Art Database: 2003-Jun-21
Document File: 2 page(s) / 43K

Publishing Venue

IBM

Abstract

Method to Customize Online Documentation Based on Hardware Capability of Computer Systems. One of the progressive shifts in computer hardware and software documentation is the move from mostly hardcopy documentation to softcopy. A key ingredient to this move was the innovative uses of hypertext links and eventually web browsers as a common and cheap method of displaying documentation. However, with the ease of this archival and display method, the growth of displayable data has grown enormously. Thus, users have to wade though more, mostly unrelated documentation, to reach the item they wish to read. A proposed solution is an option to the documentation display algorithm that can be initiated by the user. When the user starts the documentation engine or web browser, a preparatory program first analyzes the computer hardware setup of the user's system. Then, the program will offer to customize the data to be displayed so that only relevant information is displayed. For example, suppose a site is an "ethernet only" setup. Then, it would make no sense for the user to have to wade through instructions on how to configure and diagnose problems with token ring cards. Or, if the user has only 64-bit servers, then it makes no sense to include books or chapters which discuss 32- bit programming practices.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

Method to Customize Online Documentation Based on Hardware Capability of

Computer Systems.

One of the progressive shifts in computer hardware and software documentation is the move from mostly hardcopy documentation to softcopy. A key ingredient to this move was the innovative uses of hypertext links and eventually web browsers as a common and cheap method of displaying documentation. However, with the ease of this archival and display method, the growth of displayable data has grown enormously. Thus, users have to wade though more, mostly unrelated documentation, to reach the item they wish to read.

A proposed solution is an option to the documentation display algorithm that can be initiated by the user. When the user starts the documentation engine or web browser, a preparatory program first analyzes the computer hardware setup of the user's system. Then, the program will offer to customize the data to be displayed so that only relevant information is displayed. For example, suppose a site is an "ethernet only" setup. Then, it would make no sense for the user to have to wade through instructions on how to configure and diagnose problems with token ring cards. Or, if the user has only 64-bit servers, then it makes no sense to include books or chapters which discuss 32- bit programming practices.

As mentioned before, this option would be offered at the start of the documentation server. If during this use the user wishes to investigate token ring documentation, they can hit an override button that would allow ALL of the system documentation to become visible. Additionally, this would also apply to applied software. If you had Database Program A rather than Database Program B installed on your system, then it's pointless to have Database Program B documentation offered for you to read. Detail on how this would be implemented:

a) for each chapter or...