JP4325790B2 - Method and apparatus for reflecting data in database and program thereof - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a method for reflecting data in a database and a device for reflecting the correction contents of the data in the database.
[0002]
[Prior art]
Property magazines (used car magazines, used car data, housing data, etc.) that incorporate each property into one sub-group of several types of sub-groups, and arrange several sub-groups on one page. Database publishing has appeared as a method for publishing housing magazines).
[0003]
According to database publishing, since the property data frequently fluctuates due to the sale and purchase of properties and the number of properties is large, a database is used to manage the property data. In database publishing, property data to be published in a property magazine is extracted from the database, and this is expressed in XML (eXtensible Markup Language) electronic documents. How to arrange small groups, layout of items in each small group, and each XSLT electronic document called XSLT (eXtensible Stylesheet Language Transformation) style sheet is used to specify the property to be assigned to the small group, and XSL-FO (eXtensible Stylesheet Language-Formatting Object) electronic document is generated from the XML document and the XSLT document using an XSLT processor Then, DTP data is generated from the XSL-FO electronic document using the XSL-FO processor.
[0004]
In addition, there are the following as prior art documents related to the present invention.
[0005]
[Non-Patent Document 1]
Catalog "DBPublisher 1.0, DBPress 4.0", Issued by: Japan, Sold by: DTE A, Ltd., Developer: Lynx
[0006]
In addition, the applicant has filed the following application regarding the invention related to the present invention.
[0007]
Japanese Patent Application 2001-256378
Japanese Patent Application No. 2001-362811
Japanese Patent Application 2001-37763
Japanese Patent Application No. 2002-147964
Japanese Patent Application No. 2002-299080
Japanese Patent Application No. 2003-032466
[0008]
[Problems to be solved by the invention]
By the way, even when database publishing is performed, calibration is performed on the DTP immediately before printing. In proofreading, as in normal publishing, correction of typographical errors is performed directly on the DTP data, not on the database. Therefore, in order to reflect the correction contents in the database, it is necessary to manually correct the database according to the correction contents.
[0009]
For example, with the DBPublisher 1.0 and DBPress 4.0 write-back functions of Links Inc., the correction contents are not automatically reflected directly in the database, but the correction contents for items for which bidirectional attributes of all records are set Only the described CSV format file is generated, and the user has to correct the database based on the CSV format file.
[0010]
In database publishing, when extracting property data to be published in a property magazine from the database, instead of extracting all the columns of the database table, only the necessary columns are extracted and Try to print. However, once it is determined that there is no need to print the contents of the column, it is still necessary to print during the DTP. In such a case, the data is individually displayed on the DTP. Add. When such data is added, the contents of the data are not always the same as the contents stored in the database, and are generally different. In some cases, the content of the data added on the DTP is newer than the content stored in the database, and the former content is desired to be updated with the latter content. However, conventionally, in order to do this, the database has to be operated independently of the addition on the DTP.
[0011]
Furthermore, there is a case where a small group is added on the DTP and a value is set for each item of the small group, but conventionally, there is no method for automatically reflecting the value set for each added item in the database.
[0012]
Furthermore, there is a case where all sub-sets of the page are deleted by deleting the sub-sets individually on the DTP or deleting the page. Conventionally, a record in which data is assigned to the deleted sub-set is stored in the database. There was no way to automatically delete from the table.
[0013]
The present invention has been made in view of the above problems, and an object of the present invention is to provide a data reflection method and apparatus for reflecting data in a database which can reflect the correction contents of the data almost automatically. And
[0014]
In addition, the present invention does not reflect all the data describing the correction contents in the database as they are, but efficiently checks the correction contents and reflects them in the database to maintain a highly reliable database. It is an object of the present invention to provide a method and apparatus for reflecting data in a database.
[0015]
It is another object of the present invention to provide a data reflection method and apparatus for reflecting data added to the DTP automatically in the database.
[0016]
Another object of the present invention is to provide a database reflection method and apparatus capable of automatically reflecting values set in each item of a small set added on DTP in the database. .
[0017]
It is another object of the present invention to provide a method of reflecting data in a database that enables a record in which data has been assigned to a deleted set to be automatically deleted from a database table.
[0018]
[Means for Solving the Problems]
According to the first aspect of the present invention, rendering that generates DTP data based on an electronic document for rendering apparatus In addition, for at least one page, one or more fo: block-container tags representing a small set are described in the fo: page-sequence tag representing the page of the DTP data, and at least the fo representing the small set. XSL- having one or more fo: block-container tags representing a text box or image box in the block-container tag, and having a character style hierarchy tag in the fo: block-container tag representing the text box An FO (eXtensible Stylesheet Language-Formatting Object) electronic document, which includes a fo: block-container tag representing the sub-set Attribute data Of a fo: block-container tag that has a small group ID and a property ID and represents the text box Attribute data As an array of paths of database items that have been inserted and an array of item names of database items that have been injected, Attribute data A virtual 1 representing a small set in the at least one page on the basis of having information indicating the path of the database item, the item name of the database item, the flow order of the database item, and the presence / absence of the replacement processing of the database item Alternatively, DTP data that configures a plurality of areas and further configures at least a text box or an image box in each subgroup for the at least one page. A hierarchy of text boxes and a hierarchy of image boxes below the sub-set hierarchy, at least a character-style hierarchy below the text box, and the sub-set hierarchy includes at least the sub-set ID and The property ID is described, and at least the data that has been poured into the hierarchy of the text box. An array of base item paths, an array of database item names that have been poured in, an ordering sequence of database items that have been merged, and an array of update dates and times of database items that have been merged are described. Information indicating the path of the database item, the item name of the database item, the flow order of the database item, and the presence / absence of the replacement process of the database item is described, and at least the database item that has been flowed in the hierarchy of the image box Generating an array in which an array of paths, an array of item names of the database items that have been inserted, an array of an order of the database items that have been inserted, and an array of update dates and times of the database items that have been inserted are generated rendering apparatus In this case, the small group ID and the property ID are generated based on the small group ID and the property ID of the XSL-FO electronic document, respectively, and written into the small group hierarchy of the DTP data. means And an array of paths of the database items that have been inserted, an array of names of the database items that have been injected, an array of sequences of the database items that have been injected, and an array of update dates and times of the database items that have been injected, respectively. The XSL-FO electronic document is generated on the basis of an array of paths of the database items that have been inserted, an array of database item names that have been injected, an order of the database items that have been injected, and a predetermined value, and the DTP data Create a text box to write to the text box hierarchy means And the path of the database item, the item name of the database item, the flow order of the database item, and the information indicating the presence or absence of the replacement processing of the database item, respectively, the path of the database item of the XSL-FO electronic document, A character style application that is generated based on information representing the item name of the database item, the flow order of the database item, and the presence / absence of replacement processing of the database item, and written to the character style hierarchy of the DTP data means And an array of paths of the flowed database items, an array of item names of the flowed database items, a flow order of the flowed database items, and an array of update dates and times of the flowed database items, Each of the XSL-FO electronic document is generated based on an array of paths of the database items that have been inserted, an array of item names of the database items that have been inserted, a sequence of the database items that have been inserted, and a predetermined value. Create an image box to write into the DTP data image box means And rendering characterized by comprising apparatus Is provided.
[0019]
According to a second aspect of the present invention, there is provided a rendering method for generating DTP data on the basis of an electronic document for rendering in a computer, and for at least one page, fo: page− representing a page of the DTP data. One or more fo: block-container tags representing a sub-set are described in the sequence tag, and at least a fo: block-container tag representing a text box or an image box is included in the fo: block-container tag representing the sub-set. An XSL-FO (eXtensible Stylesheet Language-Formatting Object) electronic document having one or more described fo: block-container tags representing a text box and having a tag of a character style hierarchy, representing the sub-set The attribute data of the o: block-container tag has a small group ID and the property ID, and the attribute data of the fo: block-container tag representing the text box includes an array of paths of the database items that have been injected and the database that has been injected As an attribute data of the tag of the character style hierarchy, information indicating the path of the database item, the item name of the database item, the flow order of the database item, and the presence / absence of the replacement process of the database item is included. Based on what is included, one or more virtual regions representing a small group are configured in the at least one page, and at least a text box or an image box is configured in each small group for the at least one page. DTP data, hierarchy In general terms, it has a small hierarchy below the page hierarchy, a text box hierarchy and an image box hierarchy below the subset hierarchy, and at least a character style hierarchy below the text box. At least the small group ID and the property ID are described in the small group hierarchy, and at least the database item path array, the database item name array inserted, and the text box hierarchy. The sequence of the inserted database items and the update date / time sequence of the inserted database items are described, and at least the path of the database item, the item name of the database item, and the input of the database item are included in the character style hierarchy. Describes information indicating the order and presence / absence of replacement processing of the database item The hierarchy of the image boxes includes at least an array of paths of the inserted database items, an array of item names of the input database items, an arrangement of the order of input of the input database items, and an input of the input database items. In the rendering method, characterized in that an array in which an update date / time array is described is generated, the small group ID and the property ID are respectively converted into the small group ID and the property of the XSL-FO electronic document by a small group creation unit. A pair creation step that is generated based on the ID and is written to the hierarchy of the subset of the DTP data, and a text box creation means, a path array of the database item that has been fed in, an array of the database item name that has been fed in, and the casting The sequence of the flow order of the selected database items and The update date / time array of the inserted database item is respectively the array of the path of the input database item of the XSL-FO electronic document, the array of the input database item name, the array of the input database item A text box creation step that is generated on the basis of the flow order and a predetermined value and is written in the text box hierarchy of the DTP data, and a character style applying means, by the path of the database item, the item name of the database item, the database item Information indicating the flow order and the presence / absence of replacement processing of the database item are respectively the path of the database item of the XSL-FO electronic document, the item name of the database item, the flow order of the database item, and the replacement of the database item. Processing available A character style applying step that is generated on the basis of information indicating nothing and is written in the character style hierarchy of the DTP data, and an array of paths of the database items that have been fed in by the image box creation means, An array of item names, an array of the flow order of the flowed database items, and an array of update dates and times of the flowed database items, respectively, an array of paths of the flowed database items of the XSL-FO electronic document, An image box creating step that is generated on the basis of an array of item names of the database items that have been inserted, a flow order of the database items that have been poured in, and a predetermined value, and that is written into an image box of the DTP data. Program to execute the rendering method It is offered .
[0033]
According to a fourth aspect of the present invention, there is provided a data structure generation step for generating a data structure in which a value of an item changed on the DTP and a position of the item in the database can be associated with each other. An item value changing step for accepting a change in value, a red character data generating step for generating red data for the value of the item changed on the DTP and the position, based on the data structure, and based on the red data And a reflecting step of reflecting the value of the changed item in the position of the database. A method of reflecting data in the database is provided.
[0034]
In the method for reflecting data in a database according to the fourth aspect of the present invention, a data correction step is provided between the deficit data generation step and the reflection step, and the data correction step is reflected in the position as it is. The value of the item that cannot be corrected may be corrected to a value that can be reflected in the position, and the correction step may reflect the corrected value in the position.
[0035]
According to the fifth aspect of the present invention, a deficit data generation step for generating data on the names and values of items added on the DTP, and a database table corresponding to the names of the items included in the deficit data There is provided a method for reflecting data in a database, comprising: a column specifying step for specifying a column of the data; and a reflecting step for reflecting the value of the item included in the deficient data in the specified column. The
[0036]
In the method of reflecting data in a database according to the fifth aspect of the present invention, the column specifying step may be performed by checking a column name of the database table that matches the name of the item.
[0037]
In the data reflection method according to the fifth aspect of the present invention, the column specifying step may be performed by allowing a user to select a column name of the database table corresponding to the item name. Good.
[0038]
In the method of reflecting data to a database according to the fifth aspect of the present invention, a data correction step is provided between the column specifying step and the reflecting step, and the data correcting step is reflected on the specified column as it is. The value of the item that cannot be changed is corrected to a value that can be reflected in the specified column, and the reflection step may reflect the corrected value in the specified column.
[0039]
According to the sixth aspect of the present invention, the deficit data for generating the deficit data on the value of each item of the small set added on the DTP and the information indicating which column of the database table each item corresponds to. Generating step, record information input step for inputting record information indicating which record of the table corresponds to the subgroup added on the DTP, and based on the deficit data and the record information on the DTP And a first reflecting step of reflecting the value of each item of the sub-set added in step 1 to the column indicated by the red data of the record indicated by the record information of the table. A reflection method is provided.
[0040]
According to a sixth aspect of the present invention, a method for reflecting data in a database adds a record to the table if the record information is not obtained, and adds a sub-set added on the DTP based on the deficit data. The method may further include a second reflecting step of reflecting the value of each item in the column indicated by the red data of the added record.
[0041]
According to the seventh aspect of the present invention, on the basis of the deficit data generation step of generating deficit data for the information specifying the record in which the data has been assigned to the subgroup deleted on the DTP, and the deficit data, And a deletion step of deleting the record from the table. A method of reflecting the data in the database is provided.
[0042]
According to a seventh aspect of the present invention, there is provided a method for reflecting data in a database, wherein a deletion by inputting a confirmation by a user as to whether or not to delete the specified record is performed between the deficit data generation step and the deletion step. There may be a confirmation step, and in the deletion step, only the record confirmed to be deleted in the deletion confirmation step may be deleted.
[0043]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
[0044]
[Embodiment 1]
First, referring to FIG. 1, the data reflection apparatus according to the first embodiment is roughly divided into a DTP software 103 and a deficient data return tool 113. The DTP software 103 includes a rendering unit 105 corresponding to an XSL-FO processor, a data correction unit 107, and a red data writing unit 109. The deficit data return tool 113 includes a deficit data import unit 115, a data confirmation / correction unit 117, and a reflection unit 119. The DTP software 103 is a computer program as the name indicates, and this function is realized when the computer reads and executes the DTP software 103. The deficit data return tool 113 can also be realized by a computer reading and executing a computer program for causing the computer to function as the deficit data return tool 113.
[0045]
The rendering unit 105 displays a page according to the contents of the allocated XSL-FO electronic document 101. The data correction unit 107 corrects data according to a user operation. The red data writing unit 109 writes the red data as the red data XML electronic document 111. The red data import unit 115 imports the red data XML electronic document 111. The data confirmation / correction unit 117 confirms and further corrects the red data. The reflection unit 119 updates the contents of the property database 121 using the red data.
[0046]
Next, the operation of the DTP software 103 will be described.
[0047]
The XSL-FO electronic document 101 has data necessary for reflecting the deficit data in the property database 121 in addition to data for performing normal DTP.
[0048]
The rendering unit 105 performs rendering based on the XSL-FO electronic document 101 in consideration of red data reflection. Before describing such rendering, rendering performed based on an XSL-FO electronic document that does not take into account deficit data reflection will be described. This rendering is not performed for pages such as advertisements inserted between pages describing property data.
[0049]
FIGS. 2 and 3 show examples of allocated XSL-FO electronic documents that do not take into account red data reflection. 2 and 3, a small group is provided in the lower layer of the page, and an image box and a text box are provided in the lower layer of the small group. In the case of a conventional XSL-FO electronic document, an image box and a text box are directly provided in the lower layer of the page. Therefore, according to the present invention, a small set is provided between them.
[0050]
In a portion denoted by reference numeral 401, two layout masters (layout_master_1, layout_master_2) are described. A part indicated by reference numeral 403 describes a page. A portion indicated by reference numeral 405 describes a small set. In a portion indicated by reference numeral 407, a text box is described. In a portion indicated by reference numeral 409, an image box is described.
[0051]
FIG. 4 shows a layout of a DTP document created based on an XSL-FO electronic document according to the present invention. A frame indicated by a broken line is a small set, and an image box and a text box are arranged therein. Since the small group is a virtual layer, it is neither drawn nor printed. Paragraph styles and character styles are applied to the text box characters. Here, a paragraph is a range from one line break to the next line break. A paragraph style is a style applied to characters in the corresponding paragraph. Examples of the paragraph style include a font type and a character size. The character style is a style applied to a predetermined range of characters in a paragraph, and takes precedence over the paragraph style. As the character style, there are, for example, a font type, a character size, and the like as in the paragraph style.
[0052]
FIG. 5 shows the structure of a DTP document in the form of an object class diagram. There are one or more page hierarchies below the DTP document hierarchy, zero or more sub-hierarchies below the page hierarchy, and zero or more text box hierarchies and zero below the sub-hierarchy hierarchy. There are the above image box hierarchies, and there are 0 or 1 character data hierarchy, 0 or more paragraph style hierarchies and 0 or more character style hierarchies below the text box hierarchy. Below the hierarchy is a hierarchy of zero or one image.
[0053]
The page hierarchy describes the page size, etc., the small group hierarchy describes the coordinates and size of the small group, the text box hierarchy describes the text box coordinates and size, etc., and the paragraph style hierarchy Describes the font type, character size, etc., the character style layer describes the font type, character size, etc., and the image box layer describes the image box coordinates, size, etc. In the hierarchy, an image file name, an image arrangement method, enlargement / reduction, and the like are described.
[0054]
Next, with reference to FIGS. 6 and 7, rendering based on an XSL-FO electronic document that does not take into account deficit data reflection will be described.
[0055]
First, referring to FIG. 6, the allocated XSL-FO electronic document is read (step S411). Next, the process for each page (steps S415 to S433) is repeated (step S413) until the fo: page-sequence tag is eliminated. In step S413, the attribute data of the fo: page-sequence tag in the XSL-FO electronic document is read. In step S415, a page is created based on the XSL-FO electronic document. Next, it is determined whether or not the fo: block-container tag representing a small group is in the first hierarchy. If so, the processing for each small group (steps S419 to S433) is repeated (step S417). . In step S417, attribute data of a fo: block-container tag representing a small set in the XSL-FO electronic document is read. In step S419, a small set is created based on the XSL-FO electronic document. Next, the processing for each box (steps S423 to S433) is repeated until there is no fo: block-container tag representing the box (step S421). In step S421, the attribute data of the fo: block-container tag in the XSL-FO electronic document is read. In the fo: block-container tag representing a text box, id = “T *” is described as an attribute, and in the fo: block-container tag representing an image box, id = “G *” is described as an attribute. Therefore, by checking whether or not the first character of id is T or G, it can be determined whether fo: block-container is a fo: block-container representing a box. In step S423, it is determined whether or not the current box is a text box. If the determination result of step S423 is affirmative, the process proceeds to step S425; otherwise, the process proceeds to step S429. In step S429, it is determined whether or not the current box is an image box. If the determination result of step S429 is affirmative, the process proceeds to step S431.
[0056]
In step S425, a text box is created based on the XSL-FO electronic document. Next, character data to be stored in the text box is created based on the XSL-FO electronic document (step S427).
[0057]
In step S431, an image box is created based on the XSL-FO electronic document. Next, the image is linked to the image box based on the XSL-FO electronic document (step S433).
[0058]
Next, details of the character data creation step (step S427) will be described with reference to FIG. First, the process for each paragraph style (steps S437 to S443) is repeated (step S435) until the fo: block tag disappears. In step S435, the attribute data of the fo: block tag in the XSL-FO electronic document is read.
[0059]
Next, in step S437, the paragraph style information read in step S435 and information about the range to which the paragraph style is applied are temporarily stored in the memory. Next, the processing for each character style (steps S441 to S443) is repeated (step S439) until there is no character style. In step S439, the attribute data of the character style tag (specifically, fo: inline tag) in the XSL-FO electronic document is read. In step S441, the character style information read in step S439 and information about the range to which the character style information is applied are temporarily stored in the memory. Next, the character data read in step S439 is temporarily stored in the memory (step S443).
[0060]
If the loop of steps S435 and S439 is exited, the character data temporarily stored in the memory in step S443 is poured into the DTP data (step S445). Accordingly, in step S445, all character data included in the text box is poured into the DTP data. Next, the paragraph style is applied to the character data in accordance with the paragraph style information temporarily stored in the memory in step S437 and the information about the range to which the paragraph style information is applied (step S447). Here, applying a paragraph style corresponds to storing paragraph style information in DTP data. Next, the character style is applied to the character data according to the character style information temporarily stored in the memory in step S441 and the information about the range to which the character style information is applied (step S449). Therefore, the character style has priority over the paragraph style for characters to which the character style is applied. Here, applying a character style corresponds to storing character style information in DTP data.
[0061]
A plurality of items of property data (for example, “vehicle name” and “color”) can be inserted into one text box, and one character style corresponds to each item. Such a method is used.
[0062]
8 and 9 show an example of the allocated XSL-FO electronic document 101 in consideration of the reflection of red data. This is obtained by adding an item for reflecting red data to the allocated XSL-FO electronic document which does not consider the reflection of red data shown in FIGS. Therefore, the added items are underlined and described below.
[0063]
“Id =“ K1 ”” denoted by reference numeral 141 and “bkn_id =“ 3 ”” denoted by reference numeral 140 are added to the small set of tags. “Id =“ K1 ”” denoted by reference numeral 141 is a small group ID, and “bkn_id =“ 3 ”” denoted by reference numeral 140 is a property ID. The small group ID is also described in the assigned XSL-FO document that does not consider the reflection of red data.
[0064]
The tag of the hierarchy of the text box includes “set_item =" item [@ name_asc = "BKN_NAME"], item [@ name_asc = "COLOR"] "" indicated by reference numeral 142 and "set_item_jp =" property name, "indicated by reference numeral 143. A color "" has been added. “Set_item =“ item [@ name_asc = ”BKN_NAME”], item [@ name_asc = “COLOR”] ”denoted by reference numeral 142 is an array of the paths of the database items that have been introduced, and“ set_item_jp = ”denoted by reference numeral 143 Property name, color "" is an array of database item names that have been inserted. The “arrangement of the flow-in order of database items” 145 is represented by the order of the item names in the “arrangement of the field names of the flow-in database items” 143.
[0065]
The tag of the character style hierarchy (character style tag, specifically “fo: inline” tag) includes “item_jp =“ object name ”” denoted by reference numeral 151 and “item =“ item [”denoted by reference numeral 149. @ name_asc = 'BKN_NAME] "," item_seq = "1""indicated by reference numeral 153, and" isReplaced = "n""indicated by reference numeral 155 are added. “Item_jp =“ property name ”” indicated by reference numeral 151 is the item name of the database item, and “item =“ item [@ name_asc = ”BKN_NAME”] ”indicated by reference numeral 149 is the path of the database item, and reference numeral 153 “Item_seq =“ 1 ”” indicates the flow-in order of database items, and “isReplaced =“ n ”” indicated by reference numeral 155 indicates whether or not the database item is replaced.
[0066]
The tags of other character style layers include "item_jp =" color "" denoted by reference numeral 151, "item =" item [@ name_asc = "COLOR"] "" denoted by reference numeral 149, and "item_seq =" denoted by reference numeral 153. “2” ”and“ isReplaced = “n” ”indicated by reference numeral 155 are added. “Item_jp =“ color ”” indicated by reference numeral 151 is the item name of the database item, and “item =“ item [@ name_asc = ”COLOR”] ”indicated by reference numeral 149 is the path of the database item. “Item_seq =“ 2 ”” shown is a flow order of database items, and “isReplaced =“ n ”” indicated by reference numeral 155 is the presence / absence of a database item replacement process.
[0067]
The added items shown in the above three paragraphs are not in the standard specifications of XSL-FO, but are uniquely expanded by the present invention.
[0068]
The same applies to the added items underlined.
[0069]
FIG. 10 shows the structure of the DTP document generated by the rendering unit 105 from the XSL-FO electronic document 101 in the form of an object class diagram. There are one or more page hierarchies 131 below the DTP document hierarchy 130, zero or more small hierarchies 132 below the page hierarchies 131, and zero or more text boxes below the small hierarchies 132. And a hierarchy 137 of zero or more image boxes, a hierarchy 134 of zero or one character data, a hierarchy 135 of zero or more paragraph styles, and zero or more hierarchies below the hierarchy 133 of text boxes. There is a character style hierarchy 136, and zero or one image hierarchy 138 below the image box hierarchy 137.
[0070]
The page hierarchy describes the page size, etc., the small group hierarchy describes the coordinates and size of the small group, the text box hierarchy describes the text box coordinates and size, etc., and the paragraph style hierarchy Describes the font type, character size, etc., the character style layer describes the font type, character size, etc., and the image box layer describes the image box coordinates, size, etc. In the hierarchy, an image file name, an image arrangement method, enlargement / reduction, and the like are described. In addition, in the box hierarchies 133 and 137, an “arrangement of the flowed-in database item flow order” 145 is described, and in the character style hierarchies 136 “the flow-in order of database items” 153 is written.
[0071]
Furthermore, as items necessary for reflecting the deficit data, the subgroup hierarchy 132 includes “update date and time (latest update date and time of boxes in the subgroup)” 139, “property ID” 140, and “subgroup ID” 141. In the described hierarchy of boxes 133 and 137, an “arranged database item path (XPATH in XML document)” 142, an “arranged database item item name” 143, an “introduced database” An “arrangement of the flow order of items” 145 and an “arrangement of update date and time of the flowed-in database items” 147 are described. In the character style hierarchy 136, “database item path” 149, “database item item name” 151, “database item flow order” 153, and “whether or not database item replacement processing is performed” 155 are described. The initial value of the update date / time is 0:00:00, 0: 0: 0, and if the data is updated, the update date / time becomes the date / time of the update. “There is a database item replacement process” means that the database item is not inserted into the sheet as it is, but the database item that has been replaced based on the database item is inserted into the sheet. The replacement process is, for example, a process of replacing the value of the item “vehicle inspection date” recorded as “14.3” in the database with “March 2002”, and recorded as “white” in the database. For example, processing for replacing the value of the item “color” with an image file of an icon representing white named “white.gif”.
[0072]
Next, with reference to FIGS. 11 and 12, rendering based on the XSL-FO electronic document 101 in consideration of reflection of red data performed by the rendering unit 105 will be described.
[0073]
First, referring to FIG. 11, the allocated XSL-FO electronic document 101 is read (step S181). Next, the processing for each page (steps S185 to S207) is repeated (step S183) until the fo: page-sequence tag is eliminated. In step S183, the attribute data of the fo: page-sequence tag in the XSL-FO electronic document 101 is read. In step S185, a page is created based on the XSL-FO electronic document 101. Next, the processing for each small group (steps S189 to S207) is repeated (step S187) until the fo: block-container tag for the small group disappears. In step S187, the attribute data of the fo: block-container tag for the small set in the XSL-FO electronic document 101 is read. In step S189, a small set is created based on the XSL-FO electronic document 101. Next, the processing for each box (steps S193 to S207) is repeated (step S191) until there is no fo: block-container tag for the box. In step S191, the attribute data of the fo: block-container tag for the box in the XSL-FO electronic document 101 is read. In step S193, it is determined whether or not the current box is a text box. If the determination result of step S193 is affirmative, the process proceeds to step S195. Otherwise, the process proceeds to step S201. In step S201, it is determined whether or not the current box is an image box. If the determination result of step S201 is affirmative, the process proceeds to step S203.
[0074]
In step S195, a text box is created based on the XSL-FO electronic document 101. Next, assuming that the update date and time is 0, 0, 0, 0: 0: 0, box 133 "array of path of database items that have been poured" 142, "array of item names of database items that have been fed" 143 "The arrangement of the flow-in sequence of the database items" 145 and "The array of the update date and time of the flow-in database items" 147 are stored in the DTP data (step S197). Next, character data to be stored in the text box is created based on the XSL-FO electronic document 101 (step S199).
[0075]
In step S203, an image box is created based on the XSL-FO electronic document 101. Next, in the same manner as in step S197, the update date and time is set to 0 year 0 month 0, 0 hour 0 minute 0 second. The "arrangement of item names" 143, the "arrangement of the flow-in sequence of database items" 145, and the "arrangement of the update date / time of the flow-in database items" 147 are stored in the DTP data (step S205). Next, an image is linked to the image box based on the XSL-FO electronic document 101 (step S207).
[0076]
Next, details of the character data creation step (step S199) will be described with reference to FIG. First, the process for each paragraph style (steps S211 to S217) is repeated (step S209) until the fo: block tag disappears. In step S209, the attribute data of the fo: block tag in the XSL-FO electronic document 101 is read.
[0077]
Next, the paragraph style information read in step S209 and the information about the range to which the paragraph style is applied are temporarily stored in the memory (step S211). Next, the processing for each character style (steps S215 to S217) is repeated (step S213) until there is no character style (specifically, fo: inline tag). In step S213, the attribute data of the fo: inline tag in the XSL-FO electronic document 101 is read. In step S215, the character style information read in step S213 and information about the range to which the character style information is applied are temporarily stored in the memory. This character style information includes “database item path” 149, “database item item name” 151, “database item flow order” 153, and “database item replacement process presence / absence” 155 of the character style 136. . Next, the character data read in step S213 is temporarily stored in the memory (step S217).
[0078]
If the loop of steps S209 and S213 is exited, the character data temporarily stored in the memory in step S217 is poured into the DTP data (step S219). Accordingly, in step S219, all character data included in the text box is poured into the DTP data. Next, the paragraph style is applied to the character data in accordance with the paragraph style information temporarily stored in the memory in step S211 and information about the range to which the paragraph style information is applied (step S221). Here, applying a paragraph style corresponds to storing paragraph style information in DTP data. Next, the character style is applied to the character data according to the character style information temporarily stored in the memory in step S215 and the information about the range to which the character style information is applied (step S223). Therefore, the character style has priority over the paragraph style for characters to which the character style is applied. Here, applying a character style corresponds to storing character style information in DTP data. Accordingly, in step S223, “database item path” 149, “database item item name” 151, “database item flow order” 153, and “whether or not database item replacement processing is performed” in the character style 136 (see FIG. 10). 155 is stored in the DTP data.
[0079]
A plurality of items of property data (for example, “vehicle name” and “color”) can be inserted into one text box, and one character style corresponds to each item. Such a method is used.
[0080]
In this way, in step S197 or step S205, in the boxes 133 and 137, the "array of database item paths to be inserted" 142, the "array of item names of the database items that have been injected" 143, and the "database items that have been injected" ”And“ update date / time array of database items that have been inserted ”147 are stored in the DTP data as box attributes. In step S223,“ database item path ”149 and“ database item item name ”are stored. 151, “Placement order of database items” 153, and “Presence / absence of database item replacement process” 155 are stored in the DTP data as character styles.
[0081]
In the example of the data structure shown in FIG. 13, “item [@ name_asc =” BKN_NAME ”]” and “item [@name_asc” are arranged as the “array of the paths of the database items that have been inserted” 142 as shown in the frame of reference numeral 161. “COLOR”] is “arrangement of item names of database items that have been poured in” 143, “property name” and “color” are “arrangement of the order of casting of database items that have been poured in” 145 are “1” and “2” is stored in the DTP data as “array of update date and time of inserted database items” 143 and two “0th 0th, 0: 0: 0”. As for the “property name”, “item [@ name_asc =” BKN_NAME ”]” is set as “database item path” 149 and “item name of database item” 151 is “ “Property name” is stored in the DTP data as “1” as “database item flow order” 153 and “none” as “whether or not database item replacement processing is performed” 155. Similarly, with respect to “color”, “item [@ name_asc =” COLOR ”] as“ database item path ”149 and“ item name of database item ”151 as“ database item path ”149, as shown in the frame of reference numeral 165. “Color” is stored in the DTP data “2” as “database item flow order” 153 and “none” as “whether or not database item replacement processing is performed” 155. “Database item path” 149, “Database item item name” 151, “Database item flow order” 153, and “Presence / absence of database item replacement process” 155 include item values (data to be drawn or printed). Associated. Therefore, when the item value is corrected to become red data, the “database item path” 149, the “database item item name” 151, the “database item flow order” 153, and the “database item replacement process” Presence / absence 155 is associated with the deficit data.
[0082]
Next, the operation of the data correction unit 107 will be described.
[0083]
The data correction unit 107 accepts correction by the user of item values included in the DTP data. In the case of character data, direct correction on the DTP screen as shown in FIG. 14 is accepted, and correction on the data correction screen as shown in FIG. 15 called from the DTP screen is also accepted. Any character data corrected by any method is reflected in the DTP data, the DTP screen, and the data correction screen. In the case of image data, correction on a dialog screen (not shown) displayed when image data is selected on the DTP screen as shown in FIG. 16 is accepted. In the DTP screen shown in FIG. 16, reference numeral 231 indicates image data inserted in the image box, and reference numeral 233 indicates image data inserted inline in the character box. The image data inserted inline in the character box is obtained by replacing the item value in the character box. FIG. 17 shows a screen for confirming image data inserted in the image box, and FIG. 18 shows a screen for confirming image data inserted inline in the character box. The corrected image data is reflected on the DTP data, the DTP screen, and the screen as shown in FIG.
[0084]
FIG. 19 is a flowchart showing the operation of the data correction unit 107. Referring to FIG. 19, first, when data correction is received by the above-described method, the correction is reflected in the DTP data (step S241), and the “update date / time of the poured database item” of the box including the corrected item is reflected. The value of the element corresponding to the modified item in the “array” is updated to the current date and time (step S243). Next, the “update date and time (the latest update date and time of the box in the set)” of the small set including the corrected item is updated to the current date and time (step S245).
[0085]
Next, the operation of the red data writing unit 109 will be described. FIG. 20 is a flowchart showing the operation of the red data writing unit 109. Referring to FIG. 20, first, the DTP data created by the rendering unit 105 and modified by the data modification unit 107 is scanned (step S247). Next, the processing for each page (steps S251 to S265) is repeated until there are no more pages (step S249). In step S251, the page is scanned. Next, the process for each small group of the current page (steps S255 to S265) is repeated (step S253) until there are no small groups. In step S255, it is determined whether or not the update date / time provided in the current small group is greater than 0:00:00, 0: 0: 0. If the determination result in step S255 is negative, there is no red data in the current small set, and the process for the current small set is terminated.
[0086]
If the determination result in step S255 is affirmative, since there is red data in the current small set, first, the inside of the small set is scanned (step S257). Next, the processing for each small box box (steps S261 to S265) is repeated (step S259) until there are no more boxes. In step S261, the process for each casting item (steps S263 to S265) is repeated until there is no casting item information. In step S263, it is determined whether or not the element corresponding to the current flow item in the “update date / time array of DB items poured in” box is greater than 0:00:00, 0: 0: 0. If the determination result in step S263 is affirmative, the red data for the current flow item is written in the red data XML electronic document 111 (step S265). If the determination result of step S263 is negative, the process for the current flow item is terminated.
[0087]
FIG. 21 shows the structure of the red data XML electronic document 111 generated by the red data writing unit 109. The red data XML document 111 has four layers of red data, pages, properties, and items. In the hierarchy of red data, “output date and time” is described. A “page number” is described in the page hierarchy. In the property hierarchy, “small group number”, “property ID”, and “correction classification” are described. The “correction classification” can take values of “new”, “deletion”, or “correction”, but only “correction” is handled in the first embodiment. “New” corresponds to the addition of a small set, and “delete” corresponds to the deletion of a small set. In the item hierarchy, “item name”, “item path”, “presence / absence of replacement process”, and “red character data” are described.
[0088]
FIG. 22 shows an example of the red data XML electronic document 111 generated by the red data writing unit 109. It is described according to the XML structure described above. In the example of FIG. 22, it is assumed that the number of pages is 1, the number of small groups per page is 1, and the number of items to be cast per small group is 1 for simplification of description. In practice, these are repeated as necessary.
[0089]
The red data import unit 115 imports the red data XML electronic document 111 and passes it to the data confirmation / correction unit 117.
[0090]
The confirmation / correction of the red data is performed in the red data list view shown in FIG. 23 or the update data editing view shown in FIG. When the red data import unit 115 imports the red data XML electronic document 111, the red data list view shown in FIG. 23 changes to the red data list view shown in FIG.
[0091]
Referring to FIG. 25, a row is provided for a property in which at least one item is in red data, and only the value of the item included in the page, category, property ID, property name, and red data XML document is in red. Displayed in the data list view. The field of the item not corrected by the red data is blank.
[0092]
The screen shown in FIG. 26 can be called from the screen of FIG. 25, and an arbitrary character string of an arbitrary item can be replaced with another arbitrary character string using the screen of FIG. If the item “price” is replaced with “/” from a blank by using the screen of FIG. 26 for the red data on the screen of FIG. 25, the contents of the red data are as shown in the screen of FIG. In the red data displayed on the screen of FIG. 25, “Property name” and “Price” are displayed in DTP in the format of “Property name / price” in one box. Although “/” is added, “/” before “price” is deleted by replacing “/” with a blank for “price” on the screen of FIG.
[0093]
In addition, the property ID can be checked for duplication. If a property with the same property ID is listed at a plurality of locations, and the item value of the property is changed at each location, the property ID overlaps. When the property IDs are duplicated, there is a possibility that the deficit data is mutually inconsistent between the posting locations. When a duplicate check is performed by tracing a predetermined menu in order to confirm such a contradiction, a screen as shown in FIG. 28 is displayed. In the example of FIG. 28, duplication of deficit data of the property whose property ID is 7 occurs. In the screen of FIG. 28, the price is corrected to 1,400,000 in the deficit data on the 116th page, but the price is not corrected in the deficit data on the 117th page, so there is a contradiction. The screen in FIG. 28 is a duplication confirmation screen, and correction of red data for resolving the contradiction is performed on another screen.
[0094]
Further, the deficit data can be sorted. One or more items as sorting criteria are selected on the screen of FIG. 29, and the sort order (ascending or descending order) is selected. The sorted result is displayed on the screen shown in FIG. In the screen of FIG. 30, the deficit data is sorted by property and price. The red data can be corrected on this sorted screen.
[0095]
Furthermore, deficit data can be searched. When the menu is followed and search is selected, a search condition input screen shown in the upper left of FIG. 31 is displayed. A white column on this screen is a column for inputting a search condition. When the user inputs search conditions in this field and presses the search button, a search result display screen shown in the lower right of FIG. 31 is displayed. The red data can be corrected on the search result screen.
[0096]
In the update data editing view shown in FIG. 24, the item value can be corrected for each property ID. Items of the property selected in the tree view on the left side of the screen in FIG. 24 are displayed in the table on the right side. The columns of this table are “item name”, “required”, “property data”, “update data”, and “red data”. “Mandatory” indicates whether or not the item is essential. “Property data” is the value of the current item in the property database. “Update data” is data after update. When the reflection unit 119 performs reflection, the data in the property database is updated to “update data”. “Red data” is red data described in the red data XML electronic document 111. As described above, this is corrected in the red data list view as necessary.
[0097]
There are three types of “update data”. The first type is “data that can be reflected”, the second type is “data that cannot be reflected”, and the third type is “data without data in red”. “Reflective deficit data” includes deficit data, and the deficit data can be directly reflected in the property database. “Reflective red data” is displayed with a green background color. The conditions for allowing deficit data to be directly reflected in the property database are as follows: (1) Data type is the same, (2) “Update data” is not blank for required items, (3) Replacement No processing is performed. (4) All “four conditions” that the red data is not the reference data are satisfied. The reference data is data obtained by referring to another table from the “property table”. In the example of FIG. 24, the “property name” and “price” are “reflective deficit data”, and in these items, “update data” is equal to “red data on the right”. “Unreflectable deficit data” includes deficit data, and the deficit data cannot be directly reflected in the property database. “Unreflectable deficit data” is displayed with a yellow background color. This yellow background color display corresponds to a special display of red data that cannot be reflected in the property table as it is. In the example of FIG. 24, “manufacturer”, “vehicle inspection date”, and “sales store” are “non-reflective deficit data”, and “update data” is blank in these items. The cause of the failure to reflect is that at least one of the above four conditions is not satisfied. “Data without red data” is data for which there is no red data. “Data without red data” is displayed in a default color (for example, white) background color. In the example of FIG. 24, “Property ID”, “Vehicle name”, “Color”, “Shift”, “Driving distance”, and “Image” are “data without red data”. “Update data” is equal to “Property data” on the left.
[0098]
Next, the structure of a database for importing red data, checking / modifying red data, and reflecting the data in the property database will be described.
[0099]
Referring to FIG. 32, this database includes “Property Table” 271, “Manufacturer Vehicle Table” 273, “Manufacturer Table” 275, “Area Table” 277, “Distributor Table” 279, “Table Definition Table” 281 and “ Table column definition table "283. Referring to FIG. 33, this database further includes a “red character property table” 291, a “red character property flag table” 293, a “red character property column table” 295, a “red character reference table” 297, and a “red character update table” 299. .
[0100]
Referring to FIG. 32, the column of “Property Table” 271 includes “Property ID”, “Property Name”, “Price”, “Manufacturer ID”, “Vehicle ID”, “Body Shape Grade”, “First Year Registration Year”. ”,“ Displacement ”,“ vehicle inspection date ”,“ shift ”,“ travel distance ”,“ color ”,“ remarks ”,“ area ID ”,“ store ID ”, and“ thumbnail image ”. The property ID is the primary key. Records are provided for each property.
[0101]
The columns of “maker vehicle table” 273 are “maker ID”, “vehicle ID”, and “vehicle name”. A concatenated key of “maker ID” and “vehicle ID” is a main key. A record is provided for each vehicle of each manufacturer. The “property table” 271 and the “manufacturer vehicle table” 273 are many-to-one by “manufacturer ID” and “vehicle ID” in the “property table” 271 and “manufacturer ID” and “vehicle ID” in the “manufacturer vehicle table” 273. The relation of is attached.
[0102]
The columns of “maker table” 275 are “maker ID” and “maker name”. “Manufacturer ID” is the primary key. A record is provided for each manufacturer. The “manufacturer vehicle table” 273 and the “manufacturer table” 275 are provided with a many-to-one relationship based on the “manufacturer ID” in the “maker vehicle table” 273 and the “manufacturer ID” in the “maker table” 275.
[0103]
The columns of “area table” 277 are “area ID” and “area name”. “Area ID” is the primary key. A record is provided for each area. The “property table” 271 and the “area table” 277 have a many-to-one relationship based on the “area ID” of the “property table” 271 and the “area ID” of the “area table” 277.
[0104]
The columns of the “store table” 279 include “store ID”, “store name”, “address”, “phone number”, “FAX number”, “business hours”, “regular holiday”, “HP address”, “E-mail address”, “Transfer destination” and “Remarks”. “Store ID” is the primary key. A record is provided for each store. The “property table” 271 and the “dealer table” 279 have a many-to-one relationship based on the “dealer ID” of the “property table” 271 and the “dealer ID” of the “dealer table” 279.
[0105]
The “maker table” 275, “area table” 277, and “store table” 279 are reference tables for the “property table” 271 in the sense that they are referred to from the “property table” 271.
[0106]
“Property ID”, “Property Name”, “Price”, “Manufacturer ID”, “Vehicle ID”, “Body Shape Grade”, “First Year Registration Year”, “Displacement”, “Inspection” in “Property Table” 271 “Year / Month”, “Shift”, “Mileage”, “Color”, “Remarks”, “Area ID”, “Store ID” and “Thumbnail Image”, “Manufacturer Table” 273 “Manufacturer ID”, “ "Vehicle ID", "Vehicle name", "Manufacturer ID" and "Manufacturer name" in "Manufacturer table" 275, "Area ID" and "Area name" in "Area table" 277, and "Sales" in "Reseller table" 279 “Store ID”, “Distributor Name”, “Address”, “Telephone Number”, “FAX Number”, “Business Hours”, “Regular Holidays”, “HP Address”, “E-mail Address”, “Transfer Address”, and “ “Remark” is displayed by the rendering unit 105. It is corrected by the data correction unit 107 as necessary. Also, the red data for these items is written into the red data XML electronic document 111 as necessary. However, as described above, it is impossible to reflect the red data in the column of the reference table as it is in the property database. In addition, since the “first year registration year” and “vehicle inspection date” in the “property table” 271 have been replaced, it is impossible to reflect the red data in these columns as they are in the property database. Therefore, the “reflectable deficit data” is “property name”, “price”, “maker ID”, “vehicle ID”, “body shape grade”, “displacement”, “shift”, “property table” 271. Only red data for “travel distance”, “color”, “remarks”, and “thumbnail image”.
[0107]
The columns of “table definition table” 281 are “table ID” and “table name”. “Table ID” is the primary key. The record of “table definition table” 281 is provided for “property table” 271 and all reference tables.
[0108]
The columns of the “table column definition table” 283 are “table ID”, “table column ID”, “column order”, “column name (alphanumeric notation)”, “column name (Japanese notation)”, “data type” ”,“ Length ”,“ decimal point ”,“ primary key ”, and“ foreign key ”. A record is provided for each column of each table. The “table ID” is an ID unique to each table and matches the “table ID” of the “table definition table” 281. “Table column ID” is an ID of each column in each table. “Column order” is the order of each column in each table. Immediately after defining the “property table” or the reference table, the “table column ID” is equal to the “column number”, but if the table structure is changed, the “column order” may be changed. On the other hand, the “table column ID” is not changed. “Column name (alphanumeric notation)” is a column name expressed in alphanumeric characters. “Column name (in Japanese)” is the name of the column expressed in Japanese. “Data type” indicates the data type of the column. “Data type” is, for example, a numerical value, a character string, an object, or the like. “Length” is the number of bytes in the column. The “decimal point” is the number of digits after the decimal point when the “data type” is a numerical value. “Primary key” indicates whether or not a primary key is set in the column. “Foreign key” indicates whether or not a foreign key is set in the column.
[0109]
Referring to FIG. 33, the columns of “red character property table” 291 include “page number”, “small group number”, “DTP correction category”, “reflection processing category”, “original property ID”, “original property name”, “Property ID” to “Thumbnail image”. “Property ID” to “Thumbnail image” are the same as those in “Property table” 271 in the column definition. A concatenated key of “page number” and “small group number” is a primary key. A record is provided for each small group for which red data is created. The “DTP correction category” indicates a category of updated, newly created, or deleted. This corresponds to the “correction category” of the property layer in the structure of the deficit data XML electronic document 111 shown in FIG. That is, the “DTP correction category” reflects the “correction category” in the deficit data XML electronic document 111 as it is. “Reflection processing category” indicates a category for updating, newly creating, or deleting. The “reflecting process category” indicates how the reflecting unit 119 should actually reflect in the property database 121. The “property table” 271 and the “red character property table” 291 are associated with each other by the “property ID” in the “property table” 271 and the “original property ID” in the “red character property table” 291.
[0110]
The columns of the “red character flag table” 293 are “page number”, “small group number”, “property ID flag”, “property name flag”, “price flag”, “maker ID flag”, “vehicle ID flag”, “Body shape grade flag”, “First year registration year flag”, “Exhaust gas flag”, “Vehicle inspection year / month flag”, “Shift flag”, “Driving distance flag”, “Color flag”, “Remark flag”, “ These are “area ID flag”, “store ID flag”, and “thumbnail image flag”. A concatenated key of “page number” and “small group number” is a primary key. Similar to the “red character property table” 291, a record is provided for each small group for which red data is created. The “red character property table” 291 and the “red character property flag table” 293 are “page number” and “small group number” in the “red character property table” 291 and “page number” and “small group number” in the “red character property flag table” 293. With this, a one-to-one relationship is established. The “** flag” (for example, the property ID flag) indicates whether or not the item “**” (for example, “the property ID”) has red data.
[0111]
The columns of the “red character column table” 295 are “page number”, “small group number”, “column order”, “table ID”, and “table column ID”. A concatenated key of “page number”, “small group number”, and “column order” is a primary key. A record is provided for each column of the “property table” 271 in which red data is created. For the reference table column in which the red data is created, the “red character column table” 295 record is not provided, but the “red reference table” 297 record described later is provided. The “red character property table” 291 and the “red character property column table” 295 are “page number” and “small group number” in the “red character property table” 291 and “page number” and “small group number” in the “red character property column table” 295. A one-to-many relationship is established. “Table column definition table” 283 and “red character property column table” 295 are “table ID” of “table column definition table” 283 and “table ID” of “table column ID” and “red character property column table” 295. A “one-to-one relationship” is given by “table column ID”.
[0112]
The columns of the “red character reference table” 297 are “page number”, “subgroup number”, “column order”, “reference data order number”, “item name”, “reference data”, and “red character data”. The concatenated keys of “page number”, “subgroup number”, “column order”, and “reference data order number” are the main keys. The “red character property column table” 295 and the “red character reference table” 297 are “page number”, “subgroup number” and “column order” of the “red character property column table” 295 and “page number” of the “red character reference table” 297. , “Small group number”, “column order”, and “reference data order number”, a one-to-many relation is attached. The “red character reference table” 297 is used only for displaying the red data of the reference table in the reference data table at the lower right of the screen shown in FIG. 24, in order to reflect the red data of the reference table in the property database 121. Is not used. In the present invention, the red data in the reference table is not reflected in the property database 121. Although different from the example shown in FIG. 32, for example, the “maker table” 275 has “head office address” in addition to “maker ID” and “maker name”, and is displayed in DTP by the data correction unit 107. If both the “manufacturer name” and the “head office address” are corrected, the reference data table at the lower right of the screen of FIG. The lines indicating the values before and after the correction of the “head office address” are displayed, and the “reference data order number” is used to identify these lines. “Reference data” is data in the corresponding column of the reference table of the property database before reflecting the red data, and “red data” is red data in the corresponding column of the reference table of the property database.
[0113]
The columns of the “red character update table” 299 are “page number”, “small group number”, “property ID” to “thumbnail image”. “Property ID” to “Thumbnail image” are the same as those in “Property table” 271 in the column definition. A concatenated key of “page number” and “small group number” is a primary key. A record is provided for each small group for which red data is created. The “red character property table” 291 and the “red character update table” 299 are paired by “page number” and “small group number” in the “red character property table” 291 and “page number” and “small group number” in the “red character update table” 299. A relationship is attached.
[0114]
Next, the operation of red data import performed by the red data import unit 115 will be described with reference to FIG.
[0115]
Referring to FIG. 34, first, the processing for each page tag (steps S303 to S345) is repeated (step S301) until there is no page tag in the red data XML document 111. In step S303, the page tag is read and the page number (see FIG. 21) is acquired. Next, the processing for each bukken tag (steps S307 to S345) is repeated (step S305) until there is no bukken tag in the layer below the page tag. In step S307, the bukken tag is read, and the small group number, property ID, and correction category (see FIG. 21) are acquired. Here, since the page number, small group number, property ID, and correction category have been acquired, a record is added to the “red character property table” 291 (step S309), and a record is also added to the “red character property flag table” 293 ( Step S311). The currently acquired page number, small group number, correction category, and property ID are substituted into the page number, small group number, DTP correction category, and original property ID of the additional record in the “red character property table” 291. The currently acquired page number and small group number are substituted into the page number and small group number of the “red character property flag table” 293. Next, referring to the “table column definition table” 283, the processing (step S315) for each column of the “property table” 271 is repeated (step S313). Since the “table ID” of the “property table” 271 is “1”, the process for the column order of all the records whose “table ID” of the “table column definition table” 283 is 1 is repeated. In step S315, a record is added to the “red character column table” 295, and “page number”, “subgroup number”, “column order”, “table ID”, and “table column ID” of the additional record are currently acquired. The “page ID” (= “1”), “table column ID”, and “column number” acquired from the “table column definition table” 283 are substituted. If the step S313 is repeated, a record is added to the “red character update table” 299 (step S317). Next, a record having the same “property ID” as the property ID acquired in step S307 is searched from the “property table” 271, and the “property ID” to “thumbnail image” of the record is added in step S317. Are copied to the corresponding columns (step S319).
[0116]
Next, the processing for each item (steps S323 to S345) is repeated (step S321) until there is no item tag in the hierarchy below the bukken tag. In step S323, the item name, item path, presence / absence of replacement processing, and red data associated with the current item tag are acquired. Next, by checking the item path acquired in step S323, it is determined whether the item is reference data (reference table data) (step S325).
[0117]
If the determination result in step S325 is negative (when the item is in the property table), the corresponding column (column corresponding to the item) in the “red character property table” 291 added in step S309 is in red. Data is set (step S327), and the flag in the corresponding column of the record of the “red character flag table” 293 added in step 311 is turned ON (step S329). Next, it is determined whether or not the current deficit data can be reflected in the corresponding column of the “property table” 271 by checking whether or not all of the “four conditions” described above are satisfied. (Step S331).
[0118]
If the determination result in step S331 is affirmative, the contents of the corresponding column of the record of “red character update table” 299 added in step S317 are rewritten with red data (step S335), and the update data editing view (see FIG. 24) is displayed. The background color of the update data string of the corresponding small set is set to green (step S337).
[0119]
If the determination result in step S331 is affirmative, the contents of the corresponding column of the record of “red character update table” 299 added in step S317 are cleared (step S339), and the corresponding in the update data editing view (see FIG. 24). The background color of the small update data string is set to yellow (step S341).
[0120]
When the determination result in step S325 is affirmative (when the item is that of the reference table), a record is added to the “red reference table” 297 (step S343), and data is set in the additional record (step S343). S345). The “page number” to be set is acquired in step S303, the “subgroup number” to be set is acquired in step S307, and the “column order” to be set is the current column order in the repetition of step S313. The “reference data order number” to be set is a serial number that increases each time step S345 is performed for the same combination of “page number”, “subgroup number”, and “column order”, and the “item name” to be set is The item name acquired in step S323, and the “reference data” to be set is the value of the corresponding column searched from the reference table of the current property database based on the item path acquired in step S323, and the “red data to be set” "Is the red data obtained in step S323.
[0121]
Next, data checking and correction operations performed by the data checking / correcting unit 117 will be described with reference to FIG.
[0122]
Referring to FIG. 35, first, it is determined whether or not a red data list view is selected (step S351).
[0123]
If the determination result in step S351 is affirmative (if the red data list view is selected), data correction input is accepted (step S353), and the “red character property table” 291 is selected according to the location and content of the correction. The data in the corresponding column of the corresponding record is rewritten (step S355). Next, whether or not the deficit data corrected in step S353 can be reflected in the corresponding column of the “property table” 271 by checking whether or not all the “four conditions” described above are satisfied. Is determined (step S357).
[0124]
If the determination result in step S357 is affirmative, the contents of the corresponding column of the corresponding record in the “red character update table” 299 are rewritten with red data (step S359), and the corresponding small set is updated in the update data editing view (see FIG. 24). The background color of the data string is set to green (step S361).
[0125]
If the determination result in step S357 is affirmative, the contents of the corresponding column of the corresponding record in the “red character update table” 299 are cleared (step S363), and the update data of the corresponding small set in the update data editing view (see FIG. 24) is obtained. The background color of the column is set to yellow (step S365).
[0126]
If the determination result of step S351 is negative (if the update data editing view is selected), the data correction of the update data string on the screen of FIG. 24 is accepted (step S367), and “ The data in the corresponding column of the corresponding record in the “update table” 299 is rewritten (step S369).
[0127]
As can be seen from the description of steps S353 to S369, the data displayed in the red data list view is red data, not update data. In the update data editing view, the data of the “property table” 271 is displayed in the property data column, and the data of “red update table” 299 is displayed in the update data column. What is displayed in the data column is the data of the “red character property table” 291.
[0128]
Next, the operation of reflecting the red data in the property database performed by the reflecting unit 119 will be described with reference to FIG.
[0129]
Referring to FIG. 36, first, the “red character update table” 299 is searched to determine whether there is a record with duplicate property IDs (step S371). If there is a duplicate record (YES in step S373), it is impossible to reflect the contents of the “red character update table” 299 in the “property table” 271, so an error message is displayed (step S389). , Stop processing.
[0130]
If there is no duplicate record (NO in step S373), the “red update table” 299 is searched to determine whether there is a record that cannot be reflected in the “property table” 271 (step S375). The record that cannot be reflected is, for example, a record in which an essential item is blank or a record having an item whose data type does not match. If there is a record that cannot be reflected (YES in step S377), it is impossible to reflect the contents of the “red character update table” 299 in the “property table” 271, and an error message is displayed ( In step S389), the process is stopped.
[0131]
Although it is impossible to reflect a record having an essential item of “non-reflective deficit data” in the “property table” 271, in this case, the user enters the update data column on the screen of FIG. 24. It can be reflected by inputting data that can be reflected.
[0132]
If there is no record that cannot be reflected (NO in step S377), the processing (steps S381 to S387) for each record in the “red character update table” 299 is repeated until there are no more records in the “red character update table” 299 (steps S381 to S387). Step S379). In step S381, a record is acquired from the “red character update table” 299. Next, a record having the same “property ID” as the “property ID” of the record of the “red letter update table” 299 obtained in step S381 is obtained from the “red letter property table” 291 (step S383). Next, a record having the same “property ID” as the “original property ID” of the record of the “red character property table” 291 acquired in step S383 is acquired from the “property table” 271 (step S385). Next, the contents of the record of the “property table” 271 acquired in step S385 are overwritten with the contents of the record of the “red character update table” 299 acquired in step S381 (step S387).
[0133]
If the loop of step S379 is exited, all the records of “red character property table” 291, “red character property flag table” 293, “red character property column table” 295, “red character reference table” 297, and “red character update table” 299 are stored. Delete (step S391).
[0134]
[Embodiment 2]
The second embodiment adds a database item not included in the DTP data at the stage of rendering, inputs a value to the added item, and feeds back the input value of the added item to the database.
[0135]
Referring to FIG. 37, the apparatus for reflecting deficit data in the database according to the second embodiment is roughly divided into DTP software 1103 and a deficit data return tool 1113. The DTP software 1103 includes a rendering unit 105 corresponding to an XSL-FO processor, an item addition unit 1107, and a red data writing unit 1109. The deficit data return tool 1113 includes a deficit data import unit 1115, a data confirmation / correction unit 1117, an update destination unknown data setting unit 1118, and a reflection unit 1119. The DTP software 1103 is a computer program as the name indicates, and this function is realized when the computer reads and executes the DTP software 1103. The deficit data return tool 1113 can also be realized by the computer reading and executing a computer program for causing the computer to function as the deficit data return tool 1113.
[0136]
The rendering unit 105 displays a page according to the contents of the allocated XSL-FO electronic document 101. The item addition unit 1107 adds items according to user operations and sets values for the added items. A red data writing unit 1109 writes red data as red data XML electronic document 1111. The red data import unit 1115 imports the red data XML electronic document 1111. The data confirmation / correction unit 1117 confirms and further corrects the red data. The update destination unknown data setting unit 1118 determines a reflection destination of additional data, which is unknown to which column of which table should be reflected immediately after the import, in accordance with a user operation. The reflecting unit 1119 updates the contents of the property database 121 using the red data.
[0137]
Since the rendering unit 105 is the same as that of the first embodiment, the description thereof is omitted.
[0138]
Next, the operation of the item adding unit 1107 will be described.
[0139]
First, the addition of text will be described. When a predetermined menu is traced in a state where a text box as shown in FIG. 38A is selected, a dialog screen as shown in FIG. 39A is displayed. In this dialog screen, the item names and values of the items inserted in the text box shown in FIG. In this state, by selecting a predetermined menu, the dialog screen shown in FIG. 39A is changed to the dialog screen shown in FIG. In the dialog screen shown in FIG. 39 (b), in addition to the item names and values of the items inserted in the text box shown in FIG. 38 (a), there are lines having unnamed item names and blank item values. Is displayed. When the user inputs the item name and value to the added line, the screen shown in FIG. 39 (b) changes to the screen shown in FIG. 39 (c), and when the return key is pressed, the result is shown in FIG. It is reflected on the DTP screen as shown in b).
[0140]
Next, the addition of an image will be described. When a predetermined menu is traced in a state where a screen as shown in FIG. 40A is displayed, a dialog screen as shown in FIG. 41A is displayed. In this dialog, the item name and value of the item inserted in the text box 1201 shown in FIG. In this state, by selecting a predetermined menu, the dialog screen shown in FIG. 41A changes to a dialog screen as shown in FIG. In the dialog screen shown in FIG. 41 (b), in addition to the item names and values of the items inserted in the text box shown in FIG. 41 (a), there are lines having unnamed item names and blank item values. Is displayed. When the user inputs an item name in the added line, the screen shown in FIG. 41 (b) changes to the screen shown in FIG. 41 (c), and the screen shown in FIG. 40 (a) is displayed by pressing the return key. It will be displayed again. Here, by selecting an image to be inserted in a dialog displayed by following a predetermined menu, an image 1202 is inserted as shown in FIG. In this state, when the same predetermined menu as when the dialog screen shown in FIG. 41A is displayed is followed, the dialog screen shown in FIG. 41D is displayed. In the dialog screen shown in FIG. 41 (d), the image file name of the image inserted in the added item is also displayed.
[0141]
The above text addition and image addition were adding text and images to an existing box, but you can add new boxes to the set and add text or images to the added boxes .
[0142]
Next, a method for adding a new box to the small group will be described. The menu shown in FIG. 42 is used for this addition. For example, a copy box is created on the DTP screen by copying a box in another small group and pasting it in a predetermined position. Therefore, when “Marking of unassembled item” in the menu shown in FIG. 42 is selected, the copied box is specially displayed. Therefore, if any one of the subgroups to which the copied box is to be merged is selected and “recombination” is selected from the menu shown in FIG. 42, the copied box is merged with the subgroup. Thereafter, when adding text, the item name and value are set in the copy box by the above-described method. Note that the names and values of existing items are deleted as necessary. When an image is added, an image is first added on the DTP screen by following a predetermined menu, and then an item name is set using the screen of FIG.
[0143]
FIG. 43 shows an example in which a box including a price item is added.
[0144]
44, when the item name is “color”, the item value is “black”, the item name is “price”, and the item value is “1,400,000” The data structure in DTP data is shown. This data structure is shown in the form of an object class diagram as shown in FIG. 10 as in the first embodiment.
[0145]
The small group style information includes “update date and time”, “property ID”, and “small group ID”. The value of “update date and time” is the date and time when the item was added. The values of “property ID” and “small group ID” are values read from the XSL-FO electronic document 101.
[0146]
Box style information includes: "array of paths of database items that have been poured in", "array of item names of database items that have been fed in", "array of the order in which database items have been poured in", and "databases that have been fed in" There is an array of item update date and time. As for the existing “property name”, the “array of database item path array” element is a value read from the XSL-FO electronic document 101, and the “array of item name array of database database element” element Is a value read from the XSL-FO electronic document 101, and the element of “array of the flowed-in database item flow order” is a value determined from the XSL-FO electronic document 101, and “update of flowed-in database item” The element of “date and time array” is 0000, 00:00:00, which is an initial value. For the added “color”, the element of “array of the path of the database item that has been poured in” is blank, and the element of “the array of the item name of the database item that has been fed in” is the value input by the data correction unit 1107 The element of “sequence of the flowed database items into the flow order” is an additional automatic serial number, and the element of “array of the flowed database items in the update date / time” is assigned by the data correction unit 1107 to the additional items. The date and time when it was entered.
[0147]
The character style information includes “DB item path”, “DB item item name”, “DB item flow order”, and “With / without DB item replacement process”. FIG. 44 shows only the character style information for the additional items (“color” and “price”), and the character style information for the existing items is the same as in FIG. 13 and is not shown. For both “color” and “price”, “database item path” is blank, and “database item item name” is the value entered in the dialog screen of FIG. The value of “order” is an additional automatic serial number, and the value of “without replacement” is “none”. In addition, when a box is added by copy and paste and an item there is inherited, “no replacement processing” is also inherited.
[0148]
Next, an item adding operation performed by the item adding unit 1107 will be described with reference to FIG.
[0149]
First, if a predetermined item of the menu is selected while the screen of FIG. 39A is displayed (step S1151), an element is added to each of the four arrays of box style information shown in FIG. Then, the screen of FIG. 39B is displayed (step S1153). Next, if an item name is added on the screen of FIG. 39B (step S1155), the item is added to the additional element of “injected database item name” in the box style information shown in FIG. A name is set (step S1157). Next, if an item value is input on the screen of FIG. 39B (step S1159), the screen shown in FIG. 39C is displayed and the DTP screen is updated with the item value (step S1161). 44), the character style shown in FIG. 44 is added, and values are set in the four items of the character style (step S1163), and “update date and time of the inserted database item” in the box style information shown in FIG. The current date and time is substituted for the additional element (step S1165), and the current date and time is substituted for the "update date and time" in the small set of style information shown in FIG. 44 (step S1167). The item value input in step S1159 is added to the DTP data as usual.
[0150]
Next, the deficit data writing unit 1109 will be described.
[0151]
The structure of the red data XML electronic document 1111 output from the red data writing unit 1109 is as shown in FIG.
[0152]
The structure of the red data XML electronic document 1111 shown in FIG. 46 is the same as the structure of the red data XML electronic document 111 shown in FIG. 21, but the value of “modification category” in the “property” layer is “mod”. (Correction), and the value of “item path” in the “item” hierarchy is “” ”(empty).
[0153]
A specific example of the red data XML electronic document 1111 generated by the red data writing unit 1109 based on the style information shown in FIG. 44 is shown in FIG.
[0154]
Next, the operation of the red data writing unit 1109 is the same as the operation of the red data writing unit 109 of the first embodiment shown in FIG.
[0155]
Next, a database table used by the red data return tool 1113 will be described.
[0156]
The deficit data return tool 1113 uses the tables shown in FIGS. As apparent from comparison between the tables shown in FIG. 32 and the tables shown in FIG. 33 used by the deficit data return tool 113 of the first embodiment, the deficit data return tool 1113 is used by the deficit data return tool 1113 of the first embodiment. In addition to all the tables, a “red update destination unknown table” 1292 shown in FIG. 49 and a “relation definition table” 1293 and a “relation column definition table” 1294 shown in FIG. 50 are used. Further, the “table column definition table” 283 used by the red data return tool 113 of the first embodiment is changed to “table column definition table” 1283. The “table column definition table” 1283 is different from the table column definition table in that a relation ID (indicated by reference numeral 1283-1) is added.
[0157]
The relation between the tables shown by the arrows in FIG. 48 is identified by the relation ID, and the relation indicated by each relation ID has a parent-child relationship indicated by “Relation definition table” 1293, and “Relation column definition table”. 1294 has a relationship between columns. An arbitrary column of an arbitrary table can be expressed by XPATH, which is XML in terms of the “property table” 271 based on the data of the relationship ID, “relation definition table” 1293, and “relation column definition table” 1294. it can.
[0158]
“Deficit update destination unknown table” 1292 (see FIG. 49) is a table for holding data of items for which the red data import unit 1115 has determined that the update destination is unknown. ”,“ Small group number ”,“ data order number ”,“ additional item name in DTP ”, and“ additional data in DTP ”. A copy of the data of the red data XML electronic document 1111 is inserted in the columns of “page number”, “subgroup number”, “additional item name in DTP”, and “additional data in DTP”, and “data order number” is , A serial number that increases each time a record is added is inserted.
[0159]
Next, the red data import unit 1115 will be described. The red data import unit 1115 has functions unique to the second embodiment in addition to the functions of the red data import unit 115 of the first embodiment.
[0160]
The operation of the red data import unit 1115 is shown in FIG. As is apparent from comparing FIG. 51 with FIG. 34 showing the operation of the deficit data import unit 115 of the first embodiment, steps S301 to S323 and S325 to S345 performed by the red data import unit 1115 are performed in accordance with the red data import of the first embodiment. Since these steps are the same as those performed by the unit 115, description of these steps will be omitted, and only the added steps S1301 to S1309 will be described. It is assumed that the red data import unit 1115 imports the red data XML electronic document including the item changed according to the first embodiment and the item added according to the second embodiment.
[0161]
In step S1301, it is checked whether the item path is blank. Specifically, this is done by checking whether or not “path =“ ”” is described in the item hierarchy shown in FIG. If the determination result in step S1301 is negative, the current item is a change item, and the process immediately proceeds to step S325 as in the first embodiment. If the determination result in step S1301 is affirmative, the current item is an additional item, and the process advances to step S1303.
[0162]
In step S1303, the “table column definition table” 1283 (see FIG. 48) is searched by item name, and an attempt is made to acquire the corresponding column. Specifically, in the item hierarchy shown in FIG. 46, a record having “column name (in Japanese notation)” having the same character string as the character string enclosed by ““ ”” after “name_jp =”. This is done by searching from “table column definition table” 1283.
[0163]
Next, it is determined whether or not the corresponding column could not be acquired in step S1303 (step S1305).
[0164]
If the determination result in step S1305 is negative (if the corresponding column can be acquired), an item path is created (step S1309), and the process proceeds to step S325. The item path is expressed in XPATH based on the property table, and the creation of the item path is based on “table column definition table” 1283, “relation definition table” 1293, and “relation column definition table” 1294. To do.
[0165]
If the determination result in step S1303 is affirmative (if the corresponding column could not be acquired), a record of “red letter update destination unknown table” 1292 (see FIG. 49) is created, and the red letter data XML electronic document 1111 is created in that record. Set the data of the item. Thereafter, steps S325 to S345 are skipped and the process proceeds to the next item.
[0166]
Next, the data confirmation / correction unit 1117 will be described. The data confirmation / correction unit 1117 has functions specific to the second embodiment in addition to the functions of the data confirmation / correction unit 117 of the first embodiment.
[0167]
The operation of the data checking / modifying unit 1117 is shown in FIG. As is apparent from comparing FIG. 52 and FIG. 35 showing the operation of the data confirmation / correction unit 117 of the first embodiment, steps S351 to S365 and S367 to S369 performed by the data confirmation / correction unit 1117 are the data of the first embodiment. Since these steps are the same as those performed by the confirmation / correction unit 117, description of these steps is omitted, and only the added steps S1351 and S1353 will be described.
[0168]
If the determination result in step S351 is negative (if the update data editing view is selected), it is checked whether there is update destination unknown data in the currently selected small set (step S1351). Specifically, the record having the same page number and subgroup number as the subgroup number corresponding to the currently selected subgroup is searched from the “red-letter update destination unknown table” 1292 to find one or more records. To see if the search was successful.
[0169]
If the determination result in step S1351 is affirmative, the update destination unknown data is set (step S1353), and then the process proceeds to step S367. If the determination result in step S1351 is negative, step S1353 is skipped immediately. The process proceeds to step S367.
[0170]
Step S 1353 is performed by the update destination unknown data setting unit 1118. Details of step S1353 will be described with reference to FIG.
[0171]
First, all the records searched in step S1351 are acquired, and the values of “additional item name in DTP data” and “additional data in DTP data” in the columns of those records are shown in FIG. (Step S 1361).
[0172]
Next, selection of an item name on the screen shown in FIG. 54 (a) is accepted (step S1363). This item name is selected using the pull-down list shown in FIG. Items to be displayed in the pull-down list are copied from “column names (in Japanese)” of all the records (all records in the property table) whose table ID is 1 in “table column definition table” 1283. When the above selection is made, as shown in FIG. 54 (b), the column name (item name) (“color” in FIG. 54) and the current column of the selected column of the record corresponding to the small set of the “property table” 271 are displayed. Data ("white" in FIG. 54) is displayed.
[0173]
Next, “additional data in DTP” is overwritten in each column selected in step S 1361 of the record corresponding to the current small set in the “red character property table” 291 (step S 1365).
[0174]
Next, it is determined whether or not “additional data in DTP” can be reflected in each corresponding column of the property database 291 (step S1367). This determination is made by determining whether or not all “four conditions” described in the first embodiment are satisfied.
[0175]
If the determination result in step S1367 is affirmative, the contents of the corresponding column of the record corresponding to the current small set in the “red character update table” 299 are rewritten with “additional data in DTP” (step S1369), and the update data editing view The background color of the update data string of the corresponding small set (see FIG. 24) is set to green (step S1371).
[0176]
If the determination result in step S1367 is affirmative, the contents of the corresponding column of the record corresponding to the current sub-set in the “red character update table” 299 are cleared (step S1373), and the update data editing view (see FIG. 24) is displayed. The background color of the update data string of the corresponding small set is set to yellow (step S1375).
[0177]
FIG. 55 shows a table portion of the update data editing view (see FIG. 24) after performing step S1371 or step S1375 for each “additional data in DTP”. Referring to FIG. 55, in the “price” row, the deficit data is “/ 1400,000”, but since “/” is included, “/ 1400,000” is directly reflected in the property data. Since this is not possible, the update data column is blank. In the “color” row, the deficit data is “black”, but since this can be directly reflected in the property data, the update data column is also “black”.
[0178]
Next, the reflecting unit 1119 will be described. The reflection unit 1119 has all the functions of the reflection unit 119 of the first embodiment, but differs in the following points.
[0179]
The operation of the reflecting unit 1119 is shown in FIG. As is clear from comparing FIG. 56 with FIG. 36 illustrating the operation of the reflection unit 119 of the first embodiment, steps S371 to S387 performed by the reflection unit 1119 are the same as those performed by the reflection unit 119 of the first embodiment. The only difference is step S1391, but step 1391 is different from step S391 in FIG. 36 only in that a “red-letter update destination unknown table” 1292 is added as a deletion target.
[0180]
[Embodiment 3]
In the third embodiment, a small set not included in the DTP data is added at the stage of rendering, a value is input to each item of the added small set, and the input value of each item of the added small set is fed back to the database. is there.
[0181]
Referring to FIG. 57, the apparatus for reflecting deficit data in the database according to the third embodiment is roughly divided into DTP software 2103 and deficit data return tool 2113. The DTP software 2103 includes a rendering unit 105 corresponding to an XSL-FO processor, a small group addition unit 2107, and a red data writing unit 2109. The red data return tool 2113 includes a red data import unit 2115, a data confirmation / correction unit 2117, a property data call unit 2118, and a reflection unit 2119. The DTP software 2103 is a computer program as the name indicates, and this function is realized when the computer reads and executes the DTP software 2103. The deficit data return tool 2113 can also be realized by the computer reading and executing a computer program for causing the computer to function as the deficit data return tool 2113.
[0182]
The rendering unit 105 displays a page according to the contents of the allocated XSL-FO electronic document 101. The small group addition unit 2107 adds small group data in accordance with a user operation, and sets a value for each item of the added small group. A red data writing unit 2109 writes red data as red data XML electronic document 2111. The red data import unit 2115 imports the red data XML electronic document 2111. The data confirmation / correction unit 2117 performs confirmation and further correction of the red data. The property data calling unit 2118 determines, according to the user's operation, a reflection destination record of additional data for which it is unknown which record in the property table should be reflected immediately after the import. The reflection unit 2119 updates the contents of the property database 121 using the red data.
[0183]
Since the rendering unit 105 is the same as that of the first embodiment, the description thereof is omitted.
[0184]
Next, the operation of the small group adding unit 2107 will be described.
[0185]
As shown in FIG. 58 (a), in a state where the small set is arranged on the page, the small set 2101 is selected, and after selecting “Copy small set” in the menu of FIG. 42, the point 2102 is selected, By selecting “Paste Small Set” from the menu, a small set copy 2103 is added as shown in FIG.
[0186]
The value of each item of the added small set is corrected by the method shown in the first embodiment, and the item is added to the added small set by the method shown in the second embodiment.
[0187]
FIG. 59 shows an example of the data structure related to the feedback of the red data included in the DTP data after setting the value for each item of the added small set. This data structure is shown in the form of an object class diagram as shown in FIG. 10 as in the first embodiment.
[0188]
Referring to FIG. 59, there are “update date”, “property ID”, and “small group ID” as small group style information. The value of “update date and time” is the date and time when the small set was added. “Property ID” is blank. The value of “small group ID” is an additional serial number in the page to which this small group belongs.
[0189]
Box style information includes: "array of paths of database items that have been poured in", "array of item names of database items that have been fed in", "array of the order in which database items have been poured in", and "databases that have been fed in" There is an array of item update date and time. The elements of the "array of the path of the database item that was inserted" are the same as those of the copy source sub-set, and the "array of the item name of the database item that was poured" is the same as that of the copy source sub-set, The “sequence of the flowed database items” is also the same as that of the copy source sub-set. The values of all the elements in the “update date / time array of database items” are the date and time when a small set was added.
[0190]
The character style information includes “DB item path”, “DB item item name”, “DB item flow order”, and “With / without DB item replacement process”. FIG. 59 shows only the character style information for the “color” and “price” items, but the same applies to the other items. The value of “Database item path” is the same as that of the copy source sub-set, the value of “Database item item name” is also the same as that of the copy source sub-set, and the value of “Place order of database items” Is the same as that of the copy source sub-set, and the value of “Without replacement processing” is also the same as that of the copy source sub-set.
[0191]
Next, a small group addition operation performed by the small group addition unit 2107 will be described with reference to FIG.
[0192]
First, as described above, when the user selects a small set and selects “Copy of small set” in the menu of FIG. 42, the small set is copied (step S2151), and the database reflection data shown in FIG. 59 is copied. (Step S2153). Next, when the user selects a point and selects “Paste small set” from the menu of FIG. 42, the small set is pasted to that point (step S2155), and the database reflection data shown in FIG. Paste in association (step S2157).
[0193]
Next, it is determined whether or not the copy source subset and the paste destination subset belong to the same DTP document (step S2159). Here, the DTP document corresponds to a “DTP data file” in terms of printing. One book is composed of one or a plurality of “DTP documents”, and in a prepress process using database publishing, a plurality of “DTP documents” may be created in parallel. Therefore, a small set may be copied and pasted within the same DTP document, or may be copied and pasted between DTP documents.
[0194]
If the determination result in step S2159 is affirmative, the property ID of the paste destination small set is blank (step S2161). This is because there is a high possibility that a property in the property table that is different from the property assigned to the copy source is assigned to the small set at the paste destination, or a property that is not in the property table is assigned.
[0195]
If the determination result of step S2159 is negative, step S2161 is skipped. Therefore, the same property as the property assigned to the copy source sub-group is allocated to the paste-destination sub-group. This is because there is a high possibility that the same property as the property of the copy source will be assigned to the paste destination subgroup. Thereafter, such a small group is handled as a corrected small group by the apparatus for reflecting deficient data in the database according to the first embodiment.
[0196]
Following step S2159 or step S2161, the update date / time of the small style is updated to the current date / time (step S2165), and the update date / time of the box style is updated to the current date / time (step S2165).
[0197]
Next, data correction and item addition by the user are accepted (step S2167).
[0198]
Next, the deficit data writing unit 2109 will be described.
[0199]
The structure of the red data XML electronic document 2111 output from the red data writing unit 2109 is as shown in FIG.
[0200]
The structure of the red data XML electronic document 2111 shown in FIG. 61 is the same as the structure of the red data XML electronic document 111 shown in FIG. 21, but the property ID of the “Property” layer is blank in principle, and “Property” The value of the “correction category” in the hierarchy is “new” (new).
[0201]
A specific example of the red data XML electronic document 2111 generated by the red data writing unit 2109 based on the style information shown in FIG. 59 is shown in FIG.
[0202]
Next, the operation of the red data writing unit 2109 is the same as the operation of the red data writing unit 109 of the first embodiment shown in FIG.
[0203]
Next, the deficit data return tool 2113 uses the tables shown in FIGS. 48 to 50 in the same manner as the deficit data return tool 1113 of the second embodiment.
[0204]
Next, the red character data import unit 2115 will be described. The red data import unit 2115 has functions specific to the third embodiment in addition to the functions of the red data import unit 1115 of the second embodiment.
[0205]
The operation of the red data import unit 2115 is shown in FIG. As is apparent from comparing FIG. 63 with FIG. 51 showing the operation of the red data import unit 1115 of the second embodiment, steps S301 to S317, 319 to 323, S1301 to S1309, and S325 to S345 performed by the red data import unit 2115 are as follows. Since the operation is the same as that performed by the red data import unit 1115 of the second embodiment, description of these steps is omitted, and only the added steps S2301 and S2303 are described. The deficit data import unit 2115 imports the deficit data XML electronic document including the item changed according to the first embodiment, the item added according to the second embodiment, and the subgroup added according to the third embodiment. To do.
[0206]
In step S2301, it is determined whether the correction category is new (update_type is new).
[0207]
If the determination result in step S2301 is affirmative, the “reflecting process category” of the “red character property table” 291 (see FIG. 49) is set to “create new”.
[0208]
If the determination result of step S2301 is negative, step S319 is performed as in the second embodiment.
[0209]
When step S2303 is performed, step S319 is not performed. Therefore, a record having the same “property ID” as the property ID acquired in step S307 is searched from the “property table” 271, and the “property ID” to “ The “thumbnail image” is not copied to the corresponding columns of the record of the “red character update table” 209 (see FIG. 49) added in step S317, and the “page number” of the record added to the “red character update table” 209 is not performed. In addition, a value read from the red data XML electronic document 2111 is set in “small group number”, but “property ID” to “thumbnail image” of the record are left blank.
[0210]
From step S319 or S2303, the process proceeds to step S321.
[0211]
FIG. 64 shows a screen displayed in the update data editing view for the small set to which the red data return tool 2113 is added after the red data import unit 2115 performs the processing shown in FIG.
[0212]
Referring to FIG. 64, since the property ID corresponding to the added small set is blank, the record in the property table cannot be specified. Therefore, the column of “property data” is blank for all items. The column of “update data” is a copy of “red data” only in an item with red data, and is blank in an item without “red data”. Furthermore, since the property ID corresponding to the added small set is blank, the “update data” column and the “red data” column of “Property ID” are blank.
[0213]
Next, the data confirmation / correction unit 2117 will be described. The data confirmation / correction unit 2117 has functions specific to the third embodiment in addition to the functions of the data confirmation / correction unit 117 of the first embodiment.
[0214]
The operation of the data confirmation / correction unit 2117 is shown in FIG. As is apparent from comparing FIG. 65 with FIG. 35 showing the operation of the data confirmation / correction unit 117 of the first embodiment, steps S351 to S365 and S367 to S369 performed by the data confirmation / correction unit 2117 are the data of the first embodiment. Since these steps are the same as those performed by the confirmation / correction unit 117, description of these steps is omitted, and only the added steps S2351 and S2353 are described.
[0215]
If the determination result in step S351 is negative (if the update data editing view is selected), it is determined whether or not the property data has been called (step S2351). Specifically, this is performed by checking whether or not the “call property data ...” button 2105 in the update data editing view shown in FIG. 64 is pressed.
[0216]
If the determination result in step S2351 is affirmative, the property data is called (step S2353) and then the process proceeds to step S367. If the determination result in step S2351 is negative, the process skips step S2353 and immediately proceeds to step S367. move on.
[0217]
Step S2353 is performed by the property data calling unit 2118. Details of step S2353 will be described with reference to FIG.
[0218]
First, the property data selection dialog shown in FIG. 67 is displayed (step S2361). When the user selects a desired filter (for example, “classify by store”) in the combo box 2107 of the property data selection dialog, the tree view 2109 displays the hierarchical structure of the selected filter. When the user selects a desired node (for example, “MAX Higashikawaguchi”) in the filter hierarchical structure, a query by an SQL sentence associated with the node is executed on the “property table” 271 (see FIG. 48), The result of the inquiry is displayed in the table 2111. When the user selects a row corresponding to the property to which the red data displayed in the update data edit view (see FIG. 64) is to be reflected from the table 2111, and presses an “OK” button 2113 (step S2363), the update data edit The “property table” selected in step S2363 for the “original property ID”, “original property name”, and “reflection processing category” of the record of the “red character property table” 291 whose red data is currently displayed in the view. The values of “property ID” and “property name” of the record 271 and “update” are set (step S2365).
[0219]
Next, “Property ID” to “Thumbnail image” of the record of “Red character update table” 299 (see FIG. 49) whose update data is currently displayed in the update data editing view are respectively selected in Step S2363. The values of “property ID” to “thumbnail image” in the record of the “property table” 271 are set (step S2367).
[0220]
Next, the processing of steps S2371 to S2379 is repeated for “property ID” to “thumbnail image” in the record of the current “red character property table” 291.
[0221]
In step S 2373, is it possible to reflect the current deficit data in the corresponding column of the “property table” 271 by checking whether or not all “four conditions” described in the first embodiment are satisfied? Judge whether or not.
[0222]
When the determination result in step S2371 is affirmative, the contents of the corresponding column of the current record in the “red character update table” 299 are rewritten with red data (step S2373), and the corresponding subgroup in the update data editing view (see FIG. 24) is displayed. The background color of the update data string is set to green (step S2375).
[0223]
If the determination result in step S2371 is affirmative, the contents of the corresponding column of the current record of the “red character update table” 299 are cleared (step S2377), and the corresponding small set is updated in the update data editing view (see FIG. 24). The background color of the data string is set to yellow (step S2379).
[0224]
After the property data call (step S2353) is thus performed, the contents of the table of the update data editing view (see FIG. 64) change to the contents shown in FIG.
[0225]
Accordingly, when the property data call (step S2353) is not performed, the reflection process remains “create new”, whereas when the property data call (step S2353) is performed, the reflection process is performed. Is changed to “update”, and appropriate data for updating is also set in the deficit update table 299.
[0226]
After step S2351 or step S2353, data correction or the like (steps S367 and S369) is performed, and the data of items that need correction is appropriately corrected by the user.
[0227]
Next, the reflecting unit 2119 will be described. The reflection unit 2119 has all the functions of the reflection unit 1119 of the second embodiment, but differs in the following points.
[0228]
The operation of the reflecting unit 2119 is shown in FIG. As is apparent from comparing FIG. 69 with FIG. 56 illustrating the operation of the reflection unit 1119 of the second embodiment, steps S371 to S387 and S1391 performed by the reflection unit 2119 are the same as those performed by the reflection unit 1119 of the second embodiment. is there. The reflection unit 2119 further performs steps S2371 and S2373.
[0229]
In step S2371, it is determined whether or not the “reflection processing category” in the “red-letter property table” 291 is “create new”.
[0230]
If the determination result in step S2371 is affirmative, a new record is added to the “property table” 271 and a new ID is set in “property ID” of the record, and “property name” to “thumbnail image” are set. “Property name” to “thumbnail image” of the current record in the deficit update table 299 are set (step S2373).
[0231]
If the determination result of step S2371 is negative, the process proceeds to step S385.
[0232]
[Embodiment 4]
In the fourth embodiment, the small set included in the DTP data at the stage of rendering is deleted, and the record of the property table in which the data is assigned to the deleted small set is deleted as necessary.
[0233]
Referring to FIG. 70, the apparatus for reflecting deficit data in the database according to the fourth embodiment is roughly divided into DTP software 3103 and deficit data return tool 3113. The DTP software 3103 includes a rendering unit 105 corresponding to an XSL-FO processor, a small group deletion unit 3107, and a red data writing unit 3109. The red data return tool 3113 includes a red data import unit 3115, a data confirmation / correction unit 3117, a record deletion confirmation unit 3118, and a reflection unit 3119. Note that the DTP software 3103 is a computer program as the name indicates, and this function is realized when the computer reads and executes the DTP software 3103. The deficit data return tool 3113 can also be realized by the computer reading and executing a computer program for causing the computer to function as the deficit data return tool 3113.
[0234]
The rendering unit 105 displays a page according to the contents of the allocated XSL-FO electronic document 101. The small group deletion unit 3107 deletes a small group in accordance with a user operation. The red data writing unit 3109 writes the red data as the red data XML electronic document 3111. The red data import unit 3115 imports the red data XML electronic document 3111. The data confirmation / correction unit 3117 confirms and further corrects the red data. The record deletion confirmation unit 3118 allows the record to be deleted if the user decides to delete the record of the property table in which data is assigned to the deleted set immediately after the import. The reflection unit 3119 updates the contents of the property database 121 using the red data.
[0235]
Since the rendering unit 105 is the same as that of the first embodiment, the description thereof is omitted.
[0236]
Next, the operation of the small group deletion unit 3107 will be described.
[0237]
The deletion includes (1) “deletion for each small group” and (2) “deletion of all the small groups included in the deleted page”.
[0238]
“Deletion for each small group” means, for example, that one small group is deleted from the small groups as shown in FIG. 71 (a) to be in a state as shown in FIG. 71 (b). There are two types of operations for “deletion for each small group”. One is to select a part of the small group and select the menu item “Delete small group” from the menu. The entire group is selected and deleted by the delete key.
[0239]
“Deleting all the small groups included in the deleted page” means, for example, deleting a page as shown in FIG. 72 and deleting all three small groups included in the page.
[0240]
FIG. 73 (b) shows an example of the data structure related to the feedback of the red data included in the DTP data after “deletion for each small group” is performed. This data structure is shown in the form of an object class diagram as shown in FIG.
[0241]
Referring to FIG. 73, the page style information includes “deleted property ID array”, “deleted property ID array”, and “deleted date / time array”. . These arrays contain the number of deleted subsets in the page.
[0242]
There is no set style information, box style information, and character style information related to deletion of a set.
[0243]
FIG. 74 shows an example of a data structure related to feedback of deficit data included in DTP data after performing “deletion of all small sets included in deleted page”.
[0244]
As the DTP document style information, there is an array of deleted pages as shown in FIG. The deleted page array element is an object composed of a plurality of items, as shown in FIG. As shown in FIG. 74 (b), the configuration item (property) of this element object includes “deletion date / time of this page”, “number of this page”, “array of property IDs of deleted sub-sets”, “deletion” And “deletion date array of deleted sub-sets”. The “deleted sub-group property ID array”, “deleted sub-group sub-group ID array” and “deleted sub-group deletion date / time array” are the same as those shown in FIG. 73 (b). The array of contains elements for all the pairs included in the deleted page.
[0245]
Next, an operation of “deletion for each small group” performed by the small group deletion unit 3107 will be described with reference to FIG.
[0246]
First, as described above, a user input for deleting a small set is received (step S3201). Next, an element is added to the “array of property IDs of deleted sets” shown in FIG. 73 in the page, and the property ID assigned to the set deleted in step S3201 is set as the element (step S3203). . Next, an element is added to the “array of deleted group IDs” shown in FIG. 73 in the page, and the group ID assigned to the group deleted in step S3201 is set to the element (step S3205). . Next, an element is added to the “deletion date / time array of deleted sets” shown in FIG. 73 in the page, and the current date / time is set in the element (step S3207).
[0247]
Next, an operation of “deletion of all small groups included in the deleted page” performed by the small group deletion unit 3107 will be described with reference to FIG.
[0248]
First, as described above, a user input for page deletion is received (step S3211). Next, a “red data storage page” is created as an object on the memory (step S3213). The object of this “red data storage page” is “the deletion date and time of this page”, “the number of this page”, and “the array of property IDs of deleted sub-sets”, similarly to the element object of the array of deleted pages. , “An array of deleted group IDs” and “an array of deleted date and time of deleted groups” are included as configuration items (properties). Next, all the small groups included in the deleted page are acquired by scanning the page deleted in step S3211 (step S3215). Next, the current date and time is set in “Delete date and time of this page” of “Red character data storage page” (step S3217). Next, the number of the deleted page is set to “page number” of “red character data storage page” (step S3217). Next, the operations in steps S3223 to S3227 are repeated for all the small groups included in the deleted page (step S3221).
[0249]
In step S 3223, an element is added to “arrangement of property IDs of deleted properties” in the “red character data storage page”, and the property ID assigned to the current small set is set as the added element. Next, an element is added to the “array of small group IDs of deleted properties” in the “red character data storage page”, and the small group ID assigned to the current small group is set as the added element (step S3225). Next, an element is added to the “deletion date / time array of deleted property” of the “red-letter data storage page”, and the current date and time is set to the added element (step S3227).
[0250]
If the loop of step S3221 is exited, an element is added to the “deleted page array” in the DTP document, the “red data storage page” is copied to the added element, and the “red data storage page” is set. Discard (step S3229).
[0251]
Next, the deficit data writing unit 2109 will be described.
[0252]
The structure of the red data XML electronic document 3111 output by the red data writing unit 3109 is as shown in FIG.
[0253]
The structure of the red data XML electronic document 3111 shown in FIG. 77 is the same as the structure of the red data XML electronic document 111 shown in FIG. 21, but the “Property” hierarchy is the lowest layer and the “Item” hierarchy is present. No.
[0254]
A specific example of the red data XML electronic document 3111 generated by the red data writing unit 3109 based on the style information shown in FIGS. 73 and 74 is shown in FIG.
[0255]
Referring to FIG. 78, for page 16, The value of "page_no" in the <page> tag is "116" The value of “update_type” of the <bukken> tag is “del” indicating deletion. For page 120, The value of "page_no" in the <page> tag is "120-del20021219101120", which is a combination of the page number "120" and "-del" and the deletion date and time "20021219101120". about The value of “update_type” of the <bukken> tag is “del” indicating deletion.
[0256]
Next, the operation of the red data writing unit 3109 will be described with reference to FIG.
[0257]
Referring to FIG. 79, first, the DTP document is scanned, and the DTP document hierarchy data (example shown in FIG. 74) necessary for creating red data written in the DTP document is read (step S3231). Next, in the loop of step S3233, the deficit data about the small set deleted by “deletion of all the small sets included in the deleted page” is written, and in the loop of step S3241, it is deleted by “deletion for each small set”. Write out deficit data for the small group.
[0258]
In the loop of step S3233, steps S3235-S3239 are repeated for all elements of the “deleted page arrangement” (see FIG. 74).
[0259]
In step S3235, Export <page> tag. In the tag “page_no”, the character combination described above is described. Next, step S3239 is repeated for all elements in the array item of the element object “array of deleted pages” (step S3237). In step S3239, Write <bukken> tag. The tags “kgm_seq”, “bkn_id”, and “update_type” describe the small group ID of the current small group, the property ID of the current small group, and “del”, respectively.
[0260]
Next, in the loop of step S3241, steps S3243 to S3249 are repeated.
[0261]
In step S3243, the page is scanned, and page hierarchy data (example shown in FIG. 73) necessary for creating red data written in the DTP document is read. next, Export <page> tag. The tag “page_no” describes the current page number. Next, step S3249 is repeated for the deleted small set of the current page (step S3247). In step S3249, Write <bukken> tag. The tags “kgm_seq”, “bkn_id”, and “update_type” describe the small group ID of the current small group, the property ID of the current small group, and “del”, respectively.
[0262]
Next, the deficit data return tool 3113 uses the tables shown in FIGS. 48 to 50 as in the deficit data return tool 1113 of the second embodiment.
[0263]
Next, the red data import unit 3115 will be described. The red data import unit 3115 has functions specific to the fourth embodiment in addition to the functions of the red data import unit 2115 of the third embodiment.
[0264]
The operation of the red data import unit 3115 is shown in FIG. As is apparent from comparing FIG. 80 with FIG. 63 illustrating the operation of the deficit data import unit 2115 of the third embodiment, steps S301 to S317, S2301, S2303, S319 to 323, S1301 to S1309, performed by the deficit data import unit 3115, Since S325 to S345 are the same as those performed by the red data import unit 2115 of the third embodiment, description of these steps will be omitted, and only the added step S3301 will be described. The deficit data import unit 3115 includes a red character including the item changed according to the first embodiment, the item added according to the second embodiment, the sub-set added according to the third embodiment, and the sub-set deleted according to the fourth embodiment. Assume that data XML electronic document is imported.
[0265]
In step S3301, it is determined whether or not the DTP processing category is “deleted”. Specifically, the deficit data XML electronic document 3111 Check whether the value of the item “update_type” of the <bukken> tag is “del”.
[0266]
If the determination result in step S3301 is affirmative, the process proceeds to step S321. By skipping the repetition for the <item> tag and proceeding to step S307, the next Start processing for <bukken> tag. In step S321 The <item> tag is not repeated This is because there is no <item> tag.
[0267]
FIG. 81 shows a screen displayed in the update data editing view for the small set from which the red data return tool 3113 has been deleted after the red data import unit 3115 performs the processing shown in FIG. In the screen shown in FIG. 81, the deleted table (the group to which “Ultima G Multi” is assigned) on page 116 is displayed in the table on the right side. Also, the deleted page 120, which is a deleted page, is displayed lightly in the left tree view. The property data of the deleted page can also be displayed in the table on the right side by selecting it in the tree view on the left side.
[0268]
Referring to FIG. 81, since there is no red data for the deleted small set, the red data column is blank. In addition, since the property ID of the property data assigned to the deleted subgroup has been acquired, a record having the property ID is searched from the property table, and the value of each column of the record is updated to the property data column and Displayed in the data column.
[0269]
In the initial state shown in FIG. 81, the record of the property ID is not deleted from the property table even if the reflection process is performed. Even if a small group is deleted in DTP, it is simply deletion in DTP, and there is a possibility that deletion of property data from the property table is not intended. Accordingly, when the user who has viewed the screen of FIG. 81 determines to delete the record of the property data currently displayed on the screen of FIG. 81 from the property table, the user presses the “Delete from DB” button 3001. As a result, the display format of the tree view for the currently displayed property data changes, and the background of the update data column changes to red for all rows. Due to such changes, the user can know that the record of the property data assigned to the deleted small set will be deleted from the property table when the reflection process is performed from now on.
[0270]
Thus, when the reflection process is performed, the record of the property data for which “Delete from DB” 3001 is pressed is deleted from the property table. On the other hand, even if the reflection process is performed, the record of the property data for which the “delete from DB” button 3001 is not pressed does not have to be deleted from the property table.
[0271]
Next, the data confirmation / correction unit 3117 will be described. The data confirmation / correction unit 3117 has functions specific to the fourth embodiment in addition to the functions of the data confirmation / correction unit 117 of the first embodiment.
[0272]
The operation of the data checking / modifying unit 3117 is shown in FIG. As is apparent from a comparison of FIG. 82 and FIG. 35 showing the operation of the data confirmation / correction unit 117 of the first embodiment, steps S351 to S365 and S367 to S369 performed by the data confirmation / correction unit 3117 are the data of the first embodiment. Since these steps are the same as those performed by the confirmation / correction unit 117, description of these steps is omitted, and only the added steps S3351 and S3353 are described.
[0273]
If the determination result in step S351 is negative (if the update data edit view is selected), is it selected to delete the record of the property data currently displayed in the update data edit view from the property table? It is determined whether or not (step S3351). Specifically, this is performed by checking whether or not the “delete from DB” button 3001 in the update data editing view shown in FIG. 81 is pressed.
[0274]
If the determination result in step S3351 is affirmative, a process of deleting from the database (step S3353) is performed, and then the process proceeds to step S367. If the determination result in step S3351 is negative, step S3353 is skipped and the step is immediately performed. The process proceeds to S367.
[0275]
Step S3353 is performed by the record deletion confirmation unit 3118. Details of step S3353 will be described with reference to FIG.
[0276]
First, the “reflecting process category” of the corresponding record in the deficit property table 291 (see FIG. 49) is set to “delete” (step S3361). Here, the corresponding record is a record having the same “original property ID” as the property ID currently displayed in the update data editing view. Next, the background color of all the rows in the update data sequence of the relevant small set in the update data editing view is changed to red, and the icon in the small tree view is changed (step S3363). Here, the applicable small group is a small group currently displayed in the update data editing view.
[0277]
Next, the reflecting unit 3119 will be described. The reflection unit 2119 has all the functions of the reflection unit 2119 of the third embodiment, but differs in the following points.
[0278]
The operation of the reflecting unit 3119 is shown in FIG. As is apparent from comparing FIG. 84 with FIG. 69 illustrating the operation of the reflection unit 2119 of the third embodiment, steps S371 to S387, S2371, S2373, and S1391 performed by the reflection unit 3119 are performed by the reflection unit 2119 of the third embodiment. It is the same as that. The reflection unit 3119 further performs steps S3371 and S3373.
[0279]
In step S3371, it is determined whether or not the “reflection processing category” in the “red-letter property table” 291 is “delete”.
[0280]
If the determination result in step S3371 is affirmative, a record having the same “property ID” as the “original property ID” of the current record in the “red character property table” 291 is deleted from the “property table” 271 (step S3373). ).
[0281]
【The invention's effect】
As described above, according to the present invention, deficit data input on DTP can be reflected in the database automatically or after partial correction.
[0282]
Moreover, it becomes possible to manage the property extracted from the database in a small set.
[0283]
Furthermore, it is possible to maintain a highly reliable database by not reflecting all the data describing the correction contents in the database as they are, but by reflecting the correction contents in the database after efficiently checking the correction contents.
[0284]
Furthermore, the value of the item added on the DTP can be reflected in the database.
[0285]
Further, if the name of the item added on the DTP matches the name of the column in the database table, the value of the item added on the DTP can be reflected in the database almost automatically.
[0286]
Furthermore, if the name of the item added on the DTP does not match the name of any column of any table in the database, the user selects the column of the database table that should reflect the value of the added item. can do.
[0287]
Furthermore, when a small set is added on the DTP, the values set for each item of the added small set can be reflected in an existing record or a new record in the database table.
[0288]
Furthermore, when a small set is deleted on the DTP, a record in which data is assigned to the deleted small set can be automatically deleted from the database table.
[Brief description of the drawings]
FIG. 1 is a block diagram showing a configuration of a reflection device for reflecting deficient data in a database according to Embodiment 1 of the present invention;
FIG. 2 is a first part of an example of an XSL-FO electronic document that does not take into account deficit data reflection according to Embodiment 1 of the present invention;
FIG. 3 is a second part of an example of an XSL-FO electronic document that does not take into account deficit data reflection according to Embodiment 1 of the present invention;
FIG. 4 is a diagram showing a screen rendered by a rendering unit based on an XSL-FO electronic document that does not take into account deficit data reflection according to Embodiment 1 of the present invention;
FIG. 5 is a diagram showing the structure of a DTP document created based on an XSL-FO electronic document that does not take into account deficit data reflection according to the first embodiment of the present invention in the form of an object class diagram.
FIG. 6 is a flowchart illustrating a method for creating a DTP document based on an XSL-FO electronic document that does not take into account deficit data reflection performed by the rendering unit according to the first embodiment of the present invention;
FIG. 7 is a flowchart showing details of the character data creation step shown in FIG. 6;
FIG. 8 is a first part of an example of an XSL-FO electronic document considering deficit data reflection according to the first embodiment of the present invention;
FIG. 9 is a second part of an example of an XSL-FO electronic document considering deficit data reflection according to the first embodiment of the present invention;
FIG. 10 is a diagram showing the structure of a DTP document created based on an XSL-FO electronic document in consideration of deficit data reflection according to Embodiment 1 of the present invention in the form of an object class diagram.
FIG. 11 is a flowchart illustrating a method for creating a DTP document based on an XSL-FO electronic document in consideration of deficit data reflection performed by the rendering unit according to the first embodiment of the present invention;
12 is a flowchart showing details of steps for creating character data shown in FIG. 11. FIG.
FIG. 13 is a diagram showing a screen rendered by a rendering unit based on an XSL-FO electronic document in consideration of deficit data reflection according to Embodiment 1 of the present invention;
FIG. 14 is a first diagram for explaining correction of text data by a correction unit according to the first embodiment of the present invention;
FIG. 15 is a second diagram for explaining correction of text data by the correction unit according to the first embodiment of the present invention;
FIG. 16 is a first diagram for explaining image link correction by the correction unit according to the first embodiment of the present invention;
FIG. 17 is a second diagram illustrating the correction of the image ring by the correction unit according to the first embodiment of the present invention.
FIG. 18 is a third diagram for explaining image link correction by the correction unit according to the first embodiment of the present invention;
FIG. 19 is a flowchart showing a data correction method performed by the data correction unit according to the first embodiment of the present invention;
FIG. 20 is a flowchart showing a method of writing red data to a red data XML electronic document performed by the red data writing unit according to the first embodiment of the present invention;
FIG. 21 is a diagram showing the structure of a red data XML electronic document according to Embodiment 1 of the present invention in an XML format.
FIG. 22 is a diagram showing an example of a deficit data XML electronic document according to the first embodiment of the present invention.
FIG. 23 is a diagram showing an initial state of a red data list view displayed by the red data return tool according to Embodiment 1 of the present invention;
FIG. 24 is a diagram showing a state during editing of an update data editing view displayed by the deficit data return tool according to the first embodiment of the present invention.
FIG. 25 is a diagram showing a state in which a red data list view displayed by the red data return tool according to the first embodiment of the present invention is being edited.
FIG. 26 is a diagram showing a dialog screen for replacement displayed by the data confirmation / correction unit according to the first embodiment of the present invention.
FIG. 27 is a diagram showing a state after the replacement process by the data confirmation / correction unit of the red data list view displayed by the red data return tool according to the first embodiment of the present invention is performed.
FIG. 28 is a diagram showing a state when a duplication check is performed by the data confirmation / correction unit of the red data list view displayed by the red data return tool according to the first embodiment of the present invention.
FIG. 29 is a diagram showing a dialog screen for inputting sort conditions displayed by the data checking / modifying unit according to the first embodiment of the present invention.
FIG. 30 is a diagram showing a state after a sorting process is performed by a data confirmation / modification unit of a deficit data list view displayed by the deficit data return tool according to the first embodiment of the present invention;
FIG. 31 is a diagram showing a state when the data checking / modifying unit of the red data list view displayed by the red data return tool according to the first embodiment of the present invention inputs the search condition and a state after performing the search. is there.
FIG. 32 is a first diagram showing a table used in the apparatus for reflecting deficit data to a database according to the first embodiment of the present invention;
FIG. 33 is a second diagram showing a table used in the apparatus for reflecting deficit data to the database according to the first embodiment of the present invention;
FIG. 34 is a flowchart showing a red data import method performed by a red data import unit according to Embodiment 1 of the present invention;
FIG. 35 is a flowchart showing a data correction method performed by the data confirmation / correction unit according to the first embodiment of the present invention;
FIG. 36 is a flowchart showing a method of reflecting deficit data in a database performed by the reflection unit according to the first embodiment of the present invention;
FIG. 37 is a block diagram showing a configuration of a reflection device for reflecting deficient data in a database according to Embodiment 2 of the present invention;
FIGS. 38A and 38B are diagrams showing states before and after adding a text item to a text box according to the second embodiment of the present invention. FIGS.
FIG. 39 is a diagram showing a dialog screen used when a text item is added to a text box in the second embodiment of the present invention.
FIGS. 40A and 40B are diagrams showing states before and after adding an inline image item to a text box according to the second embodiment of the present invention. FIGS.
FIG. 41 is a diagram showing a dialog screen used when an item name of an inline screen added to a text box is input in the second embodiment of the present invention.
FIG. 42 is a diagram showing a menu used when a box is newly added to a small group in the second embodiment of the present invention.
FIG. 43 is a diagram showing a small set to which a box is added in the second embodiment of the present invention.
FIG. 44 is a diagram showing a data structure embedded in DTP data and an example of its contents in Embodiment 2 of the present invention.
FIG. 45 is a flowchart showing an operation of an item adding unit according to the second embodiment of the present invention.
FIG. 46 is a diagram showing a structure XML format of a deficit data XML electronic document generated by a deficit data writing unit according to the second embodiment of the present invention.
FIG. 47 is a diagram showing an example of a deficit data XML electronic document according to the second embodiment of the present invention.
FIG. 48 is a first diagram showing a table used in the apparatus for reflecting deficit data to a database according to the second embodiment of the present invention;
FIG. 49 is a second diagram showing a table used in the apparatus for reflecting deficit data to the database according to the second embodiment of the present invention;
FIG. 50 is a third diagram showing a table used in the apparatus for reflecting deficit data to the database according to the second embodiment of the present invention;
FIG. 51 is a flowchart showing a method for importing red data performed by a red data unit according to Embodiment 2 of the present invention;
FIG. 52 is a flowchart showing a data correction method performed by a data confirmation / correction unit according to the second embodiment of the present invention;
FIG. 53 is a flowchart showing a method for setting an unknown update destination data performed by an update destination unknown data setting unit according to the second embodiment of the present invention;
FIG. 54 is a diagram showing a screen displayed by an update destination unknown data setting unit according to the second embodiment of the present invention.
FIG. 55 is a diagram illustrating a main part of a screen displayed by the data confirmation / correction unit after the data confirmation / correction unit and the update destination unknown data setting unit according to the second embodiment of the present invention perform correction and setting.
FIG. 56 is a flowchart showing a method of reflecting deficit data in a database performed by a reflection unit according to the second embodiment of the present invention.
FIG. 57 is a block diagram showing a configuration of a reflection device for reflecting deficient data in a database according to Embodiment 3 of the present invention;
FIG. 58 is a diagram showing a change in the screen accompanying the operation of the small group adding unit according to the third embodiment of the present invention.
FIG. 59 is a diagram showing a data structure embedded in DTP data and an example of its contents in the third embodiment of the present invention.
FIG. 60 is a flowchart showing the operation of the small group adding unit according to the third embodiment of the present invention.
FIG. 61 is a diagram showing a structure XML format of a deficit data XML electronic document generated by a deficit data writing unit according to the third embodiment of the present invention;
FIG. 62 is a diagram showing an example of a deficit data XML electronic document according to Embodiment 3 of the present invention.
FIG. 63 is a flowchart showing a method for importing red data performed by a red data portion according to Embodiment 3 of the present invention;
FIG. 64 is a diagram showing an update data editing view state that the deficit data return tool according to the third embodiment of the present invention first displays for the additional small set.
FIG. 65 is a flowchart showing a data correction method performed by a data confirmation / correction unit according to the third embodiment of the present invention;
FIG. 66 is a flowchart showing a property data calling method performed by the property data calling unit according to the third embodiment of the present invention.
FIG. 67 is a diagram showing a screen for selecting a record in the property table displayed by the property data calling unit according to the third embodiment of the present invention.
FIG. 68 is a view showing an update data edit view state displayed after the red letter data return tool according to the third embodiment of the present invention assigns a record of a property table for an additional small set.
FIG. 69 is a flowchart showing a method for reflecting deficit data in a database performed by a reflection unit according to the third embodiment of the present invention;
FIG. 70 is a block diagram showing a configuration of an apparatus for reflecting deficit data to a database according to Embodiment 4 of the present invention;
FIG. 71 is a diagram for explaining “deletion for each small group” according to the fourth embodiment of the present invention;
FIG. 72 is a diagram for explaining “deletion of all small sets included in a deleted page” according to the fourth embodiment of the present invention;
FIG. 73 is a diagram showing a data structure embedded in DTP data and an example of its contents when “deletion for each small set” is performed in the fourth embodiment of the present invention;
74 is a diagram showing a data structure embedded in DTP data and an example of its contents when “deletion of all small sets included in a deleted page” is performed in the fourth embodiment of the present invention. FIG.
FIG. 75 is a flowchart showing an operation when “deletion for each small group” is performed by the small group addition unit according to the third embodiment of the present invention;
FIG. 76 is a flowchart showing an operation in the case of performing “deletion of all small groups included in a deleted page” of the small group adding unit according to the third embodiment of the present invention;
FIG. 77 is a diagram showing a structure XML format of a deficit data XML electronic document generated by a deficit data writing unit according to the fourth embodiment of the present invention;
FIG. 78 is a diagram showing an example of a deficit data XML electronic document according to Embodiment 4 of the present invention;
FIG. 79 is a flowchart showing a method of writing red data to a red data XML electronic document performed by a red data writing unit according to Embodiment 4 of the present invention;
FIG. 80 is a flowchart showing a red data import method performed by a red data import unit according to Embodiment 4 of the present invention;
FIG. 81 is a diagram showing an update data editing view state that is initially displayed for a small set from which the deficit data return tool according to the fourth embodiment of the present invention has been deleted;
FIG. 82 is a flowchart showing a data correction method performed by a data confirmation / correction unit according to the fourth embodiment of the present invention;
FIG. 83 is a flowchart showing a record deletion confirmation method performed by a record deletion confirmation unit according to Embodiment 4 of the present invention;
FIG. 84 is a flowchart illustrating a method for reflecting deficit data in a database performed by a reflecting unit according to the fourth embodiment of the present invention.
[Explanation of symbols]
101 Allocated XSL-FO electronic document
103, 1103, 2103, 3103 DTP software
105 Rendering unit
107 Data correction section
109, 1109, 2109, 3109 Deficit data export section
111, 1111, 2111 Red data XML electronic document
113, 1113, 2113, 3113 Red data return tool
115, 1115, 2115, 3115 Red data import section
117, 1117, 2117, 3117 Data confirmation / correction unit
119, 1119, 2119, 3119 Reflection unit
121 Property Database
1107 Item addition part
1118 Update destination unknown data setting part
2107 Small group additional part
2118 Property data calling part
3107 Small group deletion part
3118 Record deletion confirmation part

Claims (2)

A rendering device that generates DTP data based on an electronic document for rendering,
For at least one page, one or more fo: block-container tags representing a subset are described in the fo: page-sequence tag representing the page of the DTP data, and at least the fo: block-container representing the subset. One or more fo: block-container tags representing a text box or an image box are described in the tag, and an XSL-FO (eXtensible Stylesheet having a character style hierarchy tag in the fo: block-container tag representing the text box a Language-Formatting Object) electronic documents, fo represents the subassembly: the attribute data of the block-container tag has a small set ID and property ID, representing the text box fo: b as attribute data of the ock-container tag has the sequence of the item name of the array and poured database entry path of the database item poured, as attribute data of the tag of the text style hierarchy, path database items, Based on what has information indicating the item name of the database item, the flow order of the database item, and the presence / absence of the database item replacement process, one or more virtual regions representing a small group are configured in the at least one page. ,
Further, for the at least one page, DTP data in which at least a text box or an image box is configured in each subgroup, and when expressed hierarchically, the subgroup has a subgroup hierarchy below the page hierarchy. A hierarchy of text boxes and a hierarchy of image boxes below, having at least a character style hierarchy below the text box, wherein at least the small group ID and the property ID are described in the small group hierarchy, In the hierarchy of the text box, there are at least an array of paths of the database items that have been poured in, an array of database item names that have been fed in, an ordering sequence of the database items that have been fed in, and an array of update dates and times of the database items that have been fed in. Described, and at least the database entry in the character style hierarchy. Path, the item name of the database item, the flow order of the database item, and information indicating the presence / absence of the replacement process of the database item are described, and at least the array of the path of the flowed database item is arranged in the hierarchy of the image box And a rendering device that generates an array of item names of the database items that have been inserted, an array of an order in which the database items have been merged, and an array of update dates and times of the database items that have been merged. There,
A small group creating means for generating the small group ID and the property ID based on the small group ID and the property ID of the XSL-FO electronic document, respectively, and writing the generated small group ID in the hierarchy of the small group of the DTP data;
The XSL includes an array of paths of the flowed database items, an array of the flowed database item names, a flow order of the flowed database items, and an update date / time of the flowed database items, respectively. A text box of the DTP data generated based on the array of the path of the database item that has been inserted in the FO electronic document, the array of the database item name that has been inserted, the sequence of the database item that has been poured in, and a predetermined value. Text box creation means to write to the hierarchy of
The path of the database item, the item name of the database item, the flow order of the database item, and the information indicating the presence / absence of the replacement process of the database item, respectively, the path of the database item of the XSL-FO electronic document, the database A character style applying unit that generates the information based on the item name of the item, the flow order of the database items, and information indicating the presence or absence of the replacement processing of the database items, and writes the information to the character style hierarchy of the DTP data;
An array of paths of the database items that have been poured in, an array of item names of the database items that have been fed in, an ordering sequence of the database items that have been fed in, and an array of update dates and times of the database items that have been fed in, respectively. Generated on the basis of an array of paths of the database items that have been inserted into the XSL-FO electronic document, an array of item names of the database items that have been inserted, a sequence of the database items that have been poured in, and a predetermined value, and the DTP Image box creation means for writing data into the image box;
A rendering device comprising: A rendering method for generating DTP data on a computer based on an electronic document for rendering, wherein, for at least one page, fo: block- representing a small set in a fo: page-sequence tag representing the page of the DTP data. One or more container tags are described, and at least one fo: block-container tag representing a text box or an image box is described in the fo: block-container tag representing the small set, and represents the text box fo: an XSL-FO (eXtensible Stylesheet Language-Formatting Object) electronic document having a tag of a character style hierarchy in a block-container tag, and fo: block-conta The attribute data of the ner tag has a small group ID and the property ID, and the attribute data of the fo: block-container tag representing the text box includes the array of the path of the database item that has been inserted and the item name of the database item that has been injected As the attribute data of the tag of the character style hierarchy, the database item path, the database item item name, the database item flow order, and the information indicating the presence or absence of the database item replacement process are used as the attribute data. A virtual region or regions representing a small group in the at least one page;
Further, for the at least one page, DTP data in which at least a text box or an image box is configured in each subgroup, and when expressed hierarchically, the subgroup has a subgroup hierarchy below the page hierarchy. A hierarchy of text boxes and a hierarchy of image boxes below, having at least a character style hierarchy below the text box, wherein at least the small group ID and the property ID are described in the small group hierarchy, In the hierarchy of the text box, there are at least an array of paths of the database items that have been poured in, an array of database item names that have been fed in, an ordering sequence of the database items that have been fed in, and an array of update dates and times of the database items that have been fed in Described, and at least the database entry in the character style hierarchy. Path, the item name of the database item, the flow order of the database item, and information indicating the presence / absence of the replacement process of the database item are described, and at least the array of the path of the flowed database item is arranged in the hierarchy of the image box And a rendering method characterized by generating an array of item names of the database items that have been inserted, an array of sequence of the database items that have been merged, and an array of update dates and times of the database items that have been merged. A small group creating step of generating the small group ID and the property ID based on the small group ID and the property ID of the XSL-FO electronic document and writing the small group ID and the property ID in the small group hierarchy of the DTP data, respectively, The text box is created by the text box creating means. The XSL-FO electronic document includes an array of database item paths, an array of database item names that have been poured in, an ordering sequence of the database items that have been poured in, and an update date / time of the database items that have been fed in. Are generated based on the array of paths of the database items that have been inserted, the array of database item names that have been merged, the sequence of the database items that have been merged, and a predetermined value, and are written in the text box hierarchy of the DTP data Information indicating the path of the database item, the item name of the database item, the flow order of the database item, and the presence / absence of the replacement processing of the database item, respectively, by the text box creation step and the character style applying means, FO electronic document Character style application that is generated based on information indicating the path of the database item, the item name of the database item, the flow order of the database item, and the presence / absence of replacement processing of the database item, and written to the character style hierarchy of the DTP data And an array of paths of the database items that have been fed in, an array of item names of the database items that have been fed in, an ordering sequence of the database items that have been fed in, and a database item that has been fed in The update date / time array of the XSL-FO electronic document includes an array of the paths of the database items that have been inserted, an array of item names of the database items that have been injected, a flow order of the database items that have been injected, and a predetermined number. Generated on the basis of the value D Program for executing a rendering method characterized by comprising: a picture box creation step of writing the image box P data.

Images