TW202016754A - Flexible web data management system and a method thereof - Google Patents

Abstract

A flexible WEB data management system and a method thereof is provided. The method includes steps of storing WEB data in a database according to a database schema and metadata, so as to create an entity and extension data corresponding thereto; establishing a first corresponding relationship between attributes of the entity and the extension data and the metadata; establishing a second corresponding relationship between the attributes of the entity and the extension data and the structural data exchange format; generating a data view model according to the attributes of the entity and the extension data, and the first corresponding relationship and the second corresponding relationship; providing an access and management interface to access or manage the data view model; obtaining the data view model through the access and management interface; and generating a webpage or report according to the data view model, to meet different requirements.

Description

Flexible webpage data management system and method

The invention relates to a data management technology, in particular to a flexible webpage data management system and method.

With the rapid development of digital information technology, a large number of new services are provided through the Internet, becoming the most valued technology field in recent years. When customers use services on the Internet, the first page they visit is the relevant webpage of the service. However, in the network environment where service items are constantly being updated and customer needs are diversified, how to quickly realize the idea of becoming a service appears on the webpage for customers to use The key issue of software development.

In addition, most network services need to integrate data or information objects in multiple fields, but the structure or attributes of data or information objects in different fields are different. This factor also increases the difficulty of constructing and managing web data systems.

To solve the above problems, the inventor designed based on the MVC model (Model-View-Controller), integrated Intelligent Internet Information Schema (Intelligent Internet Information Schema) and Dublin Interpretive Data Core Set (DC, Dublin Core), to provide a flexible Web page data management system and method thereof to improve the efficiency of constructing and managing the web page data system.

According to the flexible webpage data management system and method of the present invention, users can more easily organize data or information objects in different fields or with different interpretation data (Metadata) and present them as webpages.

According to the flexible web page data management system and method of the present invention, users can use the management interface to control the entire knowledge structure, and can automatically build a single page application (SPA, Single) that conforms to Responsive Web Design (RWD, Responsive Web Design) Page Application) service.

According to an embodiment, the present invention provides a flexible webpage data management system, including: a database, based on a database schema and a metadata schema with an entity and corresponding at least at least one entity An extension table stores at least one web page data, and the database includes a mapping unit for recording a first correspondence between the plurality of attributes of the entity and at least one extension data and the interpretation data format, and A second correspondence relationship with a structured data exchange format; a data model unit for accessing the mapping unit, and according to a plurality of attributes of the entity and at least one extended data, a first correspondence relationship and a second correspondence relationship, Generating a data view model; a data controller unit, providing an access management interface for accessing or managing at least one data view model; and a web page viewing unit, obtaining at least one data view through the access management interface Model and generate a webpage based on at least one data view model.

In one embodiment, the format of the interpretation data is Dublin Core, and the plural fields of the Dublin Core set include title, creator, subject, description, Publisher, contributor, date, resource type, format, identifier, source, language, relation, Coverage (coverage), and rights management (rights).

In an embodiment, the data model unit, the data controller unit, and the webpage viewing unit conform to a Model-View-Controller (MVC) architecture.

In one embodiment, the structured data exchange format is a JavaScript Object Notation (JSON) format, and the access management interface is an application programming interface (API).

In one embodiment, the mapping unit is a lookup table, and the lookup table stores the correspondence between the plurality of attributes of the entity and the at least one extended data, the plurality of fields in the Dublin core set, and the plurality of fields in JSON format.

According to an embodiment, the present invention provides a flexible webpage data management method, including: creating at least one webpage data in a database according to a table structure and an interpreted data format (metadata) and corresponding to an entity (Entity) At least one extension table (extension table); establishing a first correspondence between the plurality of attributes of the entity and at least one extension data and the interpretation data format; establishing a plurality of attributes of the entity and at least one extension data and a structural data exchange format A second correspondence between; based on a plurality of attributes of the entity and at least one extended data, the first correspondence and the second correspondence, a data view model is generated; an access management interface is provided to access or manage at least A data view model; and obtaining at least one data view model through the access management interface, and generating a webpage according to the at least one data view model.

In one embodiment, the interpretation data format is Dublin Core, and the plural fields of the Dublin Core set include title, creator, subject, description, and publication (Publisher), contributor (contributor), date (date), resource type (type), data format (format), identifier (identifier), source (source), language (language), association (relation), coverage Coverage and rights management.

In an embodiment, the data model unit, the data controller unit, and the webpage viewing unit conform to a Model-View-Controller (MVC) architecture.

In one embodiment, the structured data exchange format is a JavaScript Object Notation (JSON) format, and the access management interface is an application programming interface (API).

In one embodiment, the mapping unit is a lookup table, and the lookup table stores the correspondence between the plurality of attributes of the entity and the at least one extended data, the plurality of fields in the Dublin core set, and the plurality of fields in JSON format.

The advantages, features, and technical methods of the present invention will be described in more detail with reference to the exemplary embodiments and the accompanying drawings to make it easier to understand, and the present invention can be implemented in different forms, so it should not be understood that it is limited to the The stated embodiments, on the contrary, for those of ordinary skill in the art, the provided embodiments will make the disclosure more thorough and comprehensive and complete to convey the scope of the present invention, and the present invention will only be additional Defined by the scope of patent application.

As used herein, the term "and/or" includes any or all combinations of one or more related items. When the prefix of "at least one of them" precedes a list of components, it modifies the entire list of components rather than individual components in the list.

Please refer to FIG. 1, which is a block diagram of the flexible web page data management system of the present invention. As shown in FIG. 1, the flexible webpage data management system includes a database 11, a data model unit 12, a data controller unit 13, and a webpage viewing unit 14. The main features of the present invention are that the data model unit 12, the data controller unit 13 and the web page viewing unit 14 are implemented by using a Model-View-Controller (MVC) architecture, and the database integrates the intelligent Internet Information Architecture (Intelligent Internet Information Schema) and Dublin Interpretive Data Core Set (DC, Dublin Core) to store data, so that users can more easily organize data or information objects in different fields or different metadata (Metadata), And can use the management interface to control the entire knowledge structure, and can automatically build a single page application (SPA, Single Page Application) service that conforms to Responsive Web Design (RWD, Responsive Web Design).

The database 11 stores at least one web page data with the entity 20 and the corresponding at least one extended data 113 based on the table structure and the meta data format (MetaData) 112. In one embodiment, the interpretive data format 112 may use Dublin Core. The plural fields of the Dublin Core set include title, creator, subject, description, Publisher, contributor, date, resource type, format, identifier, source, language, relation, Coverage (coverage), and rights management (rights).

Please also refer to FIG. 2 which shows a database structure diagram of an embodiment of the flexible web page data management system of the present invention. The table structure shown in the figure is realized by Intelligent Internet Information Schema (Intelligent Internet Information Schema), which is characterized by adopting a class (Class) and object (Object) related structure, for example, in order to store a piece of web data , An entity (Entity) 20 may be created first, and the corresponding table may include a plurality of preset fields of EID, CName, and EName. Objects can contain EntityM2DC, which records the related information (Field) of each entity (Entity), and DCField and JSONFiled corresponding to each information (Field). Among them, DCField (Dublin Core Field) can be used as a cross-domain database (Domain Database) cross-reference data (Metadata) standards. Through this standard, the contents in the table fields of databases in different fields can be matched, processed and queried.

Then, an object 21 is created corresponding to the entity 20. The object 21 belongs to the entity 20, and the corresponding object table has a plurality of preset fields, such as OID, CName, CDes, Since, and LastModifiedDT, for recording the object 21 Basic information. The object relationship table 211 (ORel) records the association between objects, among which many objects are many-to-many. The object category relation table 212 (CO Table) records the category to which each object is classified. An object can be classified into multiple categories, and a category can have multiple objects at the same time, so there is a many-to-many relationship between objects and categories. The class inheritance relationship table 221 (Inheritance Table) records the association between a parent class (Parent Class) and a child class (Child Class). A parent category can have multiple subcategories; a subcategory can also correspond to multiple parent categories, which is a many-to-many association. With this structure, in addition to creating a common tree directory structure, this association structure can also be used to record a lattice structure that implements multiple inheritance.

Further, an extension table 113 is created in the intelligent internet information structure to expand fields according to the attribute requirements of the entity.

In the intelligent Internet information architecture, Class 22 is used to manage and classify objects. Plural classes are presented as hierarchical tree/lattice structures, and their corresponding class tables ( Class Table) stores the defined directory information, and records the association between the parent category and the sub-category through the class inheritance relationship table.

The database 11 further includes a mapping unit 111, such as EntityM2DC in FIG. 2, the mapping unit 111 is used to record the first correspondence between the plurality of attributes of the entity 20 and at least one extended data 113 and the interpretation data format 112, and The second correspondence between structural data exchange formats. In one embodiment, the interpreted data format 112 can be implemented in Dublin Core, and the structured data exchange format can be implemented in the JAVA script language object representation (JSON) format.

Please refer to FIG. 3 for a schematic diagram of an embodiment of the mapping unit of the flexible web page data management system of the present invention. In an embodiment, the mapping unit 111 can be implemented with a lookup table, such as the following Table 1. As shown in FIG. 3, the object type corresponding to the entity 20 is a member. The fields include the OID, CName, and EName fields of the object, and the Account and Email fields of the member. The mapping unit 111 establishes the first correspondence between the OID, CName, and EName fields, the Account and Email fields, and the Dublin Core Set field (DCField); as shown in Table 1, OID, CName, EName, Account, and Email The fields correspond to the 10th column of the Dublin Core set: identifier, 1st column: title, 1st column: title, 1st column: title and 1st column 2 columns: creator. Table I

At the same time, the mapping unit 111 records the second correspondence between the plurality of attributes of the entity 20 and the extension data 113 and the structure data exchange format. As shown in Table 1, the OID, CName, EName, Account, and Email fields correspond to the id, cname, ename, account, and email fields in the JSON field (JsonField), respectively.

The data model unit 12 is used to access the mapping unit 111 and generate a data view model (Model) 121 according to the plurality of attributes of the entity 20 and at least one extended data 113, the first correspondence and the second correspondence.

The data controller (Controller) unit 13 provides an access management interface 131 for accessing or managing at least one data view model 121. In one embodiment, the access management interface 131 may be an application programming interface (API), such as GetDataAPI and ManageDataAPI; however, this is only an example, and the present invention is not limited thereto. The webpage viewing unit 14 obtains at least one data view model 121 through the access management interface, and generates a webpage according to the at least one data view model 121.

Because the Dublin Core Collection is currently the most widely used interpretive data format for network resources, government publications, and museum collections, when users want to integrate data or information objects in different fields, even the structure of data or information objects in different fields Or attributes are not the same, as long as the mapping unit 111 records the correspondence between the structure or attributes of this data or information object and the fields of the Dublin Core Set, and the second correspondence between the record structure data exchange formats, such as Table 1 , The user can directly generate the model-view-controller (MVC) structure formed by the data model unit 12, the data controller unit 13, and the web page viewing unit 14, and automatically generate the data containing the data or information objects. Web page.

In addition, the model view controller (MVC) architecture is already a commonly used architecture, so when the flexible web page data management system of the present invention uses the MVC architecture to integrate data or information objects in different fields, it also makes it easier for users to use the ready-made API for web page management and data integration.

According to the flexible webpage data management system and method of the present invention, users can more easily organize data or information objects in different fields or with different interpretation data (Metadata) and present them as webpages. In addition, users can use the management interface to control the entire knowledge structure, and can cooperate with the WEB front-end modules that have been developed, such as React Components, to automatically build single-page applications (SPA, Responsive Web Design) in line with Responsive Web Design (SPA, Single Page Application) service.

Please refer to FIG. 4, which shows a flowchart of the flexible webpage data management method of the present invention. The invention includes steps S51-S56. In step S51, according to a table structure and an interpreted data format (metadata), at least one web page data is created in a database as an entity (Entity) and corresponding at least one extension table (extension table). In one embodiment, the interpretive data format 112 may use Dublin Core. The plural fields of the Dublin Core set include title, creator, subject, description, Publisher, contributor, date, resource type, format, identifier, source, language, relation, Coverage (coverage), and rights management (rights).

In step S52, a first correspondence between the plurality of attributes of the entity and at least one extended data and the interpretation data format is established. In step S53, a second correspondence between the plurality of attributes of the entity and at least one extended data and a structured data exchange format is established. For implementation examples of the first correspondence relationship and the second correspondence relationship, reference may be made to Table 1 and FIG. 3 above, and details are not described herein again.

In step S54, a data view model is generated according to the plurality of attributes of the entity and at least one extended data, the first correspondence and the second correspondence. In step S55, an access management interface is provided for accessing or managing at least one data view model. In step S56, at least one data view model is obtained through the access management interface, and a web page is generated according to the at least one data view model. Steps S54 to S56 are implemented according to the commonly used model view controller (MVC) architecture. Therefore, when the flexible web page data management system of the present invention uses the MVC architecture to integrate data or information objects in different fields, it also allows users to Convenient use of ready-made APIs for web page management and data integration.

In addition, when the various elements shown and discussed are placed in different positions, it can be understood that the relative positions of the various elements can be changed, and at the same time the functions mentioned above are still retained here. It is conceivable that a sub-collection of various combinations, specific features and embodiments can be carried out, and this sub-collection still falls within the scope of this description. Various features and the disclosed embodiments may be combined with or substituted for each other, and all such modifications and changes will fall within the scope defined by the appended claims of the present invention.

11: Database 111: Mapping unit 112: Interpreted data format 113: Extended data 12: Data model unit 121: Data view model 13: Data controller unit 131: Access management interface 14: Web page viewing unit 20: Entity 21: Object 211: Object relationship table 212: Object category relationship table 22: Category table 221: Category inheritance relationship table S51~S56: Steps

Figure 1 is a block diagram of the flexible web page data management system of the present invention.

Figure 2 is a database structure diagram of an embodiment of the flexible web page data management system of the present invention.

FIG. 3 is a schematic diagram of an embodiment of the mapping unit of the flexible webpage data management system of the present invention.

Figure 4 is a flowchart of the flexible web page data management method of the present invention.

S51~S56: Step

Claims (10)

A flexible webpage data management system, including: a database, based on a database schema and a metadata format, stored in at least one entity (Entity) and corresponding at least one extension table (Extension table) A web page data, and the database includes a mapping unit for recording a first correspondence between the plurality of attributes of the entity and the at least one extended data and the interpreted data format, and a structural data A second correspondence between the exchange formats; a data model unit for accessing the mapping unit and based on the plurality of attributes of the entity and the at least one extended data, the first correspondence and the second correspondence To generate a data view model; a data controller unit to provide an access management interface for accessing or managing the at least one data view model; and a web page viewing unit to obtain the data through the access management interface At least one data view model, and generating a webpage according to the at least one data view model. The flexible webpage data management system as described in item 1 of the scope of patent application, wherein the format of the interpreted data is Dublin Core, and the plural fields of the Dublin Core Set contain the title and creator ( creator), subject, description, publisher, contributor, date, resource type, format, identifier, source (source), language (language), relationship (relation), coverage (coverage), and rights management (rights). The flexible webpage data management system as described in item 2 of the patent application scope, wherein the data model unit, the data controller unit and the webpage viewing unit conform to a Model-View-Controller (MVC) architecture. The flexible web page data management method as described in item 3 of the patent application scope, wherein the table structure is implemented by Intelligent Internet Information Schema (Intelligent Internet Information Schema), which uses a Class (Object) and object (Object) associated architecture. The flexible webpage data management system as described in item 4 of the patent application scope, wherein the mapping unit is a lookup table that stores a plurality of attributes of the entity and at least one extended data and a plurality of columns of the Dublin Core Set And the corresponding relationship between the multiple fields in the JSON format. A flexible webpage data management method includes: according to a table structure and an interpreted data format (metadata), at least one webpage data is created in a database as an entity (Entity) and corresponding at least one extension data (extension table) ); Establishing a first correspondence between the plurality of attributes of the entity and the at least one extended data and the interpreted data format; establishing the plurality of attributes of the entity and the at least one extended data and a structural data exchange format A second correspondence relationship; generating a data view model based on the plurality of attributes of the entity and the at least one extended data, the first correspondence relationship, and the second correspondence relationship; providing an access management interface for access Or manage the at least one data view model; and obtain the at least one data view model through the access management interface, and generate a webpage according to the at least one data view model. The flexible web page data management method as described in item 6 of the patent application scope, wherein the interpreted data format is Dublin Core, and the plural fields of the Dublin Core Set include the title and creator ), subject (subject), description (description), publisher (publisher), contributor (contributor), date (date), resource type (type), data format (format), identifier (identifier), source ( source), language (language), association (relation), coverage (coverage), and rights management (rights). The flexible webpage data management method as described in item 7 of the patent application scope, wherein the structured data exchange format is the JAVA script language object representation (JavaScript object notation, JSON) format, and the access management interface is an application program interface ( API). The flexible webpage data management method as described in item 8 of the patent application scope, wherein the mapping unit is a lookup table that stores the plural attributes of the entity and the at least one extended data and the plural number of the Dublin Core Set The corresponding relationship between each field and the plural fields in the JSON format. The flexible webpage data management method as described in item 9 of the patent application scope, wherein the table structure is implemented by Intelligent Internet Information Schema (Intelligent Internet Information Schema), which uses a Class (Object) and object (Object) associated architecture.

Images