KR101062655B1 - Metadata Management System Using Tag and Its Method - Google Patents

Abstract

The present invention relates to a metadata management technology, specifically, the present invention can recommend a tag related to the content to the user when the user uploads his or her content, and thus the relationship between the tags based on the input tag A metadata management system and a method for managing content by setting a surname, and a method for managing the content, the metadata management system according to one aspect, the metadata for adding a tag to the first tag input by the user to create a tag object And a metadata relationship module for generating a relationship table by setting a relationship between the first tag and a second tag stored in a tag database by using the generation module.

Metadata, tagging, content, tag recommendations

Description

Metadata management system using tags and method thereof {Metadata managing system using tags and method

The present invention relates to a metadata management technology, specifically, the present invention can recommend a tag related to the content to the user when the user uploads his or her content, and thus the relationship between the tags based on the input tag A metadata management system and method for managing content by setting a last name.

The present invention is derived from a study conducted as part of the IT source technology development project of the Ministry of Knowledge Economy and the Ministry of Information and Communication Research and Development. [Task management number: 2008-F-043-01, Task name: Location / Social Relationship Cognitive Social Media] Service technology development].

According to a conventional web service, a user searches by using a title or a keyword of content for an input post or the like in order to search for input content.

However, such a conventional method of managing search and user-entered content is, as the type of the input content evolves into various forms such as text, images, videos, blogs, etc., and as the input content increases exponentially. Many inconveniences arise in search and use thereof.

As such, by adding metadata, which is semantic information of the content, to the content scattered in various forms, the concept of the semantic web is generated to increase the efficiency of searching and using the content. The semantic web defines the vocabulary to use and its ontology, and uses metadata to describe metadata through semantic annotations.

However, the semantic annotation technology of the conventional semantic web has a disadvantage in that it is difficult for general users who use the web to be easily used due to lack of user convenience. In addition, there is a problem that the technical implementation difficulty is high and the actual implementation performance is not good.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-described problem, and an object of the present invention is to solve the problem of the present invention by using a tag to configure metadata and to establish a relationship between the tags. It is to provide a data management system and method thereof.

In order to solve the above problems, a metadata management system according to an aspect of the present invention, the metadata generation module for generating a tag object by adding an attribute tag to the first tag input by the user; And a metadata relationship module for generating a relationship table by setting a relationship between the first tag and a second tag stored in a tag database using the attribute tag.

According to another aspect of the present invention, there is provided a method for managing metadata, comprising: constructing a database for the content using the first tag as index information using content input by a user and a first tag corresponding thereto; Generating an attribute tag including a domain tag, a category tag, and an item tag for the first tag; And generating a relationship table by setting a relationship between the first tag and a second tag stored in a tag database by using the attribute tag.

The present invention provides a recommendation metadata by using a tag as metadata for the content input by the user and defining relationships between such tags, so that the user can easily and conveniently enter metadata for the content. .

In addition, since the present invention uses relationship dependency and relationship importance for each tag, it is possible to effectively set the relationship between tags, and accordingly, there is an effect of easily searching or using related contents.

In addition, since the present invention stores the content using the tag as index information, it is possible to quickly search for related content.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

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

As shown in FIG. 1, the metadata management system 10 according to an embodiment of the present invention may include a user interface module 100, a metadata expression module 200, a metadata generation module 300, and a metadata management module. 400, and may include a database 500 accordingly.

The user interface module 100 receives information such as content or tag request from a user, and uses the information input by the user through an application programming interface (hereinafter, API) of the metadata management system 10. It may be provided to the metadata expression module 200 or the upload manager 301.

In more detail, the UI module 100 may include a tag expression interface unit 110 and an upload interface unit 120.

The tag expression interface unit 110 may extract a tag related to a keyword input by the user and display the tag. That is, if the content does not need to be uploaded but the user wants to know a tag set related to the keyword, the user may request a tag set related to the input keyword through the tag expression interface unit 110.

The tag expression interface unit 110 provides a keyword input from the user to the metadata expression module 200 and receives a representation object of a related tag set generated corresponding to the keyword from the metadata expression module 200. Can be displayed to the user. Such a representation object will be described later in detail when describing the metadata representation module 200.

The upload interface unit 120 may provide an interface for a user to upload content. The user may upload content and a tag corresponding thereto through the upload interface 120, and the upload interface 120 may provide the uploaded content and a tag thereof to the upload manager 301. In addition, the upload interface unit 120 may receive the recommendation tag generated by the metadata generation module 300 based on the tag input by the user and display it to the user.

The tag expression interface unit 110 and the upload interface unit 120 may be implemented as a web-based Graphic User Interface (GUI), and express metadata through an API of the metadata management system 10. Data may be exchanged with the module 200 or the metadata generation module 300.

The metadata expression module 200 receives a keyword inputted by a user and queries the tag database 510 to construct a tag set, which is a set of tags related to the keyword, and sets the configured tag set in the user interface module 100. An expression object that can be expressed in a form may be generated and provided to the user interface module 100.

In more detail, the metadata expression module 200 may include a tag relationship query unit 210 and a tag object generator 220.

The tag relationship query unit 210 receives a keyword input by the user from the tag expression interface unit 110, queries the tag database 510 to receive tags having a relationship with the keyword input by the user as a response. The tag set may be configured to include tags related to such a keyword.

The tag object generator 220 may generate a tag expression object for receiving a tag set from the tag relationship query 210 and display the same to the user, and provide the tag expression object to the tag expression interface 110. can do. In this case, the tag expression object may include information about a name of a tag included in the tag set, a font size for expressing the tag, a font color, and a background color of the tag.

In addition, the metadata expression module 200 receives a tag (eg, a tag similar to a user input tag, etc.) generated by the metadata generation module 300 to be described later, and generates a tag expression object representing the tag to generate a user. It may be provided to the interface module 100 to display to the user.

That is, the metadata expression module 200 may extract the tags related to the keyword input by the user and display them in various ways to the user through the tag expression interface 110. This can be applied when the user does not upload content but wants to know a tag associated with a particular keyword. The keyword input by the user may be input by the user directly inputting text, or may be input by the user clicking a list or the like stored in the tag expression interface 110.

The upload manager 301 may receive the content input by the user and the user input tag from the upload interface unit 120 through the API, and store the content in the media database 520 using the user input tag as index information. . In addition, the upload manager 301 may provide a user input tag input from the user to the metadata generation module 300 to set tag recommendation or relationship.

The metadata generation module 300 may receive a user input tag input by the user from the upload manager 301, generate a tag object, or extract a recommendation tag and provide the same to the user.

In more detail, the metadata generation module 300 may generate a tag object by adding an attribute tag to the user input tag, or extract a tag similar to the user input tag from the tag database 510 and recommend it to the user. Alternatively, by using a tag input by a user, a tag list table having the tag as index information may be generated and stored in the uploaded content. To this end, the metadata generation module 300 may include a tag attribute generation unit 310, a tag relationship query unit 320, a tag recommendation unit 330, and a tag list generation unit 340.

The tag attribute generator 310 may receive a user input tag and generate an attribute tag with respect to the user input tag. In this case, the attribute tag may include a domain tag, a category tag, and an item tag for the user input tag.

The domain tag includes information about a domain to which the content belongs, the category tag includes information about a classification to which the content belongs, and the item tag includes information about an item of the content. In more detail, domain tags, category tags, and item tags may be defined by the metadata management system 10. For example, when the user uploads a user's review about the A movie as the user content, the user may input a user input tag ('A movie review') together with the user content through the upload interface 120. At this time, the metadata management system 10 may determine the user input tag 'A movie review' as an item tag, and may determine 'genretion of the A movie' corresponding to the item tag as a category tag according to preset information. In this case, the domain tag may determine 'the theater where the user watched the A movie'.

The aforementioned attribute tag may be used to establish a relationship between a user input tag and a tag stored in the tag database 510 or extract a similar tag.

The tag relationship query unit 320 receives a user input tag inputted by the user together with the content through the upload interface unit 120, and then tags tags having a relationship with the user input tag with respect to the tag database 510. You can query In response to the query, the tag relationship query unit 320 receives information about tags having a relationship with a user input tag from the tag database 510, and provides the information to the tag recommendation unit 330. Alternatively, the metadata may be provided to the metadata management module 400 along with the user input tag to generate a new relationship.

The tag recommendation unit 330 may query a tag database 510 for a tag having a relationship with a user input tag, and may generate a similar tag similar to the user input tag by using the query result. In addition, the tag recommendation unit 330 may recommend similar tags of the user input tag generated to the user through the upload interface unit 120. The tag recommendation unit 330 may directly query the tag database 510 about the relationship between the user input tag and receive the result, or may receive the query result from the tag relationship query 320.

The tag list generator 340 may generate a tag list table including the input count information or the search count information for the tag using the user input tag and store the tag list table in the tag database 510. Such a tag list will be described later with reference to FIG. 5. In addition, the tag list generator 340 may configure a list table for the above-described attribute tag and store the list table in the tag database 510. That is, it is possible to generate and store a place list table based on a domain tag, a classification list table based on a category tag, and an item list table based on an item tag.

As described above, the metadata generation module 300 may generate an attribute tag with respect to a user input tag, and configure a tag list table or a respective list table for the attribute tag. In addition, the metadata generation module 300 may extract a tag similar to the user input tag from the tag database 510 and recommend it to the user according to a request of the user.

In addition, the metadata generation module 300 may provide the metadata management module 400 with information about the relationship between the user input tag or the user input tag to generate a new relationship with the user input tag.

The metadata management module 400 may set a relationship between the user input tag and the tags stored in the tag database 510 using the attribute tag generated by the metadata generation module 300. You can create or update the relationship table to reflect this.

In more detail, the metadata management module 400 may include a tag relationship generation unit 410 and a tag relationship storage unit 420.

The tag relationship generation unit 410 may generate a relationship table including at least one of a number of relationships between a user input tag and a tag stored in the tag database 510, relationship dependencies, and relationship importance. That is, the tag relationship generation unit 410 receives a user input tag and attribute information of the tag from the tag attribute generation unit 310 and receives tag information related to the user input tag from the tag relationship query unit 320. In addition, the relation table may be generated or updated by calculating the number of relationships with the user input tag, relationship dependency, and relationship importance. The relationship count, relationship dependency, and relationship importance will be described later with reference to FIG. 9.

The tag relationship storage unit 420 may store the number of relationships, relationship dependencies, and relationship importance generated by the tag relationship generation unit 410 in the tag database 510.

The tag database 510 may include the aforementioned tag object, a tag list table, a list table of attribute tags, and a tag relationship table. The tag database 510 will be described later with reference to FIGS. 4 to 6.

The media database 520 may store content input by a user, and may use a tag as index information in storing such content. In other words, by using the tag as metadata of the content, the content can be easily searched or used. The content to be stored includes various types of content input by the user, such as user's experience information, media files, and the like, which may be provided to the media database 520 by the upload manager 301. In addition, the tag corresponding to the content may be a tag input by the user or a tag recommended by the metadata generation module 300.

Hereinafter, referring to FIGS. 2 and 3, generation and storage of tag information based on information input by a user will be described.

2 is a flowchart illustrating a tag management method of a metadata management system, and FIG. 3 is an exemplary user interface screen of an upload interface unit.

The user may upload the user's content (eg, the user's experience information on a specific item) through the upload interface 120 as shown in FIG. 3. That is, the user may input the title, content, and attachment of the experience in the upload interface 120, and additionally input a user input tag for the experience.

For the information input from the user, the metadata generation module 300 may generate a domain tag for a place to which the user's experience belongs, a category tag for the experience, and an item tag for the object of the experience as described above.

The upload manager 301 may store the content in the media database 520 using the user input tag as an index. For this purpose, the upload manager 301 may generate an index of the content and the user input tag.

The metadata generation module 300 may receive a user input tag from the upload manager 301 and generate attribute tag information as described above to generate a tag object, and the attribute information and the user input tag may be generated by the tag database 510. Can be provided to

In addition, the metadata generation module 300 may generate a tag list table including the user input tag and store it in the tag database 510.

In addition, when the user requests a tag recommendation, the metadata generation module 300 queries the relation to the tag database 510 using the user input tag as a query keyword, and generates a pseudo tag using the response to the query. It may be provided to the upload interface unit 120 to display to the user.

Hereinafter, a tag object, a tag list table, and a relationship table stored in a tag database will be described with reference to FIGS. 4 to 9.

4 is a schematic diagram showing the configuration of a tag object.

As shown in FIG. 4, the tag object may be a user input tag as a tag name, and may include a domain tag, a category tag, and an item tag as attribute information for the user input tag. The tag object may generate a tag attribute. It may be generated by the unit 310. For example, assuming that a user inputs a photo of Paris and a travel experience therefor as content and inputs 'Paris' as a user input tag (tag name), the tag attribute generator 310 is a domain tag. The tag object illustrated in FIG. 4 may be generated by generating “France”, “city” as a category tag, and “Paris” as an item tag.

The tag object may also include related tag information that is related to the current tag. Such related tag information may be generated by the tag relationship query unit 320.

The tag object generated as described above may be configured in an extensible markup language (XML) format.

5 is an exemplary diagram of a tag list table.

As illustrated in FIG. 5, the tag list table may hold information about the number of times of input and the number of searches for each tag. That is, by using the tag name of each tag as index information, information on the number of times of input and search times of the tag can be stored. The tag list table may be generated or updated by the tag list generating unit 340 of the metadata generating module 300. The relationship between the tags may be set using the number of inputs and the number of searches of the tag list table, and such relationship setting will be described later with reference to FIG. 9.

FIG. 6 is a diagram illustrating a domain tag list table in which tags are identified using domain tags as index information, and FIG. 7 is a diagram of a category tag list table in which tags are classified using category tags as index information. Is a diagram illustrating an item tag list table in which tags are distinguished using item tags as index information.

To this end, the tag relationship generation unit 410 may generate or update the list table with respect to the tag recorded in the user input tag and the tag database 510 based on the domain tag, the category tag, and the item tag.

That is, in FIG. 6, the tag relationship generation unit 410 may configure the weight of the number of times of searching or inputting the tag objects Tag1 to Tag5 based on the domain. Can be. That is, using the domain tag list table, it can be seen that a tag object having a tag name of Tag2 generates or retrieves a tag object 3 times as site1 and 2 times as site2.

In addition, as shown in FIG. 7, the tag relationship generation unit 410 may include a table including weights of the number of times that the tag objects Tag1 to Tag5 are searched or input based on the category. As shown in FIG. 8, for each tag object Tag1 to Tag5, a table may be configured including a weight of the number of times of searching or inputting based on an item. .

That is, the tag relationship generation unit 410 may configure a list table for each attribute (domain tag, category tag, and item tag) included in each tag object. You can extract the tags associated with an object.

9 is an exemplary diagram of a relationship table for tag 1. FIG.

To this end, the tag relationship generation unit 410 may generate a relationship table with other tags with respect to Tag1, which is a user input tag, as shown in FIG. 9.

This relationship table may include a relationship count 910, a relationship dependency 920, and a relationship importance 930.

The relationship number 910 may indicate the number of times Tag1 has been input together with other tags. That is, the relationship frequency of Tag2 indicates the number of times that Tag2 has been inputted with Tag1, and the relationship frequency of Tag3 indicates the number of times that Tag3 has been inputted with Tag1. Since the higher the number of the number of relationships 910 is, the more often it is input together with Tag1, which may indicate that the relationship is recognized as high by the user.

The relationship dependency 920 indicates whether Tag2 to Tag4 indicate a dependency on Tag1, and may be divided into existence (Y) or absence of a dependency. This dependency may be determined using the total number of inputs of Tag2 to Tag4 and the number of relationships between Tag1. For example, if the number of relationships with Tag1 exceeds 50% of the total number of inputs of Tag2 to Tag4 (which is a value that can be changed according to a setting), the relationship dependency may exist.

For example, the relationship dependency 920 will be described with reference to FIGS. 5 and 6. Tag4 input frequency is '10' as shown in FIG. 5, and Tag4 as shown in FIG. 6. The number of relationships with Tag1 of '8' is '8'. Therefore, since the number of relationships 8 with Tag1 of Tag4 exceeds 50% of the total number of inputs 10 of Tag4, Tag4 may have a relationship dependency on Tag1.

The relationship importance 930 may be set for a tag having a relationship number exceeding a predetermined ratio (eg, 30%) with respect to the total number of relationships of Tag1. As shown in FIG. 6, since the number of relationships between Tag1 is 48 (= 15 + 25 + 8), the number of relationships with Tag3 is 25, so the number of relationships between Tag1 and Tag3 is 30% of the total number of relationships between Tag1. Tag3 can be a tag with relationship importance because it exceeds.

This relationship dependency and relationship importance can be used to query the relationship for the tag. For example, the tag recommendation unit 330 may extract a tag having a relationship dependency 920 or a relationship importance 930 with respect to a user input tag from the tag database 510 to determine a similar tag and recommend it to the user.

As mentioned above, although this invention was demonstrated in detail with reference to attached drawing, this is only an illustration, It is clear that various deformation | transformation and a change are possible within the scope of the technical idea of this invention. Therefore, the protection scope of the present invention should not be limited to the above-described embodiment, but should be determined to include the scope according to the description of the following claims and their equivalents.

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

2 is a flowchart illustrating a tag management method of a metadata management system.

3 is an exemplary user interface screen of the upload interface unit;

4 is a schematic diagram showing the configuration of a tag object;

5 is an exemplary diagram of a tag list table.

6 is an illustration of a relationship table for tag 1;

Claims (10)

A metadata generation module for generating a tag object by adding an attribute tag to a first tag input by a user; And An item indicating a relationship between the first tag and a second tag stored in a tag database using the attribute tag, wherein the number of relationships indicating the number of times the first tag and the second tag are input together And a metadata relationship module that generates a relationship table that includes at least one of relationship dependencies of the first and second tags and relationship importance of the first and second tags. The method of claim 1, An upload manager that receives the content and the first tag from the user, stores the content in a media database using the first tag as index information, and provides the first tag to the metadata generation module. Metadata management system. The method of claim 1, wherein the metadata generation module, A tag attribute generator for generating an attribute tag including a domain tag, a category tag, and an item tag with respect to the first tag; And a tag list generator which generates a tag list table including input count information or search count information for the first tag. The method of claim 1, wherein the metadata generation module, And a tag recommendation unit for querying the relation table for the relation of the first tag, and generating a similar tag using the query result and recommending the similar tag to the user. 5. The method of claim 4, And a metadata expression module for generating a tag expression object representing the pseudo tag and providing the generated tag expression object to the user. The method of claim 1, wherein the metadata relationship module, And a tag relationship generation unit for generating the relationship table. Constructing a database for the content using the first tag as index information using the content input by the user and the first tag corresponding thereto; Generating an attribute tag including a domain tag, a category tag, and an item tag for the first tag; And And generating a relationship table by setting a relationship between the first tag and a second tag stored in a tag database using the attribute tag. The method of claim 7, wherein And generating a tag list table including input count information and search count information for the first tag. The method of claim 8, wherein generating the relationship table comprises: Calculating a number of relationships of the second tag with respect to the first tag; Checking whether the second tag is dependent on the first tag by using the number of times of input of the second tag and the number of relationships of the second tag with the first tag; and  Determining whether the second tag has a relationship importance for the first tag based on a ratio of the number of relationships of the second tag to the first tag to the total number of relationships of the first tag; Metadata management method. The method of claim 7, wherein Querying the relation table for the relation of the first tag, and generating a similar tag using the query result and recommending the similar tag to the user.

Images