JP2004302684A - Data input method, input support device, and program - Google Patents

Abstract

Provided is a data input method capable of efficiently inputting set type data composed of a plurality of element data, and an input support device using the same.
For each item, as a data type of a value, a selection is made from a plurality of items in which a type of set-type data composed of a plurality of element data and a type of element data constituting the set-type data are determined. An input format corresponding to a combination of the type of set-type data and the type of element data predetermined for the selected input target item is selected, and element data is generated by element data and operation according to the selected input format. At least one of the calculation rule for generating the element data and the processing procedure for generating the element data is input as the input data for generating the value of the first item, and the value to be input is determined based on the input data. Generate.
[Selection diagram] Fig. 1

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
For example, the present invention relates to an input support device for content data of an electronic catalog.
[0002]
[Prior art]
The data expressing the technical information of parts represented by the electronic catalog of the ISO 13584 standard describes a "dictionary" that provides a vocabulary for expressing each part and the technical specifications of the actual product based on the "dictionary". It consists of “content data” (for example, see Non-Patent Documents 1, 2, and 4).
[0003]
In the "dictionary" of the ISO13584 standard, a product category expressed on a tree as a concept hierarchy and a technical attribute (property item: property) to which the product category belongs are main dictionary elements. And so on. On the other hand, content data is mainly registered as actual product information by an actual parts supplier or the like using the aforementioned standardized dictionary.
[0004]
In recent years, attempts have been made in various industries to realize inter-company electronic commerce using an electronic catalog based on ISO13584. For example, in the heavy electrical industry, a “JeMarche” project is being pursued with the aim of commercializing cross-industry supply chain management (for example, see Non-Patent Document 3).
[0005]
In “JeMarche”, based on the provisions of ISO 13584-42, simple type data (integer (Int) type, real number (Real) type, character (String) type, Boolean algebra (Boolean) type, choice (ENUM) Type) has been developed in the form of a table.
[0006]
In addition, a technology has been developed in which content data of simple type data is dynamically generated at the time of content data search by describing constraints between specification items (for example, see Patent Document 1).
[0007]
In recent years, as specific applications have progressed, the need for expansion to collective data capable of expressing more complex data has been increasing, and IEC61360, which stipulates the application of ISO13584 in the electric and electronic fields, has set as set data as set data. Type, List type, Bag type, Array type and the like are newly added.
[0008]
[Non-patent document 1]
ISO 13584-42: Industrial Automation Systems and Integration-Parts Library
[0009]
[Non-patent document 2]
IEC61360-1: Standard data elementtypes with associated classification Scheme for electrical components
[0010]
[Non-Patent Document 3]
[Retrieved February 5, 2003], Internet <URL: http: // www. jemarche. com / >>
[0011]
[Non-patent document 4]
FY1999 IPA project: Experimental work on "Construction of a complex SCM platform with SMEs in the heavy electrical crisis manufacturing industry"-External Design Book II, "Electronic Catalog"
[0012]
[Patent Document 1]
JP-A-11-85836
[0013]
[Problems to be solved by the invention]
However, in the conventional method of creating content data, since element data is targeted for input to one simple data type, when inputting set-type data including a plurality of element data, all elements of the set are It is difficult to input data as a concatenated character string or to simply input each element one by one.
[0014]
In view of the above problems, an object of the present invention is to provide a data input method capable of efficiently inputting set type data composed of a plurality of element data, and an input support device using the same. I do.
[0015]
[Means for Solving the Problems]
According to the present invention, for each of a plurality of items, set-type data composed of a plurality of element data is input as a value thereof, and each of the plurality of items has a value corresponding to each item. As the data type, the type of set-type data composed of a plurality of element data and the type of element data constituting the set-type data are determined, and the input target item selected from the plurality of items is determined in advance. A calculation rule for selecting an input format corresponding to a predetermined combination of the type of the set type data and the type of the element data, and generating the element data by the element data and the operation according to the selected input format And inputting at least one of the processing procedures for generating the element data as input data for generating the value of the first item; Based, to produce a value of said input object. ADVANTAGE OF THE INVENTION According to this invention, instead of inputting each element of the set type data which consists of several element data one by one, input by calculation rules and a processing procedure is enabled, Erroneous input can be reduced and data can be input efficiently.
[0016]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.
[0017]
In the present embodiment, a description will be given of an electronic catalog content creation system to which a data input method that facilitates input when content data is collective data is applied, using collective data defined by ISO13584 and IEC61360 as an example.
[0018]
The content data is input as a value corresponding to a specification item described later.
[0019]
Here, the collective data is data composed of a plurality of element data of a predetermined data type, and the simple data is data composed of one element data. Here, as the types of the collective data, for example, the following five types classified according to the rules of ISO13584 are used.
[0020]
-Set type (set that does not allow duplicate elements)
Constraint_Set type (one type of Set type whose subset can be used as content)
-Bag type (set that allows duplicate elements)
-List type (set in which the order of the elements is determined)
・ Array type (array type)
Some of the above-mentioned set type data further has the following attributes. That is,
“Uniqueness” is for setting whether or not element duplication is permitted. If uniqueness is required, “TRUE” is set, and if element duplication is possible, “FALSE” is set. “Uniqueness” can be set in a List type and an Array type.
[0021]
“Optional” is a setting of whether or not to allow a null value (Null) to be included in a plurality of elements. The value is “TRUE” when possible, and “FALSE” when prohibited. Take. “Optional” can be set in an Array type.
[0022]
The types of the collective data are not limited to the above five types, and there may be collective data other than the above.
[0023]
Int (integer), Int_measure (integer with unit), Int_currency (integer with monetary unit), Real (real number), Real_measure (real number with unit), Real_currency (Real number with money unit), String (character string), Boolean (Boolean), date (date), ENUM (choice type), Level (minimum value, nominal value, representative value, maximum value) And Real). This basic data type is also in accordance with the provisions of ISO13584, but is not limited to the above data type, and there may be other data types.
[0024]
The content data includes simple type data in addition to the collective type data, and the simple type data is composed of one element.
[0025]
(Configuration of electronic catalog content creation system)
FIG. 1 is a block diagram showing a functional configuration of an electronic catalog content creation system to which the input support device of the present invention is applied. The dictionary data storage unit 1, the electronic catalog content data editing unit 2, the input type selection rule editing unit 3, Input type selection rule storage unit 4, input type selection unit 5, input form editing unit 6, input form storage unit 7, generation rule editing unit 8, generation rule storage unit 9, content data generation unit 10, electronic catalog content data storage unit 11 and an interface unit 12.
[0026]
The interface unit 12 is composed of various input devices such as a keyboard and a mouse, and output devices such as a display, from which various instructions and data are input to the electronic catalog content data editing unit 2 by user operation.
[0027]
The electronic catalog content data editing unit 2 reads the dictionary data stored in the dictionary data storage unit 1 based on a user operation from the interface unit 12, and stores the dictionary data in the electronic catalog content data storage unit 11 corresponding to the dictionary data. Edit and save the content data.
[0028]
The electronic catalog content data editing unit 2 processes the input type selection rule editing unit 3, the input form editing unit 6, the generation rule editing unit 8, the content data generation unit 10, and the like according to the operation command input from the interface unit 12. Switch.
[0029]
FIG. 2 shows the data structure of the dictionary data stored in the dictionary data storage unit 1. Here, the data is expressed as tabular data. The dictionary element 201 is represented as one line. Each field of the dictionary element is configured by extracting a part necessary for the description of the present embodiment from among the requirements defined in ISO13584. That is, each dictionary element has an identification code 202 of the dictionary element, a specification item name 203, a unit 204, and information indicating whether the data type of content data corresponding to the specification item is simple type data or set type data (simple type). Type data (Simple) / set type data type (Complex) 205, presence / absence of a uniqueness request for the element of the set type data (“Uniqueness”) 206, presence / absence of null value permission for the element of the set type data (“Optional”) ) 207, a basic data type (Data Type) 208, dictionary element definitions 209, and dictionary element notes 210.
[0030]
In the case of ISO13584, when the basic data type is “ENUM type”, it is necessary to determine a discrete value of possible values in advance.
[0031]
In the present embodiment, the selection element 211 in the ENUM type dictionary element is expressed as one line. The selection element includes a dictionary element identification code 212, a name 213, a selection element value 214, and a selection element value 214. Consists of definition 215.
[0032]
FIG. 3 shows a specific example of one set of content data (product (parts) data) for a certain product stored in the electronic catalog content data storage unit 11. The product (parts) data shown in FIG. 3 includes data 2001 of each dictionary element as shown in FIG. 2 and content data 2002 as a value corresponding to each dictionary element.
[0033]
When the operation command from the user is “input request”, the input type selection rule editing unit 3 outputs the set type data when the data type of the content data corresponding to the specified item is set type data. Of the input type and the basic data type of the element, a rule for selecting an input type (input type determination rule), and an inspection for selecting an inspection process to be used when generating content data that is collective data Create and edit process selection rules.
[0034]
The input type selection rule and the inspection process selection rule created and edited by the input type selection rule editing unit 3 are stored in the input type selection rule storage unit 4.
[0035]
When the operation command from the user is “input request” and the data type of the content data corresponding to the specified specification item is set-type data, the input type selection unit 5 It is started from. Referring to the input type selection rule and the inspection processing selection rule stored in the input type selection rule storage unit 4, the input type and the inspection processing are determined based on the type of the set type data and the basic data type of the element. select.
[0036]
FIG. 4 shows an example of an input type selection rule stored in the input type selection rule storage unit 4. FIG. 5 shows an example of an inspection processing selection rule stored in the input type selection rule storage unit 4. It is shown.
[0037]
As shown in FIGS. 4 and 5, both the input type selection rule and the inspection processing selection rule arrange the types of the set type data in the horizontal axis direction (see the area 301 in FIG. 4), and the basic data type in the vertical axis direction. It is represented by a matrix in which the types of the types are arranged (see the area 302 in FIG. 5).
[0038]
The elements of the matrix shown in FIG. 4 represent the input type corresponding to the type of the aggregate data and the type of the basic data type corresponding to each of the column and row to which the element belongs. That is, this matrix determines one input type according to the type of the aggregate data and the basic data type.
[0039]
The elements of the matrix shown in FIG. 5 represent the inspection processing corresponding to the type of the collective data and the type of the basic data type corresponding to each of the column and row to which the element belongs. In other words, this matrix determines one set of inspection processing according to the type of the aggregation type data and the basic data type.
[0040]
In the matrices shown in FIGS. 4 and 5, the input type and the inspection process are stored as character information.
[0041]
The input type selection rule and the inspection processing selection rule are edited by the input type selection rule editing unit 3 not only for the input type name and the inspection processing name but also for each item in the horizontal axis and the vertical axis direction. It is also possible to construct a matrix using another standard.
[0042]
For the input type, the types of the basic data types are numeric type (Int (integer type), Int_measure (integer type with unit), Int_currency (integer type with monetary unit), Real (real type), Real_measure (real type with unit), Real_currency (real type with money unit)), character type (String), Boolean type (Boolean), date type (date), choice type (ENUM), level type (Level), Num, There are roughly six types: Str, Const.Bool, Data, ENUM, and Level. Further, the six types may be array, (if the position of the element is predetermined) or non-array (the position of the element is not predetermined). They can be divided into two types: type. Therefore, here, approximately 14 types of input types are set according to the types of the basic data type and the set type data. This classification is for grouping the same or similar input formats. Each group is associated with one input form.
[0043]
In the inspection processing, the content data generation unit 10 generates content data based on data input in an input form determined according to an input type described later, and then checks whether there is an error in the content data (the specified This is for searching for the type of the set data of the content data corresponding to the specification item, the type of the basic data type, and whether or not the condition satisfies the conditions defined by “Uniqueness” and “Optional”). . Here, there are the following inspection processing programs (inspection processing functions).
[0044]
Non_Int (): processing for checking for the existence of non-integer data
Non_Numeric (): processing for checking for the presence or absence of data other than real numbers
Non_date (): processing for checking for the presence or absence of data of Date type and Time type of ISO10303
Non_ENUM (): a process of checking whether there is data other than the selector defined by the dictionary element
Non_Boolean (): processing for checking for the presence or absence of data other than TRUE and FALSE
Uniqueness (): processing for checking whether elements included in a set are unique
Null (): processing for checking whether or not an element included in the set has a null value
Each of the inspection processing programs is stored in the input form storage unit 7.
[0045]
The input form editing unit 6 is for creating and editing an input form corresponding to the input type.
[0046]
The input form created and edited by the input form editing unit 6 is stored in the input form storage unit 7.
[0047]
The generation rule editing unit 8 synchronizes with the input to the input form displayed on the display screen and synchronizes the numerical value, character string, operator, rule, and the input type corresponding to the input form. Create and edit a generation rule that describes the basic data type and a list of selected inspection processes.
[0048]
The generation rules created and edited by the generation rule editing unit 8 are stored in the generation rule storage unit 9.
[0049]
The content data generation unit 10 generates content data based on the generation rule generated by the generation rule editing unit 8.
[0050]
(Processing operation of electronic catalog creation system)
FIG. 37 is a flowchart for explaining the processing operation of the electronic catalog content data editing unit 2 in FIG. A basic processing flow in the present embodiment will be described with reference to FIG.
[0051]
First, an operation command from a user is received (step S1). If the command is a “dictionary reading operation” (step S2), the dictionary data selected by the user is read from the dictionary data storage unit 1, and as shown in FIG. A new data input screen is generated and displayed (step S10), and the process returns to step S1 to wait for the next input.
[0052]
If the operation command from the user is “data input request operation” (step S3), simple data on the content data of the specification is obtained from the dictionary element corresponding to the specification (one cell) specified by the input request. The value V of the type 205 of the / set type data is obtained (step S11). If V is a simple type, normal data input is performed (steps S12 to S13).
[0053]
If V is a set type (step S12), the data of the dictionary element corresponding to the cell specified by the input request is read (step S14), and the generation rule editing unit 8 executes the generation rule editing process (step S15). . When the generation rule editing process ends, the process returns to step S1 and waits for the next input.
[0054]
If the operation command from the user is “collective content data generation operation” (step S4), the content data generation process is executed in the content data generation unit 10 (step S16), and the generated content data is displayed in FIG. It is displayed on the cell corresponding to the content data on the editing screen as shown, and when the processing is completed, the process returns to step S1 and waits for the next input.
[0055]
If the operation command from the user is “input form editing operation” (step S5 in FIG. 38), an input form editing process in the input form editing unit 6 is executed (step S17), and when the process ends, the process proceeds to step S1. Go back and wait for the next input.
[0056]
If the operation command from the user is "input type selection rule editing operation" (step S6), a selection rule editing process in the input type editing operation unit 3 is executed (step S18), and when the process ends, the process returns to step S1. Wait for the next input.
[0057]
If the operation command from the user is “operation for reading electronic catalog content data” (step S7), the electronic catalog content data is read from the electronic catalog content data storage unit 11, and a data input screen is generated and displayed (step S19). ), When the process is completed, the process returns to step S1 and waits for the next input.
[0058]
If the operation command from the user is “storage operation of electronic catalog content data” (step S8), the currently displayed electronic catalog content data is stored in the electronic catalog content data storage unit 11 (step S20). At this time, if there is content data newly generated by the "collective content data generation operation", the electronic catalog content data is stored as the value of the specification item in the product (parts) data corresponding to the content data. The information is stored in the unit 11. Upon completion of the process, the process returns to the step S1 and waits for the next input.
[0059]
If the operation command from the user is “end operation” (step S9), the entire process ends.
[0060]
FIG. 6 shows an example of an editing screen displayed by the electronic catalog content data editing unit 2. Each row corresponds to one product (part) data. In this embodiment, by selecting each of the dictionary read button 2201, the content read button 2202, the content save button 2203, the content generation button 2204, the selection rule edit button 2205, the input form edit button 2206, and the end button 2207, FIG. 38 are input to the electronic content data editing unit 2 as the operation commands described above.
[0061]
In the actual input of the content data, a portion of the editing screen shown in FIG. 6 where the content data is to be input (that is, a cell corresponding to one item of a certain product (part)) is selected with a mouse or the like. This allows input.
[0062]
In FIG. 6, as shown in a cell 2208, a cell in which no content data has been input is blank, and where a content data has been registered, actual data is displayed as shown in a cell 2209.
[0063]
Further, as shown in a cell 2210, when data is input on the input form and the generation rule is edited, but the content data generation processing in the content data generation unit 10 is not yet performed, "(* ) "Is displayed.
[0064]
The input screen of the content data can be viewed on the editing screen shown in FIG.
[0065]
(Generation rule editing processing: input of collective content data)
FIG. 39 is a flowchart illustrating the generation rule editing process in step S15 of FIG. This process is mainly executed in the generation rule editing unit 8 in FIG.
[0066]
Collective content data has a plurality of elements. It is of course possible to input each element one by one, but if each element has regularity, simply specify the rule (rule) and one or some of all elements, Element can also be entered. In particular, the latter input method is useful in that, when the number of elements is large, the trouble of inputting can be saved.
[0067]
Therefore, here, in the input form corresponding to the input type selected by the input type selection unit 5, in addition to the mode of inputting each element one by one (input type "manual input"), the input form is prepared in advance. Mode (input type "simple rule") for inputting an element using the simplified rule and a mode (input type "rule editing") for the user to input a desired rule and input the element using the rule Provided.
[0068]
The data and rules written (input) in the input form are stored in the generation rule storage unit 9 as generation rules. The generation rule describes data and processing procedures required when the content data generation unit 10 generates content data. Here, it can be said that the input (editing work) to the input form is a work for editing the generation rule, and is referred to herein as a generation rule editing process.
[0069]
First, it is determined whether or not a generation rule corresponding to (the content data of) one cell on the editing screen in FIG. 6 specified in step S1 in FIG. 37 exists in the generation rule storage unit 9 (step S31). If there is, the corresponding generation rule R and the input form F of the collective content data corresponding to the generation rule are read, displayed, and edited (step S42). When the editing on the displayed input form is completed (step S43), the generation rule R is stored in the generation rule storage unit 9 (step S44).
[0070]
In step S31, if the generation rule corresponding to (the content data of) one cell on the edit screen in FIG. 6 does not exist in the generation rule storage unit 9, the dictionary data read in step S14 in FIG. , "Simple / Complex", "DataType", "Uniqueness", and "Optional" are extracted (step S32).
[0071]
Next, an input type selection process is executed based on the above four values (step S33). Based on the input type T obtained by this process, a new generation rule R is created, and the list C of the inspection process also selected in the input type selection process is substituted for the newly created generation rule R. (Step S34).
[0072]
The input form F corresponding to the input type T is read from the input form storage unit 7, and the generation rule R is read into the input form F, displayed, and edited (step S35).
[0073]
When the input type T is the ENUM type (step S36), option data is read from the dictionary data and written in a predetermined dialog portion of the input form F (step S37).
[0074]
If the input type T is the Array type (step S38), the array range definition data is read from the dictionary data and written as a variable of the input form F (step S39).
[0075]
When the editing is completed (step S40), the generation rule R is stored in the generation rule storage unit 9 (step S41).
[0076]
FIG. 40 is a flowchart for explaining the input type selection processing procedure in step S33 of FIG. This processing is executed in the input type selection 5 in FIG.
[0077]
First, on the condition that the values of “Simple / Complex”, “DataType”, “Uniqueness”, and “Optional” obtained in step S32 of FIG. 39 are the conditions, the input shown in FIG. With reference to the type selection rule and the inspection processing selection rule shown in FIG. 5, an input type T and an inspection processing list C are obtained (step S51).
[0078]
If there is an input type T that satisfies the above conditions (step S52), the input type T and the list C of the inspection process are returned to the generation rule editing unit 8 (step S53). If the input type T does not exist, an error message is displayed (step S54).
[0079]
7 to 21 show examples of input forms for collective content data for each input type. 7 to 21 show display examples of a generation rule editing screen corresponding to each input form displayed by the generation rule editing unit 8. Hereinafter, a configuration of an input form for each input type and a method of inputting data to each input form will be described with reference to FIGS. The input form is stored in the input form storage unit 7. These input forms can be specified by the input form editing unit 6 such as a button configuration, an arrangement order, the number of lines of initial display, a default value of each field, and the like. Naturally, for an input type based on another standard, It is also possible to create forms.
[0080]
The input form storage unit 7 also stores the above-described inspection processing program.
[0081]
(A set type content data input form whose input type is "Num_type")
FIG. 7 shows an example of an input form of collective content data whose input type is “Num_type”. FIG. 7A shows a main screen of the “Num_type” input form, in which one input element is input to one line of input area 409.
[0082]
The move button 408 is for moving an input element corresponding to a certain line to another line.
[0083]
In a one-line input area 409 for inputting one input element, a check box 407 used when moving the input element, a dialog box 402 for specifying an input type, and an input value area are input. Field 403, a dialog box 404 for specifying an operator of the pitch calculation formula, a pitch input field 405, and buttons 406 for the user to create and edit a desired rule. The input type on the input form refers to one of “manual input”, “simple rule”, and “rule editing” as a means for inputting data on the input form. This is different from the input type selected in step 5.
[0084]
To change the order of the input elements (lines), check the check box 407 corresponding to the input element and click the move button 408 to move the position of the input element up or down. it can.
[0085]
As shown in FIG. 7B, the dialog box 402 for designating the input type displays “manual input”, “simple rule”, and “rule editing”. You can choose.
[0086]
The input field 403 in the input value range can be input only to the feed on the left side when “manual input” is selected as the input type in the dialog box 402, and is input when “simple rule” is selected as the input type. Enter the range of the element. When "edit rule" is selected as the input type, input is prohibited.
[0087]
When the input type is the “simple rule”, content data is generated by executing an operation prepared in advance as a rule for generating content data. Here, as shown in FIG. 7C, in the operator specification dialog box 404, four arithmetic operators can be selected. Of course, other binary operators can be prepared, and the form can be changed to facilitate polynomial operations. When “simple rule” is selected as the input type, an argument for the operator specified in the operator specification dialog box 404 is input to the pitch input field 405.
[0088]
When the input type is “rule editing”, the user inputs a desired rule for generating content data, and executes the rule to generate content data. When "rule edit" is selected as the input type, the rule edit button 406 starts a rule edit screen as shown in FIG. 7D. The user can create and edit a desired rule on the rule editing screen. The rules described here may be described in any language, in which case a parser for the language must be prepared.
[0089]
If a rule has already been set for a certain element, the rule may be read.
[0090]
FIGS. 22 to 24 show input examples of the input form of “Num_type” in FIG.
[0091]
FIG. 22 shows a state where two input elements are input with the input type “manual input”.
[0092]
FIG. 23 illustrates a state in which two input elements are input with the input type “simple rule” and one input element is input with the input type “manual input”.
[0093]
The input element 2401 describes a rule that sequentially adds “1.5” in a range from “1.5” to “6.0” as a “simple rule”. According to this rule, the content data generating unit 10 generates four values (1.5, 3.0, 4.5, 6.0) as content data.
[0094]
In the input element 2402, a rule in which “2” is sequentially multiplied in a range from “10” to “80” is described as a “simple rule”. According to this rule, the content data generating unit 10 generates four values (10, 20, 40, 80) as content data.
[0095]
Therefore, according to the rules described in FIG. 23, the set data (1.5, 3.0, 4.5, 6.0, 10, 20, 40, 80, 100) is generated by the content data generation unit 10. Will be generated.
[0096]
FIG. 24 shows an input type “rule editing”, in which a user-defined rule 2501 is described. According to this rule, the element value Y is given as a recurrence formula Y (n) = Y (n-1) × 2 + 0.05 Y (0) = 0.1 × 2 + 0.05 = 0.25. According to the rules, the set data of (0.25, 0.55, 1.15, 2.35, 4.75) is generated in the content data generation unit 10.
[0097]
(A collective content data input form whose input type is "Str_type")
FIG. 8 shows an example of an input form of collective content data whose input type is “Str_type”. The input form of “Str_type” is almost the same as the input form of “Num_type” in FIG. 7, but is different on the main screen shown in FIG. 8A in the calculation of the pitch calculation formula in FIG. The child designation dialog box 404 and the pitch input field 305 are replaced with a pitch calculation formula designation dialog box 501.
[0098]
When the "simple rule" is specified as the input type, the pitch calculation formula specification dialog box 501 displays "Alphabet" and "Ascending" as character generation operators as shown in FIG. 8C. ), "Descending order (Alphabet)" and "Descending order (Aioueo)" can be selected. For example, if the input value range is specified as "A" to "D" and the character generation operator is "Ascending order (Alphabet)", (A, B, C, D) is generated as content data. Of course, other string operators can be provided.
[0099]
When "rule edit" is selected as the input type, a rule edit screen as shown in FIG. 8D is activated, whereby the user can create and edit a desired rule. The editing screen shown in FIG. 8D is described as a character string development rule 502 based on a combination table of characters having a plurality of arrangements. Of course, an editing screen similar to “Num_Type” is prepared. Is also good.
[0100]
FIG. 25A shows an input example of the input form of “Str_type” in FIG. In the first input element, a user-defined rule 2601 is described with an input type “rule edit”. According to this rule, content data is generated by a direct product of character strings input as elements of a plurality of arrays. For example, as shown in FIG. 25B, a rule for calculating a direct product of characters input to each column (row) of the one-dimensional array is described. According to rule 2601, (A, S) × (NX) ) × (001, 002, 003) × (#Space, −1).
[0101]
In FIG. 25A, the character string "SHT" is further input as an input element with the input type "manual input". As a result, the content data has a value of (ANS001, NX001-1, NX002, NX002-1, NX003, NX003-1, SNX001, SNX001-1, SNX002, SNX002-1, SNX003, SNX003-1, SHT). Collective data is generated.
[0102]
(Aggregated content data input form whose input type is "Bool_type")
FIG. 9 shows an example of an input form of collective content data whose input type is “Bool_type”. In this type, since the value of the element is one of the two values “TRUE, FALSE”, the field for describing the rule desired by the user is not set, and the input field is in the dialog format shown in FIG. You can choose.
[0103]
Collective Content Data Input Form with Input Type “Const1” FIG. 10 shows an example of an input form for collective content data with input type “Const1”. Since there are only two types of this type, one of them is selected by a button 701 corresponding to each type.
[0104]
(A set type content data input form whose input type is "Date_type")
FIG. 11 shows an example of an input form of collective content data whose input type is “Date_type”. In this type, each input element is set by inputting year, month, day, hour, minute, and second.
[0105]
(A set type content data input form whose input type is "ENUM_type")
FIG. 12A shows an example of an input form of collective content data whose input type is “ENUM_type”. In this type, since the value of the element is determined by the dictionary data, the input field can be selected in a dialog format.
[0106]
For example, when the code in FIG. 2 is “AAE007”, as shown in FIG. 12B, the dialog box displays “ON” and “OFF” values according to the definition of the dictionary element. Become so.
[0107]
(Aggregated content data input form whose input type is "Level_type")
FIG. 13A shows an example of an input form of collective content data whose input type is “Level_type”. This type has four fields 1001 to 1004 as input values because each input element itself can have a maximum of four types of values (Min, Nom, Type, Max).
[0108]
Normally, the input type is set individually with the input type “manual input”. However, with the input type “rule editing”, rules between four types of values included in one element can be described. . For example, the value corresponding to “Min” is 75% of the value corresponding to “Type”, the value corresponding to “Max” is 125% of the value corresponding to “Type”, the value corresponding to “Nom” and “Typ”. If the value corresponding to "is equal, only" Type "is described on the main screen of FIG. 13A, and" Min = Type × "is set as a rule on the rule editing screen shown in FIG. 13C. 0.75, Max = Type × 1.25, Mom = Type ”.
[0109]
The above is the input form of the input type which is not an array type (that is, a non-array type). Next, an input form of an array type (array type) will be described. Note that, here, for simplicity of description, a case of a one-dimensional array will be described as an example.
[0110]
(Input form corresponding to array type input type)
FIGS. 14 to 21 show input forms corresponding to the input type of the array type (Array type). Because of the array type, the position of the input element can be explicitly described as an array number.
[0111]
(1) FIG. 14A shows an example of an input form of collective content data whose input type is “Num_array”. In this type, it is difficult to imagine a scene in which the order of the input elements is moved, and therefore, no move button is set in this input form. In the dialog box for designating the input type, as shown in FIG. 14B, one of “manual input” and “rule editing” can be selected for each input element.
[0112]
In the case of "manual input", input can be made only to the feed on the left side of the array number field 1101, and in the case of "rule editing", the range of array numbers can be described in the field 1101.
[0113]
When “Rule Edit” is designated, a rule edit screen as shown in FIG. 14C is activated, and the user can describe a rule.
[0114]
In the case of the array type, since the number of elements is defined in the dictionary, a range of numbers is set in advance as a variable (described in the area 1102), and the user may use this variable in a rule. it can.
[0115]
FIG. 26 shows an input example in the input form of “Num_array” in FIG. Here, rules are described for the array numbers “1” to “5”, and respective values are set for the array numbers “6” and “7”. In the rule set here, the content is incremented by 10 in the order of the arrangement number. When this rule is executed, (10, 20, 30, 40, 50) is generated as content data. Therefore, array data ((10, 20, 30, 40, 50, 100, 1000) as content data is generated from the input elements shown in FIG.
[0116]
(2) FIG. 15 shows an example of an input form of collective content data whose input type is “Str_array”. In this example, the form matches “Num_array” in FIG.
[0117]
(3) FIG. 16 shows an example of an input form for collective content data whose input type is “Bool_array”. One of the two values “TRUE” and “FALSE” may be input to each input element for which the array number is set, and the input method is the same as “Bool_type” in FIG.
[0118]
(4) FIG. 17 shows an example of an input form of collective content data whose input type is “Const2”. In this type, the user may select a desired pattern from a plurality of patterns in which the positions and values of the input elements are predetermined. For this purpose, a selection button is provided for each pattern, and one of them is selected. That is, in this case, since only 12 patterns are possible, one of these patterns is selected.
[0119]
(5) FIG. 18 shows an example of an input form for collective content data whose input type is “Const3”. As in FIG. 17, since there are only two types of sets in this type, one of these candidates is selected.
[0120]
(6) FIG. 19 shows an example of an input form for collective content data whose input type is “Date_array”. Although the position of each input element is set by the array number, the method of inputting the value of each other input element is the same as “Date_type” in FIG.
[0121]
(7) FIG. 20 shows an example of an input form of collective content data whose input type is “ENUM_array”. Although the position of each input element is set by the array number, the method of inputting the values of the other input elements is the same as “ENUM_type” in FIG.
[0122]
FIG. 27 shows an example of input in the input form of “Enum_array”. Here, the values of the options defined in the dictionary data are set for each array number.
[0123]
(8) FIG. 21 is an example of an input form of collective content data whose input type is “Level_array”. The position of each input element is set by the array number, but the method of inputting the value of each other input element is the same as “Level_type” in FIG.
[0124]
(Generation of collective content data)
The data, rules, and the like entered in each of the above input forms are stored in the generation rule storage unit 9 as generation rules.
[0125]
FIGS. 28 and 29 show the data structure of the generation rule.
[0126]
FIG. 28 shows a data structure of a generation rule representing data, a rule, and the like input to an input form corresponding to a non-array type (not an array type). FIG. 29 shows an input type of the array type. Is a data structure of a generation rule representing data, rules, and the like input to an input form corresponding to.
[0127]
FIG. 30 shows a data structure of data representing a rule (user-defined rule) input by a user with an input type of “rule editing” among data described in the generation rule. Is a data structure when the basic data type is a character type, and is a data structure when a rule is described by a character string input to each column as shown in FIG. 25B. a) shows a data structure in which the basic data type is not a character type and a rule is described in text.
[0128]
The common point in the data structure of the generation rules shown in FIGS. 28 to 30 is that one line indicates one data record, and the data record includes an “Item” field 1901, a “Tag” field 1902, and a “Description”. It consists of a field 1903. The “Item” field has the following types.
[0129]
Format: Input type name (input type selected by input type selection unit 5)
-DataType: Basic data type
BSU: Dictionary element identification code
ID: ID for identifying content data
・ Data: Rule data
-Func: Name of inspection process
・ Range: Range of sequence (Array type only)
Text: Definition statement of the user-defined rule (only the text-type user-defined rule in FIG. 30A)
Column: Column list (only the column type user-defined rule in FIG. 30B)
Among them, a rule whose “Item” type is “Data” in the non-array type generation rule has the following Tag type.
[0130]
Value: When the basic data type is not the Date type or the Level type, the value of the element input by "manual input" is described in the "Description" field 1903.
[0131]
DateValue: When the basic data type is the Date type, the year (Yvalue), month (Mvalue), day (Dvalue), hour (Hvalue), minute (MMValue), and second ( 6) are described in a field 1903.
[0132]
LevelValue: When the basic data type is the Level type, four values of the minimum (MinValue), the nominal (NomValue), the representative (TypeValue), and the maximum (MaxValue), which are input by “manual input”, are set in a field 1903. Is described in
[0133]
PredefinedRule: Four values of a range (Bound1, Bound2) and a pitch calculation formula (CalcType, Pitch) input by a simple rule provided in an input form for set-type content data whose basic data type is not a character type are fields. 1903.
[0134]
PredefinedStrRule: 3 of range (Bound1, Bound2) and pitch calculation formula (Pitch) provided by a simple rule for a character string provided in the input form of the collective content data whose basic data type is a character type One value is described in the field 1903.
[0135]
-UserRule: Name of a user-defined rule (RuleName) input in "Rule Edit" when the basic data type is not a level type
LevelUserRule: In the case where the basic data type is the Level type, four values and the user-defined rule name (RuleName) input in “Rule Edit” are described in the field 1903.
[0136]
Further, in the array type generation rule, a rule whose “Item” type is “Data” has the following Tag type.
[0137]
Value: The array number (Num) and the value of the element (Value) input by "manual input" are described in the field 1903.
[0138]
DateValue: The array number (Num) and the data whose basic data type is Date type, which is input by "manual input", is described in the field 1903.
[0139]
LevelValue: The array number (Num) and the data of the basic data type Level type, which are input by "manual input", are described in the field 1903.
[0140]
LevelUserRule: The array number (Num), the data whose basic data type is Level type, and the name of the user-defined rule input in “Rule Edit” are described in a field 1903.
[0141]
UserRule: A range of array numbers (Num1, Num2) and a user-defined rule name (RuleName) entered in “Rule Edit” are described in a field 1903.
[0142]
FIGS. 31 to 36 show generation rules corresponding to each of the input examples to the input forms shown in FIGS. 22 to 27.
[0143]
The generation rule shown in FIG. 31 corresponds to the example of inputting Num_type to the input form shown in FIG. In this case, the name of the input type, the basic data type, the identification code of the dictionary element, the ID for identifying the content data, the values of the two elements of the content data input manually, and the names of the two selected inspection processes are included. Are described in this order.
[0144]
The generation rule shown in FIG. 32 corresponds to the input example of the Num_type input form shown in FIG. In this case, the name of the input type, the basic data type, the identification code of the dictionary element, the ID for identifying the content data, the value of the input element 2401 in the first line input by the simple rule, the value 2402 of the input element in the second line , The value of the element of the content data input manually, and the name of one selected inspection process are described in this order.
[0145]
The generation rule shown in FIG. 33A corresponds to the input example of the Num_type input form shown in FIG. In this case, the name of the input type, the basic data type, the identification code of the dictionary element, the ID for identifying the content data, the name of the user-defined rule, and the names of the two selected inspection processes are described in this order. FIG. 33B shows a generation rule describing a user-defined rule. In this case, following the name of the user-defined rule and the basic data type, the rule input by the user is described as “Text”.
[0146]
The generation rule shown in FIG. 34A corresponds to the input example of the Str_type shown in FIG. 25 into the input form. In this case, the name of the input type, the basic data type, the identification code of the dictionary element, the ID for identifying the content data, the name of the user-defined rule, and the value of the element of the manually input content data are described in this order. . FIG. 34B shows a generation rule describing a user-defined rule. In this case, following the name of the user-defined rule and the basic data type, the character string input to each column by the user is described as “column”.
[0147]
The generation rule shown in FIG. 35A corresponds to the input example of the Num_array input form shown in FIG. In this case, the name of the input type, the basic data type, the identification code of the dictionary element, the ID for identifying the content data, the range of the array (here, 1 row and 7 columns), the name of the user-defined rule, the manually input content data And the name of the selected inspection process are described in this order. FIG. 35B shows a generation rule describing a user-defined rule. In this case, following the name of the user-defined rule and the basic data type, the rule input by the user by the user is described as “Text”.
[0148]
The generation rule shown in FIG. 36 corresponds to the input example of the ENUM_array input form shown in FIG. In this case, the name of the input type, the basic data type, the identification code of the dictionary element, the ID for identifying the content data, the range of the array (here, 1 row and 6 columns), the value of the value displayed in the dialog box as the array element The value selected by the user and the name of the selected inspection process are described in this order.
[0149]
The content data generation unit 10 generates collective content data using the data described in the generation rule.
[0150]
FIG. 41 is a flowchart for explaining the content data generation processing in step S12 in FIG. This processing is executed by the content data generation unit 10.
[0151]
First, when a "collective content data generation" operation is performed on a cell specified on the editing screen of the electronic catalog content data editing unit 2, the generation rule corresponding to the specified cell is stored in the generation rule storage unit. 9 is checked (step S61). If not, an error message is displayed (step S62). If the generation rule exists, the generation rule R is read from the generation rule storage unit 9 (step S63).
[0152]
Next, a value D1 (that is, an input type) of the “Description” field of the “Format” data record R1 of the generation rule R is obtained (step S63). Then, the first record R2 of the “Data” data is extracted from the generation rule R (step S65).
[0153]
It is checked whether the input type represented by the value D1 is an array type (step S66). If the input type is not the array type, the “DataType” data record R4 of the generation rule R is extracted, and a list L of an empty set corresponding to the value of the “Description” field is generated (step S67), and the first data generation is performed. The process is executed (Step S68). Next, a search is made for the next “Data” data record of the generation rule, and the process returns to step S68 as the new R2 to execute the first data generation process, while the “Data” data record exists in the generation rule. Repeat (Step S69 to Step S70). By repeatedly executing the first data generation process, each element of the list L is generated.
[0154]
In step S66, if the input type represented by the value D1 is the array type, the process proceeds to step S71 in FIG. 42, where the “DataType” data record R4 and the “Range” data record R5 of the generation rule R are obtained, and An array A corresponding to the value of the Description field and having the value (range) of the Description field of R5 is generated (step S71), and a second data generation process is executed (step S72). Next, a search is made for a “Data” data record next to the generation rule R, and the process returns to step S72 as a new R2 to execute the second data generation process. (Steps S73 to S74). Each element of the array A is generated by repeatedly executing the second data generation process.
[0155]
When the “Data” data record ends in step S69 or S73, the leading “Func” data record R3 is extracted from the generation rule R (step S75). The inspection process program (hereinafter, referred to as an inspection function) described in the “Description” field of the data record R3 is read from the generation rule storage unit 9 and the inspection process is applied to the list L or the array A (step S76).
[0156]
When the check function detects an error, that is, there is an element of the list L or the array A that does not satisfy the conditions defined by the type and basic data type of the set-type content data and “Uniqueness” and “Optional”. If so (step S77), an error message is displayed and the process is interrupted (step S78).
[0157]
If no error is detected by applying the check function to the list L or the array A, that is, all the elements of the list L or the array A include the type or the basic data type of the set-type content data, “Uniqueness”, If the condition defined by “Optional” is satisfied, next, a “Func” data record next to the generation rule is searched, and the new R3 is returned to step S76, and the next check function is stored in the list L or array A. To check whether any of the elements of the list L or the array A does not satisfy the conditions defined by the type and the basic data type of the set-type content data, “Uniqueness”, and “Optional”. The process is repeated while the "Func" data record exists in the generation rule (steps S79 to S80).
[0158]
Each element of the list L or the array A is inspected using an inspection function corresponding to each “Func” data record described in the generation rule R, and if no error is detected in any of the inspections, The elements of the list L and array A are assigned to the designated cell (step S81).
[0159]
Next, the first data generation processing in step S68 of FIG. 41 will be described with reference to the flowcharts shown in FIGS. This process is a process for generating each element of the collective content data that is not the array type as an element of the list L. The data processing procedure differs depending on the value of the “Tag” field of the data record R2.
[0160]
If the value of the “Tag” field is “Value”, that is, if it is the value of the element input by “manual input” (step S101), the value (= Value) of the “Description” field of the data record R2 is changed. It is added to the list L (step S105).
[0161]
If the value of the “Tag” field is “DateValue”, that is, if the value of the element of the Date type input by “manual input” (step S102), the value of the “Description” field of the data record R2 (= Yvalue, Mvalue, Dvalue, Hvalue, MMValue, and Svalue) are added to the list L (step S106).
[0162]
If the value of the “Tag” field is “LevelValue”, that is, if it is the value of a Level-type element input by “manual input” (step S103), the value of the “Description” field of the data record R2 (= MinValue, NomValue, TypeValue, MaxValue) are added to the list L (step S107).
[0163]
If the value of the “Tag” field is “PredefinitionRule”, that is, if the input is performed using a simple rule provided in the input form (step S104), the value of the “Description” field of the data record R2 (= Bound1, Bound2, CalcType, and Pitch are extracted (step S108), and a value corresponding to “Bound1” is substituted into a variable X, and X is added to the list L (step S109).
[0164]
Next, an operation corresponding to “CalcType” is executed on X with a value corresponding to “Pitch” as an argument, the result is substituted into X, and a new value of X is added to the list L (step S111). ). The process of step S111 is repeated while X ≦ Bound2 is satisfied (steps S110 to S113).
[0165]
When the value of the “Tag” field is “PredefinedStrRule”, that is, when the value is input using the simple rule for a character string (step S115 in FIG. 44), the value of the “Description” field of the data record R2 (= Bound1, (Bound2, Pitch) is taken out (step S116), the value corresponding to “Bound1” is substituted for X, and the value of X is added to the list L (step S117). Next, an operation corresponding to "Pitche" is performed on X, the result is substituted into X, and a new value of X is added to the list L (step S119). The process of step S119 is repeated while X ≦ Bound2 is satisfied (steps S118 to S121).
[0166]
When the value of the “Tag” field is “LevelUserRule”, that is, when the basic data type is the Level type and the input is performed by the user-defined rule (step S116), first, the first of the Description field of the data record R2 (= MinValue, NomValue, TypeValue, MaxValue) are added to the list L (step S117), and the last value (= RuleName) of the “Description” field of the data record R2 for the list L, ie, Then, the process described in the generation rule corresponding to the user-defined rule name is executed (step S118), and the value obtained as a result of the execution is added as the contents of the list L (step S119).
[0167]
When the value of the "Tag" field is "UserRule", that is, when the basic data type is not the Level type and the value is input by the user-defined rule (step S120), the list L is used. The last value (= RuleName) of the “Description” field of the data record R2, that is, the process described in the generation rule corresponding to the user-defined rule name is executed (step S121), and the value obtained as a result of the execution is It is added as the contents of the list L (step S122).
[0168]
If the value of the “Tag” field does not correspond to any of the above, an error message is displayed (step S123).
[0169]
Next, the second data generation process in step S72 of FIG. 42 will be described with reference to the flowcharts shown in FIGS. This process is a process for generating each element of the array type content data as an element of the array A. The data processing procedure differs depending on the value of the “Tag” field of the data record R2.
[0170]
If the value of the “Tag” field is “Value”, that is, if the array number (Num) and the element value (Value) are input by “manual input” (step S131), the “Description” field of the data record R2 Then, the next value (= Value) of the “Description” field is assigned to the address of the array A that matches the first value (= Num) of (step S132).
[0171]
If the value of the “Tag” field is “DateValue”, that is, if the array number (Num) and the data whose basic data type is Date type are input by “manual input” (step S133), the data record R2 The remaining six values (= Yvalue, Mvalue, Dvalue, Hvalue, MValue, and Svalue) of the “Description” field are substituted for the address of array A that matches the first value (= Num) of the “Description” field ( Step S134).
[0172]
If the value of the “Tag” field is “LevelValue”, that is, if “manual input” and data of the array number (Num) and the data type of the basic data type are input (step S135), the data record R2 The remaining four values (= MinValue, NomValue, TypeValue, MaxValue) of the “Description” field are substituted for the address of the array A that matches the first value (= Num) of the “Description Field” (step S136).
[0173]
When the value of the “Tag” field is “LevelUserRule”, that is, when the array number (Num) and the data whose basic data type is Level type and the user-defined rule are input in “Rule editing” (step in FIG. 46) S137) At the address of the array A that matches the first value (= Num) of the “Description” field of the data record R2, add the remaining four values (= MinValue, NomValue, TypeValue, MaxValue) of the “Description” field. Substitution is performed (step S138), and then the process described in the generation rule corresponding to the last value (= RuleName) of the “Description” field of the data record R2, ie, the user-defined rule name is executed (step S138). 139), to add a value obtained as a result of execution as the contents of the array A (step S140).
[0174]
If the value of the “Tag” field is “UserRule”, that is, if the range of the array number (Num1, Num2) and the user-defined rule are input in “Rule editing” (step S141), “ The addresses of all the arrays A in the range of the first two values (= Num1, Num2) of the “Description” field correspond to the last value (= RuleName) of the “Description” field, that is, the user-defined rule name. The process described in the generation rule is executed (step S142), and the value obtained as a result of the execution is added as the contents of array A (step S143).
[0175]
If the value of the “Tag” field does not correspond to any of the above, an error message is displayed (step S144).
[0176]
(Procedure for inputting collective content data)
With reference to FIGS. 47 to 50, a user operation procedure when inputting collective content data in the electronic catalog content creation system of FIG. 1 will be described with reference to the flowchart shown in FIG.
[0177]
On the editing screen G1 displayed by the electronic catalog content data editing unit 2 as shown in FIG. 47, the user selects a non-input portion (blank cell) (step S3 in FIG. 37). Then, since the content data corresponding to the selected cell is the collective content data (steps S11 to S12), the dictionary element data corresponding to the selected cell is read, and as shown in FIG. , The generation rule editing screen G2 is activated.
[0178]
For example, the data corresponding to the cell selected by the user is “scale setting” of the code “AEE002”. From the dictionary element data shown in FIG. 2, the content data corresponding to this data is a List type data. It is a set type content data, and the basic data type is a Real type. The value of “Uniqueness” is “FALSE”. In the generation rule editing process in step S15, first, an input type and an inspection process corresponding to the cell are selected under these conditions. Then, it is found that the input type is Num_type. The input form of Num_type shown in FIG. 7 is displayed on the generation rule editing screen G2 of FIG.
[0179]
Here, a generation rule is input (edited) by “simple rule” and “manual input”, and an “OK” button provided on the generation rule editing screen is pressed, and the generation rule is stored in the generation rule storage unit 9. Is stored in
[0180]
At this point, the generation rule is stored in the selected cell of the editing screen G1 as shown in FIG. 49, but the content data generation processing in the content data generation unit 10 has not been performed yet. Is displayed.
[0181]
Next, as shown in FIG. 49, the cell in which the generation rule is stored on the editing screen G1 is selected, and the “content generation” button provided on the editing screen G1 is pressed (step S4), and the content data is generated. The generation process is started (Step S12).
[0182]
In the content data generation process at this time (specifically, the process of steps S104 and S108 to S113 of the first data generation process of FIG. 43), first, the first “Data” data record of the generation rule is set. As data to be processed, data input in the “simple rule”, that is, Bound1 = 1.5, Bound2 = 6.0, CalcType = +, Pitch = 1.5, and (1.5,3.0,4. 5, 6.0) and make this an element of the list L. Next, with the second “Data” data record of the generation rule as a processing target, the data input by the “simple rule”, that is, Bound1 = 10, Bound2 = 80, CalcType = *, Pitch = 2, and (10 , 20, 40, 80) and adds this to the elements of list L. Finally, with the third “Data” data record of the generation rule as a processing target, data input by “manual input”, that is, “100” is added as the last element of the list L. As a result, (1.5, 3.0, 4.5, 6.0, 10, 20, 40, 80, 100) is obtained as the list L.
[0183]
As shown in FIG. 50, the elements of the list L are displayed in cells selected for content generation on the editing screen G1. FIG. 50 shows a state where a part of the generated aggregated content data is displayed in the cell. In this case, by placing the cursor on the cell, the entire content data is popped up and displayed as shown in FIG.
[0184]
As described above, according to the above embodiment, calculation rules (simple rules provided in an input form) and processing are performed instead of inputting each and every element of collective data composed of a plurality of element data. By enabling the input in the procedure (user-defined rule), the more the number of element data increases, the more the time and effort required for input can be significantly reduced as compared with the case where all the element data is input manually. Many element data can be input at once without erroneous input.
[0185]
In addition, for each element data constituting the content data generated by the content data generation unit 10, it is checked whether or not a set type of the content data and a condition defined by the type of the element data are satisfied. Thus, the reliability and quality of the input content data can be improved.
[0186]
The method of the present invention described in the embodiment of the present invention (particularly, the processing procedure shown in the flowcharts of FIGS. 37 to 46) is a program that can be executed by a computer as a magnetic disk (such as a flexible disk or a hard disk). ), Optical disks (CD-ROM, DVD, etc.), semiconductor memory, and other recording media.
[0187]
Note that the present invention is not limited to the above-described embodiment as it is, and can be embodied by modifying constituent elements in an implementation stage without departing from the scope of the invention. Various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the above embodiments. For example, some components may be deleted from all the components shown in the embodiment. Further, components of different embodiments may be appropriately combined.
[0188]
【The invention's effect】
As described above, according to the present invention, it is possible to greatly reduce the task of inputting set-type data composed of a plurality of element data, which is troublesome for input.
[Brief description of the drawings]
FIG. 1 is an exemplary functional configuration of an electronic catalog content creation system according to an embodiment of the present invention.
FIG. 2 is a diagram showing a data structure of dictionary data.
FIG. 3 is a diagram showing an example of electronic catalog content data.
FIG. 4 is a diagram showing an example of an input type selection rule.
FIG. 5 is a diagram showing an example of an inspection process selection rule.
FIG. 6 is a diagram showing an example of an editing screen displayed by an electronic catalog content data editing unit.
FIG. 7 is a diagram showing a screen display example of an input form whose input type is “Num_type”.
FIG. 8 is a diagram showing a screen display example of an input form having an input type “Str_type”.
FIG. 9 is a diagram showing an example of a screen display of an input form having an input type “Bool_type”.
FIG. 10 is a diagram showing a screen display example of an input form whose input type is “Const1”.
FIG. 11 is a view showing a screen display example of an input form whose input type is “Date_type”.
FIG. 12 is a diagram showing a screen display example of an input form having an input type of “ENUM_type”.
FIG. 13 is a diagram showing a screen display example of an input form whose input type is “Level_type”.
FIG. 14 is a diagram showing a screen display example of an input form whose input type is “Num_array”.
FIG. 15 is a diagram showing a screen display example of an input form having an input type “Str_array”.
FIG. 16 is a diagram showing a screen display example of an input form whose input type is “Bool_array”.
FIG. 17 is a diagram showing a screen display example of an input form whose input type is “Const2”.
FIG. 18 is a diagram showing a screen display example of an input form whose input type is “Const3”.
FIG. 19 is a diagram showing an example of a screen display of an input form having an input type “Date_array”.
FIG. 20 is a diagram showing a screen display example of an input form whose input type is “ENUM_array”.
FIG. 21 is a diagram showing an example of a screen display of an input form having an input type “Level_array”.
FIG. 22 is a diagram showing an input example when data is input by “manual input” in an input form having an input type of “Num_type”;
FIG. 23 is a diagram showing an example of input when data is input in an input form of “Num_type” using “simple rules”.
FIG. 24 is a diagram showing an example of input when data is input by “rule editing” in an input form having an input type of “Num_type”;
FIG. 25 is a diagram showing an example of input when data is input by “rule editing” in an input form of “Str_type” as an input type.
FIG. 26 is a diagram showing an input example when data is input by “rule editing” in an input form whose input type is “Num_array”;
FIG. 27 is a diagram showing an example of data input to an input form whose input type is “ENUM_array”.
FIG. 28 is a diagram showing a data structure of a non-array type generation rule.
FIG. 29 is a diagram showing a data structure of an array type generation rule.
FIG. 30 is a diagram showing a data structure of a generation rule describing a user-defined rule.
FIG. 31 is a view showing a specific example of a generation rule corresponding to the input example of Num_type shown in FIG. 22 to the input form;
FIG. 32 is a view showing a specific example of a generation rule corresponding to the input example of the Num_type input form shown in FIG. 23;
FIG. 33 is a view showing a specific example of a generation rule corresponding to the input example of Num_type shown in FIG. 24 to the input form;
FIG. 34 is a view showing a specific example of a generation rule corresponding to an example of inputting Str_type to the input form shown in FIG. 25;
FIG. 35 is a view showing a specific example of a generation rule corresponding to the input example of the Num_array shown in FIG. 26 into the input form;
FIG. 36 is a view showing a specific example of a generation rule corresponding to an example of inputting an ENUM_array shown in FIG. 27 to an input form;
FIG. 37 is a flowchart for explaining the processing operation of the electronic catalog content data editing unit.
FIG. 38 is a flowchart for explaining the processing operation of the electronic catalog content data editing unit.
FIG. 39 is a flowchart illustrating the generation rule editing processing operation of the generation rule editing unit.
FIG. 40 is a flowchart illustrating an input type selection processing operation of the input type selection unit.
FIG. 41 is a flowchart for explaining the content data generation processing operation of the content data generation unit.
FIG. 42 is a flowchart illustrating a content data generation processing operation of the content data generation unit.
FIG. 43 is a flowchart for describing a first data generation processing operation executed in the content data generation processing.
FIG. 44 is a flowchart illustrating a first data generation processing operation executed in the content data generation processing.
FIG. 45 is a flowchart illustrating a second data generation processing operation executed in the content data generation processing.
FIG. 46 is a flowchart illustrating a second data generation processing operation executed in the content data generation processing.
FIG. 47 is a view for explaining a user operation on the editing screen.
FIG. 48 is a view showing a display example of a generation rule editing screen on which an input form is displayed.
FIG. 49 is a view showing a display example of a cell in which a generation rule is stored on an edit screen.
FIG. 50 is a view showing a display example of generated content data on an editing screen.
[Explanation of symbols]
DESCRIPTION OF SYMBOLS 1 ... Dictionary data storage part, 2 ... Electronic catalog content data editing part, 3 ... Input type selection rule editing part, 4 ... Input type selection rule storage part, 5 ... Input type selection part, 6 ... Input form editing part, 7 ... Input form storage unit 8, generation rule editing unit 9, generation rule storage unit 10, content data generation unit 11, electronic catalog content data storage unit 12, interface unit

Claims (12)

A data input method for inputting set-type data including a plurality of element data as a value for each of a plurality of items,
For each of the plurality of items, a type of aggregate data including a plurality of element data and a type of element data forming the aggregate data are defined as a data type of a value corresponding to each item. ,
A first selection step of selecting an input target item from the plurality of items;
A second selection step of selecting an input format corresponding to a combination of the type of the set-type data and the type of the element data that are predetermined for the input target;
According to the selected input format, at least one of a calculation rule for generating the element data by the element data and the operation and a processing procedure for generating the element data is set to a value of the first item. An input step for inputting as input data for generating;
A generation step of generating the value of the input target based on the input data;
A data input method having When the type of the element data predetermined for the input target is a character type, the processing procedure is to generate the element data by a direct product of each element of a plurality of arrays. Item 1. The data input method according to Item 1. Of the plurality of combinations of the type of the set-type data and the type of the element data, those of the same input format are grouped in advance, and from the combination predetermined for the input target, the group corresponding to the combination 2. The data input method according to claim 1, wherein an input format is selected. A search is performed to determine whether each element data included in the value of the input target generated in the generation step satisfies a condition defined by a type of set-type data and a type of element data predetermined for the input target. 2. The data input method according to claim 1, further comprising an inspection step of performing the inspection. 2. The data input method according to claim 1, wherein each of the plurality of items is a specification item specified in ISO13584 PLIB. An input support device for inputting a value of a predetermined data type for each of a plurality of items,
In each of the plurality of items, as a data type of the value, a set type data composed of a plurality of element data or a simple type data composed of one element data is predetermined. In addition, the type of set-type data and the type of element data of the set-type data are determined in advance,
When a first item having the set type data as a value is selected from the plurality of items, an input corresponding to a combination of the type of the set type data corresponding to the first item and the type of the element data Means for selecting a format;
According to the input format selected by the selection means, at least one of the element data and a calculation rule for generating the element data by calculation and a processing procedure for generating the element data are set in the first format. First input means for inputting as input data for generating an item value;
Generating means for generating a value of the first item based on the input data input by the first input means;
First storage means for storing the value generated by the generation means as the value of the first item;
A second input unit for inputting a value of the second item when a second item whose value is the simple type data is selected from the plurality of items;
Second storage means for storing the value input by the second input means as the value of the second item;
An input support device comprising: When the type of the element data predetermined for the first item is a character type, the processing procedure is to generate the element data by a direct product of each element of a plurality of arrays. The input support device according to claim 6, wherein Of a plurality of combinations of the type of the set-type data and the type of the element data, those having the same input format are grouped in advance, and the selection unit performs the following from the combination corresponding to the first item: The input support device according to claim 6, wherein an input format of a group corresponding to the combination is selected. Each of the element data constituting the value of the first item generated by the generation means satisfies a condition defined by the type of set-type data and the type of element data predetermined for the first item. 7. The input support device according to claim 6, further comprising an inspection unit that searches for a presence. And a display unit for displaying information for identifying an item of which the input data has been input by the first input unit but the value of which has not been generated by the generation unit, among the plurality of items. The input support device according to claim 6, wherein: 7. The input support device according to claim 6, wherein each of the plurality of items is a specification item specified in ISO13584 PLIB. A program for inputting a value of a predetermined data type for each of a plurality of items,
In each of the plurality of items, as a data type of the value, a set type data composed of a plurality of element data or a simple type data composed of one element data is predetermined. In addition, the type of set-type data and the type of element data of the set-type data are determined in advance,
When a first item having the set type data as a value is selected from the plurality of items, an input corresponding to a combination of the type of the set type data corresponding to the first item and the type of the element data A selection step of selecting a format;
According to the input format selected by the selection means, at least one of the element data and a calculation rule for generating the element data by operation and a processing procedure for generating the element data are defined by the first A first input step of inputting as input data for generating an item value;
A generating step of generating a value of the first item based on the input data input in the first input step;
A first storage step of storing the value generated in the generation step as a value of the first item in a storage unit;
A second input step of inputting a value of the second item when a second item having the simple type data as a value is selected from the plurality of items;
A second storage step of storing the value input in the second input step as the value of the second item in the storage means;
A program that causes a computer to execute.

Images