JP2004362076A - Data registering device and method therefor - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To register data in consideration of a convenience for a user frequently using the data. <P>SOLUTION: A determining part for an entity registration destination 320 receives a data registration instruction, refers to a table for determining the entry registration destination 40A, and determines whether registers are carried out in the entity as it is to the specified registration destination or to other registration destination, according to information from a recipient issuing destination and on a utility status. If the determining part 320 determines to register the entity as it is in the registration destination, a first registration control unit 330 is activated, and the data are registered in a normal manner into a development block database 20A at the specified registration destination. If the determining part 320 determines to register the entity into other registration destination; a second registration control unit 340 is activated to acquire information about registration destinations in which the entity is assorted to be registered, to register the entity in the assorted registration destinations, i.e., a production block database 20B etc. and to register the data into the database 20A while converting references at the assorted registration destinations into the entity of the data. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a data registration technique most suitable for registering large data such as drawings and the like, and in particular, to maximize the convenience of those who frequently access data.
[0002]
[Prior art]
As the performance and cost of personal computers have increased, it has become possible to build a drawing management system according to the scale of the customer, and instead of building a large-scale mono-centralized system, disperse a plurality of relatively inexpensive systems. It is now possible to build a system that manages data.
[0003]
By the way, black-and-white drawings have been the mainstream in the past, but now, with the improvement of color processing technology, colorized documents and color drawings have increased. For this reason, an inexpensive database system cannot cope with it, and it is necessary to introduce an expensive large-scale database system or to use an ASP (Application Service Provider) to outsource data management to an external vendor.
[0004]
When accessing a large-scale database system or an ASP, there is a problem of cost for accessing data (network traffic, usage fee, etc.), and it is better to access data in a database system that is as cheap as possible.
[0005]
Therefore, it is necessary for the user to switch the data to be used depending on the operation.
[0006]
For such a request, the following conventional techniques, namely, (1) a technique of registering entity data in a location different from a database of a registration destination and a technique of registering a reference at a registration destination, and (2) a technique of registering a reference according to the size of data. This can be dealt with by combining a technique of dividing the server into automatically registered servers (for example, Patent Document 1).
[0007]
However, in a company, data does not always refer only to people in the registered department. For example, when considering distribution of drawings in the manufacturing industry, drawings are created in a development department, drawings are issued in a department that manages drawings, and drawings are distributed in paper form. The development department may access the entity data due to the design change, but the department that outputs the drawing often refers to the entity data, which causes additional network traffic. Therefore, it is not possible to solve the problem simply by allocating the server for registering the entity based on only the data amount.
[0008]
[Patent Document 1]
JP-A-9-37013
[Problems to be solved by the invention]
The present invention has been made in view of the above circumstances, and in consideration of the convenience of a user who frequently uses data, registers an entity of data near the user who frequently uses the data, and The purpose is to allow smooth access to.
[0010]
[Means for Solving the Problems]
According to the present invention, in order to achieve the above object, a configuration as described in the claims is adopted.
[0011]
In one example of the present invention, a data registration service is realized using the following functions.
(1) A function for determining a domain (network section) to which an entity is to be registered, based on a predefined data use form and a registered department when registering data.
(2) Function to determine the server to register the entity from the domain of the registration destination.
{Circle around (3)} When the entity is registered in a server different from the destination specified by the user by automatic distribution, a reference (or reference information) of the entity is simultaneously registered in the destination specified by the user.
[0012]
Even if the registration destination is to be registered in a server different from the registration destination, the entity can be easily and reliably accessed by the reference information. By determining the server for registering the entity based on the data use form and the department for registering the data, network traffic can be suppressed and operation considering security can be performed.
[0013]
Further, the present invention will be described. According to one aspect of the present invention, in order to achieve the above object, the data registration device includes: registering data to be registered in a predetermined registration system or a registration system designated by a user. Means for receiving a registration instruction to be registered; and a registration system in which a part of the data to be registered is to be registered, from the predetermined registration system or the registration system designated by the user, and another registration system. Means for selecting from the group of registration systems based on the attribute of the registration instruction; the registration system predetermined as the registration system for registering some entities of the data to be registered, or When the registration system specified by the user is selected, all the data to be registered are stored in the predetermined registration system or the user system. Means for registering in the registration system designated by the user; when one of the other registration systems is selected as the registration system in which a part of the data to be registered is to be registered, A part of the data to be registered is registered in the first registration system, and reference information for accessing the part of the data registered in the first registration system is referred to as another reference data. And means for registering in the predetermined registration system or the registration system specified by the user.
[0014]
In this configuration, a part of the data can be registered at the optimum registration destination, and, for example, a user who frequently uses the data can smoothly access the data. The attribute of the registration instruction is, for example, the form of use of the data, or a section for registering the data. For example, the department of the user who frequently uses the data can be determined according to the usage form, and the entity of the data is registered in a server of the domain (network section) of the user so as to achieve the convenience of the user. Such a user can access a server designated by the registration department when searching for data or the like, and can take out its substantial part from, for example, the nearest server.
[0015]
If a server for registering an entity is determined in accordance with a department in which data is registered, the entity can be registered in consideration of a security level determined in accordance with the registered department.
[0016]
The present invention can be realized not only as a device or a system but also as a method. In addition, it goes without saying that a part of such an invention can be configured as software. Also, it goes without saying that a software product used for causing a computer to execute such software is also included in the technical scope of the present invention.
[0017]
The above and other aspects of the invention are set forth in the appended claims and described in detail below using embodiments.
[0018]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be described.
[0019]
FIG. 1 shows a document management system to which the present invention is applied. In this figure, a development site domain 10A, a production site domain 10B, and a head office site domain 10C are connected via, for example, an external network 10D. “Domain” means a network partition, and may be a LAN segment of a LAN (including a virtual LAN) or a broadcast domain. It may be a management target area of the network management system. A development base database 20A is provided in the development base domain 10A, and document management is performed using the development base database 20A. The distribution base server 10A is provided in the development base domain 10A.
The distribution registration server 30A executes processing of functional blocks as shown in FIG. 2, and controls registration of data specifying the development base database 20A. This data registration differs from the conventional registration in that the entity part is registered in another desired database with reference to the entity registration destination determination table 40A. This will be described in detail later.
The client (also referred to as a client device) 50A designates data to be registered and sends a registration instruction to the distribution registration server 30A. The distribution registration server 30A refers to the entity registration destination determination table 40A and registers data in a desired registration mode described later.
[0020]
The production base database 20B and the headquarter base database 20C are similarly provided in the production base domain 10B and the headquarter base domain 10C. 50B and 50C are clients. A drawing system 60B is provided in the production base domain 10B. Of course, a drawing system may be provided in other domains 10A and 10B.
[0021]
A server similar to the distribution registration server 30A may be provided in the production base domain 10B and the headquarter base domain 10C to perform similar processing. Alternatively, the distribution registration server 30A for the development base domain may receive a registration instruction from another domain and control registration in the production base database 20B or the headquarter base database 20C.
Although not shown in FIG. 1, it goes without saying that other domains may be added, and in the following examples, the business base domain is also referred to.
[0022]
FIG. 2 schematically shows the function of the distribution registration server 30A of FIG. 1. In this drawing, the distribution registration server 30A includes a registration instruction receiving unit 310, an entity registration destination determining unit 320, a first registration control unit 330. , The second registration control unit 340 and the like.
[0023]
The registration instruction receiving unit 310 receives a registration instruction for data (specifications, in-house materials, drawing images, etc.) from the client 50A or the like and sends it to the entity registration destination determination unit 320. The registration instruction is associated with the issue destination department (that is, the department to which the client 50A or the like belongs), the usage mode, and the registration destination. Here, it is assumed that the registration destination is the development base database 20A. The entity registration destination determination unit 320 draws up the entity registration destination determination table 40A based on the information of the issuing department and the usage mode, and registers the entity as it is at the designated registration destination, or registers the entity at another registration destination. Decide whether to register.
[0024]
If the entity registration destination determination unit 320 determines that the entity is to be registered as it is at the designated registration destination, the first registration control unit 330 is activated and the data is registered in the normal manner in the development base database 20A of the designated registration destination Is done. This aspect is indicated by arrow A in FIG. The record indicated by the arrow A has the management number “10002002020”, the name “functional specification.doc”, the data type “data”, and is registered in the development base database 20A as it is. Note that entities such as image data and documents are accessed with a predetermined pointer under the management of the development base database 20A.
[0025]
On the other hand, if the entity registration destination determination unit 320 determines that the entity is to be registered at another registration destination, the second registration control unit 340 is activated, and the entity registration destination determination unit 320 registers the entity for sale registration. Is acquired and the entity is sorted and registered based on the information in the production base database 20B, the headquarter base database 20C, or the like. Further, the second registration control unit 340 acquires the reference of the distribution registration destination, replaces the reference with the entity of the data, and registers the data in the development base database 20A. This aspect is indicated by arrow B in FIG. The record indicated by the arrow B has the management number “10002002021”, the name “drawing A1.dat”, the data type “reference”, and the URL registered as a reference to the entity instead of the entity data or the pointer. You.
[0026]
FIG. 4 shows the operation of the distribution / registration server 30A. In this figure, when a registration instruction is received, information on the issuing department and the data use form is acquired (S10). Next, the entity registration destination is determined with reference to the entity registration destination determination table 40A based on the information (S11). This will be described later with reference to FIG.
Next, it is determined whether or not the server (database) designated as the registration destination matches the server (database) for registering the entity (S12). If the server (database) matches, the data including the entity is included in the designated registration destination. Is registered (S13). If they do not match, the entity is registered in the registration destination of the entity (S14), and the data including the reference of the entity is registered before being designated (S15).
[0027]
FIG. 5 shows the details of step S11 in FIG. 4. In this figure, one condition (each row of the table in FIG. 5) is extracted from the entity registration destination determination table 40A (see FIG. 5) (S20). It is determined whether the acquired information of the issuing department and the use form matches the condition, and if the information matches, the registration destination of the condition is determined as the distribution registration destination of the entity (S22). If the conditions do not match, the next condition is extracted, and steps S20 to S21 are repeated in the same manner. If it is finally found that the matching conditions are not scattered, the designated registration destination is set as the registration destination of the entity (normal data registration; S24).
[0028]
Finally, returning to FIG. 1, the data search will be described. The data is registered in the management source database 20A or the like (the registration destination of the entity is not limited to this). The user sends a search request to the database 20A or the like that manages the data to be searched, and acquires the data. At this time, the substantial parts such as images and documents may be registered in another database. For example, drawing images are generated and managed at a development site, but are used more frequently at a production site (drawing). The user of the production base accesses the production base database 20B using Klein and 50B, and searches for a desired drawing. At this time, it is assumed that parts other than the substantial part such as data images and documents are registered in the development base database 20A as they are, and the substantial part is registered in the production base database 20B. Then, the entity can be smoothly acquired from the client 50B at the production base, and the drawing can be smoothly performed using the drawing system 60.
[0029]
As described above, according to this embodiment, the registration destination of the entity of the data can be determined in various modes. For example, the data can be quickly acquired by registering it near the user who frequently uses the data. It becomes possible.
[0030]
It should be noted that the present invention is not limited to the above-described embodiment, and various changes can be made without departing from the gist of the present invention. For example, in the above-described example, the distribution registration server is arranged only in the development base domain, but may be arranged in one or more other domains. Further, a plurality of databases (servers) may be provided in a domain, or a configuration in which a database (server) is not provided in a predetermined domain may be adopted. In the above-described example, the entity registration destination is determined using the entity registration destination determination table. However, the user can specify the entity registration destination without using this table or together with this table, and based on the user's selection. The registration destination may be determined.
[0031]
【The invention's effect】
As described above, according to the present invention, a large amount of data such as a drawing image can be registered while ensuring convenience and security for a user who frequently uses the data.
[Brief description of the drawings]
FIG. 1 is a diagram showing an embodiment of the present invention as a whole.
FIG. 2 is a block diagram schematically showing main functions of a distribution registration server according to the embodiment.
FIG. 3 is a diagram for explaining how data is registered in the embodiment.
FIG. 4 is a flowchart illustrating a data registration process according to the embodiment.
FIG. 5 is a flowchart illustrating details of an important part of FIG. 4;
FIG. 6 is a diagram illustrating an example of an entity registration destination determination table used in the embodiment.
[Explanation of symbols]
10A Development base domain 10B Production base domain 10C Headquarter base domain 10D External network 20A Development base database 20B Production base database 20C Headquarter base database 30A Distribution registration server 40A Entity registration destination determination table 50A Client 50B Client 50C Client 60C Charting system 310 Registration instruction Receiver 320 Entity registration destination determiner 330 First registration controller 340 Second registration controller

Claims (8)

Means for receiving a registration instruction having a content of registering data to be registered in a predetermined registration system or a registration system specified by a user;
A registration system in which a part of the data to be registered is to be registered, from the predetermined registration system, or a registration system designated by the user, and a registration system group including another registration system, Means for selecting based on the attribute of the registration instruction,
When the predetermined registration system or the registration system specified by the user is selected as the registration system in which a part of the data to be registered is to be registered, all of the data to be registered is described above. Means for registering in a predetermined registration system or a registration system specified by the user;
When one of the other registration systems is selected as the registration system to register a part of the data of the registration target, the part of the data of the registration target is stored in the registration system. Reference information for registering in the first registration system and accessing the partial entity registered in the first registration system, together with another part of the data to be registered, in the predetermined registration system, Or a means for registering in a registration system designated by the user. 2. The data registration device according to claim 1, wherein the attribute of the registration instruction is a department to which the user to be registered belongs and a use of the data to be registered. The registration system for registering the data to be registered is managed by a network section. The attributes of the registration instruction are the network section corresponding to the department to which the registered user belongs and the use of the data to be registered. 2. The data registration apparatus according to claim 1, wherein the data registration apparatus is arranged in a network section different from a network section corresponding to a department to which the registered user belongs. In a data registration device in which a plurality of registration systems are distributed and arranged on a network,
Each of the plurality of registration systems,
Means for receiving a registration instruction having a content of registering data to be registered in the registration system body;
Means for selecting, based on the attribute of the registration instruction, a registration system to register a part of the data of the registration target from among the plurality of registration systems including the registration system body;
Means for registering all the data to be registered in the registration system body, when the registration system body is selected as a registration system in which a part of the data to be registered is to be registered,
When one registration system other than the registration system is selected as a registration system in which a part of the data to be registered is to be registered, the part of the data to be registered is registered in the one registration system. Means for registering in the system and registering reference information for accessing the partial entity registered in the first registration system in the registration system main body together with other parts of the data to be registered. A data registration device, characterized in that: Means for receiving a registration instruction having a content of registering data to be registered in a predetermined registration system or a registration system specified by a user;
Determining means for determining an entity registration destination in which a part of the registration target data is to be registered based on the attribute of the registration instruction;
Means for registering a part of the data to be registered in the entity registration destination determined by the determination means;
Means for registering the data to be registered, with reference information for accessing the partial entity being a component at the entity registration destination, instead of the partial entity. Data registration device. Means for receiving a registration instruction having a content of registering data to be registered in a predetermined registration system or a registration system specified by a user;
Means for receiving designation of another registration system in which a part of the data to be registered is to be registered;
If the designation of another registration system in which a part of the data to be registered is to be registered is not accepted, all of the data to be registered is registered in a predetermined registration system or registered by the user. Means for registering with the system;
If the designation of another registration system in which a part of the data to be registered is to be registered is accepted, the part of the data to be registered is replaced based on the designation of the other registration system. The reference information for accessing the partial entity registered in the other registration system is registered in the predetermined registration system or the registration system specified by the user. Means for registering data together with the data. A step of receiving a registration instruction having a content of registering data to be registered in a predetermined registration system or a registration system specified by a user,
A registration system in which a part of the data to be registered is to be registered, from the predetermined registration system, or a registration system designated by the user, and a registration system group including another registration system, Selecting based on the attribute of the registration instruction;
When the predetermined registration system or the registration system specified by the user is selected as the registration system in which a part of the data to be registered is to be registered, all of the data to be registered is described above. Registering in a predetermined registration system or a registration system specified by the user;
When one of the other registration systems is selected as the registration system to register a part of the data of the registration target, the part of the data of the registration target is stored in the registration system. Reference information for registering in the first registration system and accessing the partial entity registered in the first registration system, together with another part of the data to be registered, in the predetermined registration system, Or a step of registering in the registration system designated by the user. A step of receiving a registration instruction having a content of registering data to be registered in a predetermined registration system or a registration system specified by a user,
A registration system in which a part of the data to be registered is to be registered, from the predetermined registration system, or a registration system designated by the user, and a registration system group including another registration system, Selecting based on the attribute of the registration instruction;
When the predetermined registration system or the registration system specified by the user is selected as the registration system in which a part of the data to be registered is to be registered, all of the data to be registered is described above. Registering in a predetermined registration system or a registration system specified by the user;
When one of the other registration systems is selected as the registration system to register a part of the data of the registration target, the part of the data of the registration target is stored in the registration system. Reference information for registering in the first registration system and accessing the partial entity registered in the first registration system, together with another part of the data to be registered, in the predetermined registration system, Alternatively, a computer program for registering data is used for causing a computer to execute the step of registering in a registration system designated by the user.

Images