Dynamic document merging method and system

[0001] The present invention relates to a method and associated system for merging documents based on various parameters.

[0002] Combining specific data portions from various data streams typically comprises a complicated and inefficient process with little flexibility. Accordingly, there exists a need in the art to overcome at least some of the deficiencies and limitations described herein above.

[0003] The present invention provides a document merging method comprising:

[0004] receiving, by a computing system, a plurality of documents, wherein said computing system comprises a memory system;

[0005] receiving, by said computing system from a first user, a first command for tagging portions of each document of said plurality of documents according to various parameters;

[0006] assigning, by said computing system in response to said first command, identification tags to said portions of each said document, wherein each portion of said portions is assigned an associated identification tag of said identification tags;

[0007] storing, by said computing system within said memory system, said documents comprising said identification tags;

[0008] receiving, by said computing system from a second user, a second command for generating a merged document;

[0009] presenting, by said computing system to said second user, said identification tags;

[0010] receiving, by said computing system from said second user, a first selection of a first tag of said identification tags, said first tag associated with a first portion of a first document of said plurality of documents;

[0011] receiving, by said computing system from said second user, a second selection of a second tag of said identification tags, said second tag associated with a second portion of a second document of said plurality of documents;

[0012] generating, by said computing system in response to said first selection and said second selection, said merged document, said merged document comprising said first portion of said first document and said second portion of said second document; and

[0013] storing, by said computing system, said merged document in said memory system.

[0014] The present invention provides a computing system comprising a processor coupled to a computer-readable memory unit, said memory unit comprising instructions that when executed by the processor implement a document merging method, said method comprising:

[0015] receiving, by said computing system, a plurality of documents;

[0016] receiving, by said computing system from a first user, a first command for tagging portions of each document of said plurality of documents according to various parameters;

[0017] assigning, by said computing system in response to said first command, identification tags to said portions of each said document, wherein each portion of said portions is assigned an associated identification tag of said identification tags;

[0018] storing, by said computing system within said computer-readable memory unit, said documents comprising said identification tags;

[0019] receiving, by said computing system from a second user, a second command for generating a merged document;

[0020] presenting, by said computing system to said second user, said identification tags;

[0021] receiving, by said computing system from said second user, a first selection of a first tag of said identification tags, said first tag associated with a first portion of a first document of said plurality of documents;

[0022] receiving, by said computing system from said second user, a second selection of a second tag of said identification tags, said second tag associated with a second portion of a second document of said plurality of documents;

[0023] generating, by said computing system in response to said first selection and said second selection, said merged document, said merged document comprising said first portion of said first document and said second portion of said second document; and

[0024] storing, by said computing system, said merged document in said computer-readable memory unit.

[0025] The present invention provides a process for supporting computer infrastructure, said process comprising providing at least one support service for at least one of creating, integrating, hosting, maintaining, and deploying computer-readable code in a computing system comprising a computer-readable memory unit, wherein the code in combination with the computing system is capable of performing a document merging method, said method comprising:

[0026] receiving, by said computing system, a plurality of documents;

[0027] receiving, by said computing system from a first user, a first command for tagging portions of each document of said plurality of documents according to various parameters;

[0028] assigning, by said computing system in response to said first command, identification tags to said portions of each said document, wherein each portion of said portions is assigned an associated identification tag of said identification tags;

[0029] storing, by said computing system within said computer-readable memory unit, said documents comprising said identification tags;

[0030] receiving, by said computing system from a second user, a second command for generating a merged document;

[0031] presenting, by said computing system to said second user, said identification tags;

[0032] receiving, by said computing system from said second user, a first selection of a first tag of said identification tags, said first tag associated with a first portion of a first document of said plurality of documents;

[0033] receiving, by said computing system from said second user, a second selection of a second tag of said identification tags, said second tag associated with a second portion of a second document of said plurality of documents;

[0034] generating, by said computing system in response to said first selection and said second selection, said merged document, said merged document comprising said first portion of said first document and said second portion of said second document; and

[0035] storing, by said computing system, said merged document in said computer-readable memory unit.

[0036] The present invention provides a computer program product, comprising a computer readable medium comprising a computer readable program code embodied therein, said computer readable program code adapted to implement a document merging method within a computing system, said method comprising:

[0037] receiving, by said computing system, a plurality of documents;

[0038] receiving, by said computing system from a first user, a first command for tagging portions of each document of said plurality of documents according to various parameters;

[0039] assigning, by said computing system in response to said first command, identification tags to said portions of each said document, wherein each portion of said portions is assigned an associated identification tag of said identification tags;

[0040] storing, by said computing system, said documents comprising said identification tags;

[0041] receiving, by said computing system from a second user, a second command for generating a merged document;

[0042] presenting, by said computing system to said second user, said identification tags;

[0043] receiving, by said computing system from said second user, a first selection of a first tag of said identification tags, said first tag associated with a first portion of a first document of said plurality of documents;

[0044] receiving, by said computing system from said second user, a second selection of a second tag of said identification tags, said second tag associated with a second portion of a second document of said plurality of documents;

[0045] generating, by said computing system in response to said first selection and said second selection, said merged document, said merged document comprising said first portion of said first document and said second portion of said second document; and

[0046] storing, by said computing system, said merged document.

[0047] The present invention advantageously provides a method and associated system capable of combining specific data portions from various data streams.

[0054] FIG. 1 illustrates a system 2 for merging source documents 25 according to various parameters, in accordance with embodiments of the present invention. Source documents 25 may comprise any type of documents such as, inter alia, word processing documents, PDF documents, web page documents, email documents, etc. Merging documents 25 may comprise:

• [0055] 1. Extracting different portions of various documents (i.e., from source documents 25 such that the various portions of the documents (e.g., paragraphs, sentences, etc) are placed in a single merged document).
• [0056] 2. Generating a merged document such that only specified portions of the original source documents (e.g., paragraphs, sentences, etc) are viewable by a second user (i.e., viewing the merged document).

[0057] Source document(s) 25 may be merged by a user that generates (i.e., an author of the documents) the documents or by a first user that receives the documents from a second user that generates the documents. System 2 provides dynamic document merging and management capabilities. System 2 allows a user to:

• [0058] 1. Create and input source documents 25 into system 2.
• [0059] 2. Visually scan source documents 25 and identify keywords that match a set of predefined tags (e.g., take user input to learn new tags specific to the documents). A tag comprises a method to denote a topic (i.e., a subject to be discussed or addressed in a general or a specified method) to be categorized.
• [0060] 3. Accept user input for specified weighting applied to the tags.

[0061] Based on the document(s) and the predefined tags, system 2 allows user to generate merged documents 28 based on any combination of the following parameters:

• [0062] 1. Dynamic merging of source documents 25 based on tagged elements such as, topic, category (i.e., a grouping system of the item based on commonality or similarities determined by a user or specified by a specific role), team or workgroup, user's role (i.e., a set of connected behaviors or actions that are performed by a person, team, or group in a specific context), user's responsibility, or low level task description.
• [0063] 2. Dynamic merging of source documents 25 based on a topic predefined priority or rating (i.e., a severity level that takes precedence over other severity levels).
• [0064] 3. Dynamic merging of source documents 25 based on a fragment level.
• [0065] 4. Dynamic merging of source documents 25 based on an audience's (i.e., a second user) interest.
• [0066] 5. Dynamic creation of table of contents (TOC) based on the user's selection of a topic for merging.

[0067] Once tags are defined and stored in a repository, a user may automate system 2 by:

• [0068] 1. Checking access control for source documents 25 residing in computing system 10.
• [0069] 2. Select sections of source documents 25 based on tags defined for the source documents 25.
• [0070] 3. Handle cross domain merging for creation and viewing of merged documents 28 through access privilege and granted permission at the tagged document section and user ID levels.
• [0071] 4. Look-up standard templates on top of the dynamic merge performed in order to generate document formats that a specific user is familiar with.

[0072] System 2 additionally allows an administrator to perform an authorization process to allow a user to merge source documents 25. The authorization process may be performed via, instant messaging, email, etc. The authorization process may comprise:

• [0073] 1. Verifying access privileges for each of source documents 25 used for the merging.
• [0074] 2. Soliciting permission to be used as a source where necessary based on policies defined in role based access control systems and tags.
• [0075] 3. Obtaining approval in real time with integration of instant messaging and email.

[0076] System 2 of FIG. 1 comprises a plurality of input/output (I/O) devices 5A . . . 5D connected to a computing system 10 through a network 7. I/O devices 5A . . . 5D may comprise any type of I/O device such as, inter alia, a notebook computer 5A, a cellular telephone 5B, a desktop computer 5C, a personal digital assistant (PDA) 5D, etc. Network 7 may comprise any type of network including, inter alia, a local area network, (LAN), a wide area network (WAN), the Internet, etc. Additionally, system 2 comprises an administrator terminal 9. Computing system 10 may comprise any type of computing system including, inter alia, a personal computer (PC), a server computer, a database computer, etc. Computing system 10 comprises a memory apparatus 14. Memory apparatus 14 comprises a software application 18, tagging data 27, merged documents 28, and source documents 25. Software application 18 controls all functions related to:

• [0077] 1. Merging source documents 25.
• [0078] 2. Authorizing a user to merge (portions of) source documents 25.

[0079] Tagging data 27 comprises data related to predefined tags. A tag is defined herein as a data marker used to denote a topic to be categorized. Merged documents 28 comprise any of source documents 25 that have been merged. I/O devices 5A . . . 5D allow users to submit source documents 25 into computing system 10 and access computing system 10 for merging source documents. Administrator terminal 9 allows an administrator to authorize a merged document.

[0080] Software application 18 allows for the following functionality with respect to merging source documents 25:

• [0081] 1. Creation of topics by using a tagging library that may be applied to document content for enabling a dynamic rearrangement of the document. A priority level and rating may also be applied to each topic. This function is performed by a designer of the document.
• [0082] 2. In the case of a central repository system (as illustrated in FIG. 1), a user may extract or search content section(s) from any source document that resides on a central server (i.e., computing system 2). In the case of a peer-to-peer system, a user may extract or search content section(s) from any source document that resides on any peer machine(s) (i.e., on any of I/O devices 5A . . . 5D).
• [0083] 3. Encapsulating access control implementations into the merging policy by applying a security model. Handles cross domain merging for creation and viewing of documents through access privilege and granted permission at the tagged document section and user ID levels.
• [0084] 3. Enables federated document management to simplify document creation and dynamic customization for viewing, which also avoids duplicate document sections and duplicate efforts.
• [0085] 5. Enables static and dynamic security policies in a federated document management environment and ties role, document tag, and fragment level based on access control to federated document management.
• [0086] 6. Enable a user to create documents based on a set of standard templates that the client company is familiar with. For example, company A employees are used to viewing user guides in a specific format set by company A. Using a set standard templates combined with a tagging library, any document that company B delivers to company A will follow similar standards and formatting regardless of any information provided. Therefore company B may quickly deliver documents to company A in company A's preferred format without exposing any company B formats or related IP.

[0087] Software application 18 allows for the following functionality with respect to allowing an administrator to authorize a merging process:

• [0088] 1. Extended control capability for the original source documents so that when a second user (i.e., receiving user) executes a drag-n-drop menu or selects sections to create a merged document, the original author of the document may be notified of the change. Depending on a security setting, the original author of the source document may be prompted to dynamically authorize the change in real-time and from a remote location.
• [0089] 2. Rapid approval with instant message (IM) integration. An original author's information is embedded during a source document creation process and therefore a modification process applied to tagged section(s) of the source document may trigger an approval process via IM or email. Computing system 10 will parse an IM response or email subject line and apply the appropriate approval code and response to the documents across network 7. Computing system 10 may also integrate with a computer telephony integration (CTI) system in order to solicit a document merging approval using LAN or VOIP lines.
• [0090] 3. Provides a separation of duty capability in order to comply with federal regulations and company security policies. For example, two approvers may be required (i.e., a person who generated the merged document may not be the approver for a particular document or section(s) of a document).
• [0091] 4. Provides a full audit capability. For example, logging essential data, a tags/field/section/document may be configurable by an administrator, storing a history trail of document merging and approval, including an archive utility at a database and document level, etc.

[0092] The following description (steps) illustrates an example of implementation for using source documents 25 to generate a merged document according to various parameters:

• [0093] 1. A user A begins a search for content information (i.e., from source documents) that he/she needs.
• [0094] 2. User A access a database (i.e., computing system 10) and retrieves relevant documents.
• [0095] 3. Computing system 10 performs a search of the retrieved documents to locate content associated with selected parameters.
• [0096] 4. User A verifies and highlights relevant content.
• [0097] 5. XML tags are generated to consolidate the relevant content.
• [0098] 6. Computing system 10 performs a role document process and fragment level check.
• [0099] 7. If the role document process and fragment level check determines any errors, then user A will be required to fix the errors and repeat the process.
• [0100] 8. If the role document process and fragment level check determines no errors then a security check is performed.
• [0101] 9. If the security check determines a problem, then user A will be required to correct the problem and repeat the process.
• [0102] 10. If the security check determines no problem then an initial draft of a merged document is generated.
• [0103] 11. User A reviews the merged document and performs any necessary modifications.
• [0104] 12. User A determines which template model to apply to the merged document.

[0105] FIG. 2 illustrates a flowchart describing an overall algorithm used by system 2 of FIG. 1 for generating and tagging source documents, in accordance with embodiments of the present invention. In step 202, a user generates a source document. In step 204, the user tags portions of the source document according to various parameters. Parameters may include, inter alia, a user role, a priority, a topic of preference, a category, etc. In step 206, the source document and tags are stored in computing system 10 and the process terminates is step 208.

[0106] FIG. 3 illustrates a flowchart detailing step 202 of FIG. 2, in accordance with embodiments of the present invention. In step 302, the user selects to generate the source document using a template. In step 304, the user enters source document details and source document content data. Source document details may include, inter alia, a specified template type, a company for the user, an arrangement for the content data, etc. In step 306, software application 18 loads the selected template and entered content data. In step 310, software application 18 generates the source document using the selected template and entered content data. In step 312, software application 18 prompts the user to review the source document. In step 314, the user determines if the source document is ok (i.e., comprises correct content). If in step 314, the user determines that the source document is ok then in step 318, the source document is finalized and stored and the process ends in step 322. If in step 314, the user determines that the source document is not ok, then step 304 is repeated.

[0107] FIG. 4 illustrates a flowchart describing an overall algorithm used by system 2 of FIG. 1 for generating a merged document, in accordance with embodiments of the present invention. In step 402, a merged document template for generating a merged document is selected and opened. In step 404, source documents and the associated tags are loaded onto an I/O device (e.g., one of I/O devices 5A . . . 5D) being used by the user. In step 408, the user selects specified parameters for merging the source documents. The specified parameters may include a ranking or weight, specified topics, a role, content, task, category, etc. In step 410, the user ranks the parameters by importance. In step 414, software application 18 generates a merged document according to the parameters selected in step 408 and the parameter ranking from step 410. In step 418, the merged document is displayed for the user and the process terminates in step 422.

[0108] FIG. 5 illustrates a flowchart describing an overall algorithm used by system 2 of FIG. 1 for authorizing a merging of source documents, in accordance with embodiments of the present invention. In step 502, a merging template is selected and opened. In step 508, user A uses a drag-n-drop method to select portions of the source documents and place the selected portions into the template for merging. In step 510, computing system 10 determines if a dynamic approval process is necessary.

[0109] If in step 510, computing system 10 determines that a dynamic approval process is not necessary then in step 514, an alert message specifying that a dynamic approval process is not necessary is transmitted (i.e., via email, IM, cell phone, etc.) to user A.

[0110] If in step 510, computing system 10 determines that a dynamic approval process is necessary then in step 518, an alert message specifying that a dynamic approval process is necessary and is transmitted (i.e., via email, IM, cell phone, etc.) to an authorizer and user A. The alert message generated in step 518 additionally highlights the portions of the source documents selected in step 508. In step 522, an approval request is transmitted to the authorizer and/or user A. In step 524, the authorizer and/or user transmits a response (i.e., approving or disapproving the merging of the source documents) back to computing system 10. In step 532, computing system 10 determines if the authorizer and/or user A has approved the merging of the source documents.

[0111] If in step 532, computing system 10 determines that the authorizer and/or user A has not approved the merging of the source documents then in step 534, user A modifies the portions for merging (e.g., selects new portions of the source documents for merging) and step 508 is repeated.

[0112] If in step 532, computing system 10 determines that the authorizer and/or user A has approved the merging of the source documents then in step 538, the source documents are merged. In step 540, the merged document is displayed for user A and/or the authorizer. In step 544, the merged document and the merging history are stored in computing system 10 and the process terminates in step 548.

[0113] FIG. 6 illustrates a computer apparatus 90 (e.g., computing system 10 of FIG. 1) used for merging source documents according to various parameters, in accordance with embodiments of the present invention. The computer system 90 comprises a processor 91, an input device 92 coupled to the processor 91, an output device 93 coupled to the processor 91, and memory devices 94 and 95 each coupled to the processor 91. The input device 92 may be, inter alia, a keyboard, a mouse, etc. The output device 93 may be, inter alia, a printer, a plotter, a computer screen, a magnetic tape, a removable hard disk, a floppy disk, etc. The memory devices 94 and 95 may be, inter alia, a hard disk, a floppy disk, a magnetic tape, an optical storage such as a compact disc (CD) or a digital video disc (DVD), a dynamic random access memory (DRAM), a read-only memory (ROM), etc. The memory device 95 includes a computer code 97. The computer code 97 includes algorithms (e.g., the algorithms of FIGS. 2-5) for merging source documents according to various parameters. The processor 91 executes the computer code 97. The memory device 94 includes input data 96. The input data 96 includes input required by the computer code 97. The output device 93 displays output from the computer code 97. Either or both memory devices 94 and 95 (or one or more additional memory devices not shown in FIG. 6) may comprise the algorithms of FIGS. 2-5 and may be used as a computer usable medium (or a computer readable medium or a program storage device) having a computer readable program code embodied therein and/or having other data stored therein, wherein the computer readable program code comprises the computer code 97. Generally, a computer program product (or, alternatively, an article of manufacture) of the computer system 90 may comprise said computer usable medium (or said program storage device).

[0114] Still yet, any of the components of the present invention could be created, integrated, hosted, maintained, deployed, managed, serviced, etc. by a service provider who offers to merge source documents according to various parameters. Thus the present invention discloses a process for deploying, creating, integrating, hosting, maintaining, and/or integrating computing infrastructure, comprising integrating computer-readable code into the computer system 90, wherein the code in combination with the computer system 90 is capable of performing a method for merging source documents according to various parameters. In another embodiment, the invention provides a business method that performs the process steps of the invention on a subscription, advertising, and/or fee basis. That is, a service provider, such as a Solution Integrator, could offer to merge source documents according to various parameters. In this case, the service provider can create, maintain, support, etc. a computer infrastructure that performs the process steps of the invention for one or more customers. In return, the service provider can receive payment from the customer(s) under a subscription and/or fee agreement and/or the service provider can receive payment from the sale of advertising content to one or more third parties.

[0115] While FIG. 6 shows the computer system 90 as a particular configuration of hardware and software, any configuration of hardware and software, as would be known to a person of ordinary skill in the art, may be utilized for the purposes stated supra in conjunction with the particular computer system 90 of FIG. 6. For example, the memory devices 94 and 95 may be portions of a single memory device rather than separate memory devices.

[0116] While embodiments of the present invention have been described herein for purposes of illustration, many modifications and changes will become apparent to those skilled in the art. Accordingly, the appended claims are intended to encompass all such modifications and changes as fall within the true spirit and scope of this invention.