JP2002099528A - Information processing equipment, its method and computer-readable memory - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an information processing equipment, its method and computer-readable memory which can produce an integrated electronic document from different plural material electronic documents with annotation information added, and can easily edit while keeping the relation between the annotation information added to the material electronic document and the annotation information that is newly/further added to the integrated electronic document. SOLUTION: An electronic binder builder 102 holds plural types of material electronic documents 101, and selects a desired material page unit electronic document from each material page unit electronic document in plural types of the held material electronic documents 101. On the basis of selected material page unit electronic document, an integrated electronic document 103 including control information for controlling the addition of the annotation information is constituted.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an information processing apparatus and method for constructing an integrated electronic document composed of a plurality of types of material electronic documents, and a computer readable memory.

[0002]

2. Description of the Related Art Enterprises have introduced a document management system to promote the reuse of documents. Early products used paper scanners to capture images as images with a scanner and store them. However, more and more electronic documents created on personal computers have recently been able to register and store them. Also, recently, an arbitrary page can be extracted from a plurality of registered electronic documents and bound like a binder to form one electronic document. It is called an electronic binder here. An annotation can be added to such an electronic binder as additional information.

[0003]

However, the annotation information to be added to the conventional electronic binder is an electronic document (material electronic document) on the material side constituting the electronic binder.
Can be added to each of the generated electronic documents generated by binding the material electronic documents, but there is no relationship between the respective pieces of annotation information. Therefore, for example, the generated electronic document is composed of the material electronic document to which the annotation information is already added, and when further adding the annotation information to the generated electronic document, the generated electronic document is added to the composed material electronic document. Even when the file format of the annotation information and the file format of the annotation information to be added to the generated electronic document are the same, they must be managed separately.

[0004] Further, when a generated electronic document is configured as an image image using a material electronic document to which the annotation information is added, the annotation information is related only to that image image. Therefore, for example, when a generated electronic document is configured with a newly created image image by modifying the material electronic document, the annotation information added to the material electronic document before the change is added to the material electronic document after the change. Could not be reflected.

SUMMARY OF THE INVENTION The present invention has been made in view of the above-described problems. One integrated electronic document is created from a plurality of different material electronic documents to which annotation information is added, and the annotation information added to the material electronic document is created. Another object of the present invention is to provide an information processing apparatus and method capable of easily performing editing while maintaining the relationship of newly added / further added annotation information to an integrated electronic document, and a computer readable memory.

[0006]

An information processing apparatus according to the present invention for achieving the above object has the following arrangement.
That is, also preferably, an information processing apparatus constituting an integrated electronic document composed of a plurality of types of material electronic documents, holding means for holding the plurality of types of material electronic documents to which annotation information is added, A selection unit that selects a desired material page unit electronic document from each material page unit electronic document of the plurality of types of material electronic documents held by the holding unit, and a material page unit electronic document selected by the selection unit. Based on the control information for controlling the addition of the annotation information.

[0007] Preferably, the control information is set for the entire integrated electronic document or for each material page-based electronic document constituting the integrated electronic document.

[0008] Preferably, the configuration unit configures the material electronic document to which the annotation information is added and the integrated electronic document to which the annotation information is added, which constitutes the integrated electronic document, as one electronic document. .

Preferably, the constituent means includes: first annotation information added to the material electronic document;
Converting means for converting the second annotation information added to the integrated electronic document into a predetermined file format.

An information processing method according to the present invention for achieving the above object has the following configuration. That is, an information processing method for configuring an integrated electronic document including a plurality of types of material electronic documents, wherein a holding step of holding the plurality of types of material electronic documents to which annotation information is added in a storage medium; A step of selecting a desired material page unit electronic document from each material page unit electronic document of the plurality of types of material electronic documents held in the storage medium in the step; and a material page unit electronic document selected in the selecting step. A configuration step of configuring an integrated electronic document including control information for controlling the addition of the annotation information based on the document.

A computer readable memory according to the present invention for achieving the above object has the following configuration. That is,
A computer-readable memory storing a program code of information processing constituting an integrated electronic document composed of a plurality of types of material electronic documents, wherein the plurality of types of material electronic documents to which annotation information is added are stored in a storage medium. And a program code of a selecting step of selecting a desired material page unit electronic document from each material page unit electronic document of the plurality of types of material electronic documents held in the storage medium in the holding step. When,
And a program code of a configuration step of configuring an integrated electronic document including control information for controlling addition of the annotation information based on the material page unit electronic document selected in the selection step.

[0012]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Preferred embodiments of the present invention will be described below in detail with reference to the drawings.

FIG. 1 is a conceptual diagram of the document management system of the present embodiment.

In FIG. 1, reference numeral 101 denotes a group of electronic documents created by different application software. Here, for example, it is assumed that the electronic document 1 is an electronic document 1 created by Microsoft Word, an electronic document 2 created by Microsoft PowerPoint, an image read by a scanner, or an HTML electronic document 3 used on the Internet. 102 is an electronic binder builder (E (Electronic)-
Binder Builder), and one generated electronic document 103 can be configured by bundling the electronic documents 1 to 3 in page units.

Next, an example of a generated electronic document configured by the electronic binder builder 102 of the document management system according to the present embodiment will be described with reference to FIG.

FIG. 2A is a block diagram showing the format of a generated electronic document constituted by the electronic binder builder according to the present embodiment, and FIG. 2B is a specific XML description example.

According to the present invention, XML (Extensible Markup La
nguage) Use the description to compose the generated electronic document. The structure is a plurality of types of material electronic documents created with different application software for each document. In the basic configuration, for example, a document called E-Binder.xml is configured as a Top description, a predetermined description is performed therein, and related elements (contents) such as files are indicated by external links.
The element indicated by the external link must be in a location where its location is known. FIG. 4 is an example of a folder and a file configuration of the generated electronic document. E-Binder of Top document.
You can know the holding position of those external link elements by relative position from xml.

In FIG. 2B, <? Xml version = "1.0" en
coding = "Shift_JIS"?> is the description of the declaration made at the top.

In FIG. 2A, the EBINDE section (20
1) indicates the beginning of this document. In FIG. 2B, a portion surrounded by <EBINDER> to </ EBINDER> is the main body of the document.

In FIG. 2A, EBINDER_INF
The OR unit (202) is a unit that holds meta information (management information) of the document. And in FIG. 2B, <EBIN
The meta information is held in a portion surrounded by DER_INFO> to </ EBINDER_INFO>. In particular, here, <TITLE> to </ TITLE> indicating the file name and <CREATOR> indicating the creator name
~ <// CREATOR> and <DATE> to </ DATE> indicating creation date.

Incidentally, the expression of the meta information is not limited to this. For example, <EFILE_INFO> to <EFILE_INFO> in FIG.
And RDF (Resource Data Framework) defined by the World Wide Web Consortium (W3C) as shown inside <EBINDER_INFO> to </ EBINDER_INFO>
Such a mechanism may be used.

In FIG. 2A, the MATERIAL section (2
03) is a part for holding information of the material electronic document.
Then, in FIG. 2B, <MATERIAL files = "2> ~ <//
MATERIAL> holds the information in the area enclosed by <MATERIAL>. file
s = is the number of material electronic documents, and here shows an example in which two files are held.

In FIG. 2A, an EFILE unit (204)
Is a portion for holding information of one material electronic document, and a portion for converting the material electronic document into an electronic document in page units and holding the information. Then, in FIG. 2B, <EFILE href
= "Material \ ef0001 \ Original \ F_c01.ppt" composedpage
file = "Material \ efile0001.pdf" type = "pdf" totalpage
= "2" id = "ef0001"> The information is held in a portion surrounded by </ EFILE>. Here, href = is storage information of the material electronic document. composedpagefile = is storage information of a file in which material electronic documents are combined in page units. The following type = is the file format. Here, Adobe
An example of the PDF format of the company is shown. In addition, a format that can store a plurality of images, such as MultiPageTIFF, can be set. totalpa
ge = is the number of pages of the material electronic document. id = is a management number.

In FIG. 2A, an EFILE unit (204)
The EFILE_INFO section (205) stores management information of the material electronic document. And in FIG. 2B, <
EFILE_INFO datatype = "PowerPoint2000"> ~ </ EFILE_I
The management information is held in the portion surrounded by NFO>. Here, datatype = is the type of the material electronic document. Here, it indicates that it is PowerPoint2000. Also,
<TITLE> to </ TITLE> indicating a file name and <CREATOR> to </ CREATOR> indicating a creator name are parts for holding the management information.

In FIG. 2A, DOC_SUMMARY
The unit (206) holds outline information of the material electronic document.
This part is full text Tex so that you can understand the outline of the contents of the material
The sentence simplified by the summarization engine is saved from t. still,
This part is omitted in FIG. 2B.

In FIG. 2A, the EPAGES section (20
7) stores a document (material page unit electronic document) converted from material electronic document to information in page units. For example,
In a material electronic document of Word, a page is determined only at the time of display or printing, but the determined material page unit document is stored for each page. Then, in FIG. 2B, the material page unit electronic document is stored in a portion surrounded by <EPAGES> to </ EPAGES>. Actually, the following <EPAGE
page = "1" thumbnail = "Material \ ef0001 \ thumb1.bmp" /
>, <EPAGE page = "2" thumbnail = "Material \ ef0001 \ th
The part enclosed by <EPAGE ~ /> like umb2.bmp> is a part for storing the electronic document in unit of material page. here,
“page =” is information indicating the page of the entire material electronic device. The thumbnail = is information holding a thumbnail image (reduced image) of the electronic document in unit of material page. The following description is also information of a material page unit electronic document.
As described above, the page development information (material page unit electronic document information) of the material electronic document is held. Further, a developed document of the material page unit electronic document, for example, an image developed to A4 size is also stored here.

<EPAGE page = "1" thumbnail = "Material \ e
f0001 \ thumb1.bmp "Pagefile =" Material \ ef0001 \ page00
01.bmp "type =" bmp "/> where pagefile = holds the thumbnail image of the first page in this example.
pe = is the retained file format. In this example, the material page unit electronic document is in the image file format of bmp, but may be in PDF format or another compressed file format. The necessary condition is that it is in units of one page. Also, the number of <EPAGE ~ /> is determined by the number of pages of the material electronic document.

When the material electronic document has the annotation information and the annotation information is held on the generated electronic document, three holding methods as shown in FIG. 24 can be considered.

For example, for a material page unit electronic document 2501 having the annotation information 2500, the first holding method is a case where the annotation information as indicated by 2502 is ignored. At this time, in the generated electronic document,
Only the electronic document in unit of material page is retained. The structure of the generated electronic document is the same as that described above.

In the second holding method, as indicated by reference numeral 2503, a file format (for example, image, PD, etc.) that can be combined into a material page unit electronic document by combining the material page unit electronic document 2501 and the annotation information 2500 is used.
F, etc.) and hold. In this case, in order to hold the converted material page unit electronic document, <EFILE>
Composedpagefile in section (204) or <EPA
A material page unit electronic document converted into one of the pagefiles in the GE> section (207) is described.

In the third holding method, as shown by reference numerals 2504 and 2505, the electronic document and the annotation information are separated and stored in the generated electronic document. That is, in the generated electronic document, the material page unit electronic document and the annotation information are held independently of each other.

The annotation information may or may not be held in the generated electronic document. Otherwise, the structure of the generated electronic document is not different from that described above. On the other hand, when retaining the annotation information,
The format block configuration is as shown in FIG.

In FIG. 25, the annotation information is
ANNOT in the ANNOTATIONS section (2401)
It is held in the ATION section (2402). The information is
The file may be held as an external file, or may be held in the ANNOTATION section (2402) if it is in XML format. As the external file, for example, an image file or Adobe's FDF (Forms Data Forma
t) etc. In the case of a material page-based electronic document having no annotation information, as shown in 2403, it does not have an ANNOTATIONS section.

When the annotation information is provided in page units, the format block configuration is as shown in FIG.

In FIG. 26, ANNOTATIONS
In the section (2701), the annotation information for each page is A
It is stored in the NNOTATION section (2702).

Next, a specific XML description when the annotation information is held will be described with reference to FIG.

In FIG. 27, a part of FIG. 2B is extracted, and the first material electronic document (2601) has the annotation information of the entire material electronic document, and the second material electronic document (2604) has the annotation information. On the other hand, an example is shown in which the second page has the annotation information.

In the <ANNOTATIONS> tag (2602),
<ANNOTATON href = "Material \ ef0001 \ an0001.tiff" typ
e = "tiff" page = "all"/><ANNOTATION> tag (2603) is described. Here, href = holds the annotation information of the entire material electronic document. Whether the annotation information is the annotation information of the entire material electronic document is determined from the fact that the value of page = is all. type = is the file format held. In this example, the material page unit electronic document is in an image format called tiff, but may be in the FDF format or another file format.

Also, the <ANNOTATIONS> tag (2605)
Inside, <ANNOTATION href = "Material \ ef0002 \ Annotation \ an00"
02p0001.bmp "type =" bmp "page =" 1 "/><ANNOTATION href =" Material \ ef0002 \ Annotation \ an00
02p0003.bmp "type =" bmp "page =" 3 "/><ANNOTATION> tag (2606, 2607) is described.Because the value of page = is a numerical value (not all), This is annotation information for each page.
The annotation information described by href = is applied to the number of pages given by the value of page =. type = is the file format held. In this example, the material page unit electronic document is in the image format of bmp.
Format or any other file format.

FIG. 3 is a block diagram showing the format of a generated electronic document when a necessary material page unit electronic document is selected from material electronic documents and held.

In FIG. 3, the PAGEINDEX section (3
01) holds information indicating the page of the material electronic document that has been developed. The generated electronic document manages the ids and page numbers of the material electronic document, and forms a continuous electronic document by reading out the page images in that order. <PAGEINDEX> to </ PAGEIN in the description example of FIG. 2B
DEX> is a description for managing and storing the pages of the generated electronic document. Inside, it is described as <INDEXpage = "1" idref = "efile0002" efilepage = "3"/><INDEXpage = "2" idref = "efile0001" efilepage = "2"/>.<INDEX ~ /> indicates a page of the generated electronic document. Here, page = is the page of the generated electronic document. idref = is the id of the material electronic document. efilepage = is a used page number of the material electronic document corresponding to id. The above description example shows that pages specified separately from two material electronic documents are used. Specifically, the first page of the generated electronic document has the id
Becomes the third page of the material electronic document of "efile0002",
The second page is the second page of the material electronic document whose id is “efile0001”.

The format block configuration of the generated electronic document can be displayed through application software that has created each material electronic document constituting the generated electronic document. In some cases, such as when printing or distributing by attaching it to an e-mail or the like, it may be more convenient for the generated electronic document to be converted into a predetermined file format. In this case, a BOOKBINDING unit (2201) as shown in FIG. 22 is introduced for the format block configuration in FIG.

This BOOKBINDING section (220
1) PAGEIN for managing pages of generated electronic documents
A generated electronic document composed of each material page unit electronic document obtained from the DEX unit (301) is converted into a predetermined file format,
For example, it is a portion that holds a generated electronic document converted into a file format such as a predetermined image file format (tiff or the like) or PDF. The specific XML description example is shown in FIG. 23 as <BOOKBINDING href = "Bookbinding \ bind.pdf" type = "pd
f ">, where href = is information of a file obtained by converting the generated electronic document into a predetermined file format.
Is information on the format used to convert the generated electronic document into a predetermined file format. In this example, the format is PDF.

The <BPAGE> section (220 in FIG. 22)
2) is a portion for holding thumbnail images of each page constituting the generated electronic document converted into a predetermined file format. This specific XML description example is shown in FIG. 23 by <BPAGE page = "2" thumbnail = "Bookbinding \ page2.png"
//>, where page = is information on the number of the whole page. thumbnail = is information holding a thumbnail image (reduced image) of the page.

When the generated electronic document has the annotation information, the format block configuration is as shown in FIG.

FIG. 28 shows a file format configuration similar to the case where the material electronic document has the annotation information, as shown in FIGS.
OTATIONS section (2801) and its internal ANN
The annotation information is stored in the OTATION section (2802). As described above with reference to FIG. 25 and FIG. 26, the ANNOTATION unit (2802) can have annotation information for the entire material electronic document or annotation information in page units.

Next, a specific XML description in the case where the generated electronic document has annotation information of the entire electronic document will be described with reference to FIG.
9 will be described.

In FIG. 29, the <ANNOIATIONS> tag (29
01), <ANNOTATION href = "Annotation \ annotation.tiff" typ
e = "tiff" page = "all"/><ANNOTATION> tag (2902) is described. Here, href = holds the annotation information of the entire generated electronic document. Whether or not the generated electronic document is the annotation information is determined from the fact that the value of page = is all. type = is the file format held. In this example, the material page unit electronic document is in an image format called tiff, but may be in the FDF format or another file format.

A specific XML description in a case where the generated electronic document has annotation information in page units will be described with reference to FIG.

In FIG. 30, the <ANNOTATIONS> tag (30
01), <ANNOTATION href = "Annotation \ annotation1.bmp" typ
e = "bmp" page = "1"/><ANNOTATION href = "Annotation \ annotation3.bmp" typ
e = "bmp" page = "3"/> An <ANNOTATION> tag (3002) is described. Here, since the value of page = is a numerical value (not all), the annotation information is page-based annotation information. The annotation information described by href = is applied to the number of pages given by the value of page =. type = is the file format held. In this example, the material page unit electronic document is in the image format of bmp, but may be in the FDF format or another file format.

The format block configuration of the generated electronic document as described above is a configuration in which the material electronic document, the material page unit electronic document, and the generated electronic document can be simultaneously stored. , It is possible to replace the page again. Also, the electronic document in unit of material page is an imaged document, P
The configuration may be a DF format or XML format document, and can be switched according to a software environment that can be converted into a page.

Next, an example of an operation screen related to the processing of the electronic binder builder 102 will be described with reference to FIG.

FIG. 5 is a view showing an example of an operation screen relating to the processing of the electronic binder builder of the present embodiment.

Reference numeral 501 denotes an example of a document management software screen. Reference numeral 502 denotes an example of a file management screen managed on the OS of the computer. Reference numeral 503 denotes the software of the electronic binder builder 102 (E-Binder Bui
lder) This is an example of a screen. Reference numeral 504 denotes an example of a Collection Window screen for managing a material electronic document. Reference numeral 505 denotes an example of a Composed Window screen for managing a generated electronic document. 506
Is a display software (Vi
ewer) It is an example of a screen.

Next, with regard to the process of creating the generated electronic document,
This will be described with reference to FIGS.

FIG. 6 is a flowchart showing a process for creating a generated electronic document according to the present embodiment.

First, in step S601, a material electronic document is selected from the file management screen 502. Next, in step S602, the selected material electronic document is moved to the software screen 503 of the electronic binder builder 102 by drag and drop (Drag & Drop). This operation is to move the file with the mouse as depicted by the arrow in FIG. The moved file is stored in step S
At 603, a thumbnail is displayed on the CollectionWindow screen 504. In this operation, in the background, the creation software of the material electronic document is opened, a pseudo printing operation is performed, and a file (material page unit electronic document) that can be handled in page units is created. For example, if a printer driver called ImageDriver is used, a page image can be created. At the same time, a thumbnail image can be created.
Then, in step S603, the created thumbnail image is displayed. When the file is actually created, the <EFIL> enclosed in <MATERIAL> shown in FIG. 2B
The link destination (address) of the material electronic document is described in href = of E href = "~>, and <EPAGE page =" 1 "thumbnail =" ~ \ th
A thumbnail image is held in thumbnail = shown in umb1.bmp ">>. This operation is the same as when moving a plurality of other material page unit electronic documents.

At step S604, the Collection Window
Select the thumbnail on the screen 504 and select Composed Windo
w Drag and drop to the screen 505. This operation is to display a thumbnail image of the electronic document in unit of material page required as the final generated electronic document on the Collection Window screen 504.
Select from above and move the thumbnail image to Composed Window screen 505 where the generated electronic document is configured,
That page will be prepared.

The input of the material electronic document is not limited to the above-described drag-and-drop method, but it is also possible to specify and input the material electronic document on the local or network from the electronic binder builder 102. Further, in the calling software (the document management system in the present embodiment), for example, a necessary material electronic document is selected in advance by the calling software, and a button for starting the electronic binder builder 102 is pressed. May be input by the action of.

In step S605, a thumbnail image of the generated electronic document is displayed on the Composed Window screen 505. This operation is an operation of displaying the thumbnail image moved in step 604 at the specified position where the thumbnail image was dropped.

By completing this processing, it is possible to construct a generated electronic document composed of necessary pages from the material electronic document.

Next, a specific example will be described in which a thumbnail image of a necessary electronic page unit material document is selected from the Collection Window screen 504 and the thumbnail image is moved to the Composed Window screen 505 in which the generated electronic document is configured. This will be described with reference to FIG.

In FIG. 7, reference numeral 701 denotes a collection window.
w A material page unit electronic document selected from material electronic documents on the screen 504. Reference numeral 702 denotes a state in which the material page unit electronic document 701 has been moved to the first page of the generated electronic document on the Composed Window screen 505.

Here, this state will be described with reference to FIG. 2B. In FIG. 2B, <EFILE ~><EPAGES><EPAGE page = "1" thumbnail = "Material \ ppt0000 \ thumb1.bmp"/>. . . . . </ EPAGES></EFILE>. . . . . <PAGEINDEX><INDEXpage = "1" idref = "efile0002" efilepage = "3"/><INDEXpage = "2" idref = "efile0001" efilepage = "2"/><INDEXpage = "3" idref = "efile0002" efilepage = "2"/> In the description of </ PAGEINDEX>, there is a description in <EPAGE ~> that holds a thumbnail image. This is Collection Window screen 5
4 is a thumbnail image displayed on the display unit 04. <PAGEIN
The part between DEX> and </ PAGEINDEX> is Composed Wi
This is page information of the thumbnail image displayed on the ndow screen 505. It does not have the actual thumbnail image but refers to the file name and page in the material electronic document. For example, <INDEXpage = "1" idref = "efile0002"
efilepage = "3"/> is a description indicating that the id of the material electronic document is specified on the first page of the generated electronic document, and that the third page of the file is used.

As described above, the electronic binder builder 102 can select a material page unit electronic document of a necessary page from material electronic documents of different formats, and can reedit it. In particular, as a feature when constructing a generated electronic document, an original material electronic document for generating a page can be followed by a link, and operations can be performed on a page-by-page material page-based electronic document.

Next, a specific example of moving the material electronic document stored on the Collection Window screen 504 to the Composed Window screen 505 will be described with reference to FIG.

In FIG. 8, two material electronic documents are input to the software screen 503 of the electronic binder builder 102,
The llection Window screens 504a and 504b respectively show a state in which a material electronic document is held.

Reference numeral 801 denotes a state in which a thumbnail image of a certain page of the material electronic document 1 is selected, and reference numeral 802 denotes a state in which a thumbnail image of a certain page of the material electronic document 2 is selected. When these thumbnail images are moved to the Composed Window screen 505, the thumbnail images are displayed in the selected order. In this case, as a result of selecting in order of 801 and 802, Compos
Thumbnail images 803 and 804 are displayed on the ed Window screen 505.

FIG. 9 shows a Collection Window screen 5
When a thumbnail image 901 of a page of the same electronic document on the document 04 is dragged and dropped between two thumbnail images displayed on the Composed Window screen 505, a thumbnail image 902 is inserted between the two thumbnail images. This is a specific example. By this operation, the total page is moved up by one.

FIGS. 10A to 10C show Collecti.
Composed Wi of thumbnail image on on Window screen 504
This is a specific example showing that the arrangement of pages of a generated electronic document generated by moving to the ndow screen 505 is in the order of selecting material page unit electronic documents.

FIG. 10A shows a state in which thumbnail images 1002 and 1001 on the Collection Window screen 504 are selected in the selection order shown in FIG. Then, thumbnail images 1002, 1001, 1 in the selection order shown in FIG.
When 001 is moved to the Composed Window screen 505, Com
On the posed Window screen 505, thumbnail images are arranged in the selection order.

FIG. 10 (b) shows the Collection Win
Thumbnail images 1003, 1004 on dow screen 504
Is selected. Then, when these thumbnail images 1003 and 1004 are moved to the Composed Window screen 505, the thumbnail images are arranged in the page order of the material electronic document.

FIG. 10C shows a plurality of source electronic documents in the selection order shown in FIG.
thumbnail image 100 on the Option Window screen 504a
5. The thumbnail image 1006 on the Collection Window screen 504b has been selected. And FIG.
These thumbnail images 1005 and 100 shown in (c)
6 to the Composed Window screen 505, Compose
On the d Window screen 505, thumbnail images are arranged in the order of selection. However, batch selection when selecting thumbnail images over a plurality of material electronic documents is prohibited or a priority order is set for each material electronic document, and the thumbnail images are arranged on the Composed Window screen 505 according to the priority order.

FIG. 11 is a specific example showing from which material electronic document the thumbnail image moved on the Composed Window screen 505 was moved. When a thumbnail image of 1/3, 2/3 page on the Composed Window screen 505 is selected, a thumbnail image 1101 of the corresponding Collection Window screen 504a and a Collection Window screen 50 are displayed.
The thumbnail image 1102 of 4b is displayed in a frame or translucent, indicating that the thumbnail image 1102 is in the selected state.

This corresponds to <PAGEINDEX>, <INDEXpage = "1"
This is because the management number and the page number of the material electronic document are described in the description of idref = "efile0002" efilepage = "3"/>, so that the page of the material electronic document can be traced.

FIG. 12 shows a specific example in which the pages of the thumbnail images stored on the Composed Window screen 505 are replaced. Here, when the thumbnail image 1201 of the ／ page is dragged and dropped on the right thumbnail image, the thumbnail image 1202 is replaced with the next thumbnail image.

This is as follows: <PAGEINDEX><INDEXpage = "1" idref = "efile0001" efilepage = "3"/><INDEXpage = "2" idref = "efile0001" efilepage = "2"/><INDEXpage = "3""idref=" efile0002 "efilepage =" 2 "/><INDEXpage=" 4 "idref =" efile0001 "efilepage =" 4 "/></PAGEINDEX> This description is <PAGEINDEX><INDEXpage=" 1 "idref = "efile0001" efilepage = "3"/><INDEXpage = "2" idref = "efile0002" efilepage = "2"/> <INDEXpage = "3" idref = "efile0001" efilepage = "2"/><INDEXpage = " 4 "idref =" efile0001 "efilepage =" 4 "/></PAGEINDEX> Edited as underlined.

FIG. 13 shows a plurality of thumbnail images separately selected on the Composed Window screen 505,
This is a specific example in the case of performing page replacement. The numbers are stored in the order of selection, and they are moved to the designated location as they are.
Reference numerals 1301 and 1302 denote results of the movement of the selected thumbnail image. After the movement, the thumbnail images are packed and arranged. In this movement, the thumbnail images are exchanged in the order of selection, so that FIG. 13 shows the normal order. However, if the larger page is selected first, the arrangement of the pages is reversed after the exchange. In the example of FIG. 13, when the selection order 1 and 2 are reversed, 1301 and 1302 are reversed.

FIG. 14 shows a specific example in which a material electronic document that has been used once is re-edited and reused. This specific example will be described together with the flowchart of FIG.

In step S1501, the Collection Window
w Double-click the thumbnail image 1401 of the electronic document in unit of material page on the screen 504. As a result, in step S1502, the application software that created the material electronic document receives and starts the material electronic document of the material page unit electronic document 1402.

In step S1503, the application software modifies the material page unit electronic document. After the correction, in step S1504, the material electronic document 1403 corrected by the application software is overwritten and saved.
As a result of this storage, the electronic binder builder 102 receives the change notification, prompts the user for an instruction, and proceeds to step S150.
In 5, a thumbnail creation process for creating a thumbnail image of the updated material page unit electronic document is started.

Next, in step S1506, Composed W
An inquiry is made to the user on the indow screen 505 as to whether to update or delete the material page unit electronic document currently used. This is because the content of the page of the material electronic document is shifted by updating the material page unit electronic document, so that the generated electronic document also needs to be changed.

If the instruction is for deletion, step S150
In step 8, the old thumbnail image 1405 arranged on the Composed Window screen 505 is deleted. Next, step S1
At 509, the display of the old thumbnail image 1401 arranged on the Collection Window screen 504 is replaced with a new thumbnail image 1404. This is the end of deletion.

If the instruction is not a delete instruction, that is, if it is an update instruction, in step S1510, the Composed Window
w The position of the old thumbnail image arranged on the screen 505 is stored, and the old thumbnail image is deleted. Next, in step S1511, the display of the old thumbnail image 1401 on the Collection Window screen 504 is changed to the new thumbnail image 1
Replace with 406. Then, in step S1512,
A new thumbnail image 1407 is displayed at the position stored on the Composed Window screen 505.

FIG. 16 shows a specific example in which a thumbnail image stored on the Composed Window screen 505 is rotated.

In FIG. 16, two thumbnail images shown at 1601 are selected. Next, when a rotation instruction of 90 degrees to the right is issued, the page direction (vertical placement) does not change as indicated by 1602, but the contents are rotated to the right by 90 degrees so as to match the page direction. Similarly, a rotation instruction of 90 degrees to the left can be given.

FIG. 17 shows another specific example in which the thumbnail image stored on the Composed Window screen 505 is rotated.

In FIG. 17, two thumbnail images indicated by 1701 are selected. Next, when a rotation instruction of 180 degrees is given, the selected thumbnail image is rotated 180 degrees as shown by 1702, and is turned upside down.

FIG. 18 is a diagram showing a correlation in rotation of a thumbnail image according to the present embodiment.

The generated electronic document finally saved by the rotation has several formats.

(1) A format for storing all information including a material electronic document and a generated electronic document.

(2) A format for storing only the generated electronic document.

(3) A format for storing only a material electronic document. There is. The above cases will be described in order. (1) A format including all information including a material electronic document and a generated electronic document.

This is a format that can be traced from the generated electronic document to the information of the material electronic document, and is the description format described with reference to FIG. This state is as shown below in an excerpt of the XML description.

<EBINDER><MATERIAL files = "2><EFILE~><EPAGES><EPAGE page =" 1 "thumbnail =" Material \ ef0001 \ thumb1.bmp "pagefile =" Material \ ppt0000 \ page1.tiff type = TIFF / ＞． . . . . <EPAGES></EFILE><EFILE~>. . . . . </ EFILE></MATERIAL><PAGEINDEX><INDEXpage = "1" idref = "efile0002" efilepage = "3"/><INDEXpage = "2" idref = "efile0001" efilepage = "1"/><INDEXpage = "3" idref = "efile0002" efilepage = "2"/></PAGEINDEX></EBINDER> This state is a thumbnail image for each page of the source electronic document, a page-based document used in the generated electronic document, In this example, it is provided as an image format (TIFF) (however, an intermediate format that can be described in page units, for example, PDF, XML / SVG, etc. may be used). Since the page is specified on the generated electronic document side, it has all information documents that can reconstruct the page. Conversely, a material page unit electronic document on the material electronic document side that is not specified on the generated electronic document side has a large file. In this way, the document is stored as an aggregate of a plurality of electronic documents on the material electronic document side and the generated electronic document side. (2) A format for storing only generated electronic documents.

This is a storage method when only the generated electronic document is required.

The document of the format (1) is a form in which the material electronic document and the generated electronic document are integrated, and is shown in FIG.
When a process of collecting information of a material page unit electronic document is performed in the bookbinding unit (2201), the material page unit electronic document is completely extracted from the material electronic document and held. This state is shown in an excerpt of the XML description.
It looks like this:

<EBINDER><MATERIALfiles = "2><EFILE~><EPAGES> ... <EPAGES></EFILE><EFILE~> ... </ EFILE></MATERIAL><PAGEINDEX><INDEXpage = "1" idref = "efile0002" efilepage = "3"/><INDEXpage = "2" idref = "efile0001" efilepage = "1"/><INDEXpage = "3" idref = "efile0002" efilepage = "2"/><PAGEINDEX><BOOKBINDING href = "Bookbinding \ bind.tiff" type = "tiff"><BPAGE page = "1" thumbnail = "Bookbinding \ page1.png"/><BPAGE page = "2" thumbnail = "Bookbinding \ page2.png"/><BPAGE page = "3" thumbnail = "Bookbinding \ page3.png"/></BOOKBINDING></EBINDER> In this state, <BOOKBINDING href = "Bookbinding \ bin
d.tiff "type =" tiff "> to </ BOOKBINDING>, which is a format in which the generated electronic document is stored in one file format.
In the example, the image is bundled as a multi-page image called bind.tiff (sometimes called bind.pdf or bind.xml). The thumbnail image of each page is <
BPAGE page = "1" thumbnail = "Bookbinding \ page1.png" /
It is described in the place of>. This copies the thumbnail image used in the material electronic document and brings it under your own control. The state where all of these are complete is the complete state on the generated electronic document side. At this point, <MATERIAL> to </ MATAT
The information enclosed by <ERIAL> and <EFILES> to </ EFILES> becomes unnecessary.

Therefore, the above description is made as follows: <EBINDER> <BOOKBINDING href = "Bookbinding \ bind.tiff" type = "tiff"> <BPAGE page = "1" thumbnail = "Bookbinding \ page1.png" /> <BPAGE page = "2" thumbnail = "Bookbinding \ page2.png" /> <BPAGE page = "3" thumbnail = "Bookbinding \ page3.png" /> </ BOOKBINDING> </ EBINDER> it can.

Further, there is a description that saves only the bind.tiff file more simply. In this case, it is used when only the bundled file is to be obtained. (3) A format in which only a material electronic document is stored.

This is a format in which only the material electronic document is stored, and the material electronic document once brought to the electronic binder builder 102 side holds a thumbnail image for each page together with the original document. This state is as shown below in an excerpt of the XML description.

<EBINDER><EBINDER_INFO>. . . . . </ EBINDER_INFO><MATERIAL files = "2><EFILE href =" Material \ ef0001 \ Original \ F_c01.ppt "composedpagefile =" Material \ efile0001.pdf "type =" pdf "totalpage =" 2 "id =" ef0001 "><EFILE_INFOdatatype = "PowerPoint2000"> ... </ EFILE_INFO><EPAGES><EPAGE page = "1" thumbnail = "Material \ ef0001 \ thumb1.bmp"/><EPAGE page = "2" thumbnail = " Material \ ef0001 \ thumb2.bmp "/></EPAGES></EFILE><EFILE href =" Material \ ef0001 \ Original \ HTML.doc "composedpagefile =" Material \ efile0002.pdf "type =" pdf "totalpage =" 3 "id =" ef0002 "><EFILE_INFO datatype =" Word2000 "> ... </ EFILE_INFO></EFILE></MATERIAL></EBINDER> In this example, only the material electronic document is stored. The generated electronic document is in a format that is not stored, which is a method frequently used when the construction of the generated electronic document is temporarily stopped and stored.
If you change the original electronic document in the above and want only the modified original electronic document,
== Extract and save only the electronic document at the location described in "Material \ ef0001 \ Original \ F_c01.ppt".

The three types of format have been described above. A specific example is shown in FIG.

In FIG. 19, reference numeral 1901 denotes Composed Win.
This is a state in which a generated electronic document has been created on the dow screen 505. If this state is stored as it is, in the document management system, a binder mark is attached to the upper right corner as indicated by 1902, indicating the form of the compound document. The document management system displays the thumbnail image of the generated electronic document.
The presence of the binder mark informs the user of its presence. When the electronic document is stored in the file management screen 1903 on the normal OS, the generated electronic document is stored in a configuration of a plurality of files and a plurality of folders as shown in FIG. For example, an XML document (E-Binder.xml in this example) describing this structure and a style sheet (CSS: Cascading Style Sheet or XS
L: Extensible Stylesheet Language) is a method of checking two types of files with a browser. Another method is to directly view the bundled generated electronic documents in the Bookbinding folder. In any case, the associated file group can be obtained.

Next, a process for adding annotation information to a generated electronic document will be described. The file format configuration for retaining the annotation information in the generated electronic document is as described with reference to FIGS. 28, 29, and 30. When the annotation information is added to the generated electronic document, the following two forms are used. Conceivable.

(A) Annotation information is newly added.

(B) Annotation information is added in a format to be added to existing annotation information.

In the case of (A), the XML description shown in FIG. 29 or the XML description shown in FIG.
The XML description shown in FIG. In this case, the file format of the annotation information may be any file format that can be understood by the system.

On the other hand, in the case of (B), first, the existing annotation information added to the material page unit electronic document constituting the generated electronic document and the annotation information added to the generated electronic document are stored in the same file. The format must be unified. Hereinafter, a process in a case where the annotation information is further added in a format to be added to the existing annotation information added to the material page unit electronic document constituting the generated electronic document will be described with reference to FIGS.
A description will be given using the flowchart of FIG. 1B and a specific example of the XML description example of the generated electronic document in FIGS.

FIGS. 31A and 31B are flowcharts showing a process for adding annotation information to a generated electronic document according to the present embodiment.

In step S3101, a page to which annotation information is to be added is selected from the generated electronic document. Here, as an example, first, a case is considered where annotation information is added to the second page of the generated electronic document. Step S
In step 3102, the page selected in step S3101 (2
Get the INDEX element in the PAGEINDEX element corresponding to (Page). In this case, it is the INDEX element 3201 in FIG.

Next, in step S3103, it is determined whether an INDEX element corresponding to the selected page exists. If it does not exist (NO in step S3103), the process advances to step S3104 to perform error processing. On the other hand, if it exists (YES in step S3103), the process advances to step S3105.

In step S3105, the idref of the INDEX element
= Value of efilepage = and the value of efilepage =
Store in DR and EFP. In this example, IDR = ef000
1, EFP = 2. In step S3106, an EFILE element whose id = value matches the IDR value is determined. In the case of FIG. 32, the EFILE element is an EFILE element 320
3, the EFILE element 3203 whose id = value matches the IDR value.

In step S3107, it is determined whether there is an EFILE element that matches the value of IDR. If it does not exist (NO in step S3107), the process advances to step S3108 to perform error processing. On the other hand, if it exists (YES in step S3107), the flow advances to step 3109.

In step S3109, ANN is added to the EFILE element.
Determine whether the OTATIONS element exists. If it does not exist (NO in step S3109), it means that the existing annotation information does not exist, and step S3110
To perform a new annotation creation process. on the other hand,
If it exists (YES in step S3109), the process advances to step S3111. In the case of FIG. 32, the EFILE element 320
Within 3, there is an ANNOTATIONS element 3205.

In step S3111, it is determined whether or not the value of page = of the ANNOTATION element in the ANNOTATIONS element is “all”. In the case of FIG. 32, the ANNOTATIONS element 3205
The value of page = of the ANNOTATION element 3206 is “all”.

If “all” is present in step 3111 (YES in step S3111), step S3
Proceeding to 116, the annotation information corresponding to the EFP value (number of pages) is extracted from the annotation information indicated by the value of href = of the ANNOTATION element. Here, although not explicitly shown, if there is no corresponding annotation information, error processing is performed.

On the other hand, in step S3111, "al
If l "does not exist (NO in step S3111), the process advances to step S3112. Here, after adding the annotation information to the second page of the generated electronic document, the annotation information is added to the first page of the generated electronic document shown in FIG. Consider the case of adding (INDEX element 3202 in Fig. 32) In this case, step S is performed on the INDEX element 3202 in Fig. 32.
The ANNOTATIONS element to be processed in 3109 is shown in FIG.
ANNOTATIONS element 3207, and the ANNOIAT inside it
Since the value of page = of the ION element is not "all", step S
The process advances from step 3111 to step S3112.

In step S3112, among the page = values of each ANNOTATION element in the ANNOTATIONS element, those that match the EFP value are determined. In FIG. 32, since the value of efilepage = of the INDEX element 3202 is “3”,
The value of FP becomes “3”. Therefore, of the two ANNOTATION elements 3208 and 3209 in the ANNOTATIONS element, page
The value of = matches the value of EFP because ANNOTATION element 3
209.

In step S3113, it is determined whether or not there is an ANNOTATION element that matches the EFP value among the page = values of each ANNOTATION element in the ANNOTATIONS element. If it does not exist (NO in step S3113), there is no existing annotation information, and the process advances to step S3114 to perform a new annotation creation process. On the other hand, if it exists (Y in step S3113)
ES), and it proceeds to step S3115.

In step S3115, the ANNOTATION element
Get the annotation information indicated by the value of href =.
In step S3117, the value of type = of the ANNOTATION element is obtained. In step S3118, it is determined whether the unified format used for the annotation information is the same as the format represented by the value of type =. If they are not the same, the process advances to step S3119 to perform a format conversion process for making the format of all the annotation information added to the generated electronic document the same. Then, step S312
Go to 0. On the other hand, if they are the same (step S3118)
Then, the process proceeds to step 3120.

In step S3120, an annotation creation process is performed. In step S 3121, the generated annotation information is compared with steps S 3115 and S 3
A superimposition process is performed with existing annotation information obtained in step S116 or converted in step S3119, and the combined information is stored. This means that the XML description of the annotation information as described above is added to the XML description of the generated electronic document to be added and stored.

FIG. 33 shows an example of the XML description of the generated electronic document to which the annotation information has been added by the above processing. This is an example in which an image file format called bmp is used as a unified format used for annotation information. Annotation information 3301 in FIG.
Are annotation information added to the first and second pages of the generated electronic document.

As described above, according to the present embodiment, one integrated electronic document (generated electronic document) is created from a plurality of different electronic documents (material electronic documents) to which annotation information is added, and the integrated electronic document is generated as the material electronic document. One electronic document is configured in a state where the relationship between the added annotation information and the newly added / further added annotation information to the integrated electronic document is tightly coupled. That is, it is possible to provide a single document structure that maintains the relationship between the annotation information added to the material electronic document and the annotation information added to the generated electronic document.

For example, when the annotation information is further added to the material electronic document to which the annotation information forming the generated electronic document is added, the file format of the annotation information added to the material electronic document to be composed and the generated electronic document By synthesizing the file information of the annotation information to be added to the same file format, the generated electronic document can be efficiently managed as the generated electronic document to which the annotation information of the unified file format is added.

Even if the material electronic document to which the annotation information making up the generated electronic document is added is changed, the annotation information can be reflected on the changed material electronic document. [Other Embodiments] FIG. 20 shows a configuration having a plurality of generated electronic documents, and FIG. 20A is a specific example. Reference numerals 2001 and 2002 denote Composed Window screens for working on the generated electronic document. FIG. 20B is a format block configuration example of the generated electronic document shown in FIG. 20A. In the present embodiment, a plurality of PageIndex units are configured. With this configuration, FIG.
As shown in FIG.
1 and 2002 are arranged, and a plurality of generated electronic documents can be created. Also, 2003 and 20 in FIG.
Reference numeral 04 denotes a configuration example that holds a plurality of generated electronic documents.
For example, a configuration is possible in which the cover can be changed so that a confidential matter can be separated into a document and a non-confidential document. Further, 2005 and 2006 in FIG. 20B are configuration examples in which annotation information is held in each of a plurality of generated electronic documents. This makes it possible to add different annotation information to each of the plurality of generated electronic documents. Reference numerals 3401 and 3402 in FIG. 34 are configuration examples in which a plurality of pieces of annotation information are held in one generated electronic document. For example, members of the project are notified of the changes using annotation information, and if the materials are to be shown outside, the annotation information is used to emphasize the points (such as circles). Can be used to represent it.

Further, in the format of the generated electronic document described in the above embodiment, it is not necessary to have an image which is a development document of the electronic document in unit of material page held in the EPAGE unit. In other words, another format can be configured as the format of the three finally generated electronic documents described in the embodiment. That is, (4) Including material electronic documents and generated electronic documents,
A format that does not include the expanded image of the material page unit electronic document in the unit. This forms a generated electronic document that has been converted into a predetermined file format in advance. This is a method of saving when a generated electronic document converted into a predetermined file format is created again when a change is made to the document. Since this storage format retains the relationship between the generated electronic document converted to the predetermined file format and the material electronic document, and does not have a developed image or a thumbnail image of the material page unit electronic document,
There is a feature that the total file size as a whole can be reduced.

The BOOKBINDING section of FIG.
01), the information of the material page unit electronic document (information indicating the page number of which material electronic document) is stored in PAGEINDE.
A thumbnail image of a material page unit electronic document is obtained from the material electronic document by using the X part, and held. Also, it holds the annotation information. This state is shown in FIG.
An excerpt of the XML description of B is as follows.

<EBINDER><MATERIAL files = "2><EFILE href =" Material \ ef0001 \ Original \ F_c01.ppt "type =" pdf "totalpage =" 2 "id =" ef0001 "><EFILE_INFO datatype =" PowerPoint2000 "> ... </ EFILE_INFO></EFILE><EFILE~> ... </ EFILE></MATERIAL><PAGEINDEX><INDEX page =" 1 "idref =" efile0002 "efilepage =" 3 "/><INDEX page =" 2 "idref =" efile0001 "efilepage =" 1 "/><INDEX page =" 3 "idref =" efile0002 "efilepage =" 2 "/></PAGEINDEX><BOOKBINDING href = "Bookbinding \ bind.tiff" type = "tiff"><BPAGE page = "1" thumbnail = "Bookbinding \ page1.png"/><BPAGE page = "2" thumbnail = "Bookbinding \ page2.png"/>< BPAGE page = "3" thumbnail = "Bookbinding \ page3.png"/></BOOKBINDING><ANNOTATIONS><ANNOTATION href = "Annotation \ annotation.tiff" type = "tiff" page = "all"/></ANNOTATIONS></EBINDER> where <EFILE ~> and <EPAGES> ~ </ EPAGES>
And the description of <EFILE ~>,
Please note that agefile = "Material \ efile0001.pdf is not described. <EPAGES> to </ EPAGES> are not described in the BOOKBINDING part to hold the thumbnail image of the electronic document in unit of material page. However, if redundancy is allowed, <EPAGES> to </ EPAGES> are prepared, and there is a description for holding the thumbnail image of the electronic document in unit of material page. You can also do composedpagefile = "
The reason why Material \ efile0001.pdf is not described is that a generated electronic document is created by using a material electronic document including a material page unit electronic document when it becomes necessary, which is a feature of this storage mode. Also in this case, it is possible to hold the annotation information added to the generated electronic document. If the annotation information is also present on the material electronic document side, the annotation information can be held in the same manner as when it is added to the generated electronic document. However, in the case of this storage mode, the feature is to reduce the total file size, and thus it is not necessary to have the annotation information for the material electronic document. As another storage format, there is a format in which a material electronic document itself is not stored, but only a file created from the material electronic document and divided into individual page units is stored. This can be applied to all cases where the material electronic document described above is stored, including how to hold the annotation information. Specifically, <EBINDER><MATERIAL files = "2><EFILE href =" Material \ ef0001 \ Original \ F_c01.ppt "nohref =" YES "type =" pdf "totalpage =" 2 "id =" ef0001 "><EFILE_INFO datatype = "PowerPoint2000"> ... </ EFILE_INFO><ANNOTATIONS><ANNOTATION href = "Material \ ef0001 \ Anotation \ an0001.tiff" type = "TIFF" type = "ALL"/></ANNOTATIONS><EPAGES><EPAGE page = "1" thumbnail = "Material \ ef0001 \ thumb1.bmp"/><EPAGE page = "2" thumbnail = "Material \ ef0001 \ thumb2.bmp"/></EPAGES>< / EFILE><EFILE href = "Material \ ef0001 \ Original \ HTML.doc" nohref = "YES" composedpagefile = "Material \ efile0002.pdf" type = "pdf" totalpage = "3" id = "ef0002"><EFILE_INFO datatype = "Word2000"> ... </ EFILE_INFO><EPAGES> ... </ EPAGES></EFILE></MATERIAL></EBINDER> In the <EFILE> part of this description , Nohref = "YE
The attribute "S" is added. If the nohref attribute is YES, it indicates that the material electronic document itself does not exist. That is, for example, href = "Material \ ef0001 \ Origin"
al \ F_c01.ppt ", but the file represented by href does not exist. In such a storage format, editing operations such as rearranging pages can be performed without having a source electronic document. In addition, since the annotation file is retained, it is also possible to edit the annotations.When the size of the material electronic document is large, when the material is not changed, when you want to perform the editing operation but do not want to attach the material, etc. The storage format up to now handles a plurality of files as shown in FIG. 4, but these may be combined into a compressed format.

FIG. 35 shows an information processing apparatus applicable to the document management system according to the embodiment of the present invention described above.

FIG. 35 is a block diagram showing the configuration of an information processing apparatus applicable to the document management system of the present invention.

In FIG. 35, a CPU 101 controls the entire information processing apparatus 1000 via a main bus 107, and also controls input devices 110 (for example, an image scanner, a storage device, and a network) connected outside the information processing apparatus 1000. Other information processing device connected via line, facsimile connected via telephone line, etc.)
Is controlled via an input I / F (interface) 104. Further, the output device 112 (for example, a printer, a monitor, another information processing device connected via a network line, a facsimile connected via a telephone line, etc.) connected to the outside of the information processing device 1000 is output to the output I. / F10
Control via 5. In addition, the CPU 101
/ F (keyboard interface) 107 according to an instruction input from an input unit (for example, a keyboard 112, a pointing device 113, or a pen 114).
A series of processing such as image input, image processing, color conversion processing, and image output control is executed. Further, a display unit 109 that displays image data input from the input device 110 and image data created using the keyboard 112, the pointing device 113, and the pen 114 is controlled via a video I / F (interface) 108. .

The ROM 102 stores various control programs for executing various controls of the CPU 101. RAM
The CPU 103 loads and executes an OS and other control programs including a control program for realizing the present invention by the CPU 101. In addition, it functions as various work areas used for executing the control program and a temporary save area. Further, image data input from the input device 110, the keyboard 112, the pointing device 1 and the like.
A VRAM (not shown) that temporarily holds image data created by using the pen 13 or the pen 114 is configured.

Even if the present invention is applied to a system including a plurality of devices (for example, a host computer, an interface device, a reader, a printer, etc.), a device including one device (for example, a copying machine, a facsimile machine) Etc.).

An object of the present invention is to provide a storage medium storing a program code of software for realizing the functions of the above-described embodiments to a system or an apparatus, and to provide a computer (or CPU)
And MPU) read and execute the program code stored in the storage medium.

In this case, the program code itself read from the storage medium realizes the function of the above-described embodiment, and the storage medium storing the program code constitutes the present invention.

As a storage medium for supplying the program code, for example, a floppy disk, hard disk, optical disk, magneto-optical disk, CD-ROM, CD
-R, a magnetic tape, a nonvolatile memory card, a ROM, or the like can be used.

When the computer executes the readout program code, not only the functions of the above-described embodiment are realized, but also the OS (Operating System) running on the computer based on the instruction of the program code. ) May perform some or all of the actual processing, and the processing may realize the functions of the above-described embodiments.

Further, after the program code read from the storage medium is written into a memory provided on a function expansion board inserted into the computer or a function expansion unit connected to the computer, based on the instructions of the program code, It goes without saying that the CPU included in the function expansion board or the function expansion unit performs part or all of the actual processing, and the processing realizes the functions of the above-described embodiments.

When the present invention is applied to the storage medium, the storage medium includes the above-described storage medium shown in FIGS. 6, 15, and 31A.
And the program code corresponding to the flowchart shown in FIG. 31B.

[0141]

As described above, according to the present invention,
One integrated electronic document is created from a plurality of different material electronic documents to which annotation information has been added, and the relationship between the annotation information added to the material electronic document and the newly added / added annotation information to the integrated electronic document Information processing apparatus and method capable of easily performing editing while maintaining the same, and a computer-readable memory.

[Brief description of the drawings]

FIG. 1 is a conceptual diagram of a document management system according to an embodiment.

FIG. 2A is a block diagram illustrating a format of a generated electronic document configured by an electronic binder builder according to the embodiment;

FIG. 2B is a diagram illustrating an example of an XML description of a generated electronic document configured by the electronic binder builder according to the embodiment;

FIG. 3 is a block diagram illustrating a format of a generated electronic document configured by an electronic binder builder according to the embodiment;

FIG. 4 shows an example of a folder and a file configuration of a generated electronic document according to the embodiment.

FIG. 5 is a diagram illustrating an example of an operation screen related to processing of the electronic binder builder according to the embodiment.

FIG. 6 is a flowchart illustrating a generation process of a generated electronic document according to the embodiment.

FIG. 7 is a diagram illustrating an operation example of the electronic binder builder of the embodiment.

FIG. 8 is a diagram illustrating an operation example of the electronic binder builder according to the embodiment.

FIG. 9 is a diagram showing an operation example of the electronic binder builder of the embodiment.

FIG. 10 is a diagram showing an operation example of the electronic binder builder of the embodiment.

FIG. 11 is a diagram illustrating an operation example of the electronic binder builder of the embodiment.

FIG. 12 is a diagram showing an operation example of the electronic binder builder of the embodiment.

FIG. 13 is a diagram illustrating an operation example of the electronic binder builder of the embodiment.

FIG. 14 is a diagram illustrating an operation example of the electronic binder builder of the embodiment.

FIG. 15 is a flowchart illustrating editing processing of a generated electronic document according to the present embodiment.

FIG. 16 is a diagram showing an operation example of the electronic binder builder of the embodiment.

FIG. 17 is a diagram illustrating an operation example of the electronic binder builder of the embodiment.

FIG. 18 is a diagram illustrating a correlation in rotation of a thumbnail image according to the present embodiment.

FIG. 19 is a diagram illustrating an operation example of the electronic binder builder of the embodiment.

FIG. 20A is a diagram showing an operation example of the electronic binder builder of the embodiment.

FIG. 20B is a format block configuration diagram of a generated electronic document configured by the electronic binder builder of the embodiment.

FIG. 21 is a diagram illustrating an example of an XML description when RDF is used as meta information of a generated electronic document configured by the electronic binder builder according to the embodiment.

FIG. 22 is a block diagram illustrating a format of a generated electronic document configured by the electronic binder builder according to the embodiment.

FIG. 23 is an XML of the generated electronic document of FIG.
It is a figure showing the example of description.

FIG. 24 is a diagram illustrating a method of retaining annotation information according to the present embodiment.

FIG. 25 is a configuration block diagram of a material electronic document to which annotation information configured by the electronic binder builder according to the embodiment is added.

FIG. 26 is a block diagram showing a format of a material electronic document to which annotation information configured by the electronic binder builder according to the embodiment is added.

FIG. 27 is a diagram illustrating the XML of the material electronic document in FIG.
It is a figure showing the example of description.

FIG. 28 is a configuration block diagram of a generated electronic document to which annotation information configured by the electronic binder builder of the present embodiment is added.

FIG. 29 is an XML diagram of the generated electronic document of FIG. 28 according to the present embodiment.
It is a figure showing the example of description.

30 is another X of the generated electronic document of FIG. 28 according to the present embodiment.
It is a figure showing the example of ML description.

FIG. 31A is a flowchart illustrating a process of adding annotation information to a generated electronic document according to the embodiment;

FIG. 31B is a flowchart illustrating processing for adding annotation information to a generated electronic document according to the present embodiment.

32 is a diagram illustrating an example of an XML description of a generated electronic document obtained by the processing of FIG. 31 according to the present embodiment.

FIG. 33 is a diagram illustrating an example of an XML description of a generated electronic document obtained by the processing of FIG. 31 according to the present embodiment.

FIG. 34 is a block diagram illustrating a format of a generated electronic document formed by an electronic binder builder.

FIG. 35 is a block diagram illustrating a configuration of an information processing apparatus applicable to the document management system of the present invention.

[Explanation of symbols]

 101 Material electronic document 102 Electronic binder builder 103 Generated electronic document

Claims (9)

[Claims] 1. An information processing apparatus for forming an integrated electronic document including a plurality of types of material electronic documents, comprising: holding means for holding the plurality of types of material electronic documents to which annotation information is added; Selecting means for selecting a desired material page unit electronic document from each material page unit electronic document of the plurality of types of material electronic documents held by the means, based on the material page unit electronic document selected by the selecting means An information processing apparatus comprising: an integrated electronic document including control information for controlling the addition of the annotation information. 2. The information processing apparatus according to claim 1, wherein the control information is set for the entire integrated electronic document or for each material page unit electronic document constituting the integrated electronic document. 3. The electronic document according to claim 1, wherein the constituent electronic unit forms the material electronic document to which the annotation information is added and the integrated electronic document to which the annotation information is added, which constitutes the integrated electronic document, as one electronic document. The information processing apparatus according to claim 1. 4. The method according to claim 1, wherein the configuration unit includes a first annotation information added to the material electronic document and a conversion unit configured to convert the second annotation information added to the integrated electronic document into a predetermined file format. The information processing apparatus according to claim 3, wherein 5. An information processing method for forming an integrated electronic document including a plurality of types of material electronic documents, comprising: a holding step of holding the plurality of types of material electronic documents to which annotation information has been added in a storage medium; A selection step of selecting a desired material page unit electronic document from each material page unit electronic document of each of the plurality of types of material electronic documents held in the storage medium in the holding step; and a material selected in the selection step A configuration step of configuring an integrated electronic document including control information for controlling the addition of the annotation information based on the page-based electronic document. 6. The information processing method according to claim 5, wherein the control information is set for the entire integrated electronic document or for each material page unit electronic document constituting the integrated electronic document. 7. The composition step is characterized in that the material electronic document to which the annotation information is added and which constitutes the integrated electronic document and the integrated electronic document to which the annotation information is added are formed as one electronic document. The information processing method according to claim 5, wherein 8. The method according to claim 1, wherein the configuration step includes a conversion step of converting the first annotation information added to the material electronic document and the second annotation information added to the integrated electronic document into a predetermined file format. The information processing method according to claim 7, wherein: 9. A computer-readable memory storing information processing program codes constituting an integrated electronic document composed of a plurality of types of material electronic documents, wherein the plurality of types of material electronic documents to which annotation information is added. And a desired material page unit electronic document from each material page unit electronic document of the plurality of types of material electronic documents held in the storage medium in the holding step. A program code of a selecting step; and a program code of a constituent step of configuring an integrated electronic document including control information for controlling addition of the annotation information based on the material page unit electronic document selected in the selecting step. A computer readable memory characterized by the following.