KR101084339B1 - Shared file management system and method - Google Patents

Abstract

The present invention relates to a shared file management system and method, comprising: a wiki engine for providing a user interface, a shared file management manager for interworking with a wiki engine and setting user rights and constraints for a shared file in a file attribute specification; And a data management unit verifying a user's authority and verifying a constraint according to a user's data input by referring to a file attribute specification. According to the present invention, a plurality of users can manage the shared document efficiently.

Shared File Management, Wiki Engine, File Attribute Specification, Validation

Description

SHARED FILE MANAGEMENT SYSTEM AND METHOD}

The present invention relates to a shared file management system and method, and more particularly, to a shared file management system and method using a wiki engine.

Several systems and applications have been studied for managing documents created, modified, and reviewed by multiple users.

Documents are often written by a small number of people, but many are often created simultaneously or by review. Also, even after a document is written and published, the document can be constantly changed through the development process. During development, you need to keep track of the documentation of other teams or parts, as well as the documents of yourself or the teams or parts you belong to. However, this process may refer to old documents and different versions of documents rather than the latest document. Also, in the case of collaboration, it can be very difficult to assemble the document itself and produce the current version.

SUMMARY OF THE INVENTION An object of the present invention is to provide a shared file management system and method for efficiently creating and managing documents shared by a plurality of users.

The shared file management system according to an aspect of the present invention for solving this problem is a wiki engine that provides a user interface, a share that is linked with the wiki engine and sets user rights and constraints for a shared file in a file attribute specification. A file management manager, and a data manager for verifying the user's authority and verifying the constraint according to a user's data input with reference to the file attribute specification.

The file attribute specification may include a file table including shared file information, wiki page information, and access type information indicating the user's authority, a data type table including data type information about the shared file, and an attribute for the data type. It may include a data field table containing information.

The shared file management unit includes a list management module for managing a list of the shared file, a registration and modification management module for managing to register or modify the file attribute specification, and a history management module for managing a change history for the shared file. can do.

The data management unit may include a data type management module managing a data type using the file attribute specification, and a verification management module verifying a constraint condition on the shared file.

According to another aspect of the present invention, there is provided a method of managing a shared file, the method comprising: setting user rights and constraints on a shared file in a file attribute specification, receiving a request for obtaining user rights by the wiki engine, and allowing a user to use the wiki engine. Receiving shared data by the user when acquiring a user right; validating the shared data using the file attribute specification; and storing the shared data when the validity is verified. .

The validating step may include loading the file attribute specification, checking data input authority for the shared data with reference to the file attribute specification, and constraints on the shared data with reference to the file attribute specification. And verifying the condition.

The file attribute specification may include shared file information, wiki page information, access type information indicating the user's authority, data type information about the shared file, and attribute information about the data type.

According to the present invention, various attributes can be assigned to a shared document created, modified, and reviewed by a plurality of users, and the shared document can be efficiently managed based on this. Therefore, the change of the shared document is propagated in real time, the latest document can be referred to, and various management of the shared document, such as checking the change history and canceling the modified matter, can improve the collaboration effect among multiple users.

In the following detailed description, reference is made to the accompanying drawings, which form a part hereof. Unless otherwise indicated in the context, like reference numerals generally refer to like elements in the drawings. The illustrative embodiments described in the detailed description, drawings, and claims are not meant to be limiting. Other embodiments may be utilized and other changes may be made without departing from the spirit or scope presented herein. The components herein can be arranged, substituted, combined, and designed in different configurations within a wide variety of different configurations, as generally described herein and shown in the figures, all of which are clearly It will be readily understood that it has been considered and forms part of this application.

First, a shared file management system according to an exemplary embodiment of the present invention will be described in detail with reference to FIGS. 1 to 4.

1 is a block diagram illustrating a shared file management system according to an embodiment of the present invention, and FIG. 2 is a diagram illustrating a data structure of a file attribute specification used in a shared file management system according to an embodiment of the present invention. 3 is a block diagram of the shared file manager of FIG. 1, and FIG. 4 is a block diagram of the data manager of FIG. 1.

As shown in FIG. 1, the shared file management system 100 according to an embodiment of the present invention includes a wiki engine 110, a shared file manager 120, a data manager 130, a file input / output manager 140, and It includes a database 150, and is connected to the plurality of user terminals 200 through the communication network (300).

Wiki engine 110 is a program that implements WikiWiki by satisfying Wiki Principles. WikiWiki is a community web site system that anyone can modify anything, anytime, anywhere. The wiki engine 110 may use Moin Moin, MoniWiki, MediaWiki, DokuWiki, PmWiki, North Momoin Moin, etc., which are open to date. It is not limited.

The wiki engine 110 provides a user interface to the user terminal 200, supports document collaboration such as editing, updating or modifying a document by a plurality of users on a web page, and related materials (pages or files) and Make it work. The wiki engine 110 basically shows the most recent document, makes it possible to refer to the change history for the document, and to easily recover the document. Document is used here as a concept that includes files and web pages (wiki pages).

The database 150 stores a plurality of shared files and a plurality of web pages, and stores a file attribute specification having information about each shared file.

Referring to FIG. 2, the file attribute specification includes a file table 410, a data set table 420, a data type table 430 representing attributes of each data type, and a data field including attributes of individual items of each data type. Table 440.

The file table 410 includes information about a shared file (File ID) and information about a wiki page (Wiki Page ID). This allows shared files and wiki pages to work together. In addition, the file table 410 includes information such as an access type (Author), indicating the access and modification rights of the user. In multi-user collaboration, the right to edit is very important. Examples of the right to modify may be classified as "non-modifiable", "only allowed users", "any user can".

The data set table 420 represents information on at least one table or data included in one document or wiki page, and includes information on a shared file (File ID), information on a data set (Data Set ID), and data. Type information (Data Type ID), a set sequence, a data set name, and the like. Here, the set sequence indicates how many times the corresponding data is located in the data set.

The data type table 430 defines what data type the document has, and includes data type ID, Wiki Template ID and field number (No. of). Fields). The data type is used to represent a single intact value using related data. For example, if the information is about an orbit, the type of the track, the altitude, the local time, the inclination, etc. The aggregate is the "orbit" data type.

The data field table 440 defines data attributes for a data type, and includes data type information (Data Type ID), a field sequence, a field name, a field type, a constraint ( Restrictions). Here, the field sequence indicates how many times the corresponding data is located in the data type, and the constraints include the conditions for the data. Documents can be basically divided into several parts, each of which can have constraints based on its content. This constraint can be applied to the process of constructing each table. In the "orbit" data type mentioned earlier, the orbit types can be sun synchronous, circular orbit, and polar orbit, which are data attributes for "orbit type" data. . That is, one piece of information or a table may be expressed through a data type in which data attributes having constraints are collected.

According to such a file attribute specification, it is possible to know the name of the shared file and the name of the wiki page linked thereto, and also to know what data type the document has, and what constraints it has.

For example, if a document is a page that estimates power consumption in a satellite system specification, the page may include a table with a description of the document and a detailed value of power consumption. In this case, the description may be defined in the form of plain text, and the power consumption table may be defined in the form of a database. In addition, the field indicating the value of the power consumption in the power consumption table may be a number or data of a predefined form. If the user enters anything here that is not a numeric or pre-defined data value, the system can automatically reject the entry.

Referring to FIG. 3, the shared file manager 120 manages a list management module 122 for managing a list of shared files, a registration and modification management module 124 for managing to register or modify a shared file attribute specification, and a share. A history management module 126 manages a file change history, and manages a shared file using a file attribute specification. The shared file manager 120 may set various user rights on the file property specification for the document, limit the format and the type of data that the document should contain, and set constraints on data included in the document. .

Referring to FIG. 4, the data manager 130 includes a data type management module 132 for managing data types using a file attribute specification and a verification management module 134 for verifying constraint conditions. The data manager 130 may designate a data type of a document or an attribute of data included in the document, and determine whether the data input by the user is valid using a file attribute specification that is already defined. You can decide to update. Therefore, if a user inputs data different from the original intention, the contents may not be propagated to other users. For example, if the user inputs "Triangle" for the above-described trajectory type, the data manager 130 may determine that there is a problem with the corresponding input during the constraint condition verification, and thus the user's input is invalid. .

The file input / output manager 140 stores the shared file input from the user terminal 200 in the database 150 or outputs the shared file stored in the database 150 to the user terminal 200.

The user terminal 200 is a communication terminal device that allows a user to input, modify, and output a shared file. The user terminal 200 accesses the shared file management system 100 through the communication network 300 to exchange information. Of course, the user terminal 500 may access the shared file management system 100 through user authentication such as login and transmit and receive information therefrom. The user terminal 200 may be a desktop computer as well as a laptop computer, a workstation, a palmtop computer, an ultra mobile personal computer, a tablet PC, a personal digital assistant (PDA), a web pad, a mobile phone. It may be made of a terminal having a computing power by including a memory means and a microprocessor.

The communication network 300 may include a telephone network as well as a data communication network including a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), the Internet, and the like. It can be used, and it does not matter wired and wireless, and it does not matter which communication method is used.

The shared file management system 100 may be implemented in the form of a server, or may be implemented to be included in the user terminal 200. In addition, although the database 150 has been described as being included in the shared file management system 100 according to the embodiment of the present invention, it is not necessarily included, and in this case, the database 150 is external to the shared file management system 100. It may be implemented and may be connected to the shared file management system 100 through the communication network (300).

In this way, Wiki Engine adds an extension for document management and manages shared documents using file attribute specifications to handle information on shared documents. Various properties can be given to a document, and shared documents can be managed efficiently based on the document. Therefore, the change of the shared document is propagated in real time, the latest document can be referred to, and various management of the shared document, such as checking the change history and canceling the modified matter, can improve the collaboration effect among multiple users.

Next, a shared file management method according to another embodiment of the present invention will be described in detail with reference to FIGS. 5 and 6.

FIG. 5 is a flowchart illustrating a shared file management method according to an embodiment of the present invention, and FIG. 6 is a flowchart illustrating the validation process of FIG. 5 in detail.

First, referring to FIG. 5, a user requests a user right by the wiki engine 110 (S100). A user may input his or her ID and password in the user terminal 200 and receive user authentication. In the user authentication process, the wiki engine 110 may grant a certain user right to the user. However, whether the user authority is acquired by the wiki engine 110 is not essential according to the type of the wiki engine 110, and thus, the user authority obtained by the wiki engine 110 may be omitted as necessary.

If it is determined in step S110 that the user has obtained the authority, the user performs an operation on the shared document such as registering or modifying the shared data through the user terminal 200 (S120). However, the wiki engine 110 ends the operation when it is determined in step S110 that the user is not registered or is not allowed.

The data manager 130 validates the data input or modified by the user (S130). If it is determined that the data input by the user is valid (S140), the user input data is stored in the database 150 (S150) and the operation is completed. However, if it is determined that the data input by the user is invalid (S140), the input data of the user is discarded and the operation ends.

Next, the data validity verification in the data manager 130 will be described in more detail with reference to FIG. 6.

When the validation starts (S210), the data manager 130 loads the file attribute specification from the database 150 (S220). In operation S230, the user authority for the corresponding user is checked with reference to the file attribute specification and the user has a data input authority. If it is determined that there is an input right (S240), the condition for the constraint is verified by referring to the data attribute of the input data (S250). If it is determined that the data input by the user meets the constraint (S260), the validation is successful and the operation is returned. On the other hand, if it is determined that there is no input authority in step S240 or if the input data of the user does not meet the constraints in step S260, the operation is returned as the validation fails (S280).

Referring to the method of managing a shared file according to the present embodiment, the user may first obtain a user right by the wiki engine 110, and the user who has obtained the user right may input data. When the user completes the data input, the shared file management system 100 checks again by referring to the file attribute specification whether the user has the right to modify the document and also verifies the constraint on the input data.

Although the preferred embodiments of the present invention have been described in detail above, the scope of the present invention is not limited thereto, and various modifications and improvements of those skilled in the art using the basic concepts of the present invention defined in the following claims are also provided. It belongs to the scope of rights.

1 is a block diagram illustrating a shared file management system according to an embodiment of the present invention.

2 is a diagram illustrating a data structure of a file attribute specification used in a shared file management system according to an embodiment of the present invention.

3 is a block diagram of the shared file manager of FIG. 1.

4 is a block diagram of the data manager of FIG. 1.

5 is a flowchart illustrating a shared file management method according to an embodiment of the present invention.

FIG. 6 is a flowchart illustrating the validation process of FIG. 5 in detail.

≪ Description of reference numerals &

100: shared file management system, 110: wiki engine,

120: shared file management unit, 122: list management module,

124: registration and modification management module, 126: history management module,

130: data management unit, 132: data type management module,

134: verification management module, 140: file input and output management unit,

150: database, 200: user terminal,

300: network

Claims (7)

A shared file management system connected to a plurality of user terminals to manage shared files, A wiki engine providing a user interface to the user terminal and receiving a request for obtaining user authority from the user terminal; A shared file manager interworking with the wiki engine and setting user rights and constraints on the shared file in a file attribute specification; and A data management unit which validates the shared data received from the user terminal with reference to the file attribute specification, and stores the shared data in a database when the validity is verified Shared file management system comprising a. In claim 1, The file attribute specification is A file table including shared file information, wiki page information, and access type information indicating the user's authority; A data type table including data type information for the shared file, and Data field table containing attribute information for the data type Shared file management system that includes. The method of claim 1 or 2, The shared file management unit includes a list management module for managing a list of the shared file, a registration and modification management module for managing to register or modify the file attribute specification, and a history management module for managing a change history for the shared file. Shared file management system. The method of claim 1 or 2, The data management unit includes a data type management module managing a data type using the file attribute specification, and a verification management module verifying a constraint condition on the shared file. A shared file management method of a shared file management system connected to a plurality of user terminals to manage shared files, Setting, by the shared file management system, user rights and constraints on the shared file in a file attribute specification; Receiving, by the shared file management system, a request for obtaining user authority by a wiki engine from the user terminal; When the user acquires a user right by the wiki engine, the shared file management system receiving input of shared data by the user; The shared file management system validating the shared data using the file attribute specification; and Storing the shared data in a database by the shared file management system when the validity is verified Shared file management method comprising a. The method of claim 5, The validation step, Loading the file attribute specification; Confirming data input authority for the shared data by referring to the file attribute specification; and Verifying a constraint condition on the shared data by referring to the file attribute specification Shared file management method comprising a. In claim 5 or 6, The file attribute specification includes shared file information, wiki page information and access type information indicating the user's authority, data type information for the shared file, and attribute information for the data type.

Images