US20080016039A1 - System and method for generating and retrieving different document layouts from a given content - Google Patents
System and method for generating and retrieving different document layouts from a given content Download PDFInfo
- Publication number
- US20080016039A1 US20080016039A1 US11/775,514 US77551407A US2008016039A1 US 20080016039 A1 US20080016039 A1 US 20080016039A1 US 77551407 A US77551407 A US 77551407A US 2008016039 A1 US2008016039 A1 US 2008016039A1
- Authority
- US
- United States
- Prior art keywords
- document
- components
- search
- documents
- program code
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/951—Indexing; Web crawling techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/93—Document management systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
- G06F16/9532—Query formulation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
- G06F16/9538—Presentation of query results
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99931—Database or file accessing
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99931—Database or file accessing
- Y10S707/99932—Access augmentation or optimizing
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99931—Database or file accessing
- Y10S707/99933—Query processing, i.e. searching
Definitions
- the present invention is related to searching and retrieving electronic documents over a computer network and more specifically, to dynamically assembling electronic documents at retrieval, based on the document type most suitable for the user context.
- search engines Normally, someone wishing to find information over the Internet uses a search engine to identify and retrieve relevant documents.
- Documents available over the Internet normally have a fixed document type (e.g. Download, Hints & Tips, White Paper, etc.) with static content layout.
- Specialized search engines may filter search results based on document type, filtering out all documents not matching the specified document type or types.
- FIG. 1 illustrates a traditional document search and retrieval system 100 or search engine that may be used for such searches.
- the search engine 100 returns documents of one preferred type only without returning other possibly more relevant documents.
- the system 100 includes a user interface 102 , a search unit 104 , a textual index 106 and a document storage system 108 .
- the document storage system 108 contains different types of static documents, e.g., Frequently Asked Questions (FAQ), Downloads and Authorized Program Analysis Reports (APAR).
- the textual index 106 contains a searchable index for documents in document storage system 108 .
- Each search query includes both search terms and preferred document type that are entered at user interface 102 and passed to search unit 104 .
- Search unit 104 searches textual index 106 to identify a hitlist, e.g., of FAQ documents, that contain specified search terms. Search unit 104 returns the document hitlist through user interface 102 . So, for example, listed FAQs are selected from document storage system 108 for viewing through user interface 102 .
- this typical system 100 may not provide an answer/solution to the query, especially, when the correct answer is embedded in a document that does not match the requested document type/layout.
- a prior art system may limit the search scope to Download documents only. So, the search engine may overlook relevant information that appears in a Hints&Tips document instead for example. So, the search result is somewhat limited by a document layout or type that is normally once and forever determined by the document provider.
- the searcher cannot choose content layout.
- typical state of the art search engines are restricted by the static nature of available documents. Thus, navigating through document storage to find relevant information often requires a level of familiarity with the document type schema. Document organization may hamper searching. Different content providers cannot choose suitable content and layout for particular local portals. So, users must live with whatever documents are stored and available.
- the present invention is a document search and retrieval system and program product therefor.
- Search requests are provided to the system through a user interface.
- a document decomposer decomposes documents into individual document components. Document components and corresponding searchable indices for each are stored in a Component Library.
- a search unit searches stored document components responsive to search queries.
- a results validator compares document hitlists with a document type identified in a search query to select valid hitlists entries for a final hitlist.
- a document view assembly module collects identified document components and assembles them into a document for view at the user interface.
- FIG. 1 shows a block diagram of a prior art document retrieval system
- FIG. 2 shows a block diagram of an example of a preferred embodiment of the present invention
- FIG. 3 shows an example of document decomposition and indexing schema according to a preferred embodiment wherein a Document Decomposer module extracts document components and stores them in the Component Library;
- FIG. 4 shows an example of a document decomposition and indexing flow chart showing how the Document Decomposer module interacts with other modules
- FIG. 5 shows an example of a preferred embodiment document search schema, wherein different type documents are returned by the Search Engine for selection and viewing;
- FIG. 6 shows an example of a preferred document search flow chart of how the Results Validator module interacts with other modules of the present invention
- FIG. 7 is an example of a document viewing schema, wherein the Document View Builder module retrieves document components from the Component Library module and assemble a document for view according to the selected context;
- FIG. 8 shows an example of a preferred document viewing flow chart of how the Document View Builder interacts with other modules of the present invention.
- content components are extracted from original documents and stored in a component library.
- a query calls for information found in the content components, a context is selected in which retrieved information is viewed.
- Documents of the chosen type/layout are constituted on the fly from stored document components. More relevant documents may be identified and rendered in a selected context/layout.
- FIG. 2 shows an example of a component based document search and retrieval system 110 according to a preferred embodiment of the invention.
- the system 110 includes an User Interface 112 , a Search Unit 114 , a Textual Index 116 , Document Storage 118 , a Component Library 120 , a Document Decomposer 122 , a Document View Builder 124 and a Result Validator 126 .
- the Document Storage 118 contains different types of documents, e.g., FAQs 128 , Downloads 130 and APARs 132 .
- the Document Decomposer 122 distills individual components from each of the documents 128 , 130 , 130 and the components are stored in the Component Library 120 .
- a typical FAQ 128 might include a Title, a Problem Statement, a Solution and, optionally a reference link to additional information. Further, these document components can be collected and assembled to form an FAQ document.
- a Download document may include a Title, a Solution, an Attachment and a reference.
- Table 1 is an example illustrating typical document components for several document types. Typically, each of these components is tagged by a section subtitle in the original document. Each document type has its own set of sections according to predefined corporate templates.
- the Document Decomposer 122 locates each tagged component, extracts each located component and stores extracted components in the Component Library 120 . Then, the individual components are indexed in the Textual Index Unit 116 , making each indexed component available for full text search.
- TABLE 1 Refer- Doc. Type Title Abstract Problem Solution Attachment ence FAQ X X X X APAR X X X X X Hints&Tips X X X Download X X X X X X
- a search is initiated with a query that specifies both search terms and preferred document type passing through the User Interface 112 to Search Unit 114 .
- Search Unit 114 searches component indices in Textual Index 116 and retrieves a hitlist for specified search terms.
- Results Validator 126 checks the hitlist and identifies candidates that include all of the components needed to constitute a document in the selected format, e.g., FAQ format. The Results Validator 126 returns a list of remaining documents that can be constituted into the selected format.
- Each request also passes through User Interface 112 to Document View Assembly Module 124 which retrieves and assembles components into a document in the selected format. The assembled document is returned for viewing through User Interface 112 .
- FIG. 3 illustrates document decomposition and indexing document collections 140 , 142 , 144 by Document Decomposer 122 .
- Different types of documents pass from collections 140 , 142 , 144 to Document Decomposer 122 .
- the Document Decomposer 122 locates and extracts document components/elements, according to the original document type model (e.g., Table 1). Extracted document components are stored in Component Library 120 . Then, the content of each of the document components is indexed in the Textual Index 116 for full text search.
- FIG. 4 shows an example of a document decomposition and indexing flow chart 150 .
- the Document Storage System 116 passes a document 152 to Document Decomposer 122 .
- the Document Decomposer 122 extracts document components 154 and passes the extracted components to Component Library 120 .
- Document components are passed from Component Library 120 to Indexer 156 which creates an inverted Textual Index 158 of all words in each document component to enable full text search.
- the Indexer 156 associates the entries in this Textual Index 158 with documents that contain the components.
- the Component Library 120 contains a table of document type masks for every supported document type.
- Table 2 shows an example of a document type mask table for the above example of four identified document types.
- Each document type mask defines a set of components constituting a particular document type.
- TABLE 2 Refer- Doc. Type Title Abstract Problem Solution Attachment ence FAQ 1 0 1 1 0 1 APAR 1 1 1 1 0 1 Hints&Tips 1 1 0 1 0 0 0 Download 1 0 0 1 1 1
- a document search is constrained such that the search result hitlist includes only documents that can be rendered in the requested viewing context. So, for example, while search results may identify numerous documents in each of the document types, the search results hitlist would list only those documents that can be constitute a FAQ type layout, i.e., FAQ and APAR type documents.
- FIG. 5 shows an example of this second preferred embodiment document search schema 160 .
- a Search Query 162 that specifies both query terms and a selected document type is submitted to Search Engine 164 .
- the Search Engine 164 uses the Textual Index 166 to find stored document components that contain the specified query terms.
- a hitlist of document hits of appropriate document types is extracted from Textual Index 166 as Search Results 168 .
- the Search Results 168 hitlist is passed to the Results Validator 170 which uses an appropriate document type mask to perform document selection, selecting documents that can be rendered in the selected context.
- the Results Validator 170 uses a requested document type mask from the Component Library 120 to filter documents (exclude) from the hitlist that could not be configured to match the requested document type.
- Results Validation Table 174 is an example of results validation output from Results Validator 170 .
- the Final Results 176 hitlist is a reduced hitlist that includes only documents with at least matching components necessary for requested document type.
- FIG. 6 shows a flow chart of a document search 180 using the document schema 160 of FIG. 5 .
- a user submits a search query 182 to Search Engine 184 initiating the search.
- the Search Engine 184 uses the Textual Index 186 to produce a hitlist 188 of documents with components that match query terms.
- the Results Validator 190 checks document hits in the hitlist 188 against the requested document type mask from Component Library 120 . Only documents with at least components in the document type mask are output in a Final Hitlist 192 .
- FIG. 7 shows an example of a preferred document viewing schema 200 .
- the user may select one of the listed documents to view the document content.
- the request is passed to a Document Retrieval Module 200 that retrieves requested document components from the Component Library 120 .
- One of the hits e.g., an APAR document
- the Document View Builder 204 retrieves requested components from Component Library 120 and assembles the document components according to the requested document mask (FAQ mask) by applying the layout defined by the requested document type.
- FAQ mask requested document mask
- FIG. 8 shows an example of a document view construction flow chart 210 .
- the Document View Builder 218 assembles the document by including and omitting relevant components to match the requested document type. After selecting an entry from final hitlist 212 , the Document View Builder 214 retrieves components for the selected entry from the Component Library 216 . Then, the Document View Builder 214 assembles the components into a viewable document according to the selected format and outputs the assembled document over the user interface for viewing 218 .
- search result documents are provided in a user selected document type based upon the user request.
- Documents of a requested type are assembled dynamically from a given content.
- the document with an answer/solution for the user's question/problem can be found, even if its static document type does not match the document type requested by the user.
- the number of available document types for a given content is supplemented from previously unavailable documents.
Abstract
A document search and retrieval system and program product therefor. Search requests are provided to the system through a user interface. A document decomposer decomposes documents into individual document components. Document components and corresponding searchable indices for each are stored in a Component Library. A search unit searches stored document components responsive to search queries. A results validator compares document hitlists with a document type identified in a search query to select valid hitlists entries for a final hitlist. A document view assembly module collects identified document components and assembles them into a document for view at the user interface.
Description
- The present application is a divisional application of allowed U.S. patent application Ser. No. 10/159,373, (Attorney docket No. YOR920020124US1) entitled “A SYSTEM AND METHOD FOR GENERATING AND RETRIEVING DIFFERENT DOCUMENT LAYOUTS FROM A GIVEN CONTENT” to Gregory T. Brown et al., filed Jun. 3, 2002, now issued as U.S. Pat. No. 7,254,571, which is assigned to the assignee of the present invention and incorporated herein by reference.
- 1. Field of the Invention
- The present invention is related to searching and retrieving electronic documents over a computer network and more specifically, to dynamically assembling electronic documents at retrieval, based on the document type most suitable for the user context.
- 2. Background Description
- Normally, someone wishing to find information over the Internet uses a search engine to identify and retrieve relevant documents. Documents available over the Internet normally have a fixed document type (e.g. Download, Hints & Tips, White Paper, etc.) with static content layout. Specialized search engines may filter search results based on document type, filtering out all documents not matching the specified document type or types.
-
FIG. 1 illustrates a traditional document search andretrieval system 100 or search engine that may be used for such searches. In response to each search query, thesearch engine 100 returns documents of one preferred type only without returning other possibly more relevant documents. Thesystem 100 includes auser interface 102, asearch unit 104, atextual index 106 and adocument storage system 108. Thedocument storage system 108 contains different types of static documents, e.g., Frequently Asked Questions (FAQ), Downloads and Authorized Program Analysis Reports (APAR). Thetextual index 106 contains a searchable index for documents indocument storage system 108. Each search query includes both search terms and preferred document type that are entered atuser interface 102 and passed tosearch unit 104. Searchunit 104 searchestextual index 106 to identify a hitlist, e.g., of FAQ documents, that contain specified search terms.Search unit 104 returns the document hitlist throughuser interface 102. So, for example, listed FAQs are selected fromdocument storage system 108 for viewing throughuser interface 102. Two such examples of technical support search engines that include document type with a search query are support sites from Microsoft Corporation (support.microsoft.com/default.aspx?scid=fh;EN-US;sql), where topic category must specify document type; and, from IBM Corporation (www-1.ibm.com/support/manager.wss?rs=0&rt=2), where the user directly specifies document type. - Unfortunately, very often this
typical system 100 may not provide an answer/solution to the query, especially, when the correct answer is embedded in a document that does not match the requested document type/layout. In another example, to find downloadable video driver for product A, a prior art system may limit the search scope to Download documents only. So, the search engine may overlook relevant information that appears in a Hints&Tips document instead for example. So, the search result is somewhat limited by a document layout or type that is normally once and forever determined by the document provider. Typically, unless the same document is stored in multiple formats, the searcher cannot choose content layout. So, typical state of the art search engines are restricted by the static nature of available documents. Thus, navigating through document storage to find relevant information often requires a level of familiarity with the document type schema. Document organization may hamper searching. Different content providers cannot choose suitable content and layout for particular local portals. So, users must live with whatever documents are stored and available. - These search constraints are especially troublesome in corporate technical support systems, typically a complex hierarchical schema of document types combined with a product taxonomy tree. Usually corporate-wide documents are standardized to provide a unified document view through the corporate technical support portal. These constraints make retrieving information from a corporate technical support system a challenging task especially if the document storage system contains heterogenous document collections.
- Thus, there is a need for a way to select document presentation according to the needs of a particular user or presentation context.
- It is a purpose of the invention to facilitate finding relevant information regardless of the format of documents containing the information;
- It is another purpose of the invention to present such information in a selectable document type and/or layout that may not match the format of the original document containing the information;
- It is yet another purpose of the invention to choose a most suitable document content layout.
- The present invention is a document search and retrieval system and program product therefor. Search requests are provided to the system through a user interface. A document decomposer decomposes documents into individual document components. Document components and corresponding searchable indices for each are stored in a Component Library. A search unit searches stored document components responsive to search queries. A results validator compares document hitlists with a document type identified in a search query to select valid hitlists entries for a final hitlist. A document view assembly module collects identified document components and assembles them into a document for view at the user interface.
- The foregoing and other objects, aspects, and advantages will be better understood from the following non limiting detailed description of preferred embodiments of the invention with reference to the drawings that include the following:
-
FIG. 1 shows a block diagram of a prior art document retrieval system; -
FIG. 2 shows a block diagram of an example of a preferred embodiment of the present invention; -
FIG. 3 shows an example of document decomposition and indexing schema according to a preferred embodiment wherein a Document Decomposer module extracts document components and stores them in the Component Library; -
FIG. 4 shows an example of a document decomposition and indexing flow chart showing how the Document Decomposer module interacts with other modules; -
FIG. 5 shows an example of a preferred embodiment document search schema, wherein different type documents are returned by the Search Engine for selection and viewing; -
FIG. 6 shows an example of a preferred document search flow chart of how the Results Validator module interacts with other modules of the present invention; -
FIG. 7 is an example of a document viewing schema, wherein the Document View Builder module retrieves document components from the Component Library module and assemble a document for view according to the selected context; -
FIG. 8 shows an example of a preferred document viewing flow chart of how the Document View Builder interacts with other modules of the present invention. - According to a preferred embodiment of the present invention, content components are extracted from original documents and stored in a component library. When a query calls for information found in the content components, a context is selected in which retrieved information is viewed. Documents of the chosen type/layout are constituted on the fly from stored document components. More relevant documents may be identified and rendered in a selected context/layout.
-
FIG. 2 shows an example of a component based document search andretrieval system 110 according to a preferred embodiment of the invention. Thesystem 110 includes anUser Interface 112, a Search Unit 114, aTextual Index 116,Document Storage 118, aComponent Library 120, aDocument Decomposer 122, aDocument View Builder 124 and aResult Validator 126. TheDocument Storage 118 contains different types of documents, e.g.,FAQs 128, Downloads 130 andAPARs 132. - The
Document Decomposer 122 distills individual components from each of thedocuments 128, 130, 130 and the components are stored in theComponent Library 120. For example, atypical FAQ 128 might include a Title, a Problem Statement, a Solution and, optionally a reference link to additional information. Further, these document components can be collected and assembled to form an FAQ document. Likewise, a Download document may include a Title, a Solution, an Attachment and a reference. Table 1 is an example illustrating typical document components for several document types. Typically, each of these components is tagged by a section subtitle in the original document. Each document type has its own set of sections according to predefined corporate templates. TheDocument Decomposer 122 locates each tagged component, extracts each located component and stores extracted components in theComponent Library 120. Then, the individual components are indexed in theTextual Index Unit 116, making each indexed component available for full text search.TABLE 1 Refer- Doc. Type Title Abstract Problem Solution Attachment ence FAQ X X X X APAR X X X X X Hints&Tips X X X Download X X X X - A search is initiated with a query that specifies both search terms and preferred document type passing through the
User Interface 112 to Search Unit 114. Search Unit 114 searches component indices inTextual Index 116 and retrieves a hitlist for specified search terms.Results Validator 126 checks the hitlist and identifies candidates that include all of the components needed to constitute a document in the selected format, e.g., FAQ format. TheResults Validator 126 returns a list of remaining documents that can be constituted into the selected format. Each request also passes throughUser Interface 112 to DocumentView Assembly Module 124 which retrieves and assembles components into a document in the selected format. The assembled document is returned for viewing throughUser Interface 112. -
FIG. 3 illustrates document decomposition andindexing document collections Document Decomposer 122. Different types of documents pass fromcollections Document Decomposer 122. TheDocument Decomposer 122 locates and extracts document components/elements, according to the original document type model (e.g., Table 1). Extracted document components are stored inComponent Library 120. Then, the content of each of the document components is indexed in theTextual Index 116 for full text search. -
FIG. 4 shows an example of a document decomposition andindexing flow chart 150. TheDocument Storage System 116 passes adocument 152 toDocument Decomposer 122. TheDocument Decomposer 122extracts document components 154 and passes the extracted components toComponent Library 120. Document components are passed fromComponent Library 120 toIndexer 156 which creates an invertedTextual Index 158 of all words in each document component to enable full text search. TheIndexer 156 associates the entries in thisTextual Index 158 with documents that contain the components. - In addition to document components, the
Component Library 120 contains a table of document type masks for every supported document type. Table 2 shows an example of a document type mask table for the above example of four identified document types. Each document type mask defines a set of components constituting a particular document type.TABLE 2 Refer- Doc. Type Title Abstract Problem Solution Attachment ence FAQ 1 0 1 1 0 1 APAR 1 1 1 1 0 1 Hints&Tips 1 1 0 1 0 0 Download 1 0 0 1 1 1 - In another preferred embodiment of the present invention, a document search is constrained such that the search result hitlist includes only documents that can be rendered in the requested viewing context. So, for example, while search results may identify numerous documents in each of the document types, the search results hitlist would list only those documents that can be constitute a FAQ type layout, i.e., FAQ and APAR type documents.
-
FIG. 5 shows an example of this second preferred embodimentdocument search schema 160. ASearch Query 162 that specifies both query terms and a selected document type is submitted toSearch Engine 164. TheSearch Engine 164 uses theTextual Index 166 to find stored document components that contain the specified query terms. A hitlist of document hits of appropriate document types is extracted fromTextual Index 166 asSearch Results 168. The Search Results 168 hitlist is passed to theResults Validator 170 which uses an appropriate document type mask to perform document selection, selecting documents that can be rendered in the selected context. TheResults Validator 170 uses a requested document type mask from theComponent Library 120 to filter documents (exclude) from the hitlist that could not be configured to match the requested document type. Results Validation Table 174 is an example of results validation output fromResults Validator 170. TheFinal Results 176 hitlist is a reduced hitlist that includes only documents with at least matching components necessary for requested document type. -
FIG. 6 shows a flow chart of adocument search 180 using thedocument schema 160 ofFIG. 5 . A user submits asearch query 182 toSearch Engine 184 initiating the search. TheSearch Engine 184 uses theTextual Index 186 to produce ahitlist 188 of documents with components that match query terms. TheResults Validator 190 checks document hits in thehitlist 188 against the requested document type mask fromComponent Library 120. Only documents with at least components in the document type mask are output in aFinal Hitlist 192. -
FIG. 7 shows an example of a preferreddocument viewing schema 200. Once the search is completed, (i.e., in 176 and 192 ofFIGS. 5 and 6 ), the user may select one of the listed documents to view the document content. The request is passed to aDocument Retrieval Module 200 that retrieves requested document components from theComponent Library 120. One of the hits (e.g., an APAR document) in theHitlist 202 is selected for viewing. TheDocument View Builder 204, retrieves requested components fromComponent Library 120 and assembles the document components according to the requested document mask (FAQ mask) by applying the layout defined by the requested document type. -
FIG. 8 shows an example of a document viewconstruction flow chart 210. TheDocument View Builder 218 assembles the document by including and omitting relevant components to match the requested document type. After selecting an entry fromfinal hitlist 212, theDocument View Builder 214 retrieves components for the selected entry from the Component Library 216. Then, theDocument View Builder 214 assembles the components into a viewable document according to the selected format and outputs the assembled document over the user interface forviewing 218. - Thus, search result documents are provided in a user selected document type based upon the user request. Documents of a requested type are assembled dynamically from a given content. The document with an answer/solution for the user's question/problem can be found, even if its static document type does not match the document type requested by the user. Advantageously, the number of available document types for a given content is supplemented from previously unavailable documents.
- While the invention has been described in terms of preferred embodiments, those skilled in the art will recognize that the invention can be practiced with modification within the spirit and scope of the appended claims.
Claims (21)
1. A system for searching document components and retrieving search result documents, said system comprising:
a document decomposer decomposing documents into individual document components;
a component library storing said document components;
a search unit searching stored said document components responsive to search queries; and
a results validator analyzing document hitlists of documents identified by said search unit against a document type identified in a search query to select valid hitlists entries for a final hitlist.
2. A system as in claim 1 wherein search requests are provided as said search queries including search terms and a preferred document type to said system through a user interface and search results are provided from said system through said user interface.
3. A system as in claim 1 wherein the document decomposer locates document components within an identified document, extracts each located component and stores extracted components in said component library.
4. (canceled)
5. A system as in claim 3 wherein said results validator identifies documents in said hitlist containing components constituting a selected document type.
6. A document search and retrieval system as in claim 5 wherein said document decomposer decomposes documents of document types including frequently asked questions (FAQ), downloads and authorized program analysis reports (APAR).
7. A system as in claim 1 further comprising:
a textual index unit containing a searchable index of said components stored in said component library.
8. A system as in claim 7 wherein said textual index unit includes an indexer indexing components in said component library to create a textual index for each component.
9. A system as in claim 1 , further comprising:
a document view assembly module collecting identified said document components and assembling collected said document components into a document for view at said user interface.
10. A document component search system operating on one or more computer systems, the computer systems having one or more central processing units (CPUs), one or more memories, and one or more network interfaces connecting the computer system to one or more computer networks, said document search system comprising:
a document decomposer extracting text subportions from documents to distill document components, said documents being defined by one or more document type models, document components being indexed for full text searching;
a document search unit identifying relevant documents of static document type and validating search results, valid search results being documents that include all components of a requested document type; and
a document retrieval unit collecting components for a selected document type from a selected valid document and dynamically assembling said document components according to said selected document type for display.
11. A document component search system as in claim 10 , said document decomposer comprising:
identification means for identifying document components according to document type;
storage means for storing documents for decomposition and storing document components in a component library; and
text indexing means for indexing document component content for text searching.
12-13. (canceled)
14. A computer program product for searching and retrieving document components and presenting documents constituted from retrieved components for view, said computer program product comprising a computer usable medium having computer readable program code thereon, said computer readable program code comprising:
computer readable program code means for entering search requests and presenting search results for view;
computer readable program code means for decomposing documents into individual document components;
computer readable program code means for storing said document components;
computer readable program code means for searching stored document components responsive to a search query and listing documents identified as responding to said search query in a hitlist; and
computer readable program code means for analyzing document hitlists against a document type identified in said search query to select valid hitlists entries for a final hitlist.
15. A computer program product as in claim 14 , wherein decomposable document types include frequently asked questions (FAQ), downloads and authorized program analysis reports (APAR).
16. A computer program product as in claim 14 , wherein the computer readable program code means for entering search requests accepts queries including search terms and a preferred said document type.
17. A computer program product as in claim 14 , further comprising:
computer readable program code means for storing a searchable index of said document components stored in said component library.
18. A computer program product as in claim 17 , wherein said computer readable program code means for decomposing documents locates document components within an identified document, extracts each located component and stores extracted components in said component library.
19. A computer program product as in claim 17 , wherein said computer readable program code means for storing a searchable index includes computer readable program code means for indexing components in said component library to create a textual index for each stored said document component, said textual index being stored as a searchable index.
20. (canceled)
21. A computer program product as in claim 17 , wherein said computer readable program code means for analyzing document hitlists identifies documents in said hitlist containing components constituting a selected document type.
22. A computer program product as in claim 14 , further comprising: computer readable program code means for collecting identified said document components and assembling collected said document components into a document for view.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/775,514 US20080016039A1 (en) | 2002-06-03 | 2007-07-10 | System and method for generating and retrieving different document layouts from a given content |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/159,373 US7254571B2 (en) | 2002-06-03 | 2002-06-03 | System and method for generating and retrieving different document layouts from a given content |
US11/775,514 US20080016039A1 (en) | 2002-06-03 | 2007-07-10 | System and method for generating and retrieving different document layouts from a given content |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/159,373 Division US7254571B2 (en) | 2002-06-03 | 2002-06-03 | System and method for generating and retrieving different document layouts from a given content |
Publications (1)
Publication Number | Publication Date |
---|---|
US20080016039A1 true US20080016039A1 (en) | 2008-01-17 |
Family
ID=29582883
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/159,373 Expired - Fee Related US7254571B2 (en) | 2002-06-03 | 2002-06-03 | System and method for generating and retrieving different document layouts from a given content |
US11/775,514 Abandoned US20080016039A1 (en) | 2002-06-03 | 2007-07-10 | System and method for generating and retrieving different document layouts from a given content |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/159,373 Expired - Fee Related US7254571B2 (en) | 2002-06-03 | 2002-06-03 | System and method for generating and retrieving different document layouts from a given content |
Country Status (1)
Country | Link |
---|---|
US (2) | US7254571B2 (en) |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8521757B1 (en) * | 2008-09-26 | 2013-08-27 | Symantec Corporation | Method and apparatus for template-based processing of electronic documents |
US20140278364A1 (en) * | 2013-03-15 | 2014-09-18 | International Business Machines Corporation | Business intelligence data models with concept identification using language-specific clues |
US9544906B2 (en) | 2007-01-22 | 2017-01-10 | Samsung Electronics Co., Ltd. | Channel allocation method in wireless mesh network and communication device using the method |
US9984116B2 (en) | 2015-08-28 | 2018-05-29 | International Business Machines Corporation | Automated management of natural language queries in enterprise business intelligence analytics |
US10002179B2 (en) | 2015-01-30 | 2018-06-19 | International Business Machines Corporation | Detection and creation of appropriate row concept during automated model generation |
US10698924B2 (en) | 2014-05-22 | 2020-06-30 | International Business Machines Corporation | Generating partitioned hierarchical groups based on data sets for business intelligence data models |
Families Citing this family (47)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7464072B1 (en) | 2001-06-18 | 2008-12-09 | Siebel Systems, Inc. | Method, apparatus, and system for searching based on search visibility rules |
US6952691B2 (en) * | 2002-02-01 | 2005-10-04 | International Business Machines Corporation | Method and system for searching a multi-lingual database |
US7254571B2 (en) * | 2002-06-03 | 2007-08-07 | International Business Machines Corporation | System and method for generating and retrieving different document layouts from a given content |
US7721192B2 (en) * | 2002-11-27 | 2010-05-18 | Microsoft Corporation | User interface for a resource search tool |
US7949937B2 (en) | 2002-12-31 | 2011-05-24 | Business Objects Software Ltd | Apparatus and method for delivering portions of reports |
US20050262047A1 (en) * | 2002-12-31 | 2005-11-24 | Ju Wu | Apparatus and method for inserting portions of reports into electronic documents |
US7483877B2 (en) * | 2003-04-11 | 2009-01-27 | International Business Machines Corporation | Dynamic comparison of search systems in a controlled environment |
US7854009B2 (en) * | 2003-06-12 | 2010-12-14 | International Business Machines Corporation | Method of securing access to IP LANs |
US20070130132A1 (en) * | 2003-06-30 | 2007-06-07 | Business Objects | Apparatus and method for personalized data delivery |
US8014997B2 (en) * | 2003-09-20 | 2011-09-06 | International Business Machines Corporation | Method of search content enhancement |
US20050065774A1 (en) * | 2003-09-20 | 2005-03-24 | International Business Machines Corporation | Method of self enhancement of search results through analysis of system logs |
EP1695235A4 (en) * | 2003-12-19 | 2009-08-26 | Business Objects Sa | Apparatus and method for using data filters to deliver personalized data from a shared document |
US8370166B2 (en) * | 2004-06-15 | 2013-02-05 | Sap Aktiengesellschaft | Script-based information retrieval |
US20060136438A1 (en) * | 2004-12-20 | 2006-06-22 | Mcchrystal Peter S | Process server array for processing documents and document components and a method related thereto |
US20060238919A1 (en) * | 2005-04-20 | 2006-10-26 | The Boeing Company | Adaptive data cleaning |
US7693888B2 (en) * | 2005-05-10 | 2010-04-06 | Siemens Communications, Inc. | Data synchronizer with failover facility |
US8527540B2 (en) * | 2005-05-24 | 2013-09-03 | Business Objects Software Ltd. | Augmenting a report with metadata for export to a non-report document |
US20060271509A1 (en) * | 2005-05-24 | 2006-11-30 | Ju Wu | Apparatus and method for augmenting a report with parameter binding metadata |
US20090049104A1 (en) * | 2005-06-08 | 2009-02-19 | William Pan | Method and system for configuring a variety of medical information |
US8412514B1 (en) * | 2005-10-27 | 2013-04-02 | At&T Intellectual Property Ii, L.P. | Method and apparatus for compiling and querying a QA database |
US20070100836A1 (en) * | 2005-10-28 | 2007-05-03 | Yahoo! Inc. | User interface for providing third party content as an RSS feed |
US20070198630A1 (en) * | 2006-01-06 | 2007-08-23 | Lee Jacobson | Delivery of archived content to authorized users |
US9110934B2 (en) | 2006-06-02 | 2015-08-18 | International Business Machines Corporation | System and method for delivering an integrated server administration platform |
US20070292833A1 (en) * | 2006-06-02 | 2007-12-20 | International Business Machines Corporation | System and Method for Creating, Executing and Searching through a form of Active Web-Based Content |
US7877284B2 (en) | 2006-06-05 | 2011-01-25 | International Business Machines Corporation | Method and system for developing an accurate skills inventory using data from delivery operations |
US20070282876A1 (en) * | 2006-06-05 | 2007-12-06 | Yixin Diao | Method for service offering comparitive it management activity complexity benchmarking |
US8001068B2 (en) | 2006-06-05 | 2011-08-16 | International Business Machines Corporation | System and method for calibrating and extrapolating management-inherent complexity metrics and human-perceived complexity metrics of information technology management |
US8468042B2 (en) | 2006-06-05 | 2013-06-18 | International Business Machines Corporation | Method and apparatus for discovering and utilizing atomic services for service delivery |
US20070282776A1 (en) * | 2006-06-05 | 2007-12-06 | International Business Machines Corporation | Method and system for service oriented collaboration |
US8554596B2 (en) | 2006-06-05 | 2013-10-08 | International Business Machines Corporation | System and methods for managing complex service delivery through coordination and integration of structured and unstructured activities |
US20070282653A1 (en) * | 2006-06-05 | 2007-12-06 | Ellis Edward Bishop | Catalog based services delivery management |
US20070282470A1 (en) * | 2006-06-05 | 2007-12-06 | International Business Machines Corporation | Method and system for capturing and reusing intellectual capital in IT management |
JP4929916B2 (en) * | 2006-08-17 | 2012-05-09 | 富士ゼロックス株式会社 | Information processing system, information processing apparatus, and program |
US8108410B2 (en) | 2006-10-09 | 2012-01-31 | International Business Machines Corporation | Determining veracity of data in a repository using a semantic network |
US20080086465A1 (en) * | 2006-10-09 | 2008-04-10 | Fontenot Nathan D | Establishing document relevance by semantic network density |
US8874545B2 (en) * | 2007-10-19 | 2014-10-28 | Oracle International Corporation | Data source-independent search system architecture |
US7865488B2 (en) * | 2007-11-28 | 2011-01-04 | International Business Machines Corporation | Method for discovering design documents |
US7865489B2 (en) * | 2007-11-28 | 2011-01-04 | International Business Machines Corporation | System and computer program product for discovering design documents |
EP2083360A1 (en) * | 2008-01-24 | 2009-07-29 | Sunonwealth Electric Machine Industry Co., Ltd. | Reviewing method for patent search results |
US20100185604A1 (en) * | 2009-01-14 | 2010-07-22 | International Business Machines Corporation | Search Results Embedded in a Table-Of-Contents |
US8756489B2 (en) * | 2009-09-17 | 2014-06-17 | Adobe Systems Incorporated | Method and system for dynamic assembly of form fragments |
US9009135B2 (en) * | 2010-01-29 | 2015-04-14 | Oracle International Corporation | Method and apparatus for satisfying a search request using multiple search engines |
US20110191333A1 (en) * | 2010-01-29 | 2011-08-04 | Oracle International Corporation | Subsequent Search Results |
US8271435B2 (en) * | 2010-01-29 | 2012-09-18 | Oracle International Corporation | Predictive categorization |
US10156954B2 (en) * | 2010-01-29 | 2018-12-18 | Oracle International Corporation | Collapsible search results |
US11366814B2 (en) * | 2019-06-12 | 2022-06-21 | Elsevier, Inc. | Systems and methods for federated search with dynamic selection and distributed relevance |
US20230074788A1 (en) * | 2021-09-08 | 2023-03-09 | Microsoft Technology Licensing, Llc | Machine-learning of document portion layout |
Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6065026A (en) * | 1997-01-09 | 2000-05-16 | Document.Com, Inc. | Multi-user electronic document authoring system with prompted updating of shared language |
US6094647A (en) * | 1989-06-14 | 2000-07-25 | Hitachi, Ltd. | Presearch type document search method and apparatus |
US6237011B1 (en) * | 1997-10-08 | 2001-05-22 | Caere Corporation | Computer-based document management system |
US20020042789A1 (en) * | 2000-10-04 | 2002-04-11 | Zbigniew Michalewicz | Internet search engine with interactive search criteria construction |
US20020091671A1 (en) * | 2000-11-23 | 2002-07-11 | Andreas Prokoph | Method and system for data retrieval in large collections of data |
US20030142128A1 (en) * | 2002-01-30 | 2003-07-31 | Benefitnation | User interface for a document component management and publishing system |
US20030144982A1 (en) * | 2002-01-30 | 2003-07-31 | Benefitnation | Document component management and publishing system |
US6718333B1 (en) * | 1998-07-15 | 2004-04-06 | Nec Corporation | Structured document classification device, structured document search system, and computer-readable memory causing a computer to function as the same |
US20040205656A1 (en) * | 2002-01-30 | 2004-10-14 | Benefitnation | Document rules data structure and method of document publication therefrom |
US7130867B2 (en) * | 2001-02-21 | 2006-10-31 | International Business Machines Corporation | Information component based data storage and management |
US7254571B2 (en) * | 2002-06-03 | 2007-08-07 | International Business Machines Corporation | System and method for generating and retrieving different document layouts from a given content |
-
2002
- 2002-06-03 US US10/159,373 patent/US7254571B2/en not_active Expired - Fee Related
-
2007
- 2007-07-10 US US11/775,514 patent/US20080016039A1/en not_active Abandoned
Patent Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6094647A (en) * | 1989-06-14 | 2000-07-25 | Hitachi, Ltd. | Presearch type document search method and apparatus |
US6065026A (en) * | 1997-01-09 | 2000-05-16 | Document.Com, Inc. | Multi-user electronic document authoring system with prompted updating of shared language |
US6237011B1 (en) * | 1997-10-08 | 2001-05-22 | Caere Corporation | Computer-based document management system |
US6718333B1 (en) * | 1998-07-15 | 2004-04-06 | Nec Corporation | Structured document classification device, structured document search system, and computer-readable memory causing a computer to function as the same |
US20020042789A1 (en) * | 2000-10-04 | 2002-04-11 | Zbigniew Michalewicz | Internet search engine with interactive search criteria construction |
US20020091671A1 (en) * | 2000-11-23 | 2002-07-11 | Andreas Prokoph | Method and system for data retrieval in large collections of data |
US7130867B2 (en) * | 2001-02-21 | 2006-10-31 | International Business Machines Corporation | Information component based data storage and management |
US20030142128A1 (en) * | 2002-01-30 | 2003-07-31 | Benefitnation | User interface for a document component management and publishing system |
US20030144982A1 (en) * | 2002-01-30 | 2003-07-31 | Benefitnation | Document component management and publishing system |
US20040205656A1 (en) * | 2002-01-30 | 2004-10-14 | Benefitnation | Document rules data structure and method of document publication therefrom |
US7254571B2 (en) * | 2002-06-03 | 2007-08-07 | International Business Machines Corporation | System and method for generating and retrieving different document layouts from a given content |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9544906B2 (en) | 2007-01-22 | 2017-01-10 | Samsung Electronics Co., Ltd. | Channel allocation method in wireless mesh network and communication device using the method |
US8521757B1 (en) * | 2008-09-26 | 2013-08-27 | Symantec Corporation | Method and apparatus for template-based processing of electronic documents |
US9208450B1 (en) | 2008-09-26 | 2015-12-08 | Symantec Corporation | Method and apparatus for template-based processing of electronic documents |
US20140278364A1 (en) * | 2013-03-15 | 2014-09-18 | International Business Machines Corporation | Business intelligence data models with concept identification using language-specific clues |
US10002126B2 (en) | 2013-03-15 | 2018-06-19 | International Business Machines Corporation | Business intelligence data models with concept identification using language-specific clues |
US10157175B2 (en) * | 2013-03-15 | 2018-12-18 | International Business Machines Corporation | Business intelligence data models with concept identification using language-specific clues |
US10698924B2 (en) | 2014-05-22 | 2020-06-30 | International Business Machines Corporation | Generating partitioned hierarchical groups based on data sets for business intelligence data models |
US10002179B2 (en) | 2015-01-30 | 2018-06-19 | International Business Machines Corporation | Detection and creation of appropriate row concept during automated model generation |
US10019507B2 (en) | 2015-01-30 | 2018-07-10 | International Business Machines Corporation | Detection and creation of appropriate row concept during automated model generation |
US10891314B2 (en) | 2015-01-30 | 2021-01-12 | International Business Machines Corporation | Detection and creation of appropriate row concept during automated model generation |
US9984116B2 (en) | 2015-08-28 | 2018-05-29 | International Business Machines Corporation | Automated management of natural language queries in enterprise business intelligence analytics |
Also Published As
Publication number | Publication date |
---|---|
US20030225747A1 (en) | 2003-12-04 |
US7254571B2 (en) | 2007-08-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7254571B2 (en) | System and method for generating and retrieving different document layouts from a given content | |
US20220164401A1 (en) | Systems and methods for dynamically creating hyperlinks associated with relevant multimedia content | |
US6338058B1 (en) | Method for providing more informative results in response to a search of electronic documents | |
US6708166B1 (en) | Method and apparatus for storing data as objects, constructing customized data retrieval and data processing requests, and performing householding queries | |
US7707168B2 (en) | Method and system for data retrieval from heterogeneous data sources | |
US7437363B2 (en) | Use of special directories for encoding semantic information in a file system | |
US7139977B1 (en) | System and method for producing a virtual online book | |
AU736428B2 (en) | Method and apparatus for searching a database of records | |
US7873648B2 (en) | System and method for personalized presentation of web pages | |
US10108614B2 (en) | Document handling in a web application | |
US7152054B2 (en) | Context-based help engine, dynamic help, and help architecture | |
US20060253423A1 (en) | Information retrieval system and method | |
US20050060343A1 (en) | Context-based display technique with hierarchical display format | |
JP2007122732A (en) | Method for searching dates efficiently in collection of web documents, computer program, and service method (system and method for searching dates efficiently in collection of web documents) | |
US20090327277A1 (en) | Methods and apparatus for reusing data access and presentation elements | |
US20090106286A1 (en) | Method of Hybrid Searching for Extensible Markup Language (XML) Documents | |
US7024405B2 (en) | Method and apparatus for improved internet searching | |
EP1593055A2 (en) | Text and attribute searches of data stores that include business objects | |
US7630959B2 (en) | System and method for processing database queries | |
US8954412B1 (en) | Corroborating facts in electronic documents | |
JP2003173280A (en) | Apparatus, method and program for generating database | |
US20040230564A1 (en) | Filtering algorithm for information retrieval systems | |
US8447748B2 (en) | Processing digitally hosted volumes | |
KR20090012467A (en) | System and method for providing integrated search using uniform resource identifier database | |
US20040162815A1 (en) | Adapting business objects for searches and searching adapted business objects |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BROWN, GREGORY T.;COFINO, THOMAS A.;DOGANATA, YURDAER NEZIHI;AND OTHERS;REEL/FRAME:019544/0338;SIGNING DATES FROM 20020524 TO 20020916 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |