KR102638889B1 - Method, apparatus and program for providing asset management service based on tag tree - Google Patents

Abstract

A method for providing a tag tree-based asset management service according to various embodiments of the present invention is disclosed. The method includes: defining the structure of a Tag Tree; Building an asset library by linking tags to at least one pre-stored asset based on the structure of the tag tree; When a search input related to an asset search is received from a user terminal, recognizing at least one asset corresponding to the search input in the asset library; and providing information about the at least one asset.

Description

Tag tree-based asset management service provision method, device, and program {METHOD, APPARATUS AND PROGRAM FOR PROVIDING ASSET MANAGEMENT SERVICE BASED ON TAG TREE}

The present invention relates to a method, device, and program for providing a tag tree-based asset management service, and more specifically, to a method, device, and program for providing an asset management service capable of building an asset library based on a tag tree.

As the use of electronic devices such as computers and smartphones increases, various types of user data are rapidly increasing. In addition, as video production increases due to the growth of the video platform market, various types of video data are also rapidly increasing. Here, user data and video data can be digital assets (i.e., assets) that can be used in various fields, and technology for efficiently storing and managing digital assets is being developed.

For example, in the field of video production, the work products used in one project are often neglected or not properly managed.

For example, in the past, when managing resources on a project basis, resource management was done by creating folders such as Data 1, Data 2, and Data 3 within the project and storing resources in each folder. In this case, in order for the user to use the resource in another project, there is the inconvenience of having to copy all the folders containing the resources to be used and place them in the folder of the other project. In addition, because the same resources were copied and added to the folder, resources existed in duplicate, causing problems with storage capacity and difficulties in managing duplicate resources.

As an example of a folder system to solve these problems, according to Korean Patent No. 10-1231156 (Patent Document 1), each time a QR code is recognized, a corresponding photo folder is created and the photos taken are then stored as the generated photos. We propose a folder management system and management method that can save time and money on file management by automatically saving them to folders. According to Korean Patent No. 10-1460428 (Patent Document 2), managing folders Computing devices with faster, more efficient methods and interfaces are being proposed.

However, the conventional folder structure management method makes it difficult to manage overlapping resources, and the folder path must be remembered, which may cause user inconvenience when multiple users use resources managed in one place.

Accordingly, there is a demand in the industry for a method of providing asset management services that can easily manage resources and eliminate inconvenience caused by overlapping resources.

The present invention was conceived in response to the above-described background technology and is intended to provide a method, device, and program for providing a tag tree-based asset management service.

The technical problems of the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art from the description below.

According to an embodiment of the present invention to solve the problems described above, a method for providing an asset management service based on a tag tree is disclosed. The method includes: defining the structure of a Tag Tree; Building an asset library by linking tags to at least one pre-stored asset based on the structure of the tag tree; When a search input related to an asset search is received from a user terminal, recognizing at least one asset corresponding to the search input in the asset library; and providing information about the at least one asset.

In an alternative embodiment, defining the structure of the Tag Tree includes obtaining a public tag tree and a private tag tree; It may include defining a structure of the tag tree based on the public tag tree and the private tag tree.

In an alternative embodiment, defining a structure of the tag tree based on the public tag tree and the private tag tree includes at least one first upper tag included in the public tag tree and the at least one first tag. 1 Recognizing at least one first child tag subordinate to a parent tag; Recognizing at least one second upper tag included in the personal tag tree and at least one second lower tag subordinate to the at least one second higher tag; and defining the structure of the tag tree by comparing the first upper tag and the second upper tag.

In an alternative embodiment, comparing the first parent tag and the second parent tag to define the structure of the tag tree includes merging two parent tags with overlapping names into one parent tag, subordinating lower-level tags subordinate to each of two higher-level tags with overlapping names to the merged higher-level tag; Merging lower-order tags with overlapping names among lower-level tags subordinate to each of the two upper-level tags with overlapping names into one lower-level tag; determining the remaining parent tags whose names do not overlap as independent parent tags; And defining a structure for the merged one parent tag and the independent parent tag and the child tags dependent on each of the merged one parent tag and the independent parent tag as the structure of the tag tree. can do.

In an alternative embodiment, the method includes, after defining the structure of the tag tree, storing the asset in a preset location when selection information and an asset for at least one tag included in the tag tree are uploaded. step; and updating the asset library by linking the at least one tag to the uploaded asset and adding it to the asset library.

In an alternative embodiment, updating the asset library by associating the at least one tag with the uploaded asset and adding it to the asset library includes when the at least one tag is a child tag dependent on a parent tag. , linking together a lower level tag corresponding to the at least one tag and a higher level tag corresponding to the lower level tag to the uploaded asset; and updating the asset library by adding the asset to which the child tag and the parent tag are linked to the asset library.

In an alternative embodiment, when a search input related to an asset search is received from a user terminal, recognizing at least one asset corresponding to the search input in the asset library includes two or more tags and a search operator. receiving search input; and when a search input including the two or more tags and a first operator is received, recognizing the at least one asset to which the two or more tags are all connected, and performing a search including the two or more tags and the second operator. When an input is received, the method may include recognizing the at least one asset to which at least one tag among the two or more tags is connected.

In an alternative embodiment, the method includes, when a change to the structure of the tag tree is recognized, redefining the structure of the tag tree based on the change; and rebuilding the asset library by linking tags to at least one asset stored to date based on the structure of the redefined tag tree.

According to one embodiment of the present invention for solving the above-described problems, a device is disclosed. The device includes: a memory storing one or more instructions; and a processor executing the one or more instructions stored in the memory, and the processor may perform the above-described methods by executing the one or more instructions.

According to an embodiment of the present invention for solving the above-described problem, a computer program is disclosed that is combined with a computer as hardware and stored in a computer-readable recording medium to perform the above-described methods.

Other specific details of the invention are included in the detailed description and drawings.

The present invention can provide an asset management service that facilitates resource management and eliminates inconveniences caused by overlapping resources.

The effects of the present invention are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art from the description below.

1 is a diagram illustrating a system according to an embodiment of the present invention.
Figure 2 is a hardware configuration diagram of a computing device according to an embodiment of the present invention.
Figure 3 is a flowchart illustrating an example of a method for providing a tag tree-based asset management service according to an embodiment of the present invention.
Figure 4 is a flowchart illustrating an example of a method for defining the structure of a tag tree according to an embodiment of the present invention.
Figure 5 is a flowchart illustrating an example of a method for recognizing at least one asset corresponding to a search input according to an embodiment of the present invention.
Figure 6 is a flowchart illustrating an example of a method for uploading assets according to an embodiment of the present invention.
7 to 10 are diagrams for explaining an example of a tag tree-based asset management service screen according to an embodiment of the present invention.

Various embodiments are now described with reference to the drawings. In this specification, various descriptions are presented to provide an understanding of the invention. However, it is clear that these embodiments may be practiced without these specific descriptions.

As used herein, the terms “component,” “module,” “system,” and the like refer to a computer-related entity, hardware, firmware, software, a combination of software and hardware, or an implementation of software. For example, a component may be, but is not limited to, a process running on a processor, a processor, an object, a thread of execution, a program, and/or a computer. For example, both an application running on a computing device and the computing device can be a component. One or more components may reside within a processor and/or thread of execution. A component may be localized within one computer. A component may be distributed between two or more computers. Additionally, these components can execute from various computer-readable media having various data structures stored thereon. Components can transmit signals, for example, with one or more data packets (e.g., data and/or signals from one component interacting with other components in a local system, a distributed system, to other systems and over a network such as the Internet). Depending on the data being transmitted, they may communicate through local and/or remote processes.

Additionally, the term “or” is intended to mean an inclusive “or” and not an exclusive “or.” That is, unless otherwise specified or clear from context, “X utilizes A or B” is intended to mean one of the natural implicit substitutions. That is, either X uses A; X uses B; Or, if X uses both A and B, “X uses A or B” can apply to either of these cases. Additionally, the term “and/or” as used herein should be understood to refer to and include all possible combinations of one or more of the related listed items.

Additionally, the terms “comprise” and/or “comprising” should be understood to mean that the corresponding feature and/or element is present. However, the terms “comprise” and/or “comprising” should be understood as not excluding the presence or addition of one or more other features, elements and/or groups thereof. Additionally, unless otherwise specified or the context is clear to indicate a singular form, the singular terms herein and in the claims should generally be construed to mean “one or more.”

Those skilled in the art will additionally recognize that the various illustrative logical blocks, components, modules, circuits, means, logic, and algorithm steps described in connection with the embodiments disclosed herein may be implemented using electronic hardware, computer software, or a combination of both. It must be recognized that it can be implemented with To clearly illustrate the interchangeability of hardware and software, various illustrative components, blocks, configurations, means, logics, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented in hardware or software will depend on the specific application and design constraints imposed on the overall system. A skilled technician can implement the described functionality in a variety of ways for each specific application. However, such implementation decisions should not be construed as departing from the scope of the present invention.

The description of the presented embodiments is provided to enable anyone skilled in the art to use or practice the present invention. Various modifications to these embodiments will be apparent to those skilled in the art. The general principles defined herein may be applied to other embodiments without departing from the scope of the invention. Therefore, the present invention is not limited to the embodiments presented herein. The present invention is to be interpreted in the broadest scope consistent with the principles and novel features presented herein.

In this specification, a computer refers to all types of hardware devices including at least one processor, and depending on the embodiment, it may be understood as encompassing software configurations that operate on the hardware device. For example, a computer can be understood to include, but is not limited to, a smartphone, tablet PC, desktop, laptop, and user clients and applications running on each device.

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

Each step described in this specification is described as being performed by a computer, but the subject of each step is not limited thereto, and depending on the embodiment, at least part of each step may be performed in a different device.

1 is a diagram illustrating a system according to an embodiment of the present invention.

Referring to FIG. 1, a system according to an embodiment of the present invention may include a computing device 100, a user terminal 200, and an external server 300. The system shown in FIG. 1 is according to one embodiment, and its components are not limited to the embodiment shown in FIG. 1, and may be added, changed, or deleted as necessary.

According to an embodiment of the present invention, the computing device 100 may provide a tag tree-based asset management service. Here, assets may include files (eg, image files, video files, and document files) and folders in which the files are stored, but are not limited thereto.

In one embodiment, the computing device 100 may define the structure of a tag tree.

In the present invention, the structure of the tag tree may include the levels of tags constituting the tag tree (eg, top tag, top tag, bottom tag, and bottom tag) and a structure for the dependency relationship of the tags. Additionally, the tag tree may include a plurality of tags that have a mutually dependent relationship.

For example, the tag tree may include a 'project' tag, an 'asset type' tag, an 'FX' tag, and a 'production year' tag as first-level (eg, top-level tag) tags. In addition, the tag tree is a second-level tag (e.g., parent tag) that is a child tag of the first-level tag 'Project' tag, and includes the 'Crime City' tag, the 'Avatar' tag, and the 'Lord of the Rings' tag. can do. In addition, the tag tree is a third-level tag (e.g., child tag) that is a sub-tag of the second-level tag 'Crime City' tag, and includes 'Crime City 1' tag, 'Crime City 2' tag, and 'Crime City 3' tag. ' tag can be included.

In one embodiment, when the computing device 100 defines the structure of the tag tree, the computing device 100 connects a tag to at least one asset pre-stored in the memory of the computing device 100 or an external database server based on the structure of the tag tree to create the asset. You can build a library. Here, the asset library is a library that can be used in various fields such as graphic design, multimedia production, and game development, and may refer to a tool for organizing and storing reusable assets.

Specifically, when building an asset library, the computing device 100 may connect tags to assets based on a defined tag tree while maintaining the structure of the folder in which the assets are stored.

Accordingly, the computing device 100 improves the ease of resource management by enabling systematic management through a tag tree-based asset library, while maintaining the structure of the folder in which the assets are stored, reducing inconvenience caused by overlapping resources. We can provide asset management services that can solve this problem.

In various embodiments, when an asset library is built, the computing device 100 may provide a search function for assets included in the asset library. When a search input related to an asset search is received from the user terminal 200, the computing device 100 may recognize at least one asset corresponding to the search input in the asset library. Additionally, the computing device 100 may provide information about at least one asset.

Specifically, when providing a search function for assets included in an asset library, the computing device 100 receives at least two tags and operators of the at least two tags connected to the asset, and sets search conditions according to the tags and operators. At least one asset corresponding to can be provided.

Accordingly, the computing device 100 of the present invention can provide an asset management service that improves the convenience of asset search by providing a function for searching under various conditions.

Hereinafter, an example of a method by which the computing device 100 provides a tag tree-based asset management service will be described later with reference to FIGS. 3 to 10.

In various embodiments, the computing device 100 may provide web- or application-based services. However, it is not limited to this.

Computing device 100 may include any type of computer system or computer device, such as, for example, microprocessors, mainframe computers, digital processors, portable devices, and device controllers. However, it is not limited to this.

Hereinafter, the hardware configuration of the computing device 100 will be described with reference to FIG. 2 .

Meanwhile, the user terminal 200 may be connected to the computing device 100 through the network 400 and may be a user terminal that uses the asset management service provided by the computing device 100.

Here, the user terminal 200 may include, for example, various types of computer devices. For example, the user terminal 200 may refer to various terminal devices such as a smartphone, tablet PC, desktop, or laptop.

The user terminal 200 includes a display in at least a portion of the terminal, and may include an operating system for running an application or extension program-based service provided by the computing device 100. For example, the user terminal 200 may be a smart phone, but is not limited to this. The user terminal 200 is a wireless communication device that guarantees portability and mobility, and may be used for navigation, personal communication (PCS), etc. System), GSM (Global System for Mobile communications), PDC (Personal Digital Cellular), PHS (Personal Handyphone System), PDA (Personal Digital Assistant), IMT (International Mobile Telecommunication)-2000, CDMA (Code Division Multiple Access)- 2000, all types of handheld-based wireless communication devices such as W-CDMA (W-Code Division Multiple Access), Wibro (Wireless Broadband Internet) terminals, smartpads, tablet PCs, etc. It can be included.

The external server 300 can be connected to the computing device 100 through the network 400, and can transmit and receive various information/data necessary for the computing device 100 to provide asset management services, and the computing device 100 ) can store and manage various information/data generated as it provides asset management services.

For example, the external server 300 may be a database server that stores information used in an asset management service. For another example, the external server 300 may be a server that provides information used for asset management services.

In one embodiment, the external server 300 may be a database server for storing assets stored in an asset management service.

The network 400 may refer to a connection structure that allows information exchange between nodes such as a computing device, a plurality of terminals, and servers. For example, the network 400 includes a local area network (LAN), a wide area network (WAN), the World Wide Web (WWW), a wired and wireless data communication network, a telephone network, and a wired and wireless television communication network. do.

Wireless data communication networks include 3G, 4G, 5G, 3GPP (3rd Generation Partnership Project), 5GPP (5th Generation Partnership Project), LTE (Long Term Evolution), WIMAX (World Interoperability for Microwave Access), Wi-Fi, and Internet. (Internet), LAN (Local Area Network), Wireless LAN (Wireless Local Area Network), WAN (Wide Area Network), PAN (Personal Area Network), RF (Radio Frequency), Bluetooth (Bluetooth) network, NFC (Near- Field Communication) network, satellite broadcasting network, analog broadcasting network, DMB (Digital Multimedia Broadcasting) network, etc., but is not limited thereto.

Figure 2 is a hardware configuration diagram of a computing device according to an embodiment of the present invention.

Referring to FIG. 2, the computing device 100 according to an embodiment of the present invention includes one or more processors 110 and a memory 120 that loads a computer program 151 executed by the processor 110. , it may include a bus 130, a communication interface 140, and a storage 150 that stores a computer program 151. Here, only components related to the embodiment of the present invention are shown in Figure 2. Accordingly, anyone skilled in the art to which the present invention pertains will know that other general-purpose components may be included in addition to the components shown in FIG. 2.

The processor 110 controls the overall operation of each component of the computing device 100. The processor 110 may be composed of one or more cores, and may include a central processing unit (CPU), a general purpose graphics processing unit (GPGPU), and a tensor processing unit (TPU) of the computing device. unit) may include a processor for data analysis and deep learning. Alternatively, it may be configured to include any type of processor well known in the art of the present invention.

Additionally, the processor 110 may perform operations on at least one application or program for executing methods according to embodiments of the present invention, and the computing device 100 may include one or more processors.

In various embodiments, the processor 110 includes random access memory (RAM) (not shown) and read memory (ROM) that temporarily and/or permanently store signals (or data) processed within the processor 110. -Only Memory, not shown) may be further included. Additionally, the processor 110 may be implemented in the form of a system on chip (SoC) that includes at least one of a graphics processing unit, RAM, and ROM.

Memory 120 stores various data, commands and/or information. Memory 120 may load a computer program 151 from storage 150 to execute methods/operations according to various embodiments of the present invention. When the computer program 151 is loaded into the memory 120, the processor 110 can perform the method/operation by executing one or more instructions constituting the computer program 151. The memory 120 may be implemented as a volatile memory such as RAM, but the technical scope of the present invention is not limited thereto.

Bus 130 provides communication functionality between components of computing device 100. The bus 130 may be implemented as various types of buses, such as an address bus, a data bus, and a control bus.

The communication interface 140 supports wired and wireless Internet communication of the computing device 100. Additionally, the communication interface 140 may support various communication methods other than Internet communication. To this end, the communication interface 140 may be configured to include a communication module well known in the technical field of the present invention. In some embodiments, communication interface 140 may be omitted.

Storage 150 may store the computer program 151 non-temporarily. When performing a process according to an embodiment of the present invention through the computing device 100, the storage 150 may store various information necessary to perform analysis according to the disclosed embodiment.

The storage 150 is a non-volatile memory such as Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, a hard disk, a removable disk, or a device well known in the technical field to which the present invention pertains. It may be configured to include any known type of computer-readable recording medium.

The computer program 151, when loaded into the memory 120, may include one or more instructions that cause the processor 110 to perform methods/operations according to various embodiments of the present invention. That is, the processor 110 can perform the method/operation according to various embodiments of the present invention by executing the one or more instructions.

In one embodiment, computer program 151 may include one or more instructions to perform various methods related to various tasks related to training a neural network model.

The steps of the method or algorithm described in connection with embodiments of the present invention may be implemented directly in hardware, implemented as a software module executed by hardware, or a combination thereof. The software module may be RAM (Random Access Memory), ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), Flash Memory, hard disk, removable disk, CD-ROM, or It may reside on any type of computer-readable recording medium well known in the art to which the present invention pertains.

The components of the present invention may be implemented as a program (or application) and stored in a medium in order to be executed in conjunction with a hardware computer. Components of the invention may be implemented as software programming or software elements, and similarly, embodiments may include various algorithms implemented as combinations of data structures, processes, routines or other programming constructs, such as C, C++, , may be implemented in a programming or scripting language such as Java, assembler, etc. Functional aspects may be implemented as algorithms running on one or more processors.

Figure 3 is a flowchart illustrating an example of a method for providing a tag tree-based asset management service according to an embodiment of the present invention.

Referring to FIG. 3, the computing device 100 may define the structure of a tag tree (S110).

Specifically, the computing device 100 may obtain a public tag tree and a private tag tree. Additionally, the computing device 100 may define the structure of the tag tree based on the public tag tree and the personal tag tree. Here, the public tag tree is a tag tree set by an administrator or service provider and may be a tag tree shared with all users. Additionally, the personal tag tree may be a tag tree set by the user of the asset management service.

More specifically, the computing device 100 may define the structure of the tag tree by merging the public tag tree and the personal tag tree. In the process of merging tag trees, the computing device 100 may merge overlapping tags into one tag.

Hereinafter, a detailed description of how the computing device 100 defines the structure of the tag tree will be described with reference to FIG. 4 .

In one embodiment, when the computing device 100 defines the structure of the tag tree, the computing device 100 may build an asset library by linking a tag to at least one pre-stored asset based on the tag tree structure (S120).

Specifically, the computing device 100 may link tags to folders stored in the memory 120 of the computing device 100 or a database server or to individual files included in the folders. Here, the folder may include at least one asset. Additionally, individual files may refer to assets.

More specifically, the computing device 100 may recognize the names of each of a plurality of tags included in the tag tree structure. Then, the computing device 100 compares the name of each of the plurality of tags with the name of the folder or the name of the individual file included in the folder, and selects a tag corresponding to the mutually matching name to the folder or the individual file included in the folder. can be connected to.

For example, if the name of a folder or the name of an individual file included in the folder includes the name of a specific tag among the names of a plurality of tags included in the structure of the tag tree, the computing device 100 may Alternatively, you can attach specific tags to those individual files.

For example, if the name of an individual file is 'Avatar_Jake' and a tag with the name 'Avatar' exists among a plurality of tags included in the structure of the tag tree, the computing device 100 may determine 'Avatar'. You can link a tag with the name 'Avatar' to an individual file with the name '_Jake'.

In various embodiments, the computing device 100 may recognize folders or individual files with names that do not match each other by comparing the name of each of the plurality of tags with the name of the folder or the name of the individual file included in the folder. You can. Additionally, the computing device 100 may generate an unclassified tag and link the unclassified tag to a folder or individual file whose names do not match each other.

Meanwhile, the user can modify the name of the folder or individual file to which the unclassified tag is connected through the detailed information display area 42 of the fourth screen 40, which will be described later in the description of FIG. 10, or add a tag corresponding to the folder or individual file. You can connect.

Accordingly, the computing device 100 of the present invention can automatically build an asset library and improve productivity and convenience in building the asset library by minimizing user intervention.

In one embodiment, when a search input related to an asset search is received from the user terminal 200, the computing device 100 may recognize at least one asset corresponding to the search input in the asset library (S130). And, the computing device 100 may provide information about at least one asset (S140).

Specifically, the computing device 100 may recognize the number of tags included in a search input related to an asset search. Additionally, the computing device 100 may recognize operators included in the search input. Additionally, the computing device 100 may recognize at least one asset corresponding to the number of tags and an operator and provide information about it.

For example, when the computing device 100 recognizes that the number of tags included in the search input is one, it may provide information about at least one asset to which the corresponding tag is connected.

As another example, when receiving a search input including two or more tags and a search operator, the computing device 100 may recognize search conditions according to the two or more tags and the search operator. Additionally, information about at least one asset corresponding to the recognized search condition may be provided.

Hereinafter, a detailed description of a method by which the computing device 100 recognizes at least one asset corresponding to a search input will be described later with reference to FIG. 5 .

In various embodiments, when linking a tag to at least one pre-stored asset to build an asset library, the computing device 100 may not change the storage location of the at least one pre-stored asset. That is, the computing device 100 can build an asset library by only linking a tag to at least one asset without changing the storage location of the at least one asset.

In other words, the asset management service of the present invention distinguishes between the structure for managing files or folders related to assets and the structure of the asset library for searching assets, so that administrators who manage files or folders related to assets and users who use the asset search function The structure can be configured in a way that suits each condition.

Additionally, the computing device 100 may prevent unnecessary resource use or load (for example, resource use or load due to moving files, etc.). Furthermore, the computing device 100 can increase flexibility in changing the structure of the tag tree.

In various embodiments, computing device 100 may provide the ability to change the tag tree structure.

Specifically, when a change to the structure of the tag tree is recognized, the computing device 100 may redefine the structure of the tag tree based on the change. Additionally, the computing device 100 may rebuild the asset library by linking a tag to at least one asset stored to date based on the structure of the redefined tag tree.

Therefore, the user can freely configure and move the structure of the tag tree.

In various embodiments, computing device 100 may update an asset library.

Specifically, when a user uploads an asset, the computing device 100 may update the asset library by linking a tag to the uploaded asset and adding it to the asset library.

For example, the computing device 100 connects the tag selected by the user while uploading an asset to the asset and adds it to the asset library, or compares the names of a plurality of tags included in the tag tree structure with the asset uploaded by the user, You can link tags corresponding to mutually matching names to uploaded assets.

Hereinafter, a detailed description of how the computing device 100 updates the asset library will be described with reference to FIG. 6 .

In an additional embodiment, if the storage location of the asset is changed after the computing device 100 builds the asset library, a discrepancy may occur between the information about the storage location of the asset included in the asset library and the actual storage location of the asset. You can.

To respond to this, the computing device 100 may build an asset library and then monitor the storage location of the assets.

For example, the computing device 100 compares the actual storage location of assets included in the asset library with information about the storage location included in the asset library at a preset period to determine whether an asset whose storage location has changed exists. It can be recognized.

For another example, the computing device 100 attempts to access the storage location of an asset searched by the user, but when access to the location is not possible, it recognizes that the actual storage location has changed and accesses the asset included in the asset library. By comparing the actual storage location of the assets and the information about the storage location included in the asset library, it is possible to recognize whether an asset whose storage location has changed exists.

Meanwhile, when the computing device 100 recognizes that the actual storage location of a specific asset has changed, the computing device 100 may update information related to the storage location of the specific asset included in the asset library with information related to the changed location.

In a further embodiment, when the storage location of the asset changes significantly (for example, the folder in which the asset is stored is merged with another folder, or the folder in which the asset is stored is divided into two or more folders), the structure of the tag tree and Discrepancies in asset libraries may occur.

In order to respond to this, if the storage location of the asset changes after building the asset library, the computing device 100 may update the structure of the asset library or tag tree according to the type for which the storage location of the asset has changed.

For example, when a change occurs in a folder containing an asset, the computing device 100 may update the structure of the tag tree and update the asset library to correspond to the updated structure of the tag tree.

For example, when a first folder containing a specific asset and a second folder containing other assets are combined, the computing device 100 creates a new parent tag encompassing the first folder and the second folder, and Tags connected to assets (including specific assets) included in each of folder 1 and the second folder can be designated as child tags of the new parent tag. Additionally, the computing device 100 may update the asset library by adding a new parent tag and child tags dependent on the new parent tag to the asset library. In this case, the computing device 100 may delete tags associated with each of the existing first and second folders from the asset library. Additionally, the computing device 100 may delete sub-tags of tags related to each of the existing first and second folders from the asset library.

For another example, the computing device 100 moves a specific asset and several other assets included in the first folder to a newly created third folder, and the remaining assets, excluding the specific asset and several other assets, remain in the first folder. If so, a new parent tag related to the third folder can be created, and tags connected to the assets moved to the third folder (a specific asset and several other assets) can be designated as child tags of the new parent tag. Additionally, the computing device 100 may update the asset library by adding a new parent tag and child tags dependent on the new parent tag to the asset library. In this case, the computing device 100 may delete tags connected to a specific asset moved from the first folder and some other assets from a list of lower tags that depend on the upper tag related to the first folder. However, if a tag corresponding to an asset remaining in the first folder exists among the sub-tags to be deleted, the computing device 100 may maintain the tag.

As another example, when a change occurs in the individual storage location of an asset and there is no change in the folder containing the asset, the computing device 100 maintains the structure of the tag tree and stores the information in the asset library. Only information about the storage location of tags whose storage location has changed can be updated.

Accordingly, the computing device 100 updates only the asset library or even updates the structure of the tag tree, depending on the degree of change in the storage location of the asset, so that the administrator who manages the files or folders related to the asset and the user who uses the asset search function respectively Convenience can be increased.

Figure 4 is a flowchart illustrating an example of a method for defining the structure of a tag tree according to an embodiment of the present invention.

According to one embodiment of the present invention, the computing device 100 may obtain a public tag tree and a private tag tree. Additionally, the computing device 100 may define the structure of the tag tree based on the public tag tree and the personal tag tree.

Specifically, referring to FIG. 4, the computing device 100 may obtain a public tag tree and a private tag tree to define the structure of the tag tree (S111).

In the present invention, the public tag tree is a tag tree set by an administrator or service provider and may be a tag tree shared with all users. For example, the common tag tree may be a tag tree provided by default to users of the asset management service of the present invention.

In one embodiment, when the computing device 100 obtains a common tag tree, at least one first upper tag included in the common tag tree and at least one first lower tag dependent on the at least one first upper tag can be recognized (S112).

In the present invention, the personal tag tree may be a tag tree set by the user of the asset management service. Additionally, the personal tag tree may not be shared with all users, but may be shared with specific users or specific groups, depending on the user's settings. For example, when a first user shares his or her first personal tag tree to a second user, a tag with the first user name is created on the second user's service screen, and a subtag of the tag with the first user name is created. may be displayed to include the first personal tag tree.

In various embodiments, when obtaining a personal tag tree, the computing device 100 may obtain information about the group to which the user belongs (e.g., a group in charge of a specific project) or information about other users collaborating with the user. there is. Additionally, the computing device 100 may receive from the user terminal 200 whether to share the personal tag tree with the group to which the user belongs or with other users collaborating with the user. And, when the computing device 100 recognizes that the personal tag tree is shared with a group to which the user belongs or another user collaborating with the user, the user's personal tag is displayed on the service screen of a user included in the group to which the user belongs or another user. A tree can be displayed.

In one embodiment, when the computing device 100 obtains a personal tag tree, at least one second upper tag included in the personal tag tree and at least one second lower tag subordinate to the at least one second upper tag can be recognized (S113).

In one embodiment, when the computing device 100 recognizes the first top tag and the second top tag, the computing device 100 may compare the first top tag and the second top tag to define the structure of the tag tree (S114). .

In a specific embodiment, the computing device 100 merges two parent tags with overlapping names into one parent tag and merges child tags subordinate to each of the two parent tags with overlapping names into one parent tag. It can be subordinated.

For example, if the first parent tag includes 'Avatar' and the second parent tag includes 'Avatar', these can be merged into one parent tag, 'Avatar (Merge)' tag. Additionally, child tags dependent on the 'avatar' tag included in the first parent tag and child tags dependent on the 'avatar' tag included in the second parent tag can be subordinated to the 'avatar (merge)' tag. Here, the names of the merged tags are only examples to aid understanding of the present invention and are not limited thereto.

In a specific embodiment, the computing device 100 may merge child tags with overlapping names among child tags subordinate to each of two parent tags with overlapping names into one child tag.

For example, if the first parent tag includes 'Avatar' and the second parent tag includes 'Avatar', these can be merged into one parent tag, 'Avatar (Merge)' tag. Additionally, child tags dependent on the 'avatar' tag included in the first parent tag and child tags dependent on the 'avatar' tag included in the second parent tag can be subordinated to the 'avatar (merge)' tag. Here, the names of the merged tags are only examples to aid understanding of the present invention and are not limited thereto.

Meanwhile, the computing device 100 may determine the remaining top tags whose names do not overlap as independent top tags.

In a specific embodiment, when the computing device 100 completes merging of duplicate tags and determining independent parent tags, the computing device 100 selects one merged parent tag and an independent parent tag, and one merged parent tag and an independent parent tag. The structure of each subordinate tag can be defined as a tag tree structure.

Figure 5 is a flowchart illustrating an example of a method for recognizing at least one asset corresponding to a search input according to an embodiment of the present invention.

According to an embodiment of the present invention, when an asset library is built, the computing device 100 may provide a search function for assets included in the asset library.

Specifically, referring to FIG. 5, the computing device 100 may receive a search input including two or more tags and a search operator (S131).

In this case, the computing device 100 may recognize whether the first operator is included in the search input.

When the search input includes the first operator, the computing device 100 may recognize at least one asset to which two or more tags are all connected (S132). That is, the first operator may be an AND operator.

For example, when the computing device 100 receives a search input including an 'A' tag and a 'B' tag and a first operator, the computing device 100 searches for at least one asset to which both the 'A' tag and the 'B' tag are connected. It can be recognized.

In various embodiments, the computing device 100 may receive a search expression consisting of two or more tags and a search operator from the user terminal 200. For example, when the computing device 100 receives a search expression ''A' tag AND 'B' tag', the computing device 100 may recognize at least one asset to which both the 'A' tag and the 'B' tag are connected. .

Therefore, users can narrow the search range from a comprehensive list search to a detailed search using the AND operator function.

In one embodiment, the computing device 100 may recognize that the search input includes the second operator when the first operator is not included. However, it is not limited to this, and the computing device 100 may immediately recognize whether the second operator is included in the search input.

When the computing device 100 recognizes that the search input includes a second operator, it may recognize at least one asset to which at least one tag among two or more tags is connected (S133). That is, the second operator may be an OR operator.

For example, when the computing device 100 receives a search input including an 'A' tag and a 'B' tag and a second operator, at least one of the 'A' tag and the 'B' tag is connected. Assets can be recognized.

In various embodiments, the computing device 100 may receive a search expression consisting of two or more tags and a search operator from the user terminal 200. For example, when the computing device 100 receives a search expression ''A' tag OR 'B' tag', the computing device 100 may recognize at least one asset to which at least one of the 'A' tag and the 'B' tag is connected. You can.

Therefore, users can search for various assets related to a specific tag at once.

In one embodiment, when the computing device 100 recognizes at least one asset corresponding to a search input, it may provide functions such as checking detailed information about the recognized asset, downloading the asset, moving the asset, and executing a program connected to the asset. there is.

Figure 6 is a flowchart illustrating an example of a method for uploading assets according to an embodiment of the present invention.

Referring to FIG. 6, after defining the structure of the tag tree, the computing device 100 may store the asset in a preset location when selection information and an asset for at least one tag included in the tag tree are uploaded. (S210).

Here, the preset location may be a location set by an administrator who manages files or folders related to assets. Additionally, from a hardware perspective, assets may be stored in the memory 120 of the computing device 100 or an external database server.

When at least one tag is a child tag dependent on a parent tag, the computing device 100 may link the child tag corresponding to the at least one tag and the parent tag corresponding to the child tag to the uploaded asset (S220). . Then, the computing device 100 may update the asset library by adding an asset to which a lower-level tag and a higher-level tag are connected to the asset library (S230).

For example, while the user terminal 200 uploads an asset, the computing device 100 may receive a selection input for a tag to be associated with the uploaded asset from the user terminal 200. In this case, the computing device 100 may recognize at least one of an upper tag and a lower tag related to the tag selected in the user terminal 200. Additionally, the computing device 100 may connect the selected tag and at least one of the upper tag and lower tag related to the selected tag to the asset uploaded by the user terminal 200.

For example, the computing device 100 may receive a selection input for the 'Crime City 1' tag as a tag to be associated with the uploaded asset from the user terminal 200. In this case, the computing device 100 may recognize 'Crime City', which is a parent tag related to the 'Crime City 1' tag. Additionally, the computing device 100 can recognize the 'Jang Chen' tag, which is a sub-tag related to the 'Crime City 1' tag. Additionally, the computing device 100 may link the 'Crime City' tag, the 'Crime City 1' tag, and the 'Jang Chen' tag to the assets uploaded from the user terminal 200, respectively.

Accordingly, even if only one tag related to the uploaded asset is selected, the computing device 100 can automatically connect various tags related to the selected tag, thereby increasing the convenience of asset upload.

7 to 10 are diagrams for explaining an example of a tag tree-based asset management service screen according to an embodiment of the present invention.

Referring to FIG. 7 , the first screen 10 where the asset management service is provided may include a tag tree display area 11.

In one embodiment, the structure of the tag tree can be intuitively displayed in the tag tree display area 11. For example, the tag tree display area (11) contains the top tag (11-1), the parent tag (11-2) dependent on the top tag (11-1), and the child tags dependent on the parent tag (11-2). It may include (11-3). However, it is not limited to this, and the tag tree may be configured to have fewer or more dependencies.

Referring to FIG. 8, the second screen 20 where the asset management service is provided may be a screen displayed when a user uploads an asset.

In one embodiment, the second screen 20 may include an upload input area 21. Additionally, the second screen 20 may include a tag tree display area. Here, the tag tree display area can be configured to allow selection of tags to be linked to the asset to be uploaded.

For example, when the user selects at least one tag 22 in the tag tree display area, at least one tag 22 is displayed in the selected tag display area 21-1 included in the upload input area 21. It can be entered automatically.

Referring to FIG. 9, the third screen 30 where the asset management service is provided may be a screen displayed when a user searches for an asset.

In one embodiment, the third screen 30 may include a search result display area 33. Additionally, the third screen 30 may include a tag tree area and an operator input button. Here, the operator input button may be configured to select either an AND operator or an OR operator. Additionally, the tag tree display area may be configured to allow selection of tags associated with the asset to be searched.

For example, when the user selects the OR operator 31 among the operator input buttons and selects at least one tag 32 from the tag tree display area, the operator and at least one tag are displayed in the search result display area 33. A list of assets related to may be displayed.

For example, as the OR operator 31 and the tags 32 of Avatar 1 and Avatar 2 are selected, the computing device 100 recognizes assets to which the tag of Avatar 1 is linked and assets to which the tag of Avatar 2 is linked. and can be output to the search result display area 33.

Referring to FIG. 10, the fourth screen 40 where the asset management service is provided may be a screen where detailed information about the selected asset is displayed when one of the searched assets is selected.

In one embodiment, the fourth screen 40 may include a search result display area 41 and a detailed information display area 42.

For example, when a user selects a specific asset (41-1) included in the search result display area (41), detailed information on the specific asset (41-1) may be displayed in the detailed information display area (42). there is. For example, detailed information includes basic information about the asset (e.g., asset name, asset user, date the asset was uploaded), the folder name where the asset is stored, the asset's file name, the asset's extension name, and a description of the asset. It can be done, but it is not limited to this.

In various embodiments, when the computing device 100 outputs the detailed information display area 42 as a specific asset is selected in the search result display area 41, the computing device 100 reduces the size of the search result display area 41 and displays detailed information. The information display area 42 can be output. That is, the computing device 100 may provide the search result display area 41 and the detailed information display area 42 as split screens within one screen.

Accordingly, the computing device 100 can output various information on one screen, preventing inconveniences caused by moving the screen, etc.

Above, embodiments of the present invention have been described with reference to the attached drawings, but those skilled in the art will understand that the present invention can be implemented in other specific forms without changing its technical idea or essential features. You will be able to understand it. Therefore, the embodiments described above should be understood in all respects as illustrative and not restrictive.

Claims (10)

A method performed by a computing device comprising at least one processor, comprising:
Obtaining a public tag tree and a user's personal tag tree;
defining a structure of the tag tree based on the public tag tree and the private tag tree;
Building an asset library by linking tags to at least one pre-stored asset based on the structure of the tag tree;
When a search input related to an asset search is received from a user terminal, recognizing at least one asset corresponding to the search input in the asset library; and
providing information about the at least one asset;
Including,
When obtaining the personal tag tree, obtaining information about a group to which the user belongs or information about other users collaborating with the user;
Receiving from the user terminal whether to share the personal tag tree with a group to which the user belongs or with the other user; and
If it is recognized that the personal tag tree is shared with the group to which the user belongs or the other user, displaying the personal tag tree of the user on the service screen of the user included in the group to which the user belongs or the other user. ;
It further includes,
The step of displaying the personal tag tree of the user on the service screen of the user included in the group to which the user belongs or the other user,
generating a tag of the user's name on a service screen of a user included in a group to which the user belongs or of the other user; and
indicating that the personal tag tree of the user is included in a sub-tag of the tag of the user's name;
Including,
Method of providing asset management service based on tag tree.
delete According to claim 1,
The step of defining the structure of the tag tree based on the public tag tree and the private tag tree,
Recognizing at least one first upper tag included in the common tag tree and at least one first lower tag subordinate to the at least one first higher tag;
Recognizing at least one second upper tag included in the personal tag tree and at least one second lower tag subordinate to the at least one second higher tag; and
defining a structure of the tag tree by comparing the first top tag and the second top tag;
Including,
Method of providing asset management service based on tag tree.
According to clause 3,
The step of defining the structure of the tag tree by comparing the first upper tag and the second upper tag,
Merging two high-level tags with overlapping names into one high-level tag, and subordinating low-level tags subordinate to each of the two high-level tags with overlapping names to the one merged high-level tag;
Merging lower-order tags with overlapping names among lower-level tags subordinate to each of the two upper-level tags with overlapping names into one lower-level tag;
determining the remaining high-level tags whose names do not overlap as independent high-level tags; and
Defining a structure for the merged one parent tag and the independent parent tag and a lower tag dependent on each of the merged one parent tag and the independent parent tag as the structure of the tag tree;
Including,
Method of providing asset management service based on tag tree.
According to claim 1,
The above method is,
After defining the structure of the tag tree, when selection information and an asset for at least one tag included in the tag tree are uploaded, storing the asset in a preset location; and
updating the asset library by linking the at least one tag to the uploaded asset and adding it to the asset library;
Containing more,
Method of providing asset management service based on tag tree.
According to clause 5,
The step of linking the at least one tag to the uploaded asset and adding it to the asset library to update the asset library,
If the at least one tag is a lower tag subordinate to a higher level tag, linking together a lower level tag corresponding to the at least one tag and a higher level tag corresponding to the lower level tag to the uploaded asset; and
updating the asset library by adding the asset to which the lower tag and the upper tag are connected to the asset library;
Including,
Method of providing asset management service based on tag tree.
According to claim 1,
When a search input related to an asset search is received from a user terminal, recognizing at least one asset corresponding to the search input in the asset library includes:
Receiving search input including two or more tags and a search operator; and
When a search input including the two or more tags and a first operator is received, the at least one asset to which the two or more tags are all connected is recognized, and a search input including the two or more tags and a second operator When received, recognizing the at least one asset to which at least one tag among the two or more tags is connected;
Including,
Method of providing asset management service based on tag tree.
According to claim 1,
The above method is,
When changes to the structure of the tag tree are recognized, redefining the structure of the tag tree based on the changes; and
Rebuilding an asset library by linking tags to at least one asset stored to date based on the structure of the redefined tag tree;
Containing more,
Method of providing asset management service based on tag tree.
A memory that stores one or more instructions; and
A processor that executes the one or more instructions stored in the memory
Contains,
The processor executes the one or more instructions,
An apparatus for performing the method of claim 1.
A computer program combined with a computer as hardware and stored on a computer-readable recording medium so as to perform the method of claim 1.