JP2010108453A - Document component management device and method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a document component management device correlating related document components distributed in a plurality of documents, and acquiring the document component by keyword retrieval. <P>SOLUTION: The document component management device 10 for managing a change history of the document component includes: a document storage part for storing a plurality of document information, a relation storage part for storing the document components in cross-sectional use relationship in the plurality of documents in association with each other, an index storage part for storing a keyword related to the document component, a keyword retrieval part for retrieving the document component corresponding to the keyword, a related document component retrieval part for retrieving the document component correlated with the retrieved document component, a document component acquisition part for acquiring information of the document component from the relation storage part, and a transmission part for transmitting the information of the document component acquired by the document component acquisition part to a document edit terminal. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a document parts management apparatus, method, and program. In particular, the present invention relates to a document parts management apparatus, method, and program for managing a plurality of variations of document parts distributed in a plurality of documents in association with each other.

  Conventionally, documents used in lectures, for example, presentation documents created by PowerPoint (registered trademark) of MS, etc., are rarely created every time a lecture is given. There are many. At that time, a document suitable for a lecture or the like is selected from previously created documents. Then, a part of the selected document is changed to create a new document. That is, a new document is created by changing a part of a document part constituting a document and a slide in a presentation document. For this reason, although document parts having slightly different contents are related to each other, they are distributed in a plurality of documents without being related to each other. For this reason, even when the document editor knows that there are variations of document parts when creating a document, it is difficult to find them.

Therefore, there is a technique for associating related document parts (Patent Documents 1 and 2). In Patent Document 1, document parts included in a newly created document (new document) and a document part of a source document are extracted in a technique for extracting a document part in units of pages from a plurality of documents and creating a new document. There is a technology that associates Further, in Patent Document 2, there is a technique for associating slides in a presentation document based on a story in the presentation document. Furthermore, there is a technique for performing version management of a document in page units (Patent Document 3).
JP 2002-91959 A JP-A-9-81346 JP 2007-188143 A

  However, the technique described in Patent Document 1 is for updating the document part of a new document when the document part of the extraction source document is updated, and not for managing the relationship between the document parts. Absent. The technique described in Patent Document 2 is a technique for associating slides in a presentation document, and does not associate slides between a plurality of presentation documents. The technology described in Patent Document 3 can manage versions in units of pages, but is based on CMS (Content Management System), and is actually a file composed of a plurality of pages called pages. It is only management by the unit.

  In the above-described prior art or a combination of the prior arts, related document parts that are distributed in a plurality of documents cannot be associated with each other, and related document parts are selected from the entire document parts included in each of the plurality of documents. It is difficult to find out.

  In addition, it is possible to obtain a document suitable for a lecture from among previously created documents by keyword search of the document, but to acquire document parts included in the document by keyword search. I can't.

  Therefore, the present invention associates related document parts distributed in a plurality of documents with each other in order to search for related document parts from all the document parts included in each of the plurality of documents. An object of the present invention is a document parts management apparatus, method, and program for managing usage relationships. Another object of the present invention is to provide a document part management apparatus, method, and program for acquiring a document part included in a document by keyword search.

  In view of the above problems, the present invention provides the following solutions.

  In the document part management apparatus connected to the document editing terminal according to the present invention via a network, among the one or more document parts included in each of the plurality of documents, the documents having a usage relationship across the plurality of documents. By providing a relationship storage unit that stores components in association with each other and an index storage unit that stores keywords related to document components in association with document components, the document editor can assign keywords to the document editing terminal. In response to the input, the document editor can present the document part related to the keyword and the document part used in relation to the document part related to the keyword to the document editor. As a result, the document editor can easily obtain necessary document parts.

  Further, in the document part management apparatus according to the present invention, the usage relationship between the document parts is a relation caused by diversion or modification of the document parts, and the relation storage unit stores the used document parts as parent document parts, By using the used document part as a child document part and storing the parent document part and the child document part in association with each other, the change history of the document part can be accumulated. As a result, the document part management apparatus can manage the original of the document part and the variation of the document part derived therefrom by using the relationship storage unit.

  Further, in the document part management apparatus according to the present invention, the usage relationship between the document parts is transmitted to the document editing terminal together with the document part information acquired by the document part acquisition unit. The relationship diagram of document parts is displayed based on the usage relationship. Here, the relationship diagram of document parts is a diagram showing the relationship between the document parts by connecting the document parts in the usage relationship with lines. By displaying the relationship diagram on the document editing terminal, the document editor can easily grasp the relationship between the document parts and can select an appropriate document part.

  As another aspect, the document part management apparatus according to the present invention can be provided as a document part management method and a computer program executed in a computer.

  According to the document part management apparatus according to the present invention, it is possible to manage the usage relationship of document parts by associating related document parts that are distributed in a plurality of documents, and are included in each of the plurality of documents. It is possible to find out related document parts from all document parts. Further, according to the document part management apparatus according to the present invention, the document parts included in the document can be acquired by keyword search.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the following description, a document is a presentation document (hereinafter referred to as a presentation document for simplification), and a document part is a chart included in the presentation document. Note that the document is not limited to a presentation document, and may be any document that often uses a previously created document. Further, the document part is not limited to the chart, but may be a page or an arbitrarily divided block.

[Functional configuration of document parts management device]
FIG. 1 is a diagram showing a functional configuration of a document parts management apparatus 10 according to the present embodiment. As shown in FIG. 1, the document part management apparatus 10 is connected to a plurality of document editing terminals 20 via a network 30. The document editing terminal 20 is a terminal used by a document editor to search for a chart, download the chart, and create a new presentation document using the downloaded chart. The document part management device 10 is a device that manages presentation documents and charts, and includes a document registration unit 100, an index registration unit 101, a history registration unit 102, a document part request reception unit 103, and a keyword search unit 104. , Document part acquisition unit 105, history search unit (related document part search unit) 106, transmission unit 107, repository (document storage unit) 110, index DB (index storage unit) 120, history (relationship storage unit) ) DB130.

  The document registration unit 100 registers the received presentation document in the repository 110 in response to receiving the presentation document created by the document editor from the document editing terminal 20. Here, the repository 110 is a storage medium or the like for storing information on the presentation document. The information on the presentation document includes at least the presentation document and may include information on the presentation document. There are two types of presentation documents created by document editors. One is that a document editor newly modifies a part or all of a plurality of charts constituting the presentation document, that is, a presentation document newly created using a presentation document registered in the repository 110. This is a presentation document created by diverting. The other is a presentation document newly created without using a presentation document registered in the repository 110 by the document editor.

  When registering a presentation document in the repository 110, the document registration unit 100 specifies a category of a presentation document, or a category and a sub category. This is because presentation documents are managed by category in the repository 110. The category and the like are specified by the document editor when registering the presentation document, and are transmitted from the document editing terminal 20 to the document registration unit 100 together with the presentation document.

  FIG. 2 is a diagram showing an example of category classification of a presentation document according to the present embodiment. Here, the category and sub-category of the presentation document specified when registering the presentation document in the repository will be described. Since the content of the presentation document is partially different depending on the type of lecture used, the presentation document is managed by category with the type of lecture as the category. In FIG. 2, presentation documents are classified into categories as external lectures and internal lectures. Even if the content is an internal lecture, it can be published, but if it is an external lecture, there is a content that cannot be published. Therefore, even if the original presentation document is the same, both presentation documents are partially Because it is different.

  In the category of external lectures, sub-categories are classified as university-related lectures, corporate lectures, and customer visits, and presentation documents are further classified. This is because, even if the original presentation document is the same, the presentation document is partially different due to differences in the important parts depending on the audience of the lecture. In the category of internal lectures, sub-categories are classified as overseas lectures and domestic lectures, and presentation documents are further classified. This is because the language of the presentation document differs depending on whether it is for overseas or domestic use, and the display format of the presentation document is different even if the content is the same.

  Thus, presentation documents are classified according to the type of lecture. As a result, when creating a new presentation document, do not use a presentation document presented to the same audience, or easily use a presentation document that matches the category of the lecture for which you are creating a presentation document, etc. Can do.

  In FIG. 2, the category and sub-category described are examples, so the publication year of the presentation document and the affiliation of the document creator may be used as the category or sub-category. Further, a category for further classifying the sub-category may be provided to classify the presentation document more finely.

  Returning to FIG. 1, when registering a presentation document in the repository 110, the document registration unit 100 assigns a document ID to the presentation document. All presentation documents registered in the repository 110 are registered as new.

  Further, when registering the presentation document in the repository 110, the document registration unit 100 assigns a chart ID to each of all charts included in the presentation document. When the document registration unit 100 assigns a chart ID, for a chart to which a document ID and a chart ID have already been assigned, first, a presentation registered in the repository 110 based on the already assigned document ID and the chart ID. A chart included in the document (hereinafter referred to as an existing chart) is specified. The identified existing chart is compared with the chart registered in the repository 110 (new chart), and when there is a change, the change flag of the chart attribute given to the new chart is set to TRUE. On the other hand, if there is no change, the change flag is set to FALSE. The chart attribute will be described later.

  The document ID is a unique ID in the repository 110 assigned to each presentation document. The chart ID is a unique ID in the presentation document assigned to each chart. Therefore, in order to specify a chart in the repository 110, both a document ID and a chart ID are required. The newly created document IDs and chart IDs assigned to the presentation document and chart registered in the repository 110 are hereinafter referred to as a new document ID and a new chart ID, respectively.

  The document registration unit 100 writes the new document ID and the new chart ID in the chart attribute assigned to the new chart. The chart attribute is an attribute assigned to each chart, in other words, an embedded attribute. By embedding an attribute in each chart, a search can be performed in chart units. In order to embed the chart attribute in each chart, for example, it is necessary to install a plug-in having a function of embedding the chart attribute in the chart in the document editing terminal 20. In addition, a system having a function of managing chart attributes of the chart may be connected to the document editing terminal 20 via a network, and the chart may have chart attributes using the system.

  Regardless of the change flag of the chart included in the presentation document registered in the repository 110, the document registration unit 100 includes the existing document ID and the existing chart ID acquired before the new document ID and the new chart ID are allocated, The new document ID and the new chart ID allocated to are recorded in the history DB 130. Thereby, the charts included in the presentation document registered in the repository 110 can be associated with each other. The history DB 130 will be described later.

  FIG. 3 is a diagram illustrating an example of the chart attribute according to the present embodiment. The chart attribute includes a chart ID 200a, a document ID 200b, a group ID 200c, and a change flag 200d.

  As described above, the chart ID 200 a is a unique ID in the presentation document assigned to each chart, and is automatically assigned by the document registration unit 100 when registered in the repository 110. The document ID 200 b is a unique ID in the repository 110 assigned to each document, and is automatically assigned by the document registration unit 100 when registered in the repository 110.

  The group ID 200c is an ID for handling a plurality of charts as a group, and is set by a document editor when registering a plurality of charts as a group. The change flag 200d is a flag indicating whether or not the new chart is a chart created by changing an existing chart. The change flag 200d is automatically set by comparing the new chart with the existing chart.

  Returning to FIG. 1, after assigning a new document ID to the presentation document, the document registration unit 100 associates the category specified when registering the presentation document with the repository 110 with the new document ID, and stores the new document ID in the repository 110. Store in the link table.

  FIG. 4 is a diagram showing an example of the link table of the repository 110 according to the present embodiment. The link table includes a category 201a, a sub category 201b, and a document ID 201c. The category 201a and the sub category 201b are categories into which the presentation document is classified. As described above, the document ID 201c is a unique ID in the repository assigned for each document.

  The link table stores links between categories and presentation documents, and links between categories. A link between categories indicates that the categories have a tree structure. In FIG. 4, the link table indicates that Category3 is a subcategory of Category2 and Category2 is a subcategory of Category1, so that Category1, Category2, and Category3 are arranged in this order. It is shown that. Further, it is indicated that the document ID “DOC-003” belongs to Category 2 which is a sub category of Category 1. With this link table, it is possible to specify which category the presentation document belongs to.

  FIG. 5 is a diagram showing an example of the document attribute table of the repository 110 according to the present embodiment. The document attribute table of the repository 110 is used by the document registration unit 100 for processing to store the document attribute of the presentation document registered in the repository 110 and the new document ID in association with each other. The document attribute table includes a document ID 202a, a title 202b, a creator 202c, and a lecture date 202d.

  As described above, the document ID 202a stores a unique ID in the repository 110 assigned to each presentation document. The title 202b is a title given to the presentation document, and stores the title described on the cover of the first page of the presentation document. The creator 202c is the creator who created the document, and stores the creator described on the cover of the first page of the presentation document as well as the title. The lecture date 202d is the date of the lecture in which the document was used, and stores the date described on the cover of the first page of the presentation document, like the title and the creator.

  Note that the title 202b, the creator 202c, and the lecture date 202d are automatically extracted from the first page of the presentation document when the document registration unit 100 stores the document attributes in the document attribute table.

  Further, the document registration unit 100 allocates the new document ID and the new chart ID, and simultaneously transmits the existing document ID and the existing chart ID, the new document ID and the new chart ID to the history registration unit 102. The existing document ID and the existing chart ID are associated with the new document ID and the new chart ID and transmitted to the history registration unit 102.

  The existing document ID is a document ID of a presentation document including an existing chart (hereinafter referred to as a parent chart) from which a new chart is changed, and is acquired from the document ID of the chart attribute before the new document ID is allocated. To do. If there is no parent chart, that is, a presentation document created without using a document registered in the repository 110, the existing document ID does not exist, so the existing document ID has a blank or NULL. enter.

  The existing chart ID is the chart ID of the parent chart, and is acquired from the chart ID of the chart attribute before the new chart ID is allocated. If there is no parent chart, that is, a presentation document created without using a chart of a document registered in the repository 110, the existing chart ID does not exist. NULL is entered.

  The document registration unit 100 transmits the new document ID and new chart ID of the new chart to the index registration unit 101.

  The history registration unit 102 stores the existing document ID and existing chart ID, the new document ID and the new chart ID received from the document registration unit 100 as history information in the history table of the history DB 130 for each chart. Specifically, the history registration unit 102 stores the new document ID and the new chart ID in the history table as the chart ID and the chart ID of the own chart. In addition, the history registration unit 102 stores the existing document ID and the existing chart ID in the history table as the chart ID and the chart ID of the parent chart. In this way, the history registration unit 102 can store the usage relationship between the charts, that is, the own chart (a newly created chart), its parent chart, and the parent-child relationship as history information in the history table of the history DB 130. it can.

  FIG. 6 is an example of a history table stored in the history DB 130 according to the present embodiment. The history table stores the history information of the chart, specifically, the parent-child relationship centered on the own chart. The history table shown in FIG. 6 represents the parent-child relationship of the own chart specified by the document ID “DOC-0002” and the chart ID “CHART-0002”, that is, the change history. As shown in FIG. 6, the history table has a document ID and a chart ID for each of the own chart 203a, the parent chart 203b, and the child chart 203c.

  The own chart 203a stores a document ID and a chart ID of a chart that is a reference of the parent-child relationship stored in the history table, that is, a newly created chart in the present embodiment. Specifically, the new document ID and the new chart ID received from the document registration unit 100 are stored in the document ID and the chart ID of the own chart 203a, respectively.

  In the parent chart 203b, the document ID and the chart ID of the parent chart from which the own chart is changed are stored. Specifically, the existing document ID and the existing chart ID received from the document registration unit 100 are stored in the document ID and the chart ID of the parent chart 203b, respectively. The parent chart 203b can store only one chart information. Therefore, when two charts are used as parents, either one is used as a parent. Further, when the document ID and the chart ID are not stored in the parent chart 203b, it means that the own chart is newly created.

  The child chart 203c stores a document ID and a chart ID of a child chart created from the own chart. This child chart is also a grandchild chart of the parent chart. A plurality of charts can be stored in the child chart 203c. This is because various charts may be created with one chart as a parent.

  Here, the document ID and the chart ID stored in the child chart will be described. In response to receiving the existing document ID and the existing chart ID from the document registration unit 100, the history registration unit 102 stores the received existing document ID and existing chart ID as the document ID and chart ID of the own chart. Specify the history information of the table. The new document ID and new chart ID received from the document registration unit 100 are stored in the document ID and chart ID of the child chart of the specified history information.

  In this way, the history table can manage the change history of the chart by storing the parent chart and the child chart of the own chart in association with each chart.

  Next, the history attached information table will be described. The history attached information table is stored in the history DB 130 together with the history table. Based on the new document ID and the new chart ID received from the document registration unit 100, the history registration unit 102 acquires information on the corresponding chart from the repository 110 and stores it in the history attached information table of the history DB 130. Here, the chart information is, for example, a chart creator or a creation date and time.

  FIG. 7 is an example of a history attached information table stored in the history DB 130 according to the present embodiment. Information on the chart received from the document registration unit 100 is stored in the history attached information table. As shown in FIG. 7, the history attached information table has a chart ID 204a, a document ID 204b, a creator 204c, and a creation date and time 204d. The chart ID and the document ID are associated with the history table described above.

  The index registration unit 101 extracts keywords from the repository 110 for each chart based on the new document ID and the new chart ID received from the document registration unit 100 and stores them in the index DB 120. The index DB 120 stores a keyword used for chart search and a chart registered in the repository 110 in association with each other.

Here, keywords used for chart search will be described. There are the following three types of keywords.
Keyword 1: A keyword extracted from the cover of the presentation document.
Keyword 2: A keyword extracted from within each chart, that is, a keyword extracted from a document within each chart.
Keyword 3: The category of the presentation document containing the chart.

  Keyword 1 uses a word extracted from the cover of the presentation document as a keyword. The cover of the presentation document includes the date of the lecture, the location and name of the lecture that identifies the lecture, and the name of the speaker. These are used as keywords for chart search. Note that keywords extracted from the cover of the document may be treated specially as keywords 2 and 3 as priority keywords. This is because the usage history of the chart, when, where, and by whom it was used, is important when reusing the chart.

The keyword 2 uses a word included in each chart as a keyword, that is, uses a word included in a document in each chart as a keyword. For example, if the chart includes a document including a sentence “The influence of the Internet on society ...”, “Internet society” is extracted as a keyword. When extracting a keyword from a document in the chart, the keyword may be extracted according to a condition such as a word appearing multiple times in the document or a word written in bold. Note that the number of words to be extracted as a keyword is not limited to one and may be plural.

  The keyword 3 uses a category in which the presentation document including the chart is located as a keyword. A category or sub-category that classifies the presentation document in the repository 110 is used as a keyword. If there are multiple sub-categories, they are also registered as keywords.

  FIG. 8 is an example of an index table stored in the index DB 120 according to the present embodiment. The index table includes a keyword 205a, a document ID 205b, a chart ID 205c, and a weight 205d.

  The keyword 205a stores a keyword used for chart search. The first record in FIG. 8 is an example in which the above-described keyword 1 is used as a keyword, and the lecture date, the lecture place, and the name of the lecturer extracted from the cover of the presentation document are recorded. The second record in FIG. 8 is an example in which the above-described keyword 2 is used as a keyword, and “Internet society” extracted from the document in the chart is stored. Further, the third record in FIG. 8 is an example in which the above-described keyword 3 is used as a keyword, and the category “For overseas” of the presentation document is registered.

  The document ID 205b and the chart ID 205c store the document ID 205b and the chart ID 205c of the chart associated with the keyword 205a. The weight 205d stores a weight used as a weight in the search, and is used when determining the ranking of the chart. Note that the weight 205d is arbitrary, and a value need not be set.

  The document part request receiving unit 103 receives the keyword specified by the document editing terminal 20 or the document ID and chart ID of the chart specified by the document editing terminal 20. When the document part request receiving unit 103 receives a keyword, it transmits the received keyword to the keyword search unit 104. On the other hand, when the document ID and the chart ID are received, the received document ID and chart ID are transmitted to the history search unit 106.

  The keyword search unit 104 searches the index DB 120 with the keyword received from the document part request reception unit 103, and acquires the document ID and chart ID of the chart including the keyword as a search result.

  The document component acquisition unit 105 acquires chart information from the repository 110 based on the document ID and the chart ID acquired by the keyword search unit 104. The document component acquisition unit 105 acquires chart information from the repository 110 based on the document ID and the chart ID acquired by the history search unit 106. Also, attribute information such as a title is acquired from the document attribute table of the repository 110 based on the document ID and chart ID acquired by the history search unit 106.

  The history search unit 106 searches the history table of the history DB 130 based on the document ID and the chart ID received from the document part request receiving unit 103, and has a usage relationship with the chart specified by the received document ID and chart ID. Get the document ID and chart ID of the chart. Specifically, a history table is specified in which the document ID and chart ID received from the document component request receiving unit 103 are the document ID and chart ID of the own chart, and the document ID and chart ID of the parent chart and child chart are acquired. To do.

  The transmitting unit 107 transmits the chart information acquired by the document part acquiring unit 105 to the document editing terminal 20 that transmitted the keyword. Further, when the attribute information is acquired by the document part acquisition unit 105, the transmission unit 107 transmits the attribute information together with the chart to the document editing terminal 20.

[Registration process flow]
FIG. 9 is a flowchart of the presentation document registration process according to the present embodiment. When the document registration unit 100 receives a new presentation document to be registered in the repository 110 from the document editing terminal 20, the process starts.
S100: The document registration unit 100 acquires the document ID and the chart ID from the chart attributes of all the charts included in the presentation document, and sets them as the existing document ID and the existing chart ID.
S110: If the existing document ID and the existing chart ID can be acquired in step S100, the document registration unit 100 charts included in the existing chart and the new presentation document specified by the existing document ID and the existing chart ID ( New chart) to determine whether it has been changed. If the determination result is YES, the process proceeds to step S130, and if the determination result is NO, the process proceeds to step S120.

S120: The document registration unit 100 sets the chart attribute change flag of the chart attached to the new chart to FALSE.
S130: The document registration unit 100 sets the chart attribute change flag assigned to the new chart to TRUE.
S140: The document registration unit 100 assigns a new document ID to the new presentation document, assigns a new chart ID to each of the charts included in the new presentation document, and writes them in the chart attributes of each chart.
S150: The document registration unit 100 registers a new presentation document in the repository 110.

S160: The history registration unit 102 uses the existing document ID and the existing chart ID acquired in step S100 as the parent chart document ID and chart ID, and uses the new document ID and new chart ID allocated in step S140 as the document of the own chart. It is stored in the history table of the history DB 130 as history information that is an ID and a chart ID.
S170: The history registration unit 102 determines whether there is history information in which the parent document ID and the parent chart ID are the document ID and chart ID of the own chart in the history table. If the determination result is YES, the process proceeds to step S180, and if the determination result is NO, the process proceeds to step S190.
S180: The history registration unit 102 stores the new document ID and the new chart ID in the document ID and chart ID of the child chart of the history information acquired in step S170.

S190: The index registration unit 101 acquires a keyword from the new presentation document and the chart registered in the repository in step S150 for each chart.
S200: The index registration unit 101 stores the combination of the keyword and chart acquired in step S190 in the index DB 120.

[Search process flow]
FIG. 10 is a flowchart of the keyword search process according to the present embodiment. When the keyword search unit 104 receives a keyword from the document editing terminal 20 via the document part request receiving unit 103, the process starts.
S210: The keyword search unit 104 extracts a document ID and a chart ID corresponding to the keyword received from the document editing terminal 20 from the index DB 120.
S220: The document component acquisition unit 105 acquires chart information from the repository 110 based on the document ID and the chart ID acquired in step S210.
S230: The transmission unit 107 transmits the chart information acquired in step S220 to the document editing terminal 20.

[Chart history acquisition flow]
FIG. 11 is a flowchart of the chart history acquisition process according to the present embodiment. When the history search unit 106 receives the document ID and the chart ID from the document editing terminal 20 via the document part request receiving unit 103, the process starts. In the flowchart shown in FIG. 11, it is assumed that the parent up to α generation and the child up to α generation are acquired from the chart specified by the document ID and the chart ID received from the document editing terminal 20.

S300: The history search unit 106 acquires history information having the document ID and the chart ID received from the document editing terminal 20 as its own chart from the history table of the history DB 130.
S310: The history search unit 106 determines whether the history information acquired in step S300 includes the document ID and chart ID of the parent chart. If the determination result is YES, the process proceeds to step S320, and if the determination result is NO, the process proceeds to step S350.
S320: The history search unit 106 further acquires history information using the parent chart as its own chart based on the document ID and the chart ID of the parent chart included in the history information acquired in step S300.

S330: The history search unit 106 adds 1 to n indicating how many generations of parent charts have been acquired.
S340: The history search unit 106 determines whether n is less than α. If n is less than α, steps S310, S320, and S330 are repeated. If n is greater than or equal to α, the process proceeds to step S350.

S350: The history search unit 106 determines whether the history information acquired in step S300 includes the child chart document ID and the chart ID. If the determination result is YES, the process proceeds to step S360, and if the determination result is NO, the process ends.
S360: The history search unit 106 further acquires history information using the child chart as its own chart based on the document ID and the chart ID of the child chart included in the history information acquired in step S350. If the history information includes a plurality of child charts, the process of step S360 is performed for each.

S370: The history search unit 106 adds 1 to m indicating how many generations of child charts have been acquired.
S380: The history search unit 106 determines whether m is less than α. If m is less than α, the processes of steps S350, S360, and S370 are repeated. If m is greater than or equal to α, the process ends.

  In this way, the history of the chart can be acquired by acquiring the multiple generation parent chart and the multiple generation child chart of the chart specified by the document ID and the chart ID received from the document editing terminal 20. it can.

[Search screen]
FIG. 12 is a diagram showing a keyword search screen according to the present embodiment. The search screen shown in FIG. 12 is displayed on output means such as a display of the document editing terminal 20. The search screen includes a keyword input unit 300, a search result display unit 310, a history display unit 320, and a detailed display unit 330. Before the keyword search, nothing is displayed on the search result display section 310, the history display section 320, and the detail display section 330.

  First, the document editor inputs a keyword to be searched for in the keyword input field 301 of the keyword input unit 300 and presses the search button. In response to pressing of the search button, the keyword search unit 104 of the document component management apparatus 10 searches the index DB 120 for a chart including the keyword, and displays a list of results on the search result display unit 310. In FIG. 12, the result is displayed as a thumbnail image of the chart.

  Next, in response to the document editor selecting a chart displayed on the search result display unit 310, the history search unit 106 of the document component management apparatus 10 is based on the document ID and the chart ID of the selected chart. Then, the history DB 130 is searched. As a search result, the history of the chart selected by the document editor is displayed on the history display unit 320 as a relation diagram. The history of the chart is also displayed using the thumbnail image of the chart. At this time, attributes such as the title, date, and creator of the presentation document including the chart are also acquired from the repository 110 and displayed together. In FIG. 12, assuming that the chart 321 is selected by the search result display unit 310, the history chart 320 displays the parent chart and child chart of the chart 321. The parent of the parent chart and the child of the child chart may be displayed.

  When the document editor selects a chart in the history display section 320, the contents are displayed on the detail display section 330 on a reduced screen or the like. Thereby, the document editor can confirm the contents of the chart. When the chart is displayed on the detail display unit 330, a button “Use this chart” is displayed on the detail display unit 330. When the document editor presses this button, a new presentation document can be created using the chart displayed on the history display unit 320.

  Thus, the text editor can obtain not only a chart including the keyword as a search result but also a history of the chart of the search result by keyword search. This is because the document part management apparatus 10 according to the present embodiment can manage the history of a chart by associating a chart having a usage relationship (parent-child relationship) across a plurality of presentation documents registered in the repository 110. is there. Since the history of the search result chart can be obtained, the document editor can easily find a chart that meets the desire to use the latest version of the chart or to use the original chart. In addition, by displaying the chart attributes together, the document editor can easily select a chart suitable for the lecture using the newly created document.

[Editing screen]
FIG. 13 is a diagram showing a document editing screen according to the present embodiment. The document editing screen shown in FIG. 13 is displayed on output means such as a display of the document editing terminal 20. The document editing screen includes a document display unit 400, a history display unit 410, and a detail display unit 420.

  The document display unit 400 displays a chart that is currently being edited by the document editor. In FIG. 13, the chart is displayed as a thumbnail image. In response to the document editor selecting a chart displayed on the document display unit 400, the history search unit 106 of the document component management apparatus 10 selects a history based on the document ID and the chart ID of the selected chart. The DB 130 is searched. As a search result, the history of the chart selected by the document editor is displayed on the history display unit 410. The history of the chart is also displayed using the thumbnail image of the chart. At this time, attributes such as the title, date, and creator of the presentation document including the chart are also acquired from the repository 110 and displayed together.

  When the document editor selects a chart in the history display unit 410, the contents are displayed on the detail display unit 420 on a reduced screen or the like. Thereby, the document editor can confirm the contents of the chart. When the chart is displayed on the detail display unit 420, a button “Use this chart” is displayed on the detail display unit 420. When the document editor presses this button, the document editor can copy to the document being edited or replace the chart selected in the document display unit 400.

  As described above, by managing the chart history in the document component management apparatus 10 according to the present embodiment, the document editor can easily obtain the chart history included in the document being edited. As a result, the document editor can easily replace the chart included in the document being edited.

  FIG. 14 is a diagram illustrating a hardware configuration of the document component management apparatus 10 according to the present embodiment. In FIG. 14, the document component management apparatus 10 is the information processing apparatus 1000, and its hardware configuration is illustrated. In the following, an overall configuration of an information processing apparatus typified by a computer will be described, but it goes without saying that the minimum required configuration can be selected according to the environment.

  The information processing apparatus 1000 includes a CPU (Central Processing Unit) 1010, a bus line 1005, a communication I / F 1040, a main memory 1050, a BIOS (Basic Input Output System) 1060, a parallel port 1080, a USB port 1090, a graphic controller 1020, and a VRAM 1024. , An audio processor 1030, an I / O controller 1070, and input means such as a keyboard and mouse adapter 1100. Storage means such as a flexible disk (FD) drive 1072, a hard disk 1074, an optical disk drive 1076, and a semiconductor memory 1078 can be connected to the I / O controller 1070.

  A microphone 1036, an amplifier circuit 1032, and a speaker 1034 are connected to the audio processor 1030. A display device 1022 is connected to the graphic controller 1020.

  The BIOS 1060 stores a boot program executed by the CPU 1010 when the information processing apparatus 1000 is activated, a program depending on the hardware of the information processing apparatus 1000, and the like. An FD (flexible disk) drive 1072 reads a program or data from the flexible disk 1071 and provides it to the main memory 1050 or the hard disk 1074 via the I / O controller 1070. FIG. 14 shows an example in which the information processing apparatus 1000 includes a hard disk 1074. However, an external device connection interface (not shown) is connected to the bus line 1005 or the I / O controller 1070, and the information processing apparatus A hard disk may be connected or added to the outside of 1000.

  As the optical disk drive 1076, for example, a DVD-ROM drive, a CD-ROM drive, or a DVD-RAM drive can be used. In this case, it is necessary to use the optical disk 1077 corresponding to each drive. The optical disk drive 1076 can also read a program or data from the optical disk 1077 and provide it to the main memory 1050 or the hard disk 1074 via the I / O controller 1070.

  The computer program provided to the information processing apparatus 1000 is stored in a recording medium such as the flexible disk 1071, the optical disk 1077, or a memory card and provided by the user. This computer program is read from the recording medium via the I / O controller 1070 or downloaded via the communication I / F 1040 to be installed and executed in the information processing apparatus 1000. The operation that the computer program causes the information processing apparatus to perform is the same as the operation in the apparatus that has already been described, and is therefore omitted.

  The aforementioned computer program may be stored in an external storage medium. As the storage medium, in addition to the flexible disk 1071, the optical disk 1077, or the memory card, a magneto-optical recording medium such as MD or a tape medium can be used. Alternatively, a storage device such as a hard disk or an optical disk library provided in a server system connected to a dedicated communication line or the Internet may be used as a recording medium, and a computer program may be provided to the information processing apparatus 1000 via the communication line. Good.

  In the above example, the information processing apparatus 1000 has been mainly described. However, the information described above is obtained by installing a program having the function described in the information processing apparatus in a computer and causing the computer to operate as the information processing apparatus. Functions similar to those of the processing device can be realized.

  The apparatus can be implemented as hardware, software, or a combination of hardware and software. A typical example of implementation using a combination of hardware and software is implementation on a computer system having a predetermined program. In such a case, the predetermined program is loaded into the computer system and executed, whereby the program causes the computer system to execute the processing according to the present invention. This program is composed of a group of instructions that can be expressed in any language, code, or notation. Such instructions may be either or both of the system directly performing a specific function, or (1) conversion to another language, code, or notation, and (2) copying to another medium. Can be executed after the Of course, the present invention includes not only such a program itself but also a program product including a medium on which the program is recorded. The program for executing the functions of the present invention can be stored in any computer-readable medium such as a flexible disk, MO, CD-ROM, DVD, hard disk device, ROM, RAM, and the like. Such a program can be downloaded from another computer system connected via a communication line or copied from another medium for storage in a computer-readable medium. Further, such a program can be compressed or divided into a plurality of parts and stored in a single or a plurality of recording media.

  Although the present invention has been described based on the embodiment, the present invention is not limited to the above-described embodiment. The effects described in the embodiments of the present invention are only the most preferable effects resulting from the present invention, and the effects of the present invention are limited to those described in the embodiments or examples of the present invention. Is not to be done.

It is a figure which shows the function structure of the document components management apparatus which concerns on this embodiment. It is a figure which shows an example of the category classification | category of the presentation document which concerns on this embodiment. It is a figure which shows an example of the chart attribute which concerns on this embodiment. It is a figure which shows an example of the link table of the repository which concerns on this embodiment. It is a figure which shows an example of the document attribute table of the repository which concerns on this embodiment. It is an example of the history table memorize | stored in history DB which concerns on this embodiment. It is an example of the log | history attached information table memorize | stored in log | history DB which concerns on this embodiment. It is an example of the index table memorize | stored in index DB which concerns on this embodiment. It is a flowchart of the presentation document registration process which concerns on this embodiment. It is a flowchart of the keyword search process which concerns on this embodiment. It is a flowchart of the chart history acquisition process which concerns on this embodiment. It is a figure which shows the search screen by the keyword which concerns on this embodiment. It is a figure which shows the document edit screen which concerns on this embodiment. It is a figure which shows the hardware constitutions of the document components management apparatus 10 which concerns on this embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Document parts management apparatus 20 Document editing terminal 100 Document registration part 101 Index registration part 102 History registration part 103 Document part request | requirement receiving part 104 Keyword search part 105 Document parts acquisition part 106 History search part 107 Transmission part 110 Repository 120 Index DB
130 History DB

Claims (11)

A document part management apparatus connected to a document editing terminal via a network,
A document storage unit for storing information on each of a plurality of documents;
A relation storage unit that stores document parts that are in a usage relationship across each other among the one or more document parts included in each of the plurality of documents in association with each other;
An index storage unit for storing a keyword associated with each of the one or more document parts in association with each of the one or more document parts;
A keyword search unit that searches the index storage unit for a document part corresponding to the received keyword in response to receiving the keyword from the document editing terminal;
A related document part search unit for acquiring a document part associated with the document part acquired by the keyword search unit from the relation storage unit;
A document part acquisition unit for acquiring information on the document part acquired by the keyword search unit and information on the document part acquired by the related document part search unit from the document storage unit;
A transmission unit that transmits information of the document part acquired by the document part acquisition unit to the document editing terminal;
A document parts management apparatus comprising: The usage relationship is a relationship caused by diversion or modification of the document part,
2. The relationship storage unit according to claim 1, wherein the relation storage unit stores the document part to be used as a parent document part, the used document part to be a child document part, and stores the parent document part and the child document part in association with each other. Document parts management device. The transmission unit transmits the usage relationship between the document parts to the document editing terminal together with the document part information acquired by the document part acquisition unit,
The document editing terminal is based on the usage relationship between the document parts, the document part information acquired by the keyword search unit and the document part information acquired from the related document part search unit. The document part management apparatus according to claim 1, wherein a document part relation diagram is displayed.   The document part management apparatus according to claim 1, wherein the document storage unit further stores a use history of each of the plurality of documents for each of the plurality of documents. The document storage unit classifies and stores information on each of the plurality of documents,
The document part management apparatus according to claim 1, wherein the keyword is extracted from a category in which information of a document including each of the one or more document parts is classified.   The document part management apparatus according to claim 4, wherein the keyword is extracted from the usage history.   The document part management apparatus according to claim 1, wherein the index storage unit stores a weight for a combination of the keyword and the document part.   The document parts management apparatus according to claim 1, wherein the plurality of documents are presentation documents, and the document parts are charts constituting the presentation documents. A method for managing one or more document parts included in a document created by a document editing terminal,
Storing information of each of the plurality of documents;
Storing one or more document parts included in each of the plurality of documents in association with each other in a cross-sectional manner in the plurality of documents;
Storing each of the one or more document parts in association with a keyword associated with each of the one or more document parts;
Searching for a document part corresponding to the received keyword in response to receiving the keyword from the document editing terminal;
Obtaining document parts that are in use relationship with the retrieved document parts and are associated with each other;
Obtaining information on the retrieved document parts and information on the document parts that are in a usage relationship with the retrieved document parts and are associated with each other;
Transmitting the acquired document part information to the document editing terminal;
Document part management method including A program for managing one or more document parts included in a document created by a document editing terminal by a computer,
The computer,
Storing information of each of the plurality of documents;
Storing one or more document parts included in each of the plurality of documents in association with each other in a cross-sectional manner in the plurality of documents;
Storing each of the one or more document parts in association with a keyword associated with each of the one or more document parts;
Searching for a document part corresponding to the received keyword in response to receiving the keyword from the document editing terminal;
Obtaining document parts that are in use relationship with the retrieved document parts and are associated with each other;
Obtaining information on the retrieved document parts and information on the document parts that are in a usage relationship with the retrieved document parts and are associated with each other;
Transmitting the acquired document part information to the document editing terminal;
A program that executes A document part management apparatus connected to a document editing terminal via a network,
A document storage unit that stores information on each of a plurality of documents classified into categories, and a usage history of each of the plurality of documents for each of the plurality of documents;
A relation storage unit that stores document parts that are in a usage relationship across each other among the one or more document parts included in each of the plurality of documents in association with each other;
Each of the one or more document parts is associated with at least one of a keyword extracted from a category in which document information including each of the one or more document parts is classified and a keyword extracted from the usage history, and An index storage unit for storing a weight for each combination of the keyword and the one or more document parts;
A keyword search unit that searches the index storage unit for a document part corresponding to the received keyword in response to receiving the keyword from the document editing terminal;
A related document part search unit for acquiring a document part associated with the document part acquired by the keyword search unit from the relation storage unit;
A document part acquisition unit for acquiring information on the document part acquired by the keyword search unit and information on the document part acquired by the related document part search unit from the document storage unit;
A transmission unit that transmits the usage relationship between the document parts to the document editing terminal together with the document part information acquired by the document part acquisition unit;
With
The document editing terminal is based on the usage relationship between the document parts, information on the document including the document parts acquired by the keyword search unit, and information on the document parts acquired from the related document part search unit A document part management apparatus for displaying a relationship diagram of the document parts.

Images